SAP integration is included in Pro for supported configurations. SAP-side setup and custom development are scoped separately.
FROM SAP TO THE LABEL STATION
01
Start with the SAP document
Send the production order, delivery or handling-unit data your label needs.
02
Apply your approved rules
Resolve customer codes, select the layout and hold incomplete jobs.
03
Print and follow the result
Route to the configured station and return job status against the SAP reference.
SAP supplies business data. SmartFACT manages label decisions, output and print history.
KEEP LABELLING WITH THE WORK
From a released order to the right label.
Use an operator action in SAP or an agreed business event to start the same controlled label workflow.
01
Use the data you already hold
Map materials, customer references, batches, quantities and packaging identifiers from SAP into the label workflow. Preserve meaningful leading zeros and make missing values visible.
02
Change the label requirement
Describe customer conditions in plain English, review the proposed rules and test example orders before publication. Routine label-rule changes stay in SmartFACT once the required SAP fields are mapped.
03
Route and track the job
Choose a permitted station or use approved routing rules. Pro runs unattended through the managed station agent, with job status, holds and recorded reprints linked to the original SAP document.
BUILT AROUND YOUR SAP LANDSCAPE
A maintained connection. ABAP expertise behind it.
Connect SAP ECC and SAP S/4HANA to the same SmartFACT label workflow. We agree the SAP release, data sources and trigger points during setup, with a documented support scope for your configuration.
Our SAP integration work is backed by hands-on ABAP development experience.
01
SAP ECC and S/4HANA on-premises or Private Edition
Use the maintained ABAP integration to submit mapped label data over HTTPS, select permitted workflows and stations, and retrieve the result. Connect an existing SAP output process or an explicit user action.
02
S/4HANA Cloud Public Edition
Use released SAP data interfaces and permitted ABAP Cloud extension points for operator requests and supported business events. The connection uses SmartFACT’s authenticated APIs.
03
Existing middleware, IDocs and output processes
Keep an established integration route where it fits. SAP-side code or middleware maps the required values into the SmartFACT API contract. Existing IDoc, SAPscript and Smart Forms processes are assessed for adaptation during onboarding.
CUSTOMER CHANGES, WITHOUT ANOTHER LABEL PROGRAM
“Use their code. Require the batch. Hold it if either is missing.”
Keep that requirement in reviewed SmartFACT rules and lookup tables. Test the normal order, a customer variation and the job that must stop before deploying the change.
SAP remains the source of the business document. SmartFACT keeps the label configuration, prepared output and decision history together.
Yes. The integration supports explicit SAP user requests as well as configured business-event triggers. It discovers permitted label workflows and stations, prepares the job and submits it under the same approval and validation rules as other SmartFACT jobs. The SAP screen or output-process entry point is agreed during setup.
Can we keep our existing SAP label output?
We assess your data, trigger and output path, then map a selected workflow to SmartFACT. An IDoc or SAPscript export can supply data through an adapter, but existing SAP forms, printer programs and BarTender .btw files are not automatically converted. Start with one document type and representative label artwork.
Can SAP send jobs to an on-premises Labels service?
Yes. Pro includes on-premises production, with cloud-based authoring. Supported SAP integrations can target your local Labels API. Approved configuration, new job processing, rendering and print history run locally; SAP or middleware connectivity is still required wherever those services run.
What happens if SAP retries a request?
The same identified request returns its existing job instead of creating another print run. A deliberate reprint is a separate, authorised action with a recorded reason. An uncertain printer outcome is held for reconciliation before any further send.
What status comes back to SAP?
The integration can retrieve job status or receive configured status notifications, including holds and submission results. The record distinguishes an accepted request from a confirmed physical outcome. Any update to a delivery, stock movement or business-document status needs its own agreed SAP-side process.
What should we bring to the first conversation?
Your SAP product, release and deployment edition; the document that starts printing; anonymised sample data and label artwork; and the intended printers. Include any custom fields, output-management rules or existing middleware so the supported route and setup work can be agreed.
Turn customer label requirements into tested workflows. Compare SmartFACT Labels Free and Pro automation, customer rules and support with BarTender editions.
Keep label reprints linked to their original output, selected copies and a recorded reason. Understand print history and uncertain printer submissions.
SmartFACT Labels is independent of SAP SE. SAP and the SAP product names are trademarks or registered trademarks of SAP SE.
THE SMARTFACT SUITE
Useful on their own. Better around the same floor.
Free tools for everyday checks, plus early-access services for labelling, kit checking and work instructions.
Inspect the input
ScannerBench
See the text and key events your keyboard scanner sends. Compare them with the value you expected.
With your permission, Google Analytics uses cookies to measure visits across our website and app. You can change your choice at any time. Read our privacy notice.