ORDRSP Message ORDRSP IBM Implementation Guide - Purchase Order Response Message - Feb. 2008

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

ORDERS Purchase Order Message

Functional information for outbound Advance Ship Notice (ASN) EDIFACT - DESADV ANSI X12-856

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

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

DELFOR Delivery Forecast Delivery Schedule Message

EDIFACT ORDERS D99B Guideline

OSTENQ. Order status enquiry message. Edition 2012

BORGWARNER IMPLEMENTATION GUIDELINES FOR DELFOR D96A MESSAGE DELIVERY SCHEDULE MESSAGE

ORDERS Purchase Order Message

EDI IMPLEMENTATION GUIDELINES DELFOR EDIFACT D96A

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

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

INVRPT Inventory report message

Purchase Order Message

DESADV Despatch Advice Message

DELFOR Delivery Schedule Message

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

SLSRPT. Sales data report message. Edition 2016

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

Delivery Call-Off EDIFACT DELFOR D.97A

EDI IMPLEMENTATION GUIDELINES INVRPT EDIFACT D97A

REMADV. Remittance advice message. Edition 2016

REWE STANDARD INVOICE

EDIFACT Implementation Guidelines For Shanghai GM

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

Global INVOIC / VDA 4938

OSTRPT. Order status report message. Edition 2014

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

Metcash Trading Ltd. Invoice Message Implementation Guideline

GROUP EDI DESADV - Despatch Advice Message

ORDERS Purchase Order Message

REQOTE. Request for quote message. Edition 2016

DELFOR Delivery Schedule Message

INVOIC Invoice Message

ORDERS. Purchase order message. Edition 2016

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

Delivery Forecast DELFOR EDIFACT DELFOR D97.A

COACSU. Commercial account summary message. Edition 2014

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

Volvo Car Corporation Application Of Odette / EDIFACT

Version 1.2 from

A4D Vehicle Firm Booking

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

DELJIT UN D97A (Pick Up Sheet)

THE DESPATCH ADVICE MESSAGE DESADV EDIFACT D.96A

DESADV D97A Despatch Advice Message User Guide DESADV D97A Standard

Nexteer Vega Supplier EDI Specification

DELJIT. Guidelines EDIFACT

Transmission of Dispatch advice messages via EDIFACT-Format DESADV

B2B Business Document Definition Implementation Guide

INVRPT. Inventory report message. Edition 2014

ECONOMIC COMMISSION FOR EUROPE

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

This message guide describes necessary delivery schedule informations transmitted by EDI for material deliveries to plants in the VW group.

EDI. Implementation Guidelines

INVOIC. Invoice message. Edition 2016

INVRPT. Inventory report message. Edition 2016

Metcash Trading Ltd. Despatch Advice Message Implementation Guideline

MSCONS. Metered services consumption report message. Edition 2016

INSDES. Instruction to despatch message. Edition 2016

VOLVO CAR DESADV D96A

IFTMIN - Transport Instruction

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

INVRPT. Inventory report message

Grundfos EDIFACT D.96.A

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

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

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

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

944 Warehouse Stock Transfer Receipt Advice

EDI Implementation Guidelines DESADV UN D96A

EDI X Implementation Guide. Advanced Ship Notice

IFTMIN. Instruction message. Edition 2016

Implementation. Guide For. ComEd. Electronic Data Interchange. Transaction Set. Version Remittance. Version 1.

820 Transaction 820 IBM Subset - Payment Order/Remittance Advice /2009. Pos. Seg. Req. Loop Notes and

RECADV. Receiving advice message. Edition 2016

IFTMBC Booking Confirmation

Delivery Call-Off - EDIFACT DELFOR D.97A for Magna Steyr Graz N

Basics of EDI, EDIFACT and EANCOM

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

X12 Implementation Guidelines For Inbound Price Catalog v (832I)

X12 Implementation Guidelines For Outbound Purchase Order v2001 (850O)

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

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

DESADV. Despatch advice message. Edition 2016

Guideline DESADV. Mihaescu, Anca Schau, Stephanie

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

DESADV. Despatch advice message. Edition 2012

Implementation Guide IFTSAI D.00B Version 2.0

Message handbook for Ediel. Implementation guide for Delivery schedule message

DESADV D98B. Version: November 2008 Final

ARVINMERITOR P.O.'S 850 TRANSACTION SET WILL BE UTILIZED TO COMMUNICATE CONTRACTUAL INFORMATION REGARDING PART AND PRICE

Implementation Guideline for PAYMUL North America Corporate egateway

820 Payment Order/Remittance Advice DRAFT

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

EDI Implementation Guidelines. EDIFACT DELFOR D97.A Delivery Forecast

VOLKSWAGEN AG. Message layout chart

Electronic Data Interchange

Message Specification Issue date: Print date: Version: 1.41

Transcription:

ORDRSP IBM Implementation Guide - Purchase Order Response Message - Feb. 2008 Introduction: A message from the seller to the buyer, responding to a purchase order message or a purchase order change request message. Heading Section: Pos. Seg. Req. Group Notes and M No. ID Name Des. Max.Use Repeat Comments 0010 UNH Message Header M 1 M 0020 BGM Beginning of Message M 1 M 0030 DTM Date/Time/Period M 35 0070 FTX Free Text C 99 0080 Segment Group 1: RFF C 99 M 0090 RFF Reference M 1 Detail Section: Pos. Seg. Req. Group Notes and No. ID Name Des. Max.Use Repeat Comments 0960 Segment Group 26: C 200000 LIN-QTY-SG30-SG31-SG51 M 0970 LIN Line Item M 1 1010 QTY Quantity C 10 1240 Segment Group 30: PRI C 25 M 1250 PRI Price Details M 1 1300 Segment Group 31: RFF C 999 M 1310 RFF Reference M 1 1990 Segment Group 51: SCC-SG52 C 100 M 2000 SCC Scheduling Conditions M 1 2030 Segment Group 52: QTY-DTM C 10 M 2040 QTY Quantity M 1 2050 DTM Date/Time/Period C 5 Section Control: Pos. Seg. Req. Group Notes and No. ID Name Des. Max.Use Repeat Comments M 2160 UNS Section Control M 1 Summary Section: Pos. Seg. Req. Group Notes and No. ID Name Des. Max.Use Repeat Comments M 2230 UNT Message Trailer M 1 97A 1 Feb. 2008

Segment: UNH Message Header Position: 0010 Group: Level: 0 Max Use: 1 Purpose: A service segment starting and uniquely identifying a message. The message type code for the Purchase order response message is ORDRSP. Note: Purchase order response messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 ORDRSP 0052 D 0054 97A 0051 UN M 0062 MESSAGE REFERENCE NUMBER M an..14 M S009 MESSAGE IDENTIFIER M M 0065 Message type identifier M an..6 ORDRSP Purchase order response message M 0052 Message type version number M an..3 D Draft version/un/edifact Directory M 0054 Message type release number M an..3 97A Release 1997 - A M 0051 Controlling agency M an..2 UN UN/ECE/TRADE/WP.4 0057 Association assigned code C an..6 97A 2 Feb. 2008

Segment: BGM Beginning of Message Position: 0020 Group: Level: 0 Max Use: 1 Purpose: A segment by which the sender must uniquely identify the order response by means of its number and when necessary its function. C002 DOCUMENT/MESSAGE NAME C 1001 Document/message name, coded C an..3 231 Purchase order response C106 DOCUMENT/MESSAGE IDENTIFICATION C 1004 Document/message number C an..35 1060 Revision number C an..6 1225 MESSAGE FUNCTION, CODED 6 Confirmation C an..3 97A 3 Feb. 2008

Segment: DTM Date/Time/Period Position: 0030 Group: Level: 1 Max Use: 35 Purpose: A segment specifying general dates and, when relevant, times related to the whole message. The segment must be specified at least once to identify the order response date. Examples of the use of this DTM segment are: Lead times that apply to the whole of the Order response and, if no schedule is to be specified, the delivery date. The Date/time/period segment within other Segment groups should be used whenever the date/time/period needs to be logically related to another specified data item. e.g. Payment due date is specified within the PAT Segment group. M C507 DATE/TIME/PERIOD M M 2005 Date/time/period qualifier M an..3 137 Document/message date/time 2380 Date/time/period C an..35 2379 Date/time/period format qualifier 102 CCYYMMDD C an..3 97A 4 Feb. 2008

Segment: FTX Free Text Position: 0070 Group: Level: 1 Usage: Conditional (Optional) Max Use: 99 Purpose: A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually. M 4451 TEXT SUBJECT QUALIFIER M an..3 GEN Entire transaction set C108 TEXT LITERAL C M 4440 Free text M an..70 97A 5 Feb. 2008

Group: RFF Segment Group 1: Reference Position: 0080 Group: Level: 1 Usage: Conditional (Optional) Max Use: 99 Purpose: A group of segments for giving references and where necessary, their dates, relating to the whole message, e.g. contract number, import/export licence number, reservation number. Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 0090 RFF Reference M 1 97A 6 Feb. 2008

Segment: RFF Reference Position: 0090 (Trigger Segment) Group: Segment Group 1 (Reference) Conditional (Optional) Level: 1 Max Use: 1 Purpose: A segment identifying the reference by its number and where appropriate a line number within a document. M C506 REFERENCE M M 1153 Reference qualifier M an..3 ADJ Company / syndicate reference 1 ADK Company / syndicate reference 2 CR Customer reference number 1154 Reference number C an..35 97A 7 Feb. 2008

Group: LIN Segment Group 26: Line Item Position: 0960 Group: Level: 1 Usage: Conditional (Optional) Max Use: 200000 Purpose: A group of segments providing details of the individual ordered items. This Segment group may be repeated to give sub-line details. Segment Summary Pos. Seg. Req. Max. Group: M No. ID Name Des. Use Repeat 0970 LIN Line Item M 1 1010 QTY Quantity C 10 1240 Segment Group 30: Price Details C 25 1300 Segment Group 31: Reference C 999 1990 Segment Group 51: Scheduling Conditions C 100 97A 8 Feb. 2008

Segment: LIN Line Item Position: 0970 (Trigger Segment) Group: Segment Group 26 (Line Item) Conditional (Optional) Level: 1 Max Use: 1 Purpose: A segment identifying the line item by the line number and configuration level, and additionally, identifying the product or service ordered. Other product identification numbers, e.g. Buyer product number, etc., can be specified within the following PIA segment. 1082 LINE ITEM NUMBER C an..6 97A 9 Feb. 2008

Segment: QTY Quantity Position: 1010 Group: Segment Group 26 (Line Item) Conditional (Optional) Level: 2 Usage: Conditional (Optional) Max Use: 10 Purpose: A segment identifying the product quantities e.g. ordered quantity. M C186 QUANTITY DETAILS M M 6063 Quantity qualifier M an..3 21 Ordered quantity M 6060 Quantity M n..15 6411 Measure unit qualifier C an..3 97A 10 Feb. 2008

Group: PRI Segment Group 30: Price Details Position: 1240 Group: Segment Group 26 (Line Item) Conditional (Optional) Level: 2 Usage: Conditional (Optional) Max Use: 25 Purpose: A group of segments identifying the relevant pricing information for the goods or services ordered. Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 1250 PRI Price Details M 1 97A 11 Feb. 2008

Segment: PRI Price Details Position: 1250 (Trigger Segment) Group: Segment Group 30 (Price Details) Conditional (Optional) Level: 2 Max Use: 1 Purpose: A segment to specify the price type and amount. The price used in the calculation of the line amount will be identified as 'Unit Price'. C509 PRICE INFORMATION C M 5125 Price qualifier M an..3 AAA Calculation net 5118 Price C n..15 5284 Unit price basis C n..9 6411 Measure unit qualifier C an..3 97A 12 Feb. 2008

Group: RFF Segment Group 31: Reference Position: 1300 Group: Segment Group 26 (Line Item) Conditional (Optional) Level: 2 Usage: Conditional (Optional) Max Use: 999 Purpose: A group of segments giving references and where necessary, their dates, relating to the line item. Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 1310 RFF Reference M 1 97A 13 Feb. 2008

Segment: RFF Reference Position: 1310 (Trigger Segment) Group: Segment Group 31 (Reference) Conditional (Optional) Level: 2 Max Use: 1 Purpose: A segment identifying the reference by its number and where appropriate a line number within a document. M C506 REFERENCE M M 1153 Reference qualifier M an..3 ABO Originator's reference AFV PI PL Quantity valuation number Price list version number Price list number 1154 Reference number C an..35 97A 14 Feb. 2008

Group: SCC Segment Group 51: Scheduling Conditions Position: 1990 Group: Segment Group 26 (Line Item) Conditional (Optional) Level: 2 Usage: Conditional (Optional) Max Use: 100 Purpose: A group of segments specifying requested delivery schedules relating to quantities, frequencies, and dates, required for the line item, where this is different to or not specified within the heading section. Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 2000 SCC Scheduling Conditions M 1 2030 Segment Group 52: Quantity C 10 97A 15 Feb. 2008

Segment: SCC Scheduling Conditions Position: 2000 (Trigger Segment) Group: Segment Group 51 (Scheduling Conditions) Conditional (Optional) Level: 2 Max Use: 1 Purpose: A segment specifying the type and status of the schedule being given, and optionally defining a pattern to be established, e.g. firm or proposed delivery schedule for a weekly pattern. M 4017 DELIVERY PLAN STATUS INDICATOR, CODED M an..3 1 Firm 97A 16 Feb. 2008

Group: QTY Segment Group 52: Quantity Position: 2030 Group: Segment Group 51 (Scheduling Conditions) Conditional (Optional) Level: 3 Usage: Conditional (Optional) Max Use: 10 Purpose: A group of segments to specify the scheduled quantities, date/time details of the schedule and where required the reference of the schedule. Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 2040 QTY Quantity M 1 2050 DTM Date/Time/Period C 5 97A 17 Feb. 2008

Segment: QTY Quantity Position: 2040 (Trigger Segment) Group: Segment Group 52 (Quantity) Conditional (Optional) Level: 3 Max Use: 1 Purpose: A segment to specify pertinent quantities relating to the schedule and pattern established in the SCC segment, e.g. delivery quantity. M C186 QUANTITY DETAILS M M 6063 Quantity qualifier M an..3 21 Ordered quantity M 6060 Quantity M n..15 97A 18 Feb. 2008

Segment: DTM Date/Time/Period Position: 2050 Group: Segment Group 52 (Quantity) Conditional (Optional) Level: 4 Usage: Conditional (Optional) Max Use: 5 Purpose: A segment indicating the date/time details relating to the quantity and schedule details in the SCC/QTY segments. This segment may be repeated to indicate date/time ranges, e.g. start and end dates for a delivery pattern, or delivery window. M C507 DATE/TIME/PERIOD M M 2005 Date/time/period qualifier M an..3 2 Delivery date/time, requested 2380 Date/time/period C an..35 2379 Date/time/period format qualifier 102 CCYYMMDD C an..3 97A 19 Feb. 2008

Segment: UNS Section Control Position: 2160 Group: Level: 0 Max Use: 1 Purpose: A service segment placed at the start of the summary section to avoid segment collision. M 0081 SECTION IDENTIFIER M a1 S Detail/summary section separation 97A 20 Feb. 2008

Segment: UNT Message Trailer Position: 2230 Group: Level: 0 Max Use: 1 Purpose: A service segment ending a message, giving the total number of segments in the message and the control reference number of the message. M 0074 NUMBER OF SEGMENTS IN A MESSAGE M n..6 M 0062 MESSAGE REFERENCE NUMBER M an..14 97A 21 Feb. 2008