d01 Aperak MX

Wal-Mart Stores, Inc.
Electronic Data Interchange Implementation Guideline

EDIFACT Version D01B
EANCOM 02
D
0
1
B
APERAK Message
Business Usage:
Mexico APERAK
EDI Direction: From Wal-Mart
Implementation Guide Version 1.0

Published March 2006
Last Changed March 2006
APERAK (D01B) 1
Wal-Mart Stores, Inc.Confidential
Table of Contents
UN/EDIFACT Introduction to the APERAK ................................................................................. 3
APERAK Message - Wal-Mart Stores, Inc. Introduction............................................................... 4
APERAK Message - Wal-Mart Stores, Inc. Usage ........................................................................ 5
Wal-Mart Business Example of APERAK document .................................................................... 6
Conventions used in this implementation guideline ..................................................................... 35
Change History ............................................................................................................................. 38
APERAK (D01B) 2
UN/EDIFACT Introduction to the APERAK
Introduction:
This specification provides the definition of the Application error and acknowledgement message (APERAK) to be
used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and
transport.
1. SCOPE
1.1 Functional Definition

The function of this message is:
a) to inform a message issuer that his message has been received by the addressee's application and has
been rejected due to errors encountered during its processing in the application.
b) to acknowledge to a message issuer the receipt of his message by the addressee's application.
1.2 Field of Application

The Application error and acknowledgement message may be used for both national and international
applications. It is based on universal practice related to administration, commerce and transport, and is not
dependent on the type of business or industry.
1.3 Principles
A message being first controlled at system level (CONTRL) to detect syntax errors and to acknowledge its
receipt is then transmitted to the application process to be processed.
If an error is detected at the application level, which prevents its complete processing, an APERAK
message is sent to the original message issuer giving details of the error(s) encountered.
If no error has been detected and when an acknowledgement is necessary (when no dedicated answer to the
original message exists) an APERAK message is sent precising the reasons of acknowledgement.
In case of application error, the APERAK message will need manual processing e.g. when the underlying
reason is a programming error.
In case of acknowledgement the APERAK message may be automatically or manually processed at

recipient's discretion.
2. REFERENCES
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
3. TERMS AND DEFINITIONS
3.1 Standard terms and definitions

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
4. MESSAGE DEFINITION
4.1 Data Segment Clarification

This section should be read in conjunction with the segment table which indicates mandatory, conditional
and repeating requirements.
APERAK (D01B) 3
APERAK Message - Wal-Mart Stores, Inc. Introduction
The purpose of this section is to present and explain the application of the EANCOM standards
as they pertain to the APERAK.
The purpose of the APERAK is to enable Wal-Mart to notify suppliers of invalid or insufficient
data sent to Wal-Mart. It is very important when dealing with time sensitive documents to
correct any errors and re-send those documents as soon as possible.
Functional Acknowledgment
A Syntax and Service Report, EANCOM message CONTRL should be sent within 24 hours of
receipt of an APERAK message to acknowledge receipt, or to notify Wal-Mart Stores of syntax
errors.
APERAK (D01B) 4
APERAK Message - Wal-Mart Stores, Inc. Usage
Introduction:
A message claiming payment for goods or services supplied under conditions agreed between the seller and the
buyer. The United Nations Standard Invoice Message, with correct data qualification, serves also as the
specification for Debit Note and Credit Note messages. Throughout this document, the reference to 'Invoice' may be
interpreted as conveying the wider meaning of 'Invoice/Credit Note/Debit Note'.
Heading Section:
Pos. Seg. Req. Group Notes and
No. ID Name Des. Max.Use Repeat Comments
M 0010 UNH Message header M 1
M 0020 BGM Beginning of message M 1
0030 DTM Date/time/period C 9
0090 Segment Group 2: RFF-DTM C 9
M 0100 RFF Reference M 1
0120 Segment Group 3: NAD C 9

M 0130 NAD Name and address M 1
Detail Section:
0160 Segment Group 4: ERC-FTX-SG5 C 99999
M 0170 ERC Application error information M 1
0180 FTX Free text C 1
Summary Section:
M 0220 UNT Message trailer M 1
APERAK (D01B) 5
Wal-Mart Business Example of APERAK document
UNH+000001+APERAK:D:01B:UN:EAN003 000001 is the MESSAGE REFERENCE NUMBER.
APERAK is the Message Type. “APERAK” indicates
“Application Error and Acknowledgement Message.”
D is the Message Version Number “D” indicates “Draft
Version”.
01B is the Message Release Number. “01B” indicates
“Release 2001 - B”
UN is the Controlling agency, coded. “UN” indicates
“UN/CEFACT”
EAN003 is the Association Assigned Code “EAN003”
indicates “EAN version control number (EAN Code)”.
BGM+305+987654321+27 305 is the Document Name Code. “305” indicates
“Application error and acknowledgement”
0003616687 is the Document Identifier.
27 is the Message Function Code. “27” indicates “Not
accepted”.
DTM+137:20050507:102 137 is the Date or time or period function code
qualifier. “137” indicates “Document/message date/time”.
20050507 is the Date or Time or Period Value of the
document.
102 is the Date or time or period format code. “102”
indicates “CCYYMMDD”.
RFF+IV:12345 IV is the Reference Code Qualifier. “IV” indicates
“Invoice Number”.
12345 is the Reference Identifier.
DTM+171:20050430:102 171 is the Date or time or period function code
qualifier. “171” indicates “Reference date/time” (the date
the Invoice was issued).
20050430 is the Date or time or period value of the
Invoice.
102 is the Date or time or period format code. “102”
indicates “CCYYMMDD”.
RFF+BT:AAZ BT is the Reference Code Qualifier. “BT” indicates
“Batch number/lot number” (Invoice Serial Number).
AAZ is the Reference Identifier.
RFF+ON:2255336644 ON is the Reference Qualifier. “ON” indicates “Order
number (buyer)”.
RFF+IA:987456123 IA is the Reference Code Qualifier. “IA” indicates
“Internal Vendor Number”.
NAD+BY:7507003100001++NUEVA WAL BY is the Party Function Code Qualifier. “BY” indicates
MART DE MEXICO S DE RL DE:CV “Buyer.”
7507003100001 is the Party Identifier. This is the EAN
Location Code – Format n13.
NUEVA WALMART DE MEXICO, S. DE R.L.
DE C.V. is the PARTY NAME.
NAD+SU:::++EL PROVEEDOR DE MEXICO SU is the Party Function Code Qualifier. “SU” indicates
“Supplier.”
EL PROVEEDOR DE MEXICO is the PARTY NAME.
ERC+024 024 is the Application Error Code. “024” indicates
“Other Unlisted Reason”
FTX+AAO:ERROR - UPC AAO is the Text Subject Code Qualifier. “AAO”
INVALIDO=032244045332 indicates “Error description (free text)”.
APERAK (D01B) 6
ERROR - UPC INVALIDO=032244045332 is the Free
text value.
UNT+12+1 12 is the NUMBER OF SEGMENTS IN A MESSAGE.
1 is the MESSAGE REFERENCE NUMBER.
APERAK (D01B) 7
Segment: UNH Message header
Position: 0010
Group:
Level: 0
Usage: Mandatory
Max Use: 1
Purpose: A service segment starting and uniquely identifying a message. The message type code
for the Application error and acknowledgement message is APERAK.
Note: Application error and acknowledgement messages conforming to this document
must contain the following data in segment UNH, composite S009:
Data element 0065 APERAK 0052 D 0054 01B 0051 UN
Dependency Notes:
Semantic Notes:
Comments:
Notes: Application error and acknowledgement message Heading Section
This segment is used to head, identify and specify a message.
DE's 0065, 0052, 0054 and 0051: Indicate that the message is a UNSM Application
Error and Acknowledgement message based on the D.01B directory under the
control of the United Nations.
Example:
UNH+ME000001+APERAK:D:01B:UN:EAN003'
Data Element Summary

Data Component
Element Element Name Attributes
M 0062 MESSAGE REFERENCE NUMBER M 1 an..14
Unique message reference assigned by the sender.
Senders unique message reference. Sequence number of messages in the
interchange. DE 0062 in UNT will have the same value. Generated by the
sender.
M S009 MESSAGE IDENTIFIER M 1
Identification of the type, version, etc. of the message being interchanged.
M 0065 Message type M an..6
Code identifying a type of message and assigned by its controlling agency.
Notes:
1. In UNSMs (United Nations Standard Messages), the representation is a6.
APERAK Application error and acknowledgement message
A code to identify the application error and
acknowledgement message.
EAN Description:
The function of this message is: a) to inform a
message issuer that his message has been received by
the addressee's application and has been rejected
due to errors encountered during its processing in
the application. b) to acknowledge to a message
issuer the receipt of his message by the addressee's
application.
M 0052 Message version number M an..3
Version number of a message type.
D Draft version/UN/EDIFACT Directory
Message approved and issued as a draft message (Valid
for directories published after March 1993 and prior to
March 1997). Message approved as a standard message
(Valid for directories published after March 1997).
M 0054 Message release number M an..3
APERAK (D01B) 8
Release number within the current message version number.
01B Release 2001 - B
Message approved and issued in the second 2001 release
of the UNTDID (United Nations Trade Data Interchange
Directory).
M 0051 Controlling agency, coded M an..3
Code identifying a controlling agency.
UN UN/CEFACT
United Nations Centre for Trade Facilitation and
Electronic Business (UN/CEFACT).
EAN Description:
UN Economic Commission for Europe (UN/ECE),
Committee on the development of trade (TRADE),
Working Party on facilitation of international trade
procedures (WP.4).
R 0057 Association assigned code C an..6
Code, assigned by the association responsible for the design and maintenance
of the message type concerned, which further identifies the message.
Indicates that the message is the EANCOM version 003 of the Application
Error and Acknowledgement message.
EAN003 EAN version control number (EAN Code)
N 0110 Code list directory version number C an..6
Version number of the code list directory.
0113 Message type sub-function identification C an..6
Code identifying a sub-function of a message type.
Notes:
1. The code qualifies the message type data element (0065) to allow the
recipient to identify a specific sub-function of a message.
0068 COMMON ACCESS REFERENCE C 1 an..35
Reference serving as a key to relate all subsequent transfers of data to the
same business case or file.
S010 STATUS OF THE TRANSFER C 1
Statement that the message is one in a sequence of transfers relating to the
same topic.
0070 Sequence of transfers M n..2
Number assigned by the sender indicating the transfer sequence of a message
related to the same topic. The message could be an addition or a change to an
earlier transfer related to the same topic.
Notes:
1. The first message in the sequence shall be assigned as number 1.
0073 First and last transfer C a1
Indication used for the first and last message in a sequence of messages related
to the same topic.
S016 MESSAGE SUBSET IDENTIFICATION C 1
Identification of a message subset by its identifier, version, release and source.
0115 Message subset identification M an..14
Coded identification of a message subset, assigned by its controlling agency.
0116 Message subset version number C an..3
Version number of the message subset.
0118 Message subset release number C an..3
Release number within the message subset version number.
0051 Controlling agency, coded C an..3
APERAK (D01B) 9
S017 MESSAGE IMPLEMENTATION GUIDELINE C 1
IDENTIFICATION
Identification of a message implementation guideline by its identifier, version,
release and source.
0121 Message implementation guideline identification M an..14
Coded identification of the message implementation guideline, assigned by its
controlling agency.
0122 Message implementation guideline version number C an..3
Version number of the message implementation guideline.
0124 Message implementation guideline release number C an..3
Release number within the message implementation guideline version number.
S018 SCENARIO IDENTIFICATION C 1
Identification of a scenario.
0127 Scenario identification M an..14
Code identifying scenario.
0128 Scenario version number C an..3
Version number of a scenario.
0130 Scenario release number C an..3
Release number within the scenario version number.
APERAK (D01B) 10
Segment: BGM Beginning of message
Position: 0020
Group:
Level: 0
Usage: Mandatory
Max Use: 1
Purpose: A segment to indicate the type and function of the message and to transmit the
identifying number.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to indicate the type and function of a message and to transmit
the identifying number.
Example:
BGM+305+100001+6'

Data Component
R C002 DOCUMENT/MESSAGE NAME C 1
Identification of a type of document/message by code or name. Code preferred.
R 1001 Document name code C an..3
Code specifying the document name.
305 Application error and acknowledgement
A message to inform a message issuer that a previously
sent message has been received by the addressee's
application, or that a previously sent message has been
rejected by the addressee's application.
1131 Code list identification code C an..17
Code identifying a user or association maintained code list.
Notes:
1. The codes for this data element are provided by the code list responsible
agency defined in data element 3055.
3055 Code list responsible agency code C an..3
Code specifying the agency responsible for a code list.
1000 Document name C an..35
Name of a document.
O C106 DOCUMENT/MESSAGE IDENTIFICATION C 1
Identification of a document/message by its number and eventually its version
or revision.
R 1004 Document identifier C an..35
To identify a document.
Number of the APERAK message assigned by document sender.
It is recommended that the length of the document number be restricted to

a maximum of 17 characters and that the number is unique.
This number has been given by the sender of this APERAK message it is
NOT the number of the message which is being acknowledged.
1056 Version identifier C an..9
To identify a version.
1060 Revision identifier C an..6
To identify a revision.
O 1225 MESSAGE FUNCTION CODE C 1 an..3
APERAK (D01B) 11
Code indicating the function of the message.
27 Not accepted
Message to inform that the referenced message is not
accepted by the recipient.
4343 RESPONSE TYPE CODE C 1 an..3
Code specifying the type of acknowledgment required or transmitted.
APERAK (D01B) 12
Segment: DTM Date/time/period
Position: 0030
Group:
Level: 1
Usage: Conditional (Optional)
Max Use: 9
Purpose: A segment to specify related date/time.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to specify the date of the message.
DE 2005: Identification of the 'Document/message date/time' (code value 137) is
mandatory in an EANCOM message.
Example:
DTM+137:200208301200:203'
The Application Error and Acknowledgement message was created at 12 o'clock on
the 30th of August 2002.

Data Component
M C507 DATE/TIME/PERIOD M 1
Date and/or time, or period relevant to the specified date/time/period type.
M 2005 Date or time or period function code qualifier M an..3
Code qualifying the function of a date, time or period.
137 Document/message date/time
(2006) Date/time when a document/message is issued.
This may include authentication.
R 2380 Date or time or period value C an..35
The value of a date, a date and time, a time or of a period in a specified
representation.
R 2379 Date or time or period format code C an..3
Code specifying the representation of a date, time or period.
102 CCYYMMDD
Calendar date: C = Century ; Y = Year ; M = Month ; D =
Day.
APERAK (D01B) 13
Group: RFF Segment Group 2: Reference
Position: 0090
Group:
Level: 1
Max Use: 9
Purpose: A group of segments to specify the document/message to which the current message
relates, and related date and time.
Notes: A group of segments to specify the document/message to which the current message
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
APERAK (D01B) 14
Segment: RFF Reference
Position: 0100 (Trigger Segment)
Group: SG2
Level: 1
Usage: Mandatory
Max Use: 1
Purpose: A segment to indicate the reference number of the document/message.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to specify reference numbers related to the message which is
being acknowledged.
Example:
RFF+ON:100001'
The message being acknowledged is an order.

Data Component
M C506 REFERENCE M 1
Identification of a reference.
M 1153 Reference code qualifier M an..3
Code qualifying a reference.
IV Invoice number
[1334] Reference number assigned by the seller to a
Commercial Invoice.
R 1154 Reference identifier C an..70
Identifies a reference.
This number is the same number as in the BGM segment (DE 1004) of the
message which is being acknowledged.
1156 Document line identifier C an..6
To identify a line of a document.
4000 Reference version identifier C an..35
To identify the version of a reference.
APERAK (D01B) 15
Segment: DTM Date/time/period
Position: 0110
Group: SG2
Level: 2
Max Use: 9
Purpose: A segment to specify the date and time of the referenced document/message.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to specify dates or periods relating to the previous RFF
segment.
Example:
DTM+171:200208251000:203'

Data Component
M C507 DATE/TIME/PERIOD M 1
Date and/or time, or period relevant to the specified date/time/period type.
M 2005 Date or time or period function code qualifier M an..3
Code qualifying the function of a date, time or period.
171 Reference date/time
Date/time on which the reference was issued.
R 2380 Date or time or period value C an..35
The value of a date, a date and time, a time or of a period in a specified
representation.
The date/time indicated here is the same as the date/time in the DTM
segment under BGM used with qualifier 137 of the message which is being
acknowledged.
R 2379 Date or time or period format code C an..3
Code specifying the representation of a date, time or period.
102 CCYYMMDD
Calendar date: C = Century ; Y = Year ; M = Month ; D =
Day.
APERAK (D01B) 16
Position: 0090
Group:
Level: 1
Max Use: 9
Segment Summary
APERAK (D01B) 17
Group: SG2
Level: 1
Usage: Mandatory
Max Use: 1
Dependency Notes:
Semantic Notes:
Comments:

Data Component
BT Batch number/lot number
Reference number assigned by manufacturer to a series of
similar products or goods produced under similar
conditions.
APERAK (D01B) 18
Position: 0090
Group:
Level: 1
Max Use: 9
Segment Summary
APERAK (D01B) 19
Group: SG2
Level: 1
Usage: Mandatory
Max Use: 1
Dependency Notes:
Semantic Notes:
Comments:

Data Component
ON Order number (buyer)
[1022] Reference number assigned by the buyer to an
order.
APERAK (D01B) 20
Position: 0090
Group:
Level: 1
Max Use: 9
Segment Summary
APERAK (D01B) 21
Group: SG2
Level: 1
Usage: Mandatory
Max Use: 1
Dependency Notes:
Semantic Notes:
Comments:

Data Component
IA Internal vendor number
Number identifying the company-internal vending
department/unit.
APERAK (D01B) 22
Group: NAD Segment Group 3: Name and address
Position: 0120
Group:
Level: 1
Max Use: 9
Purpose: A group of segments to specify the identifications of message sender and message
receiver with their contacts and communication channels.
Notes: A group of segments to specify the identifications of message sender and message
receiver.
Segment Summary
APERAK (D01B) 23
Segment: NAD Name and address
Group: SG3
Level: 1
Usage: Mandatory
Max Use: 1
Purpose: A segment to specify the identification of the message issuer and message receiver.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to identify the parties who exchanged the message which is
being acknowlegded.
Example:
NAD+BY+5412345000013::9'
NAD+SU+4012345500004::9'
Dependency Notes:
The following composites and data elements are only used when a coded name and
address can not be used. The affected composites and data elements are as follows:
C080 - C059 - 3164 - C819 - 3251 - 3207

Data Component
M 3035 PARTY FUNCTION CODE QUALIFIER M 1 an..3
Code giving specific meaning to a party.
BY Buyer
Party to whom merchandise and/or service is sold.
A C082 PARTY IDENTIFICATION DETAILS C 1
Identification of a transaction party by code.
M 3039 Party identifier M an..14
Code specifying the identity of a party.
For identification of parties it is recommended to use GLN - Format n13.
Notes:
R 3055 Code list responsible agency code C an..3
9 EAN (International Article Numbering association)
EAN International, based in Belgium, is an organization
of EAN Member Organizations that jointly manages the
EAN.UCC System with the Uniform Code Council.
EAN Description:
EAN International.
C058 NAME AND ADDRESS C 1
Unstructured name and address: one to five lines.
3124 Name and address description M an..35
Free form description of a name and address line.
3124 Name and address description C an..35
APERAK (D01B) 24
D C080 PARTY NAME C 1
Identification of a transaction party by name, one to five lines. Party name may
be formatted.
M 3036 Party name M an..35
Name of a party.
Party Name in clear text.
3036 Party name C an..35
Name of a party.
Name of a party.
Name of a party.
Name of a party.
3045 Party name format code C an..3
Code specifying the representation of a party name.
C059 STREET C 1
Street address and/or PO Box number in a structured address: one to four
lines.
3042 Street and number or post office box identifier M an..35
To identify a street and number and/or Post Office box number.
3042 Street and number or post office box identifier C an..35
3164 CITY NAME C 1 an..35
Name of a city.
C819 COUNTRY SUB-ENTITY DETAILS C 1
To specify a part of a country (eg county or part of a city).
3229 Country sub-entity name code C an..9
Code specifying the name of a country sub-entity.
Notes:
| 1. Recommended use ISO 3166-2. If not applicable, use appropriate code set
defined by appropriate national authority.
Notes:
3228 Country sub-entity name C an..70
Name of a country sub-entity.
3251 POSTAL IDENTIFICATION CODE C 1 an..17
APERAK (D01B) 25
Code specifying the postal zone or address.
Notes:
1. Use code defined by appropriate national authority.
3207 COUNTRY NAME CODE C 1 an..3
| Identification of the name of the country or other geographical entity as
defined in ISO 3166-1.
Notes:
| 1. Use ISO 3166-1 two alpha country code.
APERAK (D01B) 26
Group: NAD Segment Group 3: Name and address
Position: 0120
Group:
Level: 1
Max Use: 9
Purpose: A group of segments to specify the identifications of message sender and message
receiver with their contacts and communication channels.
Notes: A group of segments to specify the identifications of message sender and message
receiver.
Segment Summary
APERAK (D01B) 27
Segment: NAD Name and address
Group: SG3
Level: 1
Usage: Mandatory
Max Use: 1
Purpose: A segment to specify the identification of the message issuer and message receiver.
Dependency Notes:
Semantic Notes:
Comments:

Data Component
M 3035 PARTY FUNCTION CODE QUALIFIER M 1 an..3
Code giving specific meaning to a party.
SU Supplier
Party who supplies goods and/or services.
EAN Description:
Party which provides service(s) and/or manufactures
or otherwise has possession of goods, and consigns or
makes them available in trade.
C082 PARTY IDENTIFICATION DETAILS C 1
Identification of a transaction party by code.
3039 Party identifier M an..14
Code specifying the identity of a party.
Notes:
C058 NAME AND ADDRESS C 1
Unstructured name and address: one to five lines.
3124 Name and address description M an..35
D C080 PARTY NAME C 1
Identification of a transaction party by name, one to five lines. Party name may
be formatted.
M 3036 Party name M an..35
Name of a party.
Party Name in clear text.
APERAK (D01B) 28
Name of a party.
Name of a party.
Name of a party.
Name of a party.
3045 Party name format code C an..3
Code specifying the representation of a party name.
C059 STREET C 1
Street address and/or PO Box number in a structured address: one to four
lines.
3042 Street and number or post office box identifier M an..35
3164 CITY NAME C 1 an..35
Name of a city.
C819 COUNTRY SUB-ENTITY DETAILS C 1
To specify a part of a country (eg county or part of a city).
3229 Country sub-entity name code C an..9
Code specifying the name of a country sub-entity.
Notes:
| 1. Recommended use ISO 3166-2. If not applicable, use appropriate code set
defined by appropriate national authority.
Notes:
3228 Country sub-entity name C an..70
Name of a country sub-entity.
3251 POSTAL IDENTIFICATION CODE C 1 an..17
Code specifying the postal zone or address.
Notes:
1. Use code defined by appropriate national authority.
3207 COUNTRY NAME CODE C 1 an..3
| Identification of the name of the country or other geographical entity as
defined in ISO 3166-1.
Notes:
| 1. Use ISO 3166-1 two alpha country code.
APERAK (D01B) 29
Group: ERC Segment Group 4: Application error information
Position: 0160
Group:
Level: 1
Max Use: 99999
Purpose: A group of segments to identify the application error(s) within a specified received
message and to give specific details related to the error type or to precise the type of
acknowledgement.
Notes: Application error and acknowledgement message Detail Section
A group of segments to identify the application error(s) within a specified received
message and to give specific details related to the error type or to precise the type of
acknowledgement.
Segment Summary
M 0170 ERC Application error information M 1
0180 FTX Free text C 1
0190 Segment Group 5: Reference C 9
APERAK (D01B) 30
Segment: ERC Application error information
Group: SG4
Level: 1
Usage: Mandatory
Max Use: 1
Purpose: A segment identifying the type of application error or acknowledgement within the
referenced message. In case of an error, the error code may specify the error in detail
(e.g. a measurement relating to a piece of equipment is wrong) or as a rough indication
(e.g. a measurement is wrong).
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to identify the type of application error in the previously sent
message.
ERC+NODAT::91'
The receiver did not get any dates in the application.

Data Component
M C901 APPLICATION ERROR DETAIL M 1
Code assigned by the recipient of a message to indicate a data validation error
condition.
Should it not be possible to provide a user code in this data element and a
free form characteristic description is used in data element 9321, then it is
recommended that the code value 'ZZZ' be put in data element 1131.
M 9321 Application error code M an..8
Code specifying an application error.
Notes:
APERAK (D01B) 31
Segment: FTX Free text
Position: 0180
Group: SG4
Level: 2
Max Use: 1
Purpose: A segment to provide explanation and/or supplementary information related to the
specified application error or acknowledgement. For example, the explanation may
provide exact details relating to a generic error code.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to provide free text information related to the application
error.
Example:
FTX+AAO+1+001::ZZZ'

Data Component
M 4451 TEXT SUBJECT CODE QUALIFIER M 1 an..3
Code qualifying the subject of the text.
4453 FREE TEXT FUNCTION CODE C 1 an..3
Code specifying the function of free text.
C107 TEXT REFERENCE C 1
Coded reference to a standard text and its source.
4441 Free text value code M an..17
Code specifying free form text.
Notes:
O C108 TEXT LITERAL C 1
Free text; one to five lines.
This composite is only used if coded text can not be used.
M 4440 Free text value M an..512
Free form text.
O 4440 Free text value C an..512
Free form text.
4440 Free text value C an..512
Free form text.
Free form text.
Free form text.
3453 LANGUAGE NAME CODE C 1 an..3
Code specifying the language name.
APERAK (D01B) 32
Notes:
1. Use ISO 639-1988.
N 4447 FREE TEXT FORMAT CODE C 1 an..3
Code specifying the format of free text.
APERAK (D01B) 33
Segment: UNT Message trailer
Position: 0220
Group:
Level: 0
Usage: Mandatory
Max Use: 1
Purpose: A service segment ending a message, giving the total number of segments in the message
(including the UNH & UNT) and the control reference number of the message.
Dependency Notes:
Semantic Notes:
Comments:
Notes: Application error and acknowledgement message Summary Section
This segment is a mandatory UN/EDIFACT segment. It must always be the last
segment in the message.
Example:
UNT+11+ME000001'

Data Component
M 0074 NUMBER OF SEGMENTS IN A MESSAGE M 1 n..10
The number of segments in a message body, plus the message header segment
and message trailer segment.
The total number of segments in the message is specified here.
M 0062 MESSAGE REFERENCE NUMBER M 1 an..14
Unique message reference assigned by the sender.
The message reference numbered detailed here should equal the one
specified in the UNH segment.
APERAK (D01B) 34
Conventions used in this implementation guideline
1. Every data element on each segment is listed in the Data Element Summary section of the
segment documentation.
2. Every data element has the UN/EDIFACT data element ID noted.
3. Every data element has the UN/EDIFACT data element title noted.
4. Every data element has the UN/EDIFACT data element attributes noted:
4.1 data element requirement designation
• Mandatory (M) - This element must be used in either the segment or
composite data element in which it appears. (Mandatory data elements or
composites in EDIFACT segments retain their status in EANCOM and in
Wal-Mart guidelines.)
• Conditional (C) - This element is optional and may be included in the segment
at the option of the sender.
4.2 data element type and length
• a alphabetic characters
• n numeric characters
• an alpha numeric characters
• a3 3 alphabetic characters, fixed length
• n3 3 numeric characters, fixed length
• an3 3 alpha numeric characters, fixed length
• a..3 up to three alphabetic characters
• n..3 up to three numeric characters
• an..3 up to three alpha numeric characters
In data elements for which the Trade Data Elements Directory specifies variable
length and no other restrictions, non-significant character positions shall be
suppressed. In the case of non-significant characters, leading zeroes and trailing
spaces shall be suppressed. “Coded” data element values must be transmitted
precisely as they are shown in the code list where they appear.
For transmission purposes, all numeric data element values shall be regarded as
positive. Although conceptually a deduction is negative, it shall be represented by
a positive value. The application will interpret the meaning of the data. If a value
is to be represented as negative, it shall be immediately preceded by a minus sign,
e.g., -112. The minus sign shall not be counted when computing the maximum
field length of a data element.
The representation for a decimal sign is the point on the line (.). The decimal
point shall not be counted as a character when computing the maximum field
length of a data element. When a decimal point is transmitted, there shall be at
least one digit before and after the decimal point. For values represented by
integers only, neither decimal point nor decimal zeroes are used unless there is a
need to indicate the degree of precision.
Allowed: 0.5 and 2 and 2.0

Not Allowed: .5 and 2.
APERAK (D01B) 35
Triad separators shall not be used in an interchange. (Allowed: 2500000; Not
allowed: 2,500,000 or 2.500.000 or 2 500 000.)
DATA ELEMENT PRECISION
The following lengths may be used as a guideline:
NUMERIC CLASS FORMAT INTEGER DECIMAL

DIGIT DIGIT
Weights n..18 15 3
Cubes n..19 5 4
Quantities n..15 12 3
Unit Prices n..15 11 4
Amounts n..18 15 3
Currency Rates n..12 6 6
Percentages n..8 4 4
Tax Rates n..17 13 4
Rate Per Unit n..15 12 3
Unit Price Basis n..9 6 3
Percentage Range Value n..18 14 4
Other Range Value n..18 15 3
Control Values n..18 14 4
5. Wal-Mart utilizes AMECE implementation guidelines, which specify five status types for
data elements with a Conditional (C) EDIFACT status whether for simple, component or
composite data elements. The AMECE status is listed in the first column (to the left of
the Data Element Number Column). The five conditions are listed in the following table
along with the designation that is used in Wal-Mart implementation guides:
DESIGNATION CONDITION REQUIREMENT

M MANDATORY Indicates that the entity is required
and must be sent. NOTE:
Elements marked as “Mandatory”
by EDIFACT and “Mandatory” by
EANCOM will be marked as
“Mandatory”.
R REQUIRED Indicates that the entity is required
and must be sent. NOTE:
Elements marked as “Optional” by
EDIFACT and “Mandatory” by
AMECE will be marked as
“Required”.
A ADVISED Indicates that the entity is advised
or recommended.
D DEPENDENT Indicates that the entity must be
sent in certain conditions, as
defined by the relevant
explanatory note.
APERAK (D01B) 36
O OPTIONAL Indicates that the entity is optional
and may be sent at the discretion
of the user.
N NOT USED Indicates that the entity is not used

and should be omitted. NOTE:
An element will also be marked as
“Not Used” if AMECE allows its
use, but Wal-Mart does not use it.
6. Data elements utilized by Wal-Mart applications are noted in bold type.

7. Data elements ignored by Wal-Mart applications are noted in italicized type.
8. Every data element utilized by Wal-Mart applications has the UN/EDIFACT purpose noted.
9. Data elements which have associated codes will have the list of utilized values noted.
10. Wal-Mart comments relating to segments and data elements are noted in bold,
underlined text with a shaded background.
11. A data element marked with an asterisk (*) in the last column indicates that the listed codes
in column third are the only codes available for use with this data element, in this
segment, in this message.
APERAK (D01B) 37
Change History
Date Version Description of Changes
December 27, 2004 0.1 Original Draft
June 15, 2005 0.2 Update to Draft
March 16, 2006 1.0 Production Guide Released
APERAK (D01B) 38

d01 Aperak MX

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

d01 Aperak MX

Hochgeladen von

Copyright:

Verfügbare Formate

Wal-Mart Stores, Inc.

Electronic Data Interchange Implementation Guideline

EDI Direction: From Wal-Mart

Implementation Guide Version 1.0

UN/EDIFACT Introduction to the APERAK ................................................................................. 3

APERAK Message - Wal-Mart Stores, Inc. Introduction............................................................... 4

APERAK Message - Wal-Mart Stores, Inc. Usage ........................................................................ 5

Wal-Mart Business Example of APERAK document .................................................................... 6

Conventions used in this implementation guideline ..................................................................... 35

Change History ............................................................................................................................. 38

1.1 Functional Definition

1.2 Field of Application

In case of acknowledgement the APERAK message may be automatically or manually processed at

3. TERMS AND DEFINITIONS

3.1 Standard terms and definitions

4.1 Data Segment Clarification

0120 Segment Group 3: NAD C 9

Data Element Summary

Data Element Summary

It is recommended that the length of the document number be restricted to

Data Element Summary

Data Element Summary

Data Element Summary

Data Element Summary

Data Element Summary

Data Element Summary

Data Element Summary

Data Element Summary

Data Element Summary

Data Element Summary

Data Element Summary

Allowed: 0.5 and 2 and 2.0

DATA ELEMENT PRECISION

The following lengths may be used as a guideline:

NUMERIC CLASS FORMAT INTEGER DECIMAL

DESIGNATION CONDITION REQUIREMENT

and may be sent at the discretion

N NOT USED Indicates that the entity is not used

6. Data elements utilized by Wal-Mart applications are noted in bold type.

Date Version Description of Changes

December 27, 2004 0.1 Original Draft

June 15, 2005 0.2 Update to Draft

March 16, 2006 1.0 Production Guide Released

Das könnte Ihnen auch gefallen