How TEKLYNX SENTINEL and CODESOFT connects to SAP S/4HANA (also SAP ECC)
SENTINEL triggers
SENTINEL watches for a database record, a flat file dropped in a folder, or a REST API request from SAP, then merges the data into a CODESOFT-designed template and prints. TEKLYNX describes this in its SAP barcode label printing page.
SAP-side output
SAP produces the trigger data, for example via an output type, an ABAP report or an IDoc-to-file step. How you do that is a design choice, not fixed by TEKLYNX, so confirm the pattern in your landscape.
What data moves
| From | To | Data | When |
|---|---|---|---|
| SAP | SENTINEL | Label content: material, batch, serial, qty, delivery and handling unit data | Goods receipt, production order confirmation, delivery or pack event |
| SENTINEL | CODESOFT template | Merged fields | Trigger received |
| SENTINEL | Printer | Print job | After merge |
| SENTINEL | Log | Print result | Job completion |
Setting it up
- 1List label use casesDecide which SAP events need a label and what data each carries.
- 2Choose the trigger typeDatabase record, flat file or REST. Use REST where SAP can call HTTP, files where it cannot.
- 3Design the labels in CODESOFTCreate templates and bind fields to the incoming data names.
- 4Configure SENTINEL triggersMap each trigger to a template and printer, including error handling.
- 5Build the SAP outputCreate the output or report that emits the trigger data in the agreed format.
- 6Test and monitorTest with real batches and serials, scan outputs and set alerts on failed jobs.
What usually breaks
- !Flat file triggers can be picked up before the file is fully written, causing partial labels.
- !Field name mismatches between SAP output and template silently print blanks.
- !Re-sent triggers create duplicate labels, a problem for serialized items.
- !Printer offline or out of stock leaves SAP believing the label printed.
- !Template changes by label designers without version control break lines at shift change.
A private AI layer across both systems
Missing or wrong label diagnosis
Match SAP events to SENTINEL logs to show which expected labels never printed and why.
Template field audit
List templates using fields that SAP stopped sending after a change.
Plain-language print history
Ask which labels were printed for a batch or delivery, read-only.
Try it here, free
SAP Handling Unit Label Template
Fill in handling unit data and get a label layout with SSCC and GS1 application identifiers, ready to hand to a label developer or warehouse team.
When something else fits better
- OPAL LabelManagement or SAP's own label tooling may suit you if you want central control inside SAP.
- BarTender with an SAP integration is a comparable approach.
- Direct ZPL from ABAP is simplest for a few labels but costly to maintain.
Frequently asked questions
Is it SAP certified?
TEKLYNX states SENTINEL is SAP Certified for Integration with SAP NetWeaver. Ask TEKLYNX for the scope and releases covered, since it describes integration, not every SAP scenario.
How does SAP trigger a print?
SENTINEL can print from a database record, a flat file or a REST API request sent by SAP. Which you use depends on what your SAP landscape can emit reliably.
What does CODESOFT do?
CODESOFT is the label design tool in this pairing. Designers build templates there and SENTINEL fills them with SAP data at print time.
Pairing documented at www.teklynx.com/en/products/by-need/sap-barcode-label-printing . TEKLYNX SENTINEL and CODESOFT is a product of TEKLYNX; Netray is independent and not affiliated with either vendor.