RETURNS ANNOUNCEMENT MESSAGE RETANN. Version 1.0. agreed-upon by EDI Working Group of ECR Poland

Similar documents
EDI IMPLEMENTATION GUIDELINES DELFOR EDIFACT D96A

OSTENQ. Order status enquiry message. Edition 2012

SLSRPT. Sales data report message. Edition 2016

COACSU. Commercial account summary message. Edition 2014

Issue 7.6, September agreed-upon by EDI Working Group of ECR Poland

ORDERS Purchase Order Message

OSTRPT. Order status report message. Edition 2014

MSCONS. Metered services consumption report message. Edition 2016

ORDERS. Purchase order message. Edition 2016

INVRPT. Inventory report message. Edition 2014

Issue 1.0, December agreed-upon by EDI Working Group of ECR Poland

Version 1.2 from

INSDES. Instruction to despatch message. Edition 2016

SANMINA-SCI EDI INBOUND DELFOR RESPONSE MESSAGE VERSION: EDIFICE D97A

Functional information for inbound EDI purchase order (PO) EDIFACT - ORDERS ANSI X12-850

RECADV. Receiving advice message. Edition 2016

INVRPT. Inventory report message

1 Detailed Guidelines of commercial invoice, INVOIC, for automotive and non automotive parts within Volvo

EDIFACT ORDERS D99B Guideline

DELFOR Delivery Forecast Delivery Schedule Message

HANMOV. Cargo/goods handling and movement message. Edition 2014

BORGWARNER IMPLEMENTATION GUIDELINES FOR DELFOR D96A MESSAGE DELIVERY SCHEDULE MESSAGE

DELFOR Delivery Schedule Message Subset for Application in the European Steel Industry

DESADV. Despatch advice message. Edition 2016

Functional information for outbound Invoice EDIFACT - INVOIC ANSI X12-810

1. Function and Intention Of the Daily Call Off EDIFACT DELFOR (FAB)...2

Metcash Trading Ltd. Invoice Message Implementation Guideline

Basics of EDI, EDIFACT and EANCOM

TEXAS INSTRUMENTS. Despatch Advice Message DESADV. (Outbound from TI) Based on EDIFICE Issue 3 (Based on EDIFACT Version 92.1)

Nexteer Vega Supplier EDI Specification

INVRPT Inventory report message

VERSION 1.2, 30 October 2006 new or changed content is shown in red

NETWORK TOYS GERMANY. EDI Message Format DESADV D.96A (Despatch Advice) V1.04 of

EDIFACT Implementation Guidelines For Shanghai GM. Delivery Forecast Schedule EDIFACT DELFOR D.97A

EDI IMPLEMENTATION GUIDELINES INVRPT EDIFACT D97A

B2B Business Document Definition Implementation Guide

IFTMIN. Instruction message. Edition 2016

INVOIC. Invoice message. Edition 2016

Transmission of Dispatch advice messages via EDIFACT-Format DESADV

Grundfos EDIFACT D.96.A

Delivery Call-Off EDIFACT DELFOR D.97A

Delivery Forecast DELFOR EDIFACT DELFOR D97.A

Global INVOIC / VDA 4938

THE DESPATCH ADVICE MESSAGE DESADV EDIFACT D.96A

IFTMIN - Transport Instruction

VOLVO CAR DESADV D96A

DESADV. Despatch advice message. Edition 2012

ECONOMIC COMMISSION FOR EUROPE

DESADV Despatch Advice Message

EDI Guideline. KION Group DESADV EDIFACT DESADV D.96A. KIM/OD Integration & EDI. based on. Version

Automotive Experience Division. EDI Implementation Guideline. Despatch Advice (DESADV)

DELFOR Delivery Schedule Message

EDI IMPLEMENTATION GUIDELINE INVOIC V3 SELFBILLING

ORDERS Purchase Order Message

Purchase Order Message

ORDERS Purchase Order Message

ORDERS Purchase Order Message Subject for application in the European Steel Industry

Detailed Guidelines of Delivery Schedule DELINS/DELFOR within Volvo

EDI Guideline. KION Group Invoic EDIFACT INVOIC D.00A. KIM/OD Integration & EDI. based on. Version

DESADV D98B. Version: November 2008 Final

EDI Implementation Guidelines DESADV UN D96A

All data fields marked as mandatory in the current documentation are considered as obligatory components in all EANCOM messages.

GROUP EDI DESADV - Despatch Advice Message

Metcash Trading Ltd. Despatch Advice Message Implementation Guideline

210115/13:55 (print date/time) RFR DRAFT INVOIC. Version 1.0 D00B

DELJIT UN D97A (Pick Up Sheet)

Message definition INVOIC Consolidated invoice with Delivery note details FASHION - Austria EANCOM 2002 (Syntax 3) Version 1.1

Implementation Guideline for PAYMUL North America Corporate egateway

Message Specification Issue date: Print date: Version: 1.41

A4D Vehicle Firm Booking

Message definition INVOIC Commercial invoice FASHION - Austria EANCOM 2002 (Syntax 3) Version 1.1

Message handbook for Ediel. Implementation guide for Delivery schedule message

Volvo Car Corporation Application Of Odette / EDIFACT

EDI message for calling and directing JiT modules to be delivered for specific vehicles in sequence of production.

EDI. Implementation Guidelines

INVOIC Invoice Message

Guideline DESADV. Mihaescu, Anca Schau, Stephanie

VOLKSWAGEN AG. Message layout chart

GS1 Germany EDI Recommendation

INVOIC D97A. Version: November 2008 Final. Cummins ECommerce Modified: 11/14/2008. Cummins Inc. 1 11/14/08

American Axle & Manufacturing DESPATCH ADVICE - DESADV. Supplier EDI Implementation Guideline Version 1.0

EDI Implementation Guidelines. EDIFACT DELFOR D97.A Delivery Forecast

PAYMUL D.96A. Multiple payment order message. Recommendation of D6 EWG sub-working group Finance. for the use of the UN/EDIFACT-Message

An EIDX Convention. For Electronic Data Interchange. Message CUSRES Customs Response Message. Version 92.1

EDIFACT Implementation Guidelines For Shanghai GM. Despatch Advice Message UN/EDIFACT DESADV D97.A

Message Implementation. Guideline (MIG) SPOTLIGHT Pty Ltd RCTI INVOIC D96A. For Buyer Created Tax Invoice. Version: 1.2. Issue Date:

Advance Shipping Note (ASN)

PAYMUL Message Implementation Guideline

820 Payment Order/Remittance Advice

DELFOR Delivery Schedule Message

Manual for the Electronic Mobile Phone Invoice Information. - Call Details - Electronic Data Exchange. with EDIFACT INVOIC UN D.01B.

DSD Invoice TRANSACTION SET 810 VERSION 4010

05/25/06 EDIFACTD95B Container discharge/loading order message - COPRAR COPRAR; D 95B COPRAR D 95B. Version: 1.0 Draft

(Implementation Guide) UN/EDIFACT MESSAGE VERMAS. Version 1.0 D.16A SMDG

Guidelines & message examples Volvo s subset of DESADV D 00A (Global DESADV)

ORDERS, ORDRSP, DESADV, INVOIC & REMADV

GLOBAL DESADV. Message Implementation Guideline. based on. DESADV Despatch advice message UN D.07A S3

VOLVO CAR CORPORATION

EDIFICE Message Implementation Guideline International Forward & Transport Message, Instruction. IFTMIN Issue EDTI10. Endorsed on June

856 Ship Notice/Manifest Standard Carton Pack Structure

Transcription:

RETURNS ANNOUNCEMENT MESSAGE RETANN Version 1.0 EAN 97/EDIFACT D.96A agreed-upon by EDI Working Group of ECR Poland The document contains only these that segments and data elements that were agreed and accepted by the members of EDI Working Group of ECR Poland. The segments and data elements are used and required from commerce partners while exchanging EDI messages. This document is compliant to the standard RETANN EAN/EDIFACT message. June 2004

I. INTRODUCTION Status MESSAGE TYPE REFERENCE DIRECTORY EAN SUBSET VERSION : RETANN : D.96A : 002 Definition A message by which a party announces to another party details of goods for return due to specified reasons (e.g. returns for repair, returns because of damage, etc.). Principles This message may be used by the message sender to request credit for goods, or the replacement of goods from the message recipient. This message should stimulate the message recipient to instruct on how the named goods should be returned, destroyed, or disposed of. In the case where the recipient of the announcement refuses to accept the return of goods the sender would expect to receive notification of this decision and also instructions on what should happen instead of the return (this is to be defined in the interchange agreement). This process will usually be handled using the Instruction for Return message. The announcement for returns can be used by a party to inform another party on the requested return of: goods received in bad condition; goods received but not ordered; goods for repair; goods which have exceeded their expiry date without being sold; goods on commission; goods from sale on approval; sale or return goods; returnable transport or packaging containers; obsolete goods; goods being re-called. The announcement for returns may be used to return received goods for which receipt of delivery may already have been acknowledged by way of the Receiving Advice message (where this message is being used), e.g., the faulty goods are only discovered on opening a container for which a receiving advice has been issued.

II. MESSAGE STRUCTURE CHART Heading section UNH BGM DTM SG 2 RFF SG 2 DTM SG 2 NAD SG 2 NAD SG 2 NAD SG 2 NAD MESSAGE HEADER BEGINNING OF MESSAGE DATE OF THE DOCUMENT REFERENCE DOCUMENT NUMBER REFERENCE DOCUMENT DATE IDENTIFICATION OF THE BUYER IDENTIFICATION OF THE SUPPLIER IDENTIFICATION OF THE DELIVERY POINT IDENTIFICATION OF THE FREIGHT FORWARDER Detail section SG11 LIN LINE ITEM SG11 PIA ADDITIONAL PRODUCT ID SG11 PRI PRICE DETAILS SG11 MOA MONETARY AMOUNT SG11 SG13 QTY QUANTITY SG11 SG13 CDI PHYSICAL OR LOGICAL STATE Summary section UNS CNT MOA UNT SECTION CONTROL CONTROL TOTAL MONETARY AMOUNT MESSAGE TRAILER The segments agreed as mandatory are written in bold.

Notes: 1. The segments are presented in the sequence in which they appear in the message. The segment or segment group tag is followed by the (M)andatory / (C)onditional indicator, the maximum number of occurrences and the segment description. 2. Reading from left to right, in column one, the data element tags and descriptions are shown, followed by in the second column the EDIFACT status (M or C), the field format, and the picture of the data elements. These first pieces of information constitute the original EDIFACT segment layout. Following the EDIFACT information, EAN specific information is provided in the third, fourth, and fifth columns. In the third column a status indicator for the use of (C)onditional EDIFACT data elements (see 2.1 through 2.3 below), in the fourth column the restricted indicator (see point 3 on the following page), and in the fifth column notes and code values used for specific data elements in the message. 2.1 (M)andatory data elements in EDIFACT segments retain their status in EAN. 2.2 Additionally, there are five types of status for data elements with a (C)onditional EDIFACT status, whether for simple, component or composite data elements. These are listed below and can be identified when relevant by the following abbreviations: - 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. 2.3 If a composite is flagged as N, NOT USED, all data elements within that composite will have blank status indicators assigned to them. 3. Status indicators detailed in the fourth column which directly relate to the code values detailed in the first column may have two values; - RESTRICTED * A data element marked with an asterix (*) in the fourth column is (are) the only codes available for use with this data element, in this segment, in this message. - OPEN All data elements where coded representation of data is possible and a restricted set of code values is not indicated are open (no asterix in fourth column). The available codes are listed in the EAN Data Elements and Code Sets Directory. Code values given in tables have been agreed by the EDI Working Group. The use of other values should be bilaterally agreed.

III. SEGMENTS LAYOUT UNH - M 1 - MESSAGE HEADER Function : To head, identify and specify a message. Segment number : 1 0062 Message reference number M an..14 M Sender's unique message reference. Sequence number of messages in the interchange. DE 0062 in UNT will have the same value. Generated by the sender. S009 MESSAGE IDENTIFIER M M 0065 Message type identifier M an..6 M * RETANN = RETURNS ANNOUNCEMENT 0052 Message type version number M an..3 M * D = Draft directory 0054 Message type release number M an..3 M * 96A = Version 96A 0051 Controlling agency M an..2 M * UN = UN/ECE/TRADE/WP.4, United Nations Standard Messages (UNSM) 0057 Association assigned code C an..6 R * EAN007 = EAN Version control number. 0068 Common access reference C an..35 N S010 STATUS OF THE TRANSFER C N 0070 Sequence message transfer number M n..2 0073 First/last sequence message transfer indication Cal Segment Notes: 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 PRICE/SALES CATALOGUE based on the D.96A directory under the control of the United Nations. DE 0057: Indicates that the message is the EAN version 005 of the UNSM PRICE/SALES CATALOGUE. This segment is mandatory. Example : UNH+ME000001+RETANN:D:96A:EN:EAN001'

BGM - M 1 Beginning of message Function : To indicate the type and function of a message and to transmit the identifying number. Segment number : 2 C002 DOCUMENT/MESSAGE NAME C R 1001 Document/message name, coded C an..3 R * 70E = RETURNS ANNOUNCEMENT 1131 Code list qualifier C an..3 N 3055 Code list responsible agency, coded C an..3 N 9 = GS1 ( former EAN ) 1000 Document/message name C an..35 O 1004 Document/message number C an..35 R Message Number assigned by document sender. 1225 Message function, coded C an..3 R * 9 = original 4343 Response type, coded C an..3 N Segment Notes: This segment is used to indicate the type and function of a message and to transmit the identifying number. DE 1004: It is recommended to limit the length of the number to 17 characters. DE 1225: 9 = original RETURNS ANNOUNCEMENT original transmission. This segment is mandatory. Example : BGM+70E::9+665+9'

DTM - M 5 - Date/time/period Function : To specify date, and/or time, or period. Segment number : 3 C507 DATE/TIME/PERIOD M M 2005 Date/time/period qualifier M an..3 M * 137 = Document/message date/time 2380 Date/time/period C an..35 R 2379 Date/time/period format qualifier C an..3 R 102 = CCYYMMDD 718 = CCYYMMDD- CCYYMMDD Segment Notes: This segment is used to specify the date or period of the message. DE 2005: 137 = Document/message date/time is obligatory. This segment is mandatory. Example : DTM + 137 : 20030301:102' Document date is as follows: 01.03.2003 r.

SG2 - C 9 - RFF-DTM RFF - M 1 - Reference Function : To specify a reference. Segment number : 6 C506 REFERENCE M M 1153 Reference qualifier M an..3 M * ON = Order number (buyer) AAK = Despatch advice number DQ = Delivery note number IV = Invoice number 1154 Reference number C an..35 R Segment Notes. This segment is used to provide document reference number. The type of reference document is agreed between partners This segment must be used at least once. Example: RFF+ON+12332'

SG1 - C 9 - RFF-DTM DTM C 9 - Date/time/period Function : To specify date, and/or time, or period. Segment number : 7 C507 DATE/TIME/PERIOD M M 2005 Date/time/period qualifier M an..3 M * 171 = Reference date/time 2380 Date/time/period C an..35 R 2379 Date/time/period format qualifier C an..3 R 102 = CCYYMMDD Segment Notes: This segment is used to specify the date or period of the reference. Example : DTM+171:20031025:102'

SG23- C 10 - NAD-LOC-SG4-SG5 NAD - M 1 - NAME AND ADDRESS Function: To specify the name/address and their related function only with DE C082 or structure C080 to 3207. Segment number: 8 * DESCRIPTION 3035 Party qualifier M an..3 M BY Buyer SU Supplier DP Delivery point FW - Freight forwarder CO82 PARTY IDENTIFICATION C A DETAILS 3039 Party id. identification M M GS1 (former EAN )Location Number - Format an..35 n13 1131 Code list qualifier C N an..3 3055 Code list responsible agency, C an..3 R * 9 = GS1 ( former EAN ) coded Segment notes: This segment is used to identify buyer, supplier, delivery point and freight forwarder. Buyer and supplier identification is obligatory. Delivery point should be provided if different than buyer. Freight forwarder identification is dependable upon partners agreement. This segment is mandatory and must be used at least twice. Element 3039: for party identification it is recommended to use GS1 codes (former EAN) Example : NAD+BY+5412345000013::9'

SG11 C 9999 - LIN-PIA-IMD-MEA-DTM-PRI-LOC-MOA-SG13-SG14-SG15-SG18-SG22 LIN - M 1 - Line item Function : To identify a line item and configuration. Segment number : 17 1082 Line item number C n..6 R Application generated number of the item lines within the invoice. 1229 Action request/notification, coded C an..3 N C212 ITEM NUMBER IDENTIFICATION C 7140 Item number C an..35 R Format n..14. GS1(EAN)-8, UPC-A, GS1(EAN)-13, or GS1-14 - this is the number of the article being invoiced. 7143 Item number type, coded C an..3 R * EN = GS1 (former EAN :EAN-8, EAN-13, EAN-14) UP = UPC (UPC-A) D Segment Notes. This segment is used to identify the trade item. GS1 (former EAN.UCC) Global Trade Item Numbers should be used to identify the trade items. This segment is mandatory. Notes to elemnts with attribute D: Element composed of C212 is used to identify GS1 (former EAN/UPC )codes. Example: LIN+1++4000862141404:EN'

SG11 C 9999 - LIN-PIA-IMD-MEA-DTM-PRI-LOC-MOA-SG13-SG14-SG15-SG18-SG22 PIA - C 9 - Additional product id Function : To specify additional or substitutional item identification codes. Segment number : 18 4347 Product id. function qualifier M an..3 M * 1 = Additional identification C212 ITEM NUMBER IDENTIFICATION 7140 Item number C an..35 R M 7143 Item number type, coded C an..3 R BP = Buyer's part number SA = Supplier's article number 3055 Code list responsible agency, coded C an..3 O 91 = Assigned by supplier or supplier's agent 92 = Assigned by buyer or buyer's agent M Segment Notes. This segment is used to specify additional or substitutional item identification codes such as a buyer's or supplier's item number. Examples : PIA+1+AEX0143:BP'

SG11 C 9999 - LIN-PIA-IMD-MEA-DTM-PRI-LOC-MOA-SG13-SG14-SG15-SG18-SG22 PRI - M 9 - Price details Function : To specify price information. Segment number : 22 C509 PRICE INFORMATION C R 5125 Price qualifier M an..3 M AAA = Calculation net AAF = Information price, excluding allowances or charges and taxes 5118 Price C n..15 R Segment Notes. This segment is used to specify price information for the current line item. Example: PRI+AAA:14.50' Net price of 14.50 (excluding tax) to be used for calculation purposes. This price includes all allowances and charges.

SG11 C 9999 - LIN-PIA-IMD-MEA-DTM-PRI-LOC-MOA-SG13-SG14-SG15-SG18-SG22 MOA - C 9 - Monetary amount Function : To specify a monetary amount. Segment number : 24 C516 MONETARY AMOUNT M M 5025 Monetary amount type qualifier M an..3 M 38 = Invoice item amount 5004 Monetary amount C n..18 R Segment Notes. This segment is used to specify in monetary terms the value of current line item in previous LIN segment. Example : MOA+38:21,80'

SG11 C 9999- LIN-PIA-IMD-MEA-DTM-PRI-LOC-MOA-SG13-SG14-SG15-SG18-SG22 SG13 C QTY - C 1 - Quantity Function : To specify a pertinent quantity. Segment number : 25 C186 QUANTITY DETAILS M M 6063 Quantity qualifier M an..3 M * 61 = returned quantity 6060 Quantity M n..15 M 6411 Measure unit qualifier C an..3 M MTR = metre MTK = square metre KGM = kilogram LTR = litre PCE = piece PR = pair (two items combined) TNE = metric tone (1000kg) Segment Notes: This segment is used to specify quantities related to the current line item. This segment is mandatory Notes to elements with D attribute: The following element 6411 is only used when variable measure items are identified. Example: QTY+61:40'

SG11 C SG13 C 9- QTY-CDI 9999- LIN-PIA-IMD-MEA-DTM-PRI-LOC-MOA-SG13-SG14-SG15-SG18-SG22 CDI - C 9 - Physical or logical state Function : To describe a physical or logical state. Segment number : 26 7001 Physical or logical state qualifier M an..3 M 3E = Upon return GS1 ( former EAN Code) C564 PHYSICAL OR LOGICAL STATE INFORMATION M M 61 = returned quantity 7007 Physical or logical state, coded M n..15 M * 4 = Damaged 12E = Return goods GS1 ( former EAN Code) 1131 Code list qualifier C an..3 N 3055 Code list responsible agency, coded 7066 Physical or logical state C an..35 O C an..3 O 9 = GS1 ( former EAN ) Segment Notes: This segment is used to indicate conditions (actions) requested by the message sender for the current line item. Example: CDI+3E+13E::9' Goods to return based upon agreed conditions.

UNS - M 1 - SECTION CONTROL Function : To separate header, detail, and summary sections of a message. Segment number : 31 0081 Section identification M a1 M * S = Detail/summary section separation Segment Notes. This segment is used to separate the detail and summary sections of the message. This segment is mandatory. Example : UNS+S'

CNT - C 10 - Control total Function : To provide control total. Segment number : 39 C270 CONTROL M M 6069 Control qualifier M an..3 M * 2 = Number of line items in message 6066 Control value M n..18 M Segment Notes. This is used to provide message control information for checking on the message receiver's in-house system. This segment is mandatory Example : CNT+2:120'

SG48 M 100 - MOA - SG49 MOA - M 9 - Monetary amount Function : To specify a monetary amount. Segment number : 40 C516 MONETARY AMOUNT M M 5025 Monetary amount type qualifier M an..3 M 210 = Credit note amount 86 = Message total monetary amount 5004 Monetary amount C n..18 R Segment Notes. First MOA segment 776 with the qualifier 77 for DE 5025 defines the payable amount. Payable amount is the gross total amount of the invoice. Example : MOA+77:45612.20'

UNT - M 1 - MESSAGE TRAILER Function : To end and check the completeness of a message. Segment number : 28 0074 Number of segments in a message M n..6 M The total number of segments in the message is detailed here. 0062 Message reference number M an..14 M The message reference numbered detailed here should equal the one specified in the UNH segment. Segment Notes. This segment is a mandatory UN/EDIFACT segment. It must always be the last segment in the message. This segment is mandatory. Example : UNT+48+ME000001'