# Loftware with SAP ECC and S/4HANA: label design and printing from SAP transactions > Source: https://netray.co/stack/loftware-sap-s4hana-ecc-labeling > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Stack ## Short answer Loftware offers a certified SAP integration, an ABAP package and a cloud option, for printing labels from SAP transactions with label status sent back to SAP. It works with SAP Global Label Management Plus, and Loftware Cloud is listed as an SAP Endorsed App. The same approach covers ECC, S/4HANA and the Public Edition, and this page centres on the on-premise ECC case. ## Erp SAP ECC ## Erp Key sap-ecc ## On Prem true ## Product Loftware Cloud / NiceLabel ABAP Package ## Vendor Loftware ## Category Label printing ## Integration **Method:** ABAP package with output management **Detail:** The ABAP package hooks into SAP output determination, so a delivery, production order or goods receipt creates a label request. The request carries SAP data to Loftware, which merges it into a template and prints it. Status goes back to SAP when the print completes. **Method:** SAP Global Label Management Plus **Detail:** Loftware works with SAP GLM Plus where labels are driven by GLM label content and compliance data, such as hazardous goods or regulated labelling. Whether you need GLM depends on how much regulatory content you manage in SAP. **Method:** Loftware Cloud **Detail:** The cloud edition removes the label server from your infrastructure. For air-gapped plants, check whether an on-premise deployment is required instead. ## Data Flows **From:** SAP ECC output determination **To:** Loftware **Data:** Label request with delivery, material, batch, serial, customer and quantity data **Trigger:** Delivery, goods receipt or production order event **From:** Loftware **To:** Printer **Data:** Rendered label in printer language **Trigger:** Label request processed **From:** Loftware **To:** SAP ECC **Data:** Print status and errors **Trigger:** After printing **From:** SAP ECC **To:** Loftware **Data:** Master data changes that affect label content **Trigger:** Material or customer change ## Setup ### Inventory your labels **Detail:** List every label by process, such as shipping, pallet, product and customer-specific, and the SAP source of each field. ### Install the ABAP package **Detail:** Import transports into development, test and production in the order Loftware documents, and check compatibility with your support package level. ### Configure output determination **Detail:** Set up condition records and output types so the right documents create label requests for the right partners and plants. ### Set up the label server and printers **Detail:** Define printers, queues and drivers, and map them to SAP output devices. ### Build and map templates **Detail:** Design templates and bind each field to the SAP data, including formatting for dates, units and barcodes. ### Test with customer specs **Detail:** Print against customer label specifications and scan every barcode with a verifier. ### Plan the S/4HANA move **Detail:** Keep templates and mappings reusable so the ECC to S/4HANA conversion does not mean redesigning labels. ## Pitfalls - Output conditions that fire twice and print duplicate labels. - Unit of measure conversion on quantity fields, which prints the wrong count on a pallet label. - Template fields bound to custom Z fields that disappear or change during an S/4HANA conversion. - Customer labelling standards (GS1, retailer specs) changed without a template update. - Printer queue or network failures with no status back to SAP, so users reprint blindly. - Transport order mismatches between systems, causing production to behave differently from test. ## Ai Layer ### Label error triage **Description:** Read print status from Loftware and the related SAP documents to explain why a label failed, for example a missing field, an offline printer or a template mismatch, and suggest the fix for approval. ### Spec comparison **Description:** Compare a new customer labelling specification with the existing templates and draft the field changes a label designer should review. ### Questions about what printed **Description:** Let shipping ask which labels were printed for a delivery and see the data that went onto each one. ## Alternatives - SAP's own output forms and Adobe forms are enough for plain documents and simple barcodes. - Another label product such as BarTender or Seagull if it already runs your non-SAP labels, with a different SAP connector. - SAP GLM Plus alone if your need is mostly regulatory content rather than flexible design. ## Faq ### Is Loftware certified for SAP? **Answer:** Loftware describes a certified SAP integration and lists Loftware Cloud as an SAP Endorsed App. Check the current certification scope for your exact SAP release before you rely on it, since scope changes by product version. ### Do I need SAP GLM Plus? **Answer:** Only if you manage regulatory label content, such as hazard data, in SAP. For ordinary shipping and product labels, output determination with an ABAP package is typically enough. Loftware supports both approaches. ### Can this run on-premise or air-gapped? **Answer:** Loftware offers cloud and installed options. For isolated plants, confirm that you can run the label server on-premise and what, if anything, calls out to the internet. ### What breaks during an S/4HANA conversion? **Answer:** Usually custom fields and output determination customisations. Document the field mapping for each template before the conversion, retest every label type and keep the ABAP package version aligned with the new release. ## Source https://www.loftware.com/sap-labeling-solutions ## Search terms loftware sap s/4hana labeling integration, loftware sap ecc, nicelabel abap package, sap global label management plus, sap label printing output determination, loftware cloud sap endorsed app --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json