edi implementation guidelines receiving advice · pdf fileedi implementation guidelines...
Post on 06-Feb-2018
235 Views
Preview:
TRANSCRIPT
EDI Implementation Guidelines RECADV – 1.6 Page 1 of 19 2015-05-21
EDI Implementation Guidelines Receiving Advice Message Edifact Subset: EANCOM® Release version: EANCOM® syntax version 3, 2002 release
Message Type: RECADV REFERENCE DIRECTORY: D.01B EANCOM® SUBSET VERSION: 005 Document Version 1.6
EDI Implementation Guidelines RECADV – 1.6 Page 2 of 19 2015-05-21
History of Change
Version Date Subject Content / Trigger of Change
Responsible Person
draft 2009-09-03 Initial version n. a. A. Kürzinger
0.9 2009-10-09 Update (new document version; just formal but no real changes)
Review A. Kürzinger
1.0 2009-12-01 Goods receipt date must not be a date in the future.
Feedback from integration test
J. Bohl
1.1 2010-01-11 RFF+AAK should be the number of the delivery note.
Feedback from integration test
A. Kürzinger
1.2 2013-06-13 SG 22 QTY deleted qualifier 194, added qualifier 124.
Feedback from integration test
R. Senner
1.3 2013-07-04 Added linItemNumber. PPgoesOnline R. Senner
1.4 2014-04-11 LogisticPlatform: Added Transport instruction number.
Logistics Excellence R. Senner
1.5 2014-07-08 SG 1 RFF+CU:changed transport instruction number into transaction reference number SG1 RFF+ZZZ: added note regarding LP
Logistics Excellence G: Rogge-Przybylski
1.6 2015-05-21 Changed type of SG1 RFF+ON data element to numeric value
Change R. Senner
EDI Implementation Guidelines RECADV – 1.6 Page 3 of 19 2015-05-21
Table of content Preamble......................................................................................................................................................... 4 EDI Standard .................................................................................................................................................. 4 Business Process Overview ........................................................................................................................... 4 Implementation ............................................................................................................................................... 4
Sample ...................................................................................................................................................... 19 Contact .......................................................................................................................................................... 19
EDI Implementation Guidelines RECADV – 1.6 Page 4 of 19 2015-05-21
Preamble This document describes the use of receiving advice message in context of Media-Saturn Processes:
Multichannel-Project
PP goes Online
LogisticPlatform
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 following chapters in document “MS_EDI_Implementation_Guide.pdf”:
Fulfillment Order Process
Replenishment Order Process
Product Master Data
Availability and Inventory Adjustment
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.
EDI Implementation Guidelines RECADV – 1.6 Page 5 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
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.
EDI Implementation Guidelines RECADV – 1.6 Page 6 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
Level
UNB M 1 No. Interchange header
To start, identify and specify an interchange
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
S001 Syntax Identifier M M
0001 Syntax identifier M a4 M UNOC = UN/ECE level C UNOD = UN/ECE level D UNOE = UN/ECE level E UNOF = UN/ECE level F
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
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 C
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' 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.
EDI Implementation Guidelines RECADV – 1.6 Page 7 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
Level 0
UNH M 1 No. 1 Message header
To head, identify and specify a message.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
0062 Message reference number
M an..14 M
S009 Message identifier M M
0065 Message type M an..6 M “RECADV” = Receiving 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 „EAN005“ = EAN version control number (EAN Code)
Example: UNH+ME000001+RECADV:D:01B:UN:EAN005' Note:
Group/ Segment
Status Max. Repetition
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.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C002 Document/message name
R M
1001 Document name code R an..3 M 632 = Goods receipt
C106 Document/message identification
R M
1004 Document identifier R an..35 M Receiving Advice number assigned by the document sender.
1225 Message function code R an..3 M 9 = Original
4343 Response type code N an..3 N
Example: BGM+632+REC5488+9' Note:
EDI Implementation Guidelines RECADV – 1.6 Page 8 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
Level 1
DTM M 10 No. 3 Date/time/period To specify date, and/or time, or period.
Standard EANCOM® MS Implementation Data Element
Description Status Format
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
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
Example: DTM+137:20021111:102' Note:
Group/ Segment
Status Max. Repetition
Level 1
DTM M 10 No. 4 Date/time/period To specify date, and/or time, or period.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C507 Date/time/period M M
2005 Date or time or period function code qualifier
M an..3 M 50 = Goods receipt date/time
2380 Date or time or period value
R an..35 M
2379 Date or time or period format code
R an..3 M 102 = CCYYMMDD 204 = CCYYMMDDHHMMSS
Example: DTM+50:20091101101000:204’ Note: Data element 2380 (goods receipt date) must not be a date in the future.
EDI Implementation Guidelines RECADV – 1.6 Page 9 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
SG1 M 10 Level 1
RFF M 1 No. 5 Reference To specify a reference.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C506 Reference M M
1153 Reference code qualifier M an..3 M ZZZ = Mutually defined reference number
1154 Reference identifier R an..70 M Media Saturn Subsidiary (iso country code), e.g. “DE”, “AT”, “NL”
Example: RFF+ZZZ:DE' Note: Goods management systems at Media-Saturn differ between different subsidiaries (e.g. “DE”, “AT”, “NL”). Incoming and outgoing data have to be routed according to this qualifier. LP: WSP always sends SG1 RFF+ZZZ:LP’, means ‘LP’ is the country code for WSP.
Group/ Segment
Status Max. Repetition
SG1 M 10 Level 1
RFF M 1 No. 6 Reference To specify a reference.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C506 Reference M M
1153 Reference code qualifier M an..3 M AAK = Despatch advice number
1154 Reference identifier R an..70 M
Example: RFF+AAK:533662' Note: Media-Saturn’s in-house systems expect the number of the delivery note with this segment.
EDI Implementation Guidelines RECADV – 1.6 Page 10 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
SG1 M 10 Level 1
RFF C 1 No. 7 Reference To specify a reference.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C506 Reference M M
1153 Reference code qualifier M an..3 M CU = Consignor’s reference number
1154 Reference identifier R an..70 M
Example: RFF+CU:12548796' Note: Transaction reference number from the Warehouse service provider (WSP transaction number) to avoid doublets.
Group/ Segment
Status Max. Repetition
SG1 M 10 Level 2
DTM C 1 No. 8 Date/time/period To specify date, and/or time, or period.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C507 Date/time/period M M
2005 Date or time or period function code qualifier
M an..3 M 171 = Reference date/time
2380 Date or time or period value
R an..35 M
2379 Date or time or period format code
R an..3 M 102 = CCYYMMDD
Example: DTM+171:20021025:102' Note:
EDI Implementation Guidelines RECADV – 1.6 Page 11 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
SG1 M 10 Level 1
RFF M 1 No. 9 Reference To specify a reference.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C506 Reference M M
1153 Reference code qualifier M an..3 M ON = Order number (buyer)
1154 Reference identifier R n..70 M
Example: RFF+ON:533662' Note:
Group/ Segment
Status Max. Repetition
SG1 M 10 Level 2
DTM C 1 No. 10 Date/time/period To specify date, and/or time, or period.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat.
Description
C507 Date/time/period M M
2005 Date or time or period function code qualifier
M an..3 M 171 = Reference date/time
2380 Date or time or period value
R an..35 M
2379 Date or time or period format code
R an..3 M 102 = CCYYMMDD
Example: DTM+171:20021025:102' Note:
EDI Implementation Guidelines RECADV – 1.6 Page 12 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
SG4 M 99 Level 1
NAD M 1 No. 11 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.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
3035 Party function code qualifier
M an..3 M DP = Delivery party
C082 Party identification details
A M
3039 Party identifier M an..35 M GLN (Format n13); Distribution Center
1131 Code list identification code
N an..17 N
3055 Code list responsible agency code
R an..3 M 9 = EAN (International Article Numbering association)
Example: NAD+DP+4335347999996::9' Note:
Group/ Segment
Status Max. Repetition
SG5 C 10 Level 2
RFF C 1 No. 12 Reference To specify a reference.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C506 Reference M M
1153 Reference code qualifier M an..3 M VA = VAT registration number
1154 Reference identifier R an..70 M
Example: RFF+VA:544211' Note:
EDI Implementation Guidelines RECADV – 1.6 Page 13 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
SG4 M 99 Level 1
NAD M 1 No. 13 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.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
3035 Party function code qualifier
M an..3 M SU = Supplier
C082 Party identification details
A M
3039 Party identifier M an..35 M GLN (Format n13) or supplier id
1131 Code list identification code
N an..17 N
3055 Code list responsible agency code
R an..3 M 9 = EAN (International Article Numbering association)
Example: NAD+SU+5412345000020::9' Note:
Group/ Segment
Status Max. Repetition
SG5 C 10 Level 2
RFF C 1 No. 14 Reference To specify a reference.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C506 Reference M M
1153 Reference code qualifier M an..3 M VA = VAT registration number
1154 Reference identifier R an..70 M
Example: RFF+VA:544211' Note:
EDI Implementation Guidelines RECADV – 1.6 Page 14 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
SG4 M 99 Level 1
NAD M 1 No. 15 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.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
3035 Party function code qualifier
M an..3 M BY = Buyer
C082 Party identification details
A M
3039 Party identifier M an..35 M GLN (Format n13); Media-Saturn
1131 Code list identification code
N an..17 N
3055 Code list responsible agency code
R an..3 M 9 = EAN (International Article Numbering association)
Example: NAD+BY+4335347000007::9' Note:
Group/ Segment
Status Max. Repetition
SG5 C 10 Level 2
RFF C 1 No. 16 Reference To specify a reference.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C506 Reference M M
1153 Reference code qualifier M an..3 M VA = VAT registration number
1154 Reference identifier R an..70 M
Example: RFF+VA:544211' Note:
EDI Implementation Guidelines RECADV – 1.6 Page 15 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
SG16 M 9999 Level 1
CPS M 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.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
7154 Hierarchical structure level identifier
M an..35 M default value = 1
7166 Hierarchical structure parent identifier
A an..35 N
7075 Packaging level code N an..3 N
Example: CPS+1' Note:
Group/ Segment
Status Max. Repetition
SG22 M 9999 Level 2
LIN M 1 No. 18 Line item To indicate a line item and configuration.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
1082 Line item identifier R an..6 M
1229 Action request/notification description code
N an..3 N
C212 Item number identification
D D This composite data element will only be used for the identification of EAN/UPC codes. Media-Saturn product identifier will be detailed in the PIA segment
7140 Item identifier R an..35 M EAN code
7143 Item type identification code
R an..3 M SRV = EAN.UCC Global Trade Item Number
Example: LIN+1++5412345111115:SRV' LIN+1’ Note:
EDI Implementation Guidelines RECADV – 1.6 Page 16 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
SG22 M 9999 Level 3
PIA M 10 No. 19 Additional product id To specify additional or substitutional item identification codes.
Standard EANCOM® MS Implementation Data Element
Description Status Format
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..35 M Media Saturn product number
7143 Item type identification code
R an..3 M IN = Buyer’s item number
1131 Code list identification code
O an..17 N
Example: PIA+1+9334532:IN’ Note:
Group/ Segment
Status Max. Repetition
SG22 M 9999 Level 3
QTY M 10 No. 20 Quantity To specify a pertinent quantity.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C186 Quantity details M M
6063 Quantity type code qualifier
M an..3 M 12 = Despatch quantity
6060 Quantity M an..35 M Quantity despatched by supplier
6411 Measurement unit code D an..3 C PCE = Piece (EAN Code)
Example: QTY+12:5:PCE' Note:
EDI Implementation Guidelines RECADV – 1.6 Page 17 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
SG22 M 9999 Level 3
QTY M 10 No. 21 Quantity To specify a pertinent quantity.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C186 Quantity details M M
6063 Quantity type code qualifier
M an..3 M 124 = Damaged goods
6060 Quantity M an..35 M Quantity which is damaged at goods receipt.
6411 Measurement unit code D an..3 C PCE = Piece (EAN Code)
Example: QTY+124:5:PCE' Note:
Group/ Segment
Status Max. Repetition
SG22 M 9999 Level 3
RFF M 10 No. 22 Reference To specify a pertinent quantity.
Standard EANCOM® MS Implementation Data Element
Description Status Format
Stat. Description
C506 Reference M M
1153 Reference code qualifier M an..3 M LI = Line item number
1154 Reference identifier M an..70 M Line item number of the ordered product.
Example: RFF+LI:1' Note:
EDI Implementation Guidelines RECADV – 1.6 Page 18 of 19 2015-05-21
Group/ Segment
Status Max. Repetition
Level 0
UNT M 1 No. 23 Message trailer To end and check the completeness of a message
Standard EANCOM® MS Implementation Data Element
Description Status Format
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+36+ME000001' Note:
Group/ Segment
Status Max. Repetition
Level
UNZ M 1 No. Interchange trailer
To end and check the completeness of an interchange.
Standard EANCOM® MS Implementation Data Element
Description Status Format
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.
EDI Implementation Guidelines RECADV – 1.6 Page 19 of 19 2015-05-21
Sample UNA:+.? ' UNB+UNOC:3+5412345678908:14+8798765432106:14+20091101:1000+12345555' UNH+ME000001+RECADV:D:01B:UN:EAN005' BGM+632+REC5488+9' DTM+137:20021111:102' DTM+50:20091101101000:204’ RFF+ZZZ:DE' RFF+AAK:533662' DTM+171:20021025:102' RFF+ON:533662' DTM+171:20021025:102' NAD+DP+4335347999996::9' NAD+SU+5412345000020::9' NAD+BY+4335347000007::9' CPS+1' LIN+1’ PIA+1+9334532:IN’ QTY+12:12:PCE' QTY+124:5:PCE' RFF+LI:1’ UNT+18+ME000001' UNZ+1+12345555'
Contact Media-Saturn IT Services GmbH EDI Team Wankelstrasse 5 D-85046 Ingolstadt E-Mail: edi-team@media-saturn.com
top related