SAP label printing integration: native RFC, REST and file-based options
How EtikStudio prints labels from SAP ECC and S/4HANA — native RFC called from ABAP, the REST API, watched folders and ODBC to SAP HANA — with modules, scenarios and an implementation checklist.
SAP already knows what is being produced, packed and shipped: production orders in PP, deliveries and handling units in SD/LE, stock movements in WM and EWM. The label is the physical output of that knowledge, and the failure mode is always the same — someone reading a screen and retyping lot, quantity and destination into a label tool. EtikStudio removes the retyping with four integration paths, one of them native to SAP.
Which integration paths fit SAP
| Path | Fit | Why |
|---|---|---|
| Native RFC | Best | ABAP calls an EtikStudio function module directly; SAP treats EtikStudio as another RFC destination. No files, no HTTP, full control from the transaction that creates the document. |
| REST API | Good | From ABAP (CL_HTTP_CLIENT), SAP PI/PO/CPI or a BTP app: a REST call with the fields; immediate job status. |
| Watched folder | Good | Output determination writes a file (CSV/XML) or IDoc-derived export to a folder; EtikStudio prints it. Zero ABAP development. |
| Embedded data (ODBC) | Complement | The label reads material master, batch and customer data from SAP HANA or a CDS/database view at print time; SAP sends only the key. |
Modules and scenarios
| Module | What gets labeled | Trigger |
|---|---|---|
| PP / PP-PI | Production order labels, WIP, containers, batch and expiry on finished goods | Order release or confirmation (CO11N), goods receipt |
| SD / LE | Delivery notes, handling-unit and SSCC pallet labels, carrier labels | Delivery creation, packing (VL02N), goods issue |
| WM / EWM | Storage-bin and location labels, transfer orders, replenishment | TO creation, put-away confirmation |
| MM | Goods-receipt labels with vendor batch and inspection lot | MIGO, QM usage decision |
Recommended flow
Register the RFC destination once (SM59) pointing at the EtikStudio RFC server; in the ABAP that already processes the document, add the function call with the label name, target printer and the field values. Keep the label design in EtikStudio, not in Smart Forms or Adobe Forms, so a template change never needs a transport.
Implementation checklist
- Obtain the SAP NW RFC SDK from SAP (account holders) and install the EtikStudio RFC server on a host visible to the SAP application servers.
- Create the RFC destination in SM59 (TCP/IP, registered program) and test the connection.
- Map printers: SAP output device or plant/storage location → EtikStudio printer name.
- Define the field list per label (SSCC, GTIN-14, batch, expiry in YYMMDD for GS1 AIs) and validate GS1-128 output with a verifier.
- If no ABAP development is allowed, start with the watched folder from output determination and move to RFC later; the label design does not change.
How EtikStudio handles it
One label design serves every SAP plant regardless of printer brand: the RFC call carries data, EtikStudio renders the template in the language of the printer at that plant — ZPL, SBPL, TSPL — and records job, template version and printer for audit. Mixed fleets after acquisitions stop being a labeling problem.
Integration details vary by ERP version, deployment and licensing. Adapters and worked examples are provided during implementation.