Label printingSAP S/4HANA (also ECC)Runs on-prem

BarTender label printing with SAP S/4HANA and ECC

BarTender designs barcode, RFID and compliance labels and prints them automatically when SAP events occur. For S/4HANA Cloud there is a BarTender Cloud ERP connector. For on-premise SAP the documented options are IDoc, SAP AII, or file-based integration, with Integration Builder watching for the incoming data and driving the print job.

How BarTender (Integration Builder and ERP connectors) connects to SAP S/4HANA (also ECC)

IDoc from SAP to BarTender Integration Builder

SAP issues an outbound IDoc (for example from output determination on a delivery or production order). BarTender receives the XML or file, maps fields to label template data sources and prints to the right printer. The mapping of IDoc segments to template fields is where most of the work sits.

SAP AII or file-based drop

SAP Auto-ID Infrastructure can pass label data, or SAP can write a text or XML file to a watched folder that Integration Builder picks up. File-based is the simplest on-premise option and is easy to troubleshoot, at the cost of weaker delivery guarantees.

BarTender Cloud ERP connector (S/4HANA Cloud)

The cloud connector is documented for S/4HANA Cloud. It does not replace the on-premise options for plants running ECC or on-premise S/4HANA.

What data moves

FromToDataWhen
SAP delivery or outbound shipmentBarTenderShip-to, material, batch, quantity, SSCC or customer label fieldsOutput determination on delivery
SAP production or process orderBarTenderMaterial, batch, lot, dates, serialOrder release or confirmation
SAP goods receiptBarTenderHandling unit or receiving label dataGoods receipt posting
BarTenderPrinterRendered label in ZPL, TSPL or printer driver outputIntegration Builder detects new data
BarTenderOperator or logPrint success or failureAfter print job

Setting it up

  1. 1Pick the trigger transactionDecide which SAP events create labels: delivery, production order, goods receipt, handling unit.
  2. 2Choose IDoc, AII or fileSelect the method per label type; files are quickest for a pilot.
  3. 3Configure SAP outputSet up output types, partner profiles and port definitions, or the file output, per the chosen method.
  4. 4Design the templateBuild the label in BarTender, with data sources named to match the incoming fields.
  5. 5Build the Integration Builder integrationWatch the folder or listener, parse the data, and map it to template fields and printer names.
  6. 6Map printersDefine how plant, workstation or storage location resolves to a physical printer.
  7. 7Test edge casesRun multi-batch deliveries, long descriptions, special characters and reprints.
  8. 8Document the reprint processAgree who reprints a label and how it is traced.

What usually breaks

  • !Field lengths in SAP exceeding the label area, so descriptions are truncated or overflow.
  • !Unicode and special characters corrupting barcodes or printing as question marks.
  • !Date and number formats in the IDoc not matching the label's expected format.
  • !Duplicate labels when an IDoc is resent after a communication error.
  • !Printer mapping not updated after a printer is replaced.
  • !Customer-specific compliance label changes that require editing templates but not SAP, creating version drift.

A private AI layer across both systems

Missing label investigation

A private assistant reading SAP deliveries and the BarTender logs can say whether a label was triggered, received, parsed and printed, and where it stopped.

Template and data audit

Compare fields that SAP sends against what each template uses and flag unused or truncated fields.

Customer label spec reading

Summarize a customer's labeling requirements document into a checklist of fields for a human to map.

Try it here, free

SAP IDoc Status Codes Reference

Open full tool

Look up any IDoc status code, see whether it is inbound or outbound, whether it is an error, and which transaction to use to fix it.

When something else fits better

  • SAP Adobe Forms or SAPscript for simple labels printed directly from SAP.
  • SAP Print and Label Management, if you already license an SAP-native labeling solution.
  • Warehouse-system labeling inside an EWM or WMS if one already drives the print.

Frequently asked questions

Does BarTender integrate with on-premise SAP?

Seagull documents on-premise options as IDoc, SAP AII or file-based integration, while its cloud ERP connector targets S/4HANA Cloud. For ECC or on-premise S/4HANA, plan on one of the three on-premise methods.

Which method should I start with?

File-based is the easiest to set up and debug, so many teams pilot there. IDoc suits SAP shops that already manage ALE and partner profiles and want a more standard interface.

Can it print RFID labels?

BarTender supports RFID encoding as well as barcodes. What you need on the SAP side is the data to encode, such as serial or EPC values, and a compatible printer.

Pairing documented at help.seagullscientific.com/bartendercloud/help/en/Content/ERP/ERP_Connector_Over . BarTender (Integration Builder and ERP connectors) is a product of Seagull Scientific; Netray is independent and not affiliated with either vendor.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Software