edi implementation guidelines despatch advice...

EDI Implementation Guidelines DESADV - 5.6 of 31 2019-05-02

EDI Implementation Guidelines Despatch Advice Message Edifact Subset: EANCOM® Release version: EANCOM® syntax version 3, 2002 release

Message Type: DESADV REFERENCE DIRECTORY: D.01B EANCOM® SUBSET VERSION: 007 Document Version 5.6


History of Changes

Version Date Subject Content / Trigger of Change

Responsible Person

draft 2009-08-20 Initial version n. a. A. Kürzinger

0.9 2009-10-02 Update according to new/changed requirements (additional RFF segment with order number; routing information in UNB segment; remove of document name code 345 = Ready for despatch advice and SG20)

Review of initial version

A. Kürzinger

1.0 2009-10-19 Integration of PCI and GIN segment (goods identity number / serial number)

New request A. Kürzinger

1.1 2009-12-01 Despatch date must not be a date in the future.

Feedback from integration test

J. Bohl

1.2 2009-12-03 Correction (integration of missing CPS segment)

Integration test; review

A. Kürzinger

1.3 2009-12-23 Changes referring to fulfilment order process: new mandatory NAD segment for MS web shop / channel identifier; 2nd order number is mandatory (RFF+CR); carrier name in NAD+CA segment is mandatory; new segment QVR (quantity variances, delivery status, reason)

Use of new customer order management system

A. Kürzinger

1.4 2010-01-11 Internal outletId as web shop identification instead of using GLN in segment “NAD+PO”

Review / feedback from MC project team

A. Kürzinger

1.5 2010-01-15 Line item reference number is mandatory in Fulfilment Order process (SG18-RFF+LI), correction of sample message (segments QVR /NAD+CA)

Change request A. Kürzinger

1.6 2010-01-25 Remove of Date/time qualifier 203 in DTM segments; delivery status “CNCL” and reason code ”LCCL” are cancelled in segment QVR


1.7 2010-02-16 Definition of “dummy”-code for carrier tracking number (segment “RFF+CN”) and carrier (segment “NAD+CA”) in case of “push-back”


1.8 2010-12-01 Carrier Tracking Number is switched to package level: Old: SG 7 RFF deleted. New: SG 11/12/13/15, seg-ments PAC/HAN/PCI/RFF/DTM/GIN

Change request SA2 Exchange


1.9 2011-03-31 Added Carrier GLS in NAD segment

Information R.Senner

2.0 2012-05-03 Added late cancellation as deleted with version 1.6

Change request R.Senner

2.1 2012-06-25 Added sample for late cancellation.

Information R.Senner

2.2 2012-07-18 Refactoring Multichannel DESADV (new brick and mortar business DESADV schema)

Draft version for FSP’s and Pilot outlets

R. Senner

2.3 2012-07-19 Added TDT segment (SG6) according to a new demand from Multichannel project

Demand R. Senner

2.4 2012-07-19 Added additional Product EAN in PIA segment

Completion R. Senner

2.5 2012-08-08 Added DTM segment (SG13) Completion R. Senner

2.6 2012-09-06 Added dispatch advice number validation rule


2.7 2013-01-30 Added comments for mandatory data elements IMD and GIN


2.8 2013-09-26 Corrected Additional ProductID (SG17 PIA)

Correction R. Senner

2.9 2014-01-09 Corrected SG17 DTM+128 cardinality from mandatory to conditional

Correction R. Senner

3.0 2014-03-19 Added a note for brick and mortar business (BM) inSG11 PAC, SG11 MEA and SG11 QTY segments

update R. Senner

3.1 2014-04-28 Logistic Platform: Added a transport reference number for Idempotency of ESB (SG1 RFF+CU)

update R. Senner

3.2 2014-07-18 SG10 CPS DE 7166 changed type status from N to C SG10 CPS DE 7075 deleted and some minor additions

Change after discussion with Business App. Support Team

G. Rogge-Przybylski

3.3 2014-10-09 SG02 NAD+PO – added outlet id for MM SE in notes

update regarding new FSP SE

G. Rogge-Przybylski

3.4 2014-12-02 - Changing Preamble - SG25 QVR:

BM business: added note to clarify usage. Revised note for MC business to clarify usage of reason codes and removing reason code “CNCL” and “LCCL” in data element 4292. Added overview in note for MC business and adopt sample for Pullback. SG2-NAD and SG13-RFF were adjusted in this context.

Changes of SG25-QVR (MC case) after discussion with J.Bohl

G. Rogge-Przybylski


3.5 2014-10-28 For IHT:

Included additional items and made vars. Changes: supplement of Preamble included additional Application Reference DESADVTO in UNB clarification of use BGM, DTM, SG1 RFF, NAD+SF, NAD+PO, SG17 PIA, SG17 QTY, SG18 RFF, SG25 QVR

Change G. Rogge-Przybylski

3.6 2014-12-09 NAD+SF-Segment: clarification of use

Completion G. Rogge-Przybylski

3.7 2016-02-25 SG02 NAD+PO – correction of outlet id for MM SE in notes DTM+11 and DTM+17 added note regarding usage

Correction G. Rogge-Przybylski

3.8 2016-03-11 Clarifications for IHT after review

Made vars. amendments

G. Rogge-Przybylski

3.9 2016-06-17 For MT made vars. Changes: supplement of Preamble included additional Application Reference DESADVTA in UNB clarification of use BGM, DTM, SG1 RFF, NAD+SF, NAD+PO, SG13 RFF, SG17 PIA, SG17 QTY, SG18 RFF, SG25 QVR FOM: included additional Application Reference DESADVPU in UNB and additional reason code (PBSM) in SG25 QVR


4.0 2016-06-23 Correction of usage of reason code PBSM/PBCK and LCCL in SG25 QVR after review


4.1 2016-07-15 Once again correction of usage of reason code RDPB and LCCL in SG25 QVR after discussion with FOM-project


4.2 2016-08-10 Change of SG15/GIN/C208/7402 from AN..350 to N..18

Correction Stephan Friedl

4.3 2016-09-21 Deleted reason code RDPB in SG25 QVR for PULLBACK after usage of reason codes was harmonized between backend systems


4.4 2017-03-29 RFF+ON at header level (SG1) can be used in BM business


4.5 2017-06-29 SG17-IMD corrected field length



4.6 2017-09-11 For RTV made vars. Changes:

supplement of Preamble included additional Application Reference DESADVRTV in UNB. Clarification of use BGM, DTM, SG1 RFF, NAD+SF, NAD+PO, SG13 RFF, SG17 PIA, SG17 QTY, SG18 RFF

For IHT/MT/RTV: Clarification of use if PUSHBACK/PULLBACK within Transfer Processes

Also made some minor corrections


4.7 2017-11-20 For RTV: clarification of use after reviewing For BM: clarification of use of SG1 RFF+ZZZ

Change Change

G. Rogge-Przybylski F. Pecher

4.8 2018-05-28 SG13 RFF+CN segment deleted and adjustment of usage SG15 GIN+BJ. Made some clarifications of use for IHT/MT/RTV

Change

G. Rogge-Przybylski

4.9 2018-06-20 Added SG17 QTY+21 (unitOfMeasure) for SCE

Change

R. Senner

5.0 2018-09-05 SG0 DTM – Clarification of use Amendment

G. Rogge-Przybylski

5.1 2018-10-25 Added CN code in PAC segment (usage in SCE for Imtron)

Addition

R. Senner

5.2 2018-11-07 Added DESADVWS as application reference (UNB 0026) for SCE project

Addition

R. Senner

5.3 2018-11-23 Changed cardinality for orderPositionNumber for SCE project to mandatory

Change

R. Senner

5.4 2019-02-21 Added SG3 RFF+YC1 Addition

G. Rogge-Przybylski

5.5 2019-02-21 SG15 GIN – Clarification of use

Amendment

G. Rogge-Przybylski

5.6 2017-05-02 SG17-PIA corrected field length



Table of Content History of Changes ......................................................................................................................................... 2

History of Changes ......................................................................................................................................... 2

Table of Content ............................................................................................................................................. 6

Preamble......................................................................................................................................................... 7

EDI Standard .................................................................................................................................................. 7

Business Process Overview ........................................................................................................................... 7

Implementation ............................................................................................................................................... 8

(MC): ........................................................................................................................................................... 8

X .................................................................................................................................................................. 8

(BM): ............................................................................................................................................................ 8

X .................................................................................................................................................................. 8

Sample ...................................................................................................................................................... 29

Glossary of terms .......................................................................................................................................... 30

Contact .......................................................................................................................................................... 31

Responsible for this Guideline ...................................................................................................................... 31


Preamble This document describes the use of the EANCOM® DESADV EDI message. Within MediaSaturn there are several use cases where DESADV’s are used:

• Multichannel (MC): The so called Fulfilment Service Provider (FSP) reports to the MediaSaturn eCommerce backend systems the delivery of goods to the end customer or to an Outlet for a customer pickup.

• Brick and mortar business (BM): The supplier indicates the delivery of goods that will be delivered to the outlets of MediaSaturn.

• DropShipment (DS): The DropShipment partner indicates the delivery of goods to the end customer.

• Inhouse Transfer (IHT): The Warehouse Service Provider (WSP) indicates the delivery of goods to a SP and vice versa.

• Markttransfer (MT): The Warehouse Service Provider (WSP) indicates the delivery of goods to an Outlet

• Return to Vendor (RTV): The Warehouse Service Provider (WSP) indicates the return of goods to a Supplier

• SCE project, (SCE): The supplier indicates the delivery to the logistic service provider According to history and characteristics of partner- or backend systems not every logical information is mapped in the same way. Differences were mentioned Prefix (MC): is used for Multichannel - prefix (BM): is used for brick and mortar – prefix (IHT): is used for Inhouse Transferes – prefix (MT): is used for Marktransfers – and prefix (RTV): is used for the Return-to-Vendor-Process - prefix (SCE): is used for Wholesale business.

EDI Standard Media-Saturn supports the EDIFACT subset EANCOM® syntax version 3, 2002 release. For further details see: http://www.gs1.se/EANCOM_2002/ean02s3/index.htm This implementation guideline is based on this standard.

Business Process Overview An abstract overview of underlying business processes/flow of EDI messages is part of common EDI guide. For further details see separate Implementation guides.


Implementation

Status indicators used in this implementation guide: REQUIRED R Indicates that the entity is required and must be sent. ADVISED A Indicates that the entity is advised or recommended. DEPENDENT D Indicates that the entity must be sent in certain conditions, as defined by the

relevant explanatory note. OPTIONAL O Indicates that the entity is optional and may be sent at the discretion of the user. NOT USED N Indicates that the entity is not used and should be omitted. MANDATORY M Indicates that the entity is mandatory and must be sent. CONDITIONAL C Indicates that the entity is conditional and must not be sent. Note: The status information in segment groups and segments in this document is defined by Media-Saturn and might differ from EANCOM® status.

Group/ Segment

Status Max. Repetition

(MC): X

(BM): X

Level

UNA C 1 No. Service string advice To define the characters selected for use as delimeters and indicators in the rest of the interchange that follows.

Standard EANCOM® MS Implementation Data Element

Description Status Format

Stat. Description

UNA1 Component data element separator

M an1 M Used as a separator between component data elements contained within a composite data element (default value: ":")

UNA2 Data element separator M an1 M Used to separate two simple or composite data elements (default value: "+" )

UNA3 Decimal notation M an1 M Used to indicate the character used for decimal notation (default value:"." )

UNA4 Release character M an1 M Used to restore any service character to its original specification (value: "?" ).

UNA5 Reserved for future use M an1 M (default value: space ) UNA6 Segment terminator M an1 M Used to indicate the end of segment data (default

value: " ' ") Example: UNA:+.? ' Note: This segment is used to inform the receiver of the interchange that a set of service string characters which are different to the default characters are being used. When using the default set of service characters, the UNA segment need not be sent. If it is sent, it must immediately precede the UNB segment and contain the four service string characters (positions UNA1, UNA2, UNA4 and UNA6) selected by the interchange sender. Regardless of whether or not all of the service string characters are being changed every data element within this segment must be filled, (i.e., if some default values are being used with user defined ones, both the default and user defined values must be specified). When expressing the service string characters in the UNA segment, it is not necessary to include any element separators. The use of the UNA segment is required when using a character set other than level A.


Group/ Segment


Level

UNB M 1 No. Interchange header To start, identify and specify an interchange



Stat. Description

S001 Syntax Identifier M M 0001 Syntax identifier M a4 M UNOC = UN/ECE level C 0002

Syntax version number M n1 M 3 = Syntax version number 3

S002 Interchange Sender M M 0004 Sender identification M an..35 M GLN (n13) 0007 Partner Identification

code qualifier R an..4 M 14 = EAN International

0008 Address for reverse routing

O an..14 N

S003 Interchange recipient M M 0010 Recipient identification M an..35 M GLN (n13) 0007

Partner Identification code qualifier

R an..4 M 14 = EAN International

0014 Routing address O an..14 C GLN of DC in Replenishment Order Process S004 Date / Time of

Preparation M M

0017 Date M n6 M YYMMDD 0019 Time M n4 M HHMM

0020 Interchange control reference

M an..14 M Unique reference identifying the interchange. Created by the interchange sender.

S005 Recipient’s reference/password

O C

0022 Recipient’s reference/password

M an..14 M

0025

Recipient’s reference/password qualifier

O an2 C

0026 Application reference O an..14 M DESADV, DESADVFF (only for Multichannel) or DESADVRP (only for Multichannel) or DESADVTO (in case of IHT) or DESADVTA (in case of MT) or DESADVPU (only for Multichannel/AT) or DESADVRTV (in case of RTV) DESADVWS (in case of SCE)

0029 Processing priority code O n1 C A = Highest priority 0031 Acknowledgement

request O n1 C 1 = Requested

0032 Communications agreement identification

O an..35 C EANCOM……

0035 Test indicator O n1 C 1 = Interchange is a test


Example: UNB+UNOC:3+5412345678908:14+8798765432106:14+091101:1000+12345555++DESADVFF' Note: Data element 0026: This data element is used to identify the application, on the interchange recipient’s system, to which the interchange is directed. This data element may only be used if the interchange contains only one type of message, (e.g. only invoices). The reference used in this data element is assigned by the interchange sender. At Media-Saturn this information is used as an identifier to map into different in-house application message formats. For EDI message DESADV within this guidelines there are seven different “application references” (BGM 0026) possible: (MC):

- from Third Party Supplier (DS) or Distribution Center (WSP) in Fulfilment Order Process: DESADVFF or DESADVPU. The Application Reference DESADVPU is only used in Austria

- from Supplier in Replenishment Process: DESADVRP (BM):

- From Supplier to deliver the goods to the outlets: DESADV (IHT):

- from Distribution Center (WSP) to deliver the goods to the SP and vice versa: DESADVTO (MT) :

- from Distribution Center (WSP) to deliver the goods to the Outlet: DESADVTA (RTV) :

- from Distribution Center (WSP) if returning goods to the supplier: DESADVRTV (SCE) :

- from Supplier to the wholesale system : DESADVWS

Group/ Segment


Level 0

UNH M 1 No. 1 Message header To head, identify and specify a message.



Stat. Description

0062 Message reference number

M an..14 M

S009 Message identifier M M 0065 Message type M an..6 M “DESADV” = Despatch advice message 0052 Message version

number M an..3 M “D” = Draft version/UN/EDIFACT Directory

0054 Message release number

M an..3 M „01B“ = Release 2001 – B

0051 Controlling agency M an..2 M “UN” = UN/CEFACT 0057 Association assigned

code R an..35 M „EAN007“ = EAN version control number (EAN Code)

Example: UNH+ME000001+DESADV:D:01B:UN:EAN007' Note:


Group/ Segment


Level 0

BGM M 1 No. 2 Beginning of message To indicate the type and function of a message and to transmit the identifying number.



Stat. Description

C002 Document/message name

R M

1001 Document name code R an..3 M 351 = Despatch advice C106 Document/message

identification R M

1004 Document identifier R an..20 M Despatch advice number assigned by the document sender

1225 Message function code R an..3 M 9 = Original

Example: BGM+351+DES587441+9' Note: (BM and IHT/MT/RTV): Despatch advice numbers with more than 20 characters, which are not in uppercase and / or with leading zeroes were rejected. Group/ Segment


C Level 1

DTM M 10 No. 3 Date/time/period To specify date, and/or time, or period.



Stat. Description

C507 Date/time/period M M 2005 Date or time or period

function code qualifier M an..3 M 137 = Document/message date/time

11 = Despatch date and/or time 17 = Delivery date/time, estimated

2380 Date or time or period value

R an..35 M Document date value

2379 Date or time or period format code

R an..3 M 102 = CCYYMMDD 204 = CCYYMMDDHHMMSS

Example: DTM+137:20091101:102' Note: Data element 2380 for despatch date (11) and document date (137) must not be a date in the future. C507.2005=137 is used always. Usage of additional Qualifiers see following specification: (IHT/MT/RTV): C507.2005=137 and 17 is used in case of IHT, MT or RTV (BM): C507.2005 = 137 and 11 and 17 is used in case of BM


Group/ Segment


Level 1

ALI C 5 No. 4 Additional information To indicate that special conditions due to the origin, customs preference, fiscal or commercial factors are applicable.



Stat. Description

4183 Special condition code C C 165 = Split shipment Example: ALI+++165' Note: Split shipment is not allowed in Multichannel business and for IHT/MT/RTV-transfers. Group/ Segment


SG1 M 10 Level 1

RFF M 1 No. 5 Reference To specify a reference.



Stat. Description

C506 Reference M M 1153 Reference code qualifier M an..3 M ZZZ = Mutually defined reference number

ON = Order number (buyer or in case of IHT/MT/RTV ordering party)

CR = Customer reference number CU = Consignor’s reference number

1154 Reference identifier R an..70 M C506.1153 = ZZZ: Media Saturn Subsidiary (iso country code), e.g. “DE”, “AT”, “NL”

Example: RFF+ZZZ:DE' Note: (BM): C506.1153 = ON: Media-Saturn's Order number is necessary at least either in the header (SG1) or at item level (SG18). C506.1153 = ZZZ always used. (MC): C506.1153 = CR: Order number from Media Saturn Customer Order Management System (IHT/MT/RTV): C506.1153 = ON and ZZZ are always used. (LP): WSP has always sent SG1 RFF+ZZZ:LP’, means ‘LP’ is the country code for WSP. Transport reference number (SG1 RFF+CU) is a technical reference (Idempotency) to avoid doublets and mandatory for LP.


Group/ Segment


SG2 C 99 Level 1

NAD D 1 No. 6 Name and address To specify the name/address and their related function, either by C082 only and/or unstructured by C058 or structured by C080 thru 3207.



Stat. Description

3035 Party function code qualifier

M an..3 M CA = Carrier

C082 Party identification details

A A

3039 Party identifier M an..35 M GLN (Format n13) 1131 Code list identification

code N an..17 N

3055 Code list responsible agency code

R an..3 M 9 = GS1

C058 Name and address N N C080 Party name D M

3036 Party name M an..35 M Carrier name in clear text (e. g. DHL)

Example: NAD+CA+5411234512300::9++DPD' NAD+CA+++DHL' NAD+CA+++PUSHBACK' NAD+CA+++PULLBACK’ Note: (BM): Not necessary in brick and mortar business. (MC and IHT/MT/RTV): In “Fulfilment Order Process” and for transfers the GLN of carrier is not necessary. But the name or code of the carrier is mandatory in data element 3036. Defined codes are: DPD (Deutscher Paket Dienst) / DHL / HRM (Hermes Logistik Gruppe) / UPS / USPS / FED (Fed Ex) / TNT / GLS / OEPS (Österreichische Post) / OTHS (Other; in case of HandlingGroup: Two person handling). In case of so called “push back”or an order cancellation (pull back) no carrier exists. Therefore the dummy code “PUSHBACK” or “PULLBACK” should be used instead.


Group/ Segment


SG2 C 99 Level 1

NAD M 1 No. 7 Name and address To specify the name/address and their related function, either by C082 only and/or unstructured by C058 or structured by C080 thru 3207.



Stat. Description


M an..3 M BY = Buyer SU = Supplier DP = Delivery party SF = Ship from


A M

3039 Party identifier M an..35 M GLN (Format n13) or Supplier-Id of MediaMarkt-Saturn (only if RTV)

1131 Code list identification code

N an..17 N


R an..3 M 9 = GS1 86 = Assigned by party originating the message

C080 Party name C D 3036 Party name M an..35 M Supplier name in clear text

C059 Street and number or post office box identifier

C D

3042 Street and number or post office box identifier

M an..35 M Supplier name in clear text


M an..35 C Supplier name in clear text





3164 City name C an..35 D City/Town, clear text 3251 Postal identification

code C an..35 D Postal code

3207 Country name code C an..3 D ISO 3166 two alpha code of pick-up store Example: NAD+SU+8000234512300::9' (BM): For a more detailed supplier identification with MS supplier-no. pls. use corresponding SG3 RFF+YC1 segment (IHT/MT/RTV): NAD+SF (DE3035, C082.3039/3055) is only used for IHT, MT and RTV. Only if RTV: for NAD+DP the use the Supplier-Id of MediaMarkt-Saturn is possible if there is no GLN available.


Group/ Segment


SG3 C 10 Level 1

RFF M 1 No. Reference To specify a reference.



Stat. Description

C506 Reference M M 1153 Reference code qualifier M an..3 M YC1 = Additional party identificatio 1154 Reference identifier R an..70 M MS Supplier no.

Example: RFF+YC1:123456' Note: (BM): MediaMarkt-Saturn's supplier no. This segment is used only in BM business.


Group/ Segment


SG2 C 99 Level 1

NAD D 1 No. 8 Name and address To specify the name/address and their related function, either by C082 only and/or unstructured by C058 or structured by C080 thru 3207.



Stat. Description


M an..3 M PO = Ordering party


A M

3039 Party identifier M an..35 M ID of web shop (Media or Saturn) if MC ID of web shop (Media or Saturn) or GLN (Format n13) if IHT,MT or RTV


N an..17 N


R an..3 M 86 = Assigned by party originating the message 9 = GS1

Example: NAD+PO+718::86' Note: (MC): Segment is mandatory in “Fulfilment Order Process”. Defined web shop id’s (=outlet id) are e.g.: - 718 (=Media Markt AT) - 719 (=Saturn Markt AT) - 742 (=Media Markt NL) - 743 (=Saturn Markt NL) - 1125 (=Media Markt DE) - 1015 (=Saturn Markt DE) - 1124 (=Media Markt SE) (IHT/MT/RTV): Segment is mandatory in case of IHT, MT and RTV

Group/ Segment


SG4 C 10 Level 2

CTA C 1 No. 9 Contact information To identify a person or a department to whom communication should be directed.



Stat. Description

3139 Contact function code C an..3 C DL = Delivery contact C056 Department or employee

details C C

3413 Department or employee name

C an..35 C

Example: CTA+DL+M.MUSTERMANN' Note: (MC): Not necessary.


Group/ Segment


SG4 C Level 3

COM C 5 No. 10 Communication contact To identify a communication number of a department or a person to whom communication should be directed.



Stat. Description

C076 Communication contact M 3148 Communication address

identifier M

3155 Communication contact identifier

M TE = Telephone FX = Fax EM = Electronic Mail WWW = WWW-Site (GS1-Code)

Example: COM+004461879523:FX' Note: (MC): Not necessary. Group/ Segment


SG5 C 10 Level 1

TOD C 1 No. 11 Terms of delivery or transport To specify terms of delivery or transport.



Stat. Description

4055 Delivery or transport terms function code

C an..3 3 = Price and despatch condition

4215 Delivery or transport terms function code

C an..3 AC = Insurance costs paid by consignor

C100 Terms of delivery or transport

C

4053 Delivery or transport terms description code

C an..3 EXW = Ex works CIP = Freight, Carriage, Insurance to destination DDP = Delivery duty paid to destination


C an..17 2E = Incoterms 2000 (GS1 Code)


C an..3 9 = GS1 CIP = Freight, Carriage, Insurance to destination DDP = Delivery duty paid to destination

Example: TOD+3++EXW:2E:9’ Note: (MC): Not necessary.


Group/ Segment


SG6 C 10 Level 1

TDT D 1 No. 12 Details of transport To specify the transport details such as mode of transport, its conveyance reference number and the identification of the means of transport.



Stat. Description

8051 Transport stage code qualifier

M an..3 M 20 = Main carriage transport

C220 Mode of transport C D 8067 Transport mode name

code C an..3 M 30 = Road transport

50 = Mail C228 Transport means C D

8179 Transport means description code

C an..8 M 48 = Van X11 = Surface mail (GS1 Code – book)

Example: TDT+20++50+X11‘’ Note: (BM): Not necessary. Group/ Segment


SG10 M 9999 Level 1

CPS M 1 No. 13 Consignment packing sequence To identify the sequence in which physical packing is presented in the consignment, and optionally to identify the hierarchical relationship between packing layers.



Stat. Description

7164 Hierarchical structure level identifier

M an..35 M Default “dummy” value 1; (Usually sequential numbering recommended).

7166 Hierarchical structure parent identifier

A an..35 C

Example: CPS+1’ Note:


Group/ Segment


SG11 C 9999 Level 2

PAC D 1 No. 14 Consignment packing sequence To identify the sequence in which physical packing is presented in the consignment, and optionally to identify the hierarchical relationship between packing layers.



Stat. Description

7224 Package quantiy C n..8 O Default “dummy” value 1 C202 Package type C

7065 Package type description code

C an..17 O 08 = Oneway palltet (GS1 code) 09 = Returnable pallet (GS1 code) 200 = Pallet ISO 0 – 1/2 Euro pallet (GS1 code) 201 = Pallet ISO 1 – 1/1 Euro pallet (GS1 code) CN = Container, not otherwise specified as

transport equipment CS = Case CT = Carton RO = Roll

Example: (MC): PAC+1’ (BM): PAC+1++RO’ Note: (BM): See EDI Guideline, chapter 6 for this topic (schema dependency). (MC): This segment can be used to identify the total number of packages per hierarchical level identified in the CPS segment, in a shipment. The contents of each package is subsequently described in the following LIN segment, only PAC 7224 is needed. (IHT/MT/RTV): not used if PUSBACK/PULLBACK Group/ Segment


SG11 C Level 3

MEA C 10 No. 15 Measurements To specify physical measurements, including dimension tolerances, weights and counts.



Stat. Description

6311 Measurements purpose code qualifier

M an..3 M AAE = Measurement

C502 Measurement details C 6313 Measured attribute code C an..3 C HT = Height dimension

LN = Length dimension WD = Width dimension AAB = Unit gross weight

C174 Value/range C 6311 Measurement unit code M an..3 C MMT = Millimetre

KGM = Kilogram 6314 Measurement value C an..18 C

Example: (BM): MEA+AAE+AAB+KGM:12’ Note: (BM): See EDI Guideline, chapter 6 for this topic (schema dependency). (MC): Not necessary. (IHT/MT/RTV): not used


Group/ Segment


SG11 C Level 3

QTY C 10 No. 16 Quantity To specify a pertinent quantity.



Stat. Description

C186 Quantity details M 6063 Quantity type code

qualifier M an..3 M 52 = Quantity per pack

6060 Quantity M an..35 M Quantity Example: (BM): QTY+52+24’ Note: (BM): See EDI Guideline, chapter 6 for this topic (schema dependency). (MC): Not necessary. (IHT/MT/RTV): not used Group/ Segment


SG12 C 10 Level 3

HAN D 1 No. 17 Consignment packing sequence To identify the sequence in which physical packing is presented in the consignment, and optionally to identify the hierarchical relationship between packing layers.



Stat. Description

C524 Handling instructions C A 4079 Handling instruction

description code C an..3 R BIG = Outsized (GS1 Code)

CRU = Crushable (GS1 code) DAE = Dangerous article (GS1 code) FTD = Frost danger (GS1 code) HEA = Hevy cargo/150 kg and over per piece (GS1 code) HWC = Handle with care (GS1 code) LYG = Lying (GS1 code) OHG = Overhang item (GS1 code) RCY = Recyclable packaging (GS1 code) STR = Stacking restricted (GS1 code) UPR = Upright/standing (GS1 code) UST = Unstackable (GS1 code)

Example: HAN+BIG’ Note: This segment is used to provide handling instructions relevant to the packaging unit and level described in the PAC segment. (MC): In C524.4079 element only “BIG” and “CRU” is used. (IHT/MT/RTV): not used


Group/ Segment


SG13 C 1000 Level 3

PCI D 1 No. 18 Package identification To identify the sequence in which physical packing is presented in the consignment, and optionally to identify the hierarchical relationship between packing layers.



Stat. Description

4233 Marking instructions code

C n.3 R 33E = Marked with serial shipping container code (GS1 Code)

Example: PCI+33E‘ Note: This segment is used to provide markings and labels information relevant to the packaging unit and level identified in the PAC segment. (IHT/MT/RTV): not used if PUSBACK/PULLBACK Group/ Segment


SG13 M Level 3

DTM M 5 No. 20 Date/time/period To specify date, and/or time, or period.



Stat. Description


function code qualifier M an..3 M 11 = Despatch date and/or time (shippingTime)

2380 Date or time or period

value C an..35 M


C an..3 M 102 = CCYYMMDD 203 = CCYYMMDDHHMM 204 = CCYYMMDDHHMMSS

Example: DTM+11:20101102:102’ Note: (MC): This segment is used to specify dates relating to the references given in the preceeding RFF segment and to indicate the dates marked on the package identified in the PAC segment.


Group/ Segment


SG15 C 99 Level 4

GIN D 1 No. 21 Reference To specify a reference.



Stat. Description

7405 Object identification code qualifiercode qualifier

M an..3 M BJ= Serial shipping container code

C208 Identity number range M M 7402 Object identifier M n18

or M an..70

M SSCC if BM or SCE Carrier’s tracking number if MC or IHT/MT/RTV

Example: GIN+BJ+354123450000000014‘ Note: (BM or SCE): Mandatory (Serial Shipping Container Code SSCC). (MC and IHT/MT/RTV): Segment is mandatory in “Fulfilment Order Process” (customer order process) and for Transfer processes (IHT /MT/RTV). In these cases the segment contains the Carrier tracking number.

In case of so called “push back” no carrier tracking number exists. Therefore the dummy code “PUSHBACK” should be used instead. In case of so called “pull back” (order cancellation) no carrier tracking number exists. Therefore the dummy code “PULLBACK” should be used instead. If PUSH- or PULLBACK in a transfer process (IHT/MT/RTV) this segment is not used. This segment is used to provide identification numbers relevant to the packaging unit and level identified in the PAC segment. Group/ Segment


SG17 M 9999 Level 2

LIN M 1 No. 22 Line item To identify a line item and configuration.



Stat. Description

1082 Line item identifier R an..6 M Application generated line item number 1229 Action

request/notification description code

N an..3 N

C212 Item number identification

D D If EAN code is available

7140 Item identifier R an..35 M EAN 7143 Item type identification

code R an..3 M SRV = EAN.UCC Global Trade Item Number

Example: LIN+1++5412345123453:SRV' Note: (MC and IHT/MT/RTV): Media-Saturn product number must be delivered with PIA segment.


Group/ Segment


SG17 M Level 3

PIA M 10 No. 23 Additional product id To specify additional or substitutional item identification codes.



Stat. Description

4347 Product identifier code qualifier

M an..3 M 1 = Additional identification

C212 Item number identification

M M

7140 Item identifier R an..30 M Product number (additional) 7143 Item type identification

code R an..3 M IN = Buyer’s item number

BP = Buyer’s part number SA = Suppliers article number XY8 = Supplier assigned (GS1 Code)

Example: PIA+1+9334532:IN' Note: (MC): Suppliers article number (C212.7143=SA) is not necessary (BM and IHT/MT/RTV): if no EAN (SG17 LIN C212.7140) or buyers article (SG17 PIA C212.7140) reference is given, the suppliers article number has to be delivered. Group/ Segment


SG17 C Level 3

IMD D 25 No. 24 Item description To describe an item in either an industry or free format.



Stat. Description

7077 Description format code C an..3 M F =Free form C273 Item description C

7008 Item description C an..35 M 7008 Item description C an..35 M

Example: IMD+F++:::MINI DISPLAYPRT TO HDMI CABLE 180CM' Note: (BM): Mandatory (product description). (MC and IHT/MT/RTV): Not necessary


Group/ Segment


SG17 M Level 3

QTY M 10 No. 25 Quantity To specify a pertinent quantity



Stat. Description

C186 Quantity details M M 6063 Quantity type code

qualifier M an..3 12 = Despatch quantity

21 = Ordered quantity 47 = Invoiced quantity 73 = Outstanding quantity 119 = Short shipped 121 = Over shipped 192 = Free goods quantity 193 = Free quantity included

6060 Quantity M an..35 M 6411 Measurement unit code C an..3 C Unit of measure (SCE)

Example: QTY+12:400' QTY+21:3:PCE’ (used for SCE) Note: (MC and IHT/MT/RTV): Only C186.6063 = 12 relevant. Group/ Segment


SG17 C Level 3

DTM C 5 No. 26 Date/time/period To specify date, and/or time, or period.



Stat. Description


function code qualifier M an..3 M 128 = Delivery date/time, last

2380 Date or time or period

value C an..35 R


C an..3 R 102 = CCYYMMDD 203 = CCYYMMDDHHMM 204 = CCYYMMDDHHMMSS

Example: DTM+128:20120717:102’ Note: (MC): Not necessary


Group/ Segment


SG18 D 99 Level 3

RFF D 1 No. 27 Reference To specify a reference.



Stat. Description

C506 Reference M M 1153 Reference code qualifier M an..3 M LI = Line item reference number

ON = Order number CR = Customer reference number ABT = Customs declaration number CN = Carrier's reference number

1154 Reference identifier R an..70 M Line item number from Media Saturn Order

Example: RFF+LI:1' Note: (BM): C506.1153 = ON: Media-Saturn's Order number is necessary at least either in the header (SG1) or at item level (SG18). (MC and IHT/MT/RTV): Only C506.1153 (LI) necessary Within this segment the referring line item number from ORDERS message is transferred. In Fulfilment Order process and for IHT/MT/RTV this segment is mandatory. (IHT/MT/RTV): Carrier's reference number (C506.1153=CN) is used (optional) in case of IHT, MT and RTV (SCE): C506.1153 = ON and LI: Media-Saturn's Order number and Order position number are necessary at item level (SG18). Group/ Segment


SG22 C 9999 Level 3

PCI C 1 No. 28 Package identification To specify markings and labels on individual packages or physical units.



Stat. Description

4233 Marking instructions code

O an..3 M 17 = Supplier’s instructions

Example: PCI+17' Note: Segment PCI is used in despatch advice message if serial number information has to be transferred.


Group/ Segment


SG23 C 10 Level 4

GIN C 1 No. 29 Goods identity number To give specific identification numbers, either as single numbers or ranges.



Stat. Description

7405 Object identification code qualifier

M an..3 M BN = Serial number

C208 IDENTITY NUMBER RANGE

M M

7402 Object identifier M an..35 M 7402 Object identifier O an..35 O


O O



O O



O O



O O


Example: GIN+BN+SN100:SN104' GIN+BN+SN100+SN101+SN102+SN103+SN104' Note: Segment GIN is used in despatch advice message if serial number information referring to line item in LIN segment has to be transferred.


Group/ Segment


SG25 C 10 Level 3

QVR D 1 No. 30 Quantity variances To specify item details relating to quantity variances.



Stat. Description

C279 Quantity difference information

R M

6064 Quantity variance value M n..15 M Specify the actual variance amount here (negative quantity variance since the despatched quantity < ordered quantity)

6063 Quantity type code qualifier

R an..3 M 21 = Ordered quantity

4221 Discrepancy nature identification code

O an..3 M IC = Item cancelled RA = Item rationed

C960 Reason for change O M 4295 Change reason

description code O an..3 C


O an..17 C


D an..3 D 9 = GS1

4294 Change reason description

O an..35 M Required if delivery has not been shipped. Defined values (codes) are: - LCCL (=cancelation in case of PULLBACK) - PBCK (=PUSHBACK) - PBSM (=PUSHBACK - this variant for MS AT only) - RDPB (=products were available but non-delivery caused by push back of other items)

Example: QVR+-50:21+RA+:::PBCK' QVR+-50:21+RA+:::RDPB' Note: (BM): not used (IHT/MT/RTV): not used (MC): Segment QVR is used if the referring order position is not shipped (discrepancy between ordered and despatched quantity). The quantity variance value in data element 6064 is the difference between despatched quantity identified in data element 6060 of SG17-LIN-QTY+12 at line level and the ordered quantity. Due to this definition only negative

values are allowed in data element 6064.

The “discrepancy nature identification code” in data element 4221 refers to so called “delivery status” information in Media-Saturn’s customer order management system. Possible values / mappings for “delivery status” are:

- SHIP (delivery has been executed) / segment QVR is not transferred - CNCL (item is cancelled / pull back) / code of data element 4221 = IC - PBCK (delivery request has been pushed back) / code of data element 4221 = RA

For MS AT only: the PUSHBACK case has two different specifications/reasons: - PBCK (delivery request has been pushed back because there is enough book-keeping inventory but the

goods are temporarily unavailable/missing stock, damaged stock) - PBSM (delivery request has been pushed back because there is no or not enough book-keeping

inventory/push back is triggered by a stock mismatch)

Within this segment the “change reason description” in data element 4294 is mandatory: - in case of a pullback the reason is always LCCL - in case of a pushback the reason is PBCK or PBSM for the item(s) that could not be fully delivered and

RDPB for all other items


Overview: Delivery Status

possible values in Media-Saturn's Customer Order Management

System

Delivery Status corresponding to

SG2-NAD C080.3036 SG13-RFF C506.1154

SG25-QVR-Segment 4221

Discrepancy nature identification / coded

C960.4294 Reason code

SHIP - no QVR segment CNCL PULLBACK IC LCCL

PBCK PUSHBACK RA PBCK RDPB PBSM RDPB

Group/ Segment


Level 0

UNT M 1 No. 31 Message trailer To end and check the completeness of a message



Stat. Description

0074 Number of segments in the message

M n..6 M

0062 Message reference number

M an..14 M The message reference number detailed here is equal the one specified in the UNH segment.

Example: UNT+112+ME000001' Note: Group/ Segment


Level

UNZ M 1 No. Interchange trailer To end and check the completeness of an interchange.



Stat. Description

0036 Interchange control count

M n..6 M Number of messages or functional groups within an interchange.

0020 Interchange control reference

M an..14 M Identical to DE 0020 in UNB segment.

Example: UNZ+5+12345555' Note: This segment is used to provide the trailer of an interchange. Data element 0036: If functional groups are used, this is the number of functional groups within the interchange. If functional groups are not used, this is the number of messages within the interchange.


Sample Brick and mortar business: If someone needs an example please get in contact with MediaSaturn via the national EDI responsible person. Multichannel UNA:+.? ' UNB+UNOC:3+9099999122009:14+4335347900000:14+20130129:1640+16868++DESADVFF' UNH+0+DESADV:D:01B:UN:EAN007' BGM+351+368492+9' DTM+137:20130129:102' DTM+11:20130129163756:204' DTM+17:20130130:102' RFF+ZZZ:AT' RFF+ON:5000000165' RFF+CR:10070468' NAD+CA+++OEPS' NAD+DP+4335347853009::9' NAD+SU+9099999122009::9' NAD+PO+718::9' CPS+1' PAC+1' PCI+33E' RFF+CN:1014411000181430260203' DTM+11:20130129163756:204' DTM+17:20130130:102' GIN+BJ+1014411000181430260203' LIN+1++0711719183860:SRV' PIA+1+1151634:IN' QTY+12:4' RFF+LI:1' UNT+24+0' UNZ+1+16868' Pushback: UNA:+.? ' UNB+UNOC:3+9099999122009:14+4335347900000:14+20130129:1644+16869++DESADVFF' UNH+0+DESADV:D:01B:UN:EAN007' BGM+351+368493+9' DTM+137:20130129:102' DTM+11:20130129164315:204' DTM+17:20130129:102' RFF+ZZZ:AT' RFF+ON:5000000164' RFF+CR:10070467' NAD+CA+++PUSHBACK' NAD+SU+9099999122009::9' NAD+PO+718::9' CPS+1' PAC+1' PCI+33E' RFF+CN:PUSHBACK' DTM+11:20130129164315:204' DTM+17:20130129:102' LIN+1++0711719183969:SRV' PIA+1+1151635:IN' QTY+12:0' RFF+LI:1' QVR+-2:2+RA+:::PBCK' UNT+24+0' UNZ+1+16869'


Pullback: UNA:+.? ' UNB+UNOC:3+9099999122009:14+4335347900000:14+20130129:1645+16870++DESADVFF' UNH+0+DESADV:D:01B:UN:EAN007' BGM+351+368491+9' DTM+137:20130129:102' DTM+11:20130129164414:204' DTM+17:20130129:102' RFF+ZZZ:AT' RFF+ON:5000000163' RFF+CR:10070466' NAD+CA+++PULLBACK' NAD+DP+4335347885000::9' NAD+SU+9099999122009::9' NAD+PO+718::9' CPS+1' PAC+1' PCI+33E' RFF+CN:PULLBACK' DTM+11:20130129164414:204' DTM+17:20130129:102' LIN+1++0711719183969:SRV' PIA+1+1151635:IN' QTY+12:0' RFF+LI:1' QVR+-1:1+IC+:::LCCL' LIN+2++0711719183860:SRV' PIA+1+1151634:IN' QTY+12:0' RFF+LI:2' QVR+-1:1+IC+:::LCCL' UNT+30+0' UNZ+1+16870'

Glossary of terms

Term Description

BM Brick and Mortar business

DS Dropshipment Provider

FOM Future Order Management Project

IHT Inhouse Transfere

LP Logistic Platform

MC Multichanel strategy

MIG Message Implementation Guide

MSH Media Saturn Holding

MT Markttransfer

RTV Return to Vendor


Contact Media-Saturn IT Services GmbH Store Services SupplyChain Wankelstrasse 5 D-85046 Ingolstadt E-Mail: [email protected]

Responsible for this Guideline Media-Saturn IT Services GmbH EDI INT Wankelstrasse 5 D-85046 Ingolstadt E-Mail: [email protected]

edi implementation guidelines despatch advice...

Documents