SupplyOn acts as marketplace and therefore agreed with all customers on a standardized EDIFACT marketplace format for the individual business processes. All buy-side companies attached to the SupplyOn marketplace have been using this uniform format for a long time. Due to the marketplace effect it is therefore necessary also for all sell side companies to follow the standardized marketplace format. For you as a sell-side company, the major advantage is that you send and receive always the same format for a business process, regardless to which of your customers you exchange data with via SupplyOn . You receive the EDIFACT format guideline for the respective business process of your customer from SupplyOn and implement this in your internal IT system in a mapping. If a further customer would like to transmit data with you via SupplyOn EDI , the multiplier effect takes place: that means a new maintenance work of the format guidelines in your inhouse system is no longer necessary.
EDIFACT versions and format guideline
In order to transmit messages to SupplyOn , the messages have to correspond with the SupplyOn EDIFACT marketplace format. Messages that SupplyOn transmits to the supplier correspond to the SupplyOn EDIFACT marketplace format as well. The format guideline for the respective business process is attached with this info package.
The following EDIFACT versions are used on the SupplyOn marketplace:
| Delivery instruction: | DELFOR D10.A |
| Delivery receipt | DESADV D07 A |
| Purchase order : | ORDERS D99.B |
| Order change | ORDERS D99.B |
| Order response: | ORDRSP D99.B |
| Invoice: | INVOIC D07.A, based on VDA4938 |
| Self billing invoice: | INVOIC D07.A, based on VDA4938 |
| Credit note | INVOIC D07.A, based on VDA4938 |
| Invoice/ Order attachments | VDA Container VDA4983 |
| ASN ( Advanced shipping notification ): | DESADV D07.A based on VDA4987 |
| Inventory Report | INVRPT D99.B |
| VMI OUT-data package | DELFOR_IMO D98.B |
| VMI planned deliveries | DELFORP D97.A |
EDIFACT routing and syntax check, error emails
If you send EDIFACT message to SupplyOn , these are checked first for the routing information needed for the SupplyOn market place. Afterwards the message is checked for the correct syntax analog to the SupplyOn EDIFACT format guideline.
If your message contains a routing or a syntax error an automatically generated email with the appropriate error description is sent to you by SupplyOn (sender: SupplyChainCollaborationEDI@mail.supplyon.com). The original message that caused the error is attached to this email. The message was not processed in this case and was not transmitted to the customer.
SupplyOn uses the recipient email address for routing and syntax errors you mentioned together with the UNB sender ID in the parameter sheet.
Routing Check
Due to the SupplyOn marketplace it is necessary that you transmit certain routing information in certain segments in the EDIFACT message, so that we can identify your customer and transmit the message to the correct recipient.
We identify your customer with the help of the following 4 segments:
- Recipient ID of the customer in UNB
- Customer organization code NAD+BY
- Customer plant code in NAD+CN resp. NAD+ST
- Supplier number in NAD+SU resp. NAD+SE
Example of a Routing error email due to wrong recipient ID:
Von: SupplyChainCollaborationEDI@mail.supplyon.com
Betreff: Routing Error SO_DESADV; P: WerksCode; S: 4711
Wichtigkeit: Hoch
Fehleranalyse DESADV-UN-D07A
lfd.Segmentnr:0072
Kein Routingeintrag in der Tabelle PO_EMAILUPD für Empfaenger [BUYER002], ORGCode [Buy01]gefunden.
Example of a Routing error email due to wrong organization code:
Von: SupplyChainCollaborationEDI@mail.supplyon.com
Betreff: Routing Error SO_DESADV; P: WerksCodefalsch; S: 4711
Wichtigkeit: Hoch
Fehleranalyse DESADV-UN-D07A
lfd.Segmentnr:0072
Es konnte keine CP-Buyer-ID mit ORGCode [Buy01] und Plant [WerksCodefalsch] in der Tabelle tControlPoint_SCD gefunden werden.
Example of a Routing error email due to wrong plant code:
Von: SupplyChainCollaborationEDI@mail.supplyon.com
Betreff: Routing Error SO_DESADV; P: WerksCodefalsch; S: 4711
Wichtigkeit: Hoch
Fehleranalyse DESADV-UN-D07A
lfd.Segmentnr:0072
Es konnte keine CP-Buyer-ID mit ORGCode [Buy01] und Plant [WerksCodefalsch] in der Tabelle tControlPoint_SCD gefunden werden
Example of a Routing error email due to wrong supplier number:
Von: SupplyChainCollaborationEDI@mail.supplyon.com
Betreff: Routing Error SO_DESADV; P: WerksCode; S: 4711falsch
Wichtigkeit: Hoch
Fehleranalyse DESADV-UN-D07A
lfd.Segmentnr:0072
Es konnte keine CP-Seller-ID mit CP-Buyer ID [10000842], Lieferantennummer [4711falsch] und SellerPlant [] in den Tabellen tNetworkLink_SCD_NEW und tNetworkSupplierInfo_SCD gefunden werden.
Syntax check
Due to the standardized message format on the SupplyOn market place the messages are checked for correct syntax analog to the SupplyOn format guideline, before they are transmitted to your customer. This syntax check takes place also in reverse direction, i.e. customer messages are also checked for correct syntax before they are transmitted from SupplyOn to the supplier.
Example of a syntax error email due to incorrect date format in DTM+137:
Von: SupplyChainCollaborationEDI@mail.supplyon.com
Betreff: Syntax Error SO_DESADV; P: WerksCode; S: 4711
Wichtigkeit: Hoch
Fehleranalyse DESADV-UN-D07A
lfd.Segmentnr:0005 UNB.UNH.DTM
Überlauf im Feld UNB.UNH.DTM:C507.2380 [2003100300], nur 8 Zeichen erlaubt. Zugehöriger Qualifier UNB.UNH.DTM:C507.2379 [102]. Zugehöriger Qualifier UNB.UNH.DTM:C507.2005 [137].
Segments for message routing
In order to ensure a correct message flow to your customer, the following EDIFACT segments have to be considered for the routing of the messages:
| IMPORTANT segments for message routing |
|
|---|---|
| Sender ID (UNB.S002.0004) + Recipient ID (UNB.S003.0010) |
The Sender ID of the customer has to be copied out of the inbound message and be sent back as Recipient ID in the outbound message to SupplyOn ( see example). From SupplyOn to supplier: UNB+UNOC:3+BUYER-XY+RecipientID+031003:1947+0471104812’ From supplier to SupplyOn: UNB+UNOC:3+SenderID+BUYER-XY+031003:1947+0471104812’ |
| SupplyOn’s organisation Code (NAD.C058.3124#1) |
The SupplyOn organization code has to be copied out of the inbound message and be sent back in the outbound message to SupplyOn ( see example). From SupplyOn to supplier: NAD+BY+00700800::91+Buy01: Buyer GmbH+Buyer GmbH & Co.KG+Schlossallee 100+Neustadt++12345+DE' From supplier to SupplyOn : NAD+BY+00700800::91+Buy01: Buyer GmbH+Buyer GmbH & Co.KG+Schlossallee 100+Neustadt++12345+DE' |
| Number of customer’s plant (NAD.C082.3039) |
The number of customer’s plant has to be copied out of the inbound message and be sent back in the outbound message to SupplyOn ( see example). From SupplyOn to supplier: NAD+CN+2222::92+Buy01: Buyer GmbH+Buyer GmbH & Co.KG+Schlossalle 100+Neustadt++12366+DE' From supplier to SupplyOn : NAD+CN+2222::92+Buyer GmbH+Buyer GmbH & Co.KG+ Schlossalle 100+Neustadt++12345+DE' NAD+ST+2222 (for message type invoice) |
| Supplier number (NAD.C082.3039) |
The supplier number has to be copied out of the inbound message and be sent back in the outbound message to SupplyOn ( see example). From SupplyOn to supplier: NAD+SU+009999875::92++Supplier GmbH & Co.KG+Kastanienweg 12+Bremen++45678+DE' From supplier to SupplyOn : NAD+SU+009999875::92++Supplier GmbH & Co. KG+Kastanienweg 12+Bremen++45678+DE' NAD+SE+009999875 (for message type invoice) |