Outbound

On outbound, NCS-EDI turns a SAP document into a message in the partner’s syntax and prepares it for dispatch. Notably, the message produced is validated against your own rule set before it leaves the house.

What is this for?

• Convert SAP documents into the partner’s target syntax.
• Assign sequential reference numbers unambiguously.
• Optionally produce an e-invoice (XRechnung/ZUGFeRD) as well.
• Match incoming acknowledgements to the original exchange.

How to set it up

1. Dispatch is triggered by a timer job (document selection), from the SAP add-on or by a DocuWare workflow.
2. The document is read from SAP and transferred into the internal data model.
3. The mapping converts it into the partner’s target syntax.
4. The next reference number is drawn from the number range – transactionally, so no number is issued twice.
5. The envelope is built according to the partner’s syntax profile (UNA/UNB/UNH).
6. The produced message is validated against your own rule set – errors surface here, not at the partner.
7. Where agreed, an XRechnung or ZUGFeRD file is produced alongside.
8. The file is written to the outbox, the journal entry sits at status PO.
9. When the partner’s acknowledgement arrives later (CONTRL/APERAK), it is matched to the exchange through the reference numbers – status AK or DN.