Inbound

On inbound, NCS-EDI reads the partner messages, validates them and creates SAP documents from them. The flow is deliberately built so the original is preserved unchanged and every step stays traceable in the journal.

What is this for?

• Pick up messages from the partner’s monitored folder.
• Secure the original before anything is processed.
• Validate syntax, code lists and business rules.
• Create the document in the ERP and produce the acknowledgement.

How to set it up

1. The partner inbox folder is checked; a file is only picked up when it can be opened exclusively – so nothing still being written is touched.
2. The original is secured and given a checksum (SHA-256). Everything else works on that copy.
3. A journal entry is created with status RC (received).
4. The envelope is read (UNA/UNB) and the partner determined from sender ID and qualifier.
5. Duplicate check: if the same message arrived before, it is rejected (status DP) or merely reported, depending on the partner profile.
6. If the interchange holds several messages it is split – each message continues on its own from here.
7. The three validation stages follow: syntax, code lists and business rules – see validation.
8. The mapping fills the internal data model and translates partner values through the code lists. Status VA and MP.
9. The document is created in the ERP; SAP object and document key are written back. Status PO.
10. Finally the message is acknowledged (CONTRL and/or APERAK) and the file moved to the processed folder. Status AK or DN.