27
ORDERS Purchase order message EDIFACT/D97A/ORDERS : ORDERS Purchase order message Company: Insight Enterprises Created: 10/10/2012

ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

  • Upload
    dinhbao

  • View
    226

  • Download
    2

Embed Size (px)

Citation preview

Page 1: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

ORDERS Purchase ordermessage

EDIFACT/D97A/ORDERS : ORDERS Purchase order message

Company: Insight Enterprises Created: 10/10/2012

Page 2: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

i

Table of Contents

ORDERS Purchase order message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>UNH MESSAGE HEADER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>BGM BEGINNING OF MESSAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM DATE/TIME/PERIOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>FTX FREE TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>RFF REFERENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>NAD NAME AND ADDRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTA CONTACT INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>COM COMMUNICATION CONTACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CUX CURRENCIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TOD TERMS OF DELIVERY OR TRANSPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SCC SCHEDULING CONDITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>LIN LINE ITEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PIA ADDITIONAL PRODUCT ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>IMD ITEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>QTY QUANTITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM DATE/TIME/PERIOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PRI PRICE DETAILS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>UNS SECTION CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>UNT MESSAGE TRAILER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1

. . . . . 2

. . . . . 4

. . . . . 5

. . . . . 6

. . . . . 8

. . . . . 9

. . . . 11

. . . . 13

. . . . 14

. . . . 15

. . . . 16

. . . . 17

. . . . 18

. . . . 20

. . . . 21

. . . . 22

. . . . 23

. . . . 24

. . . . 25

Page 3: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

1

ORDERS Purchase order messageMessage Status=3

Definition: A message specifying details for goods or services ordered under conditions agreed between the sellerand the buyer.

Heading:Pos Tag Segment Name Status Rep Notes Usage0010 UNH MESSAGE HEADER M 1 N1/0010 Must use0020 BGM BEGINNING OF MESSAGE M 1 N1/0020 Must use0030 DTM DATE/TIME/PERIOD M 35 N1/0030 Must use0070 FTX FREE TEXT C 99 N1/0070 Used

0090 Segment Group 1 C 9999 N1/0090 Must use 0090 Segment Group 1 C 9999 N1/0090 Must use

0100 RFF REFERENCE M 1 N1/0100 Must use

0120 Segment Group 2 C 99 N1/0120 Must use 0120 Segment Group 2 C 99 N1/0120 Must use

0130 NAD NAME AND ADDRESS M 1 N1/0130 Must use 0220 Segment Group 5 C 5 N1/0220 Must use 0220 Segment Group 5 C 5 N1/0220 Must use

0230 CTA CONTACT INFORMATION M 1 N1/0230 Must use0240 COM COMMUNICATION CONTACT C 1 N1/0240 Must use

0290 Segment Group 7 C 5 N1/0290 Must use 0290 Segment Group 7 C 5 N1/0290 Must use

0300 CUX CURRENCIES M 1 N1/0300 Must use

0460 Segment Group 12 C 5 N1/0460 Must use 0460 Segment Group 12 C 5 N1/0460 Must use

0470 TOD TERMS OF DELIVERY ORTRANSPORT

M 1 N1/0470 Must use

0620 Segment Group 16 C 10 N1/0620 Must use 0620 Segment Group 16 C 10 N1/0620 Must use

0630 SCC SCHEDULING CONDITIONS M 1 N1/0630 Must use

Detail:Pos Tag Segment Name Status Rep Notes Usage

1030 Segment Group 28 C 200000 N2/1030 Must use 1030 Segment Group 28 C 200000 N2/1030 Must use

1040 LIN LINE ITEM M 1 N2/1040 Must use1050 PIA ADDITIONAL PRODUCT ID C 25 N2/1050 Must use1060 IMD ITEM DESCRIPTION C 99 N2/1060 Must use1080 QTY QUANTITY C 99 N2/1080 Must use1110 DTM DATE/TIME/PERIOD C 35 N2/1110 Must use

1310 Segment Group 32 C 25 N2/1310 Must use 1310 Segment Group 32 C 25 N2/1310 Must use

1320 PRI PRICE DETAILS M 1 N2/1320 Must use

Summary:Pos Tag Segment Name Status Rep Notes Usage2320 UNS SECTION CONTROL M 1 N3/2320 Must use2390 UNT MESSAGE TRAILER M 1 N3/2390 Must use

Page 4: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

2

UNH MESSAGE HEADER Pos: 0010 Max: 1Mandatory

Group: N/A Elements: 2

User Option (Usage): Must useFunction: To head, identify and specify a message.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageUNH010 0062 Message reference number

Description: Unique messagereference assigned by the sender.

M an 1/14 Must use

UNH020 S009 MESSAGE IDENTIFIER

Description: Identification of the type,version, etc. of the message beinginterchanged.

M Comp Must use

UNH020-010 0065 Message type

Description: Code identifying a type ofmessage and assigned by itscontrolling agency.

M an 1/6 Must use

CodeList Summary (Total Codes: 180, Included: 1)Code NameORDERS Purchase order message

Description: A code to identify the purchase order message.

UNH020-020 0052 Message version number

Description: Version number of amessage type.

M an 1/3 Must use

CodeList Summary (Total Codes: 8, Included: 1)Code NameD Draft version/UN/EDIFACT Directory

Description: Message approved and issued as a draft message (Valid fordirectories published after March 1993 and prior to March 1997). Messageapproved as a standard message (Valid for directories published after March1997).

UNH020-030 0054 Message release number

Description: Release number withinthe current message version number.

M an 1/3 Must use

CodeList Summary (Total Codes: 20, Included: 1)Code Name97A Release 1997 - A

Description: Message approved and issued in the first 1997 release of theUNTDID (United Nations Trade Data Interchange Directory).

UNH020-040 0051 Controlling agency, coded

Description: Code identifying a

M an 1/3 Must use

Page 5: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

Ref Tag Element Name Status Type Min/Max Usage

3

controlling agency.

CodeList Summary (Total Codes: 25, Included: 1)Code NameUN UN/CEFACT

Description: United Nations Economic UN Economic Commission for Europe(UN/ECE), Committee on the development of trade (TRADE), Working Party onfacilitation of international trade procedures (WP.4).

Notes: 1. Data element S009/0057 is retained for upward compatibility. The use of S016 and/or S017 is encouraged in

preference.2. The combination of the values carried in data elements 0062 and S009 shall be used to identify uniquely the

message within its group (if used) or if not used, within its interchange, for the purpose of acknowledgement.

Notes:Notes:Example:

UNH+17+ORDERS:D:97A:UN

Example:

UNH+17+ORDERS:D:97A:UN

Page 6: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

4

BGM BEGINNING OF MESSAGE Pos: 0020 Max: 1Mandatory

Group: N/A Elements: 3

User Option (Usage): Must useFunction: To indicate the type and function of a message and to transmit the identifying number.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageBGM010 C002 DOCUMENT/MESSAGE NAME

Description: Identification of a type ofdocument/message by code or name.Code preferred.

C Comp Must use

BGM010-010 1001 Document name code

Description: Code specifying thedocument name.

C an 1/3 Must use

CodeList Summary (Total Codes: 549, Included: 1)Code Name105 Purchase order

Description: Document/message issued within an enterprise to initiate thepurchase of articles, materials or services required for the production ormanufacture of goods to be offered for sale or otherwise supplied to customers.

BGM020 C106 DOCUMENT/MESSAGEIDENTIFICATION

Description: Identification of adocument/message by its number andeventually its version or revision.

C Comp Must use

BGM020-010 1004 Document/message number

Description: Reference numberassigned to the document/message bythe issuer.

C an 1/35 Must use

BGM030 1225 Message function code

Description: Code indicating thefunction of the message.

C an 1/3 Must use

CodeList Summary (Total Codes: 60, Included: 2)Code Name7 Duplicate

Description: The message is a duplicate of a previously generated message.9 Original

Description: Initial transmission related to a given transaction.

Notes:Notes:Example:

BGM+105+2125323+9

Example:

BGM+105+2125323+9

Page 7: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

5

DTM DATE/TIME/PERIOD Pos: 0030 Max: 35Mandatory

Group: N/A Elements: 1

User Option (Usage): Must useFunction: To specify date, and/or time, or period.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageDTM010 C507 DATE/TIME/PERIOD

Description: Date and/or time, orperiod relevant to the specifieddate/time/period type.

M Comp Must use

DTM010-010 2005 Date/time/period function codequalifier

Description: Code giving specificmeaning to a date, time or period.

M an 1/3 Must use

CodeList Summary (Total Codes: 697, Included: 1)Code Name4 Order date/time

Description: [2010] Date when an order is issued.

DTM010-020 2380 Date/time/period value

Description: The value of a date, adate and time, a time or of a period in aspecified representation.

C an 1/35 Must use

DTM010-030 2379 Date/time/period format code

Description: Code specifying therepresentation of a date, time or period.

C an 1/3 Must use

CodeList Summary (Total Codes: 74, Included: 1)Code Name102 CCYYMMDD

Description: Calendar date: C = Century ; Y = Year ; M = Month ; D = Day.

Notes:Notes:Order date in format CCYYMMDD

Example:DTM+4:20120423:102

Order date in format CCYYMMDD

Example:DTM+4:20120423:102

Page 8: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

6

FTX FREE TEXT Pos: 0070 Max: 99Conditional

Group: N/A Elements: 6

User Option (Usage): UsedFunction: To provide free form or coded text information.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageFTX010 4451 Text subject code qualifier

Description: Code specifying thesubject of the text.

M an 1/3 Must use

CodeList Summary (Total Codes: 313, Included: 2)Code NameBLR Transport document remarks

Description: Remarks concerning the complete consignment to be printed on thebill of lading.

ORI Order instructionDescription: Free text contains order instructions.

FTX020 4453 Text function, coded

Description: Code specifying thepurpose of the text.

C an 1/3 Used

FTX030 C107 TEXT REFERENCE

Description: Coded reference to astandard text and its source.

C Comp Used

FTX040 C108 TEXT LITERAL

Description: Free text; one to fivelines.

C Comp Used

FTX050 3453 Language name code

Description: Code specifying thelanguage name.

C an 1/3 Used

FTX060 4447 Text formatting, coded

Description: Code specifying theformatting parameters for the text.

C an 1/3 Used

Notes:Notes:FTX (BLR) – contains dynamic text to be printed on the printed dnote (we would like to see a copy of a currentproduction dnote and also get one printed for a test order as part of testing) Example: FTX+BLR+1++Please print this text on the dnote to check the layout

FTX (ORI) – contains instructions that would need the order to be placed on hold and looked at before processing

FTX (BLR) – contains dynamic text to be printed on the printed dnote (we would like to see a copy of a currentproduction dnote and also get one printed for a test order as part of testing) Example: FTX+BLR+1++Please print this text on the dnote to check the layout

FTX (ORI) – contains instructions that would need the order to be placed on hold and looked at before processing

Page 9: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

7

the order through your ERP

FTX+ORI+3++presence of this segment (with a 3) should cause the order to go on hold as some manualintervention is required   

the order through your ERP

FTX+ORI+3++presence of this segment (with a 3) should cause the order to go on hold as some manualintervention is required   

Page 10: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

8

RFF REFERENCE Pos: 0100 Max: 1Mandatory

Group: 1 Elements: 1

User Option (Usage): Must useFunction: To specify a reference.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageRFF010 C506 REFERENCE

Description: Identification of areference.

M Comp Must use

RFF010-010 1153 Reference function code qualifier

Description: Code giving specificmeaning to a reference segment or areference number.

M an 1/3 Must use

CodeList Summary (Total Codes: 707, Included: 2)Code NameON Order number (purchase)

Description: [1022] Reference number assigned by the buyer to an order.OP Original purchase order

Description: Reference to the order previously sent.

RFF010-020 1154 Reference identifier

Description: Identifies a reference.

C an 1/35 Must use

Notes:Notes:RFF (OP)– this will contain our Sales Order NumberRFF (ON)– this will contain our Customers’ PO Number for direct ship orders

 Example:RFF+OP:3020178RFF+ON:IS776 / 777

RFF (OP)– this will contain our Sales Order NumberRFF (ON)– this will contain our Customers’ PO Number for direct ship orders

 Example:RFF+OP:3020178RFF+ON:IS776 / 777

Page 11: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

9

NAD NAME AND ADDRESS Pos: 0130 Max: 1Mandatory

Group: 2 Elements: 7

User Option (Usage): Must useFunction: To specify the name/address and their related function, either by C082 only and/or unstructured by C058or structured by C080 thru 3207.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageNAD010 3035 Party function code qualifier

Description: Code giving specificmeaning to a party.

M an 1/3 Must use

CodeList Summary (Total Codes: 490, Included: 2)Code NameBY Buyer

Description: (3002) Party to which merchandise is sold.DP Delivery party

Description: (3144) Party to which goods should be delivered, if not identicalwith consignee.

NAD020 C082 PARTY IDENTIFICATION DETAILS

Description: Identification of atransaction party by code.

C Comp Used

NAD020-010 3039 Party identifier

Description: Code specifying theidentity of a party.

M an 1/35 Must use

NAD040 C080 PARTY NAME

Description: Identification of atransaction party by name, one to fivelines. Party name may be formatted.

C Comp Used

NAD040-010 3036 Party name

Description: Name of a party involvedin a transaction.

M an 1/35 Must use

NAD050 C059 STREET

Description: Street address and/or POBox number in a structured address:one to four lines.

C Comp Used

NAD050-010 3042 Street and number/p.o. box

Description: Street and number inplain language, or Post Office Box No.

M an 1/35 Must use

NAD050-030 3042 Street and number/p.o. box

Description: Street and number inplain language, or Post Office Box No.

C an 1/35 Must use

Page 12: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

Ref Tag Element Name Status Type Min/Max Usage

10

NAD060 3164 City name

Description: Name of a city (a town, avillage) for addressing purposes.

C an 1/35 Used

NAD080 3251 Postal identification code

Description: Code specifying thepostal zone or address.Notes: MAXIMUM LEGTH ALLOWEDBY INSIGHT FOR POSTAL ID CODEIS 9

C an 1/17 Used

NAD090 3207 Country name code

Description: Identification of the nameof the country or other geographicalentity as specified in ISO 3166.

C an 1/3 Used

Notes:Notes:NAD (BY) –this will contain our account number with you or the previously sent value

 Example:NAD+BY+316133

NAD (DP)– this will contain the delivery address, both for our warehouse orders and direct ship orders.For Warehouse orders only, we will send either a constant (e.g. ‘WH’) or a Ship To code setup in your ERPrelating to the Warehouse address. We need this value to be sent back in the Order Response, Despatch Adviceand Invoice Messages.

 Example:NAD+DP+32017796++Goods Inwards:Insight Direct UK+Tinsley Park Road::Tinsley Park Road+Sheffield++S95DE+GBNAD+DP+++Fitness First+High Street+Uxbridge++UB8 1GD+GB

NAD (BY) –this will contain our account number with you or the previously sent value

 Example:NAD+BY+316133

NAD (DP)– this will contain the delivery address, both for our warehouse orders and direct ship orders.For Warehouse orders only, we will send either a constant (e.g. ‘WH’) or a Ship To code setup in your ERPrelating to the Warehouse address. We need this value to be sent back in the Order Response, Despatch Adviceand Invoice Messages.

 Example:NAD+DP+32017796++Goods Inwards:Insight Direct UK+Tinsley Park Road::Tinsley Park Road+Sheffield++S95DE+GBNAD+DP+++Fitness First+High Street+Uxbridge++UB8 1GD+GB

Page 13: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

11

CTA CONTACT INFORMATION Pos: 0230 Max: 1Mandatory

Group: 5 Elements: 2

User Option (Usage): Must useFunction: To identify a person or a department to whom communication should be directed.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageCTA010 3139 Contact function code

Description: Code specifying thefunction of a contact (e.g. departmentor person).

C an 1/3 Must use

CodeList Summary (Total Codes: 95, Included: 2)Code NameIC Information contact

Description: Department/person to contact for questions regarding transactions.OC Order contact

Description: An individual to contact for questions regarding this order.

CTA020 C056 DEPARTMENT OR EMPLOYEEDETAILS

Description: Code and/or name of adepartment or employee. Codepreferred.

C Comp Must use

CTA020-010 3413 Department or employeeidentification

Description: Internal identificationcode.

C an 1/17 Must use

CTA020-020 3412 Department or employee

Description: The department orperson within an organizational entity.

C an 1/35 Must use

Notes:Notes:CTA (OC)/COM:EM– this will contain the Insight fixed contact name and email address for Warranty Orders (to bepassed onto the vendor, if they only accept one email address)

Example:

CTA+OC+OC UK 

CTA (IC)/COM:TE–this will contain the End Customer Name or Company (depending on if we have a FAO in theorder) and a telephone number to contact in case of issues with delivery

Example:

CTA (OC)/COM:EM– this will contain the Insight fixed contact name and email address for Warranty Orders (to bepassed onto the vendor, if they only accept one email address)

Example:

CTA+OC+OC UK 

CTA (IC)/COM:TE–this will contain the End Customer Name or Company (depending on if we have a FAO in theorder) and a telephone number to contact in case of issues with delivery

Example:

Page 14: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

12

CTA+IC+Fitness FirstCTA+IC+Goods InwardsCTA+IC+Fitness FirstCTA+IC+Goods Inwards

Page 15: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

13

COM COMMUNICATIONCONTACT

Pos: 0240 Max: 1Conditional

Group: 5 Elements: 1

User Option (Usage): Must useFunction: To identify a communication number of a department or a person to whom communication should bedirected.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageCOM010 C076 COMMUNICATION CONTACT

Description: Communication numberof a department or employee in aspecified channel.

M Comp Must use

COM010-010 3148 Communication number

Description: The communicationnumber.

M an 1/512 Must use

COM010-020 3155 Communication number codequalifier

Description: Code qualifying thecommunication number.

M an 1/3 Must use

CodeList Summary (Total Codes: 34, Included: 2)Code NameEM Electronic mail

Description: Exchange of mail by electronic means.TE Telephone

Description: Voice/data transmission by telephone.

Notes:Notes:CTA (IC)/COM:TE– this will contain the End Customer Name or Company (depending on if we have a FAO in theorder) and a telephone number to contact in case of issues with delivery Example: COM+123123123:TE CTA (OC)/COM:EM– this will contain  the End User Company Name and email address for Warranty Orders (to bepassed onto the vendor ONLY if they only accept more than one email address) Example: [email protected]:EM

CTA (IC)/COM:TE– this will contain the End Customer Name or Company (depending on if we have a FAO in theorder) and a telephone number to contact in case of issues with delivery Example: COM+123123123:TE CTA (OC)/COM:EM– this will contain  the End User Company Name and email address for Warranty Orders (to bepassed onto the vendor ONLY if they only accept more than one email address) Example: [email protected]:EM

Page 16: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

14

CUX CURRENCIES Pos: 0300 Max: 1Mandatory

Group: 7 Elements: 1

User Option (Usage): Must useFunction: To specify currencies used in the transaction and relevant details for the rate of exchange.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageCUX010 C504 CURRENCY DETAILS

Description: The usage to which acurrency relates.

C Comp Must use

CUX010-010 6347 Currency details qualifier

Description: Specification of theusage to which the currency relates.

M an 1/3 Must use

CodeList Summary (Total Codes: 7, Included: 1)Code Name2 Reference currency

Description: The currency applicable to amounts stated. It may have to beconverted.

CUX010-020 6345 Currency identification code

Description: Code specifying amonetary unit.

C an 1/3 Must use

Notes:Notes:Example:.

CUX+2:GBP

Example:.

CUX+2:GBP

Page 17: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

15

TOD TERMS OF DELIVERY ORTRANSPORT

Pos: 0470 Max: 1Mandatory

Group: 12 Elements: 2

User Option (Usage): Must useFunction: To specify terms of delivery or transport.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageTOD010 4055 Terms of delivery or transport

function, coded

Description: Indication whether theterms relate to e.g. price conditions,delivery conditions, transportconditions, or a combination of these.

C an 1/3 Must use

CodeList Summary (Total Codes: 6, Included: 2)Code Name2 Despatch condition

Description: Condition requested by the customer under which the supplier shalldeliver: Extent of freight costs, means of transport.

6 Delivery conditionDescription: Specifies the conditions under which the goods must be deliveredto the consignee.

TOD030 C100 TERMS OF DELIVERY ORTRANSPORT

Description: Terms of delivery ortransport code from a specified source.

C Comp Must use

TOD030-010 4053 Delivery or transport termsdescription code

Description: Code specifying thedelivery or transport terms.

C an 1/3 Must use

CodeList Summary (Total Codes: 3, Included: 1)Code NameP02

Notes:Notes:TOD+6 is the fill/kill indicatorC Ship complete order, back order allowedO Ship complete order immediately or reject (order fill / kill)R Partial order acceptance allowed, complete lines must be rejected (line fill / kill)Blank backorders allowed, can ship in parts

Example:

TOD+6++O'

TOD+6 is the fill/kill indicatorC Ship complete order, back order allowedO Ship complete order immediately or reject (order fill / kill)R Partial order acceptance allowed, complete lines must be rejected (line fill / kill)Blank backorders allowed, can ship in parts

Example:

TOD+6++O'

Page 18: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

16

SCC SCHEDULING CONDITIONS Pos: 0630 Max: 1Mandatory

Group: 16 Elements: 1

User Option (Usage): Must useFunction: To specify scheduling conditions.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageSCC010 4017 Delivery plan commitment level code

Description: Code specifying the levelof commitment to a delivery plan.

M an 1/3 Must use

CodeList Summary (Total Codes: 24, Included: 1)Code Name10 Immediate

Description: Indicates that the scheduling information is for immediate execution.

Notes:Notes:This segment will always be sent, for warehouse and direct ship orders

Example:

SCC+10'

This segment will always be sent, for warehouse and direct ship orders

Example:

SCC+10'

Page 19: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

17

LIN LINE ITEM Pos: 1040 Max: 1Mandatory

Group: 28 Elements: 2

User Option (Usage): Must useFunction: To identify a line item and configuration.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageLIN010 1082 Line item number

Description: Serial numberdesignating each separate item withina series of articles.

C an 1/6 Must use

LIN030 C212 ITEM NUMBER IDENTIFICATION

Description: Goods identification for aspecified source.

C Comp Must use

LIN030-010 7140 Item number

Description: A number allocated to agroup or item.

C an 1/35 Must use

LIN030-020 7143 Item type identification code

Description: Code specifying an itemcode.

C an 1/3 Must use

CodeList Summary (Total Codes: 100, Included: 1)Code NameVN Vendor item number

Description: Reference number assigned by a vendor/seller identifying aproduct/service/article.

Notes:Notes:LIN segment contains the Insight PO Line Number, and your Part Number (converted to uppercase). As our linenumber is sent here, we will not be sending a RFF+LI segment.

Example:LIN+1++1632449:VN

LIN segment contains the Insight PO Line Number, and your Part Number (converted to uppercase). As our linenumber is sent here, we will not be sending a RFF+LI segment.

Example:LIN+1++1632449:VN

Page 20: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

18

PIA ADDITIONAL PRODUCT ID Pos: 1050 Max: 25Conditional

Group: 28 Elements: 3

User Option (Usage): Must useFunction: To specify additional or substitutional item identification codes.

Element Summary: Ref Tag Element Name Status Type Min/Max UsagePIA010 4347 Product id. function qualifier

Description: Indication of the functionof the product code.

M an 1/3 Must use

CodeList Summary (Total Codes: 12, Included: 1)Code Name1 Additional identification

Description: Information which specifies and qualifies product identifications.

PIA020 C212 ITEM NUMBER IDENTIFICATION

Description: Goods identification for aspecified source.

M Comp Must use

PIA020-010 7140 Item number

Description: A number allocated to agroup or item.

C an 1/35 Must use

PIA020-020 7143 Item type identification code

Description: Code specifying an itemcode.

C an 1/3 Must use

CodeList Summary (Total Codes: 100, Included: 1)Code NameBP Buyer's part number

Description: Reference number assigned by the buyer to identify an article.

PIA030 C212 ITEM NUMBER IDENTIFICATION

Description: Goods identification for aspecified source.

C Comp Must use

PIA030-010 7140 Item number

Description: A number allocated to agroup or item.

C an 1/35 Must use

PIA030-020 7143 Item type identification code

Description: Code specifying an itemcode.

C an 1/3 Must use

CodeList Summary (Total Codes: 100, Included: 1)Code NameMF Manufacturer's (producer's) article number

Description: The number given to an article by its manufacturer.

Page 21: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

19

Notes:Notes:Example:

PIA+1+0000432672:BP+KVR667D2D8F5/2G:MF'

Example:

PIA+1+0000432672:BP+KVR667D2D8F5/2G:MF'

Page 22: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

20

IMD ITEM DESCRIPTION Pos: 1060 Max: 99Conditional

Group: 28 Elements: 1

User Option (Usage): Must useFunction: To describe an item in either an industry or free format.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageIMD030 C273 ITEM DESCRIPTION

Description: Description of an item.

C Comp Must use

IMD030-040 7008 Item description

Description: Plain languagedescription of articles or products.

C an 1/256 Must use

IMD030-050 7008 Item description

Description: Plain languagedescription of articles or products.

C an 1/256 Must use

Notes:Notes:IMD segment contains the item description stored in our ERP

Example:IMD+++:::HP Promo USB Standard Keyboard

IMD segment contains the item description stored in our ERP

Example:IMD+++:::HP Promo USB Standard Keyboard

Page 23: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

21

QTY QUANTITY Pos: 1080 Max: 99Conditional

Group: 28 Elements: 1

User Option (Usage): Must useFunction: To specify a pertinent quantity.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageQTY010 C186 QUANTITY DETAILS

Description: Quantity information in atransaction, qualified when relevant.

M Comp Must use

QTY010-010 6063 Quantity type code qualifier

Description: Code qualifying the typeof quantity.

M an 1/3 Must use

CodeList Summary (Total Codes: 412, Included: 1)Code Name21 Ordered quantity

Description: The quantity which has been ordered.

QTY010-020 6060 Quantity

Description: Alphanumericrepresentation of a quantity.

M an 1/35 Must use

QTY010-030 6411 Measurement unit code

Description: Code specifying the unitof measurement.

C an 1/3 Must use

Notes: 1. QUANTITY IS A MAXIMUM LENGTH OF 15 NUMERIC CHARACTERS. QUANTITY MUST BE WHOLE

NUMBERS, NO DECIMALS.

Notes:Notes:QTY segment contains the ordered quantity of the product

Example:QTY+21:1:EA

QTY segment contains the ordered quantity of the product

Example:QTY+21:1:EA

Page 24: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

22

DTM DATE/TIME/PERIOD Pos: 1110 Max: 35Conditional

Group: 28 Elements: 1

User Option (Usage): Must useFunction: To specify date, and/or time, or period.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageDTM010 C507 DATE/TIME/PERIOD

Description: Date and/or time, orperiod relevant to the specifieddate/time/period type.

M Comp Must use

DTM010-010 2005 Date/time/period function codequalifier

Description: Code giving specificmeaning to a date, time or period.

M an 1/3 Must use

CodeList Summary (Total Codes: 697, Included: 2)Code Name2 Delivery date/time, requested

Description: Date on which buyer requests goods to be delivered.10 Shipment date/time, requested

Description: Date on which goods should be shipped or despatched by thesupplier.

DTM010-020 2380 Date/time/period value

Description: The value of a date, adate and time, a time or of a period in aspecified representation.

C an 1/35 Must use

DTM010-030 2379 Date/time/period format code

Description: Code specifying therepresentation of a date, time or period.

C an 1/3 Must use

CodeList Summary (Total Codes: 74, Included: 1)Code Name102 CCYYMMDD

Description: Calendar date: C = Century ; Y = Year ; M = Month ; D = Day.

Notes:Notes:DTM segment - requested ship date is the qualifier but the actual date sent here would be a requested deliverydate.

format CCYYMMDD

Example:DTM+10:20120420:102

DTM segment - requested ship date is the qualifier but the actual date sent here would be a requested deliverydate.

format CCYYMMDD

Example:DTM+10:20120420:102

Page 25: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

23

PRI PRICE DETAILS Pos: 1320 Max: 1Mandatory

Group: 32 Elements: 1

User Option (Usage): Must useFunction: To specify price information.

Element Summary: Ref Tag Element Name Status Type Min/Max UsagePRI010 C509 PRICE INFORMATION

Description: Identification of pricetype, price and related details.

C Comp Must use

PRI010-010 5125 Price qualifier

Description: Identification of a type ofprice.

M an 1/3 Must use

CodeList Summary (Total Codes: 10, Included: 1)Code NameCAL Calculation price

Description: The price stated is the price for the calculation of the line itemamount.

PRI010-020 5118 Price

Description: The monetary valueassociated with a purchase or sale ofan article, product or service.

C n 1/15 Must use

Notes:Notes:PRI segment contains the price provided in your latest price file for this product. If this is outside of the agreedtolerance, we would expect our order to be rejected in line with the fill/kill flag i.e. if Partial ship is allowed, then wewould just expect the affected line rejected in a multiple line order

Example:PRI+CAL:8.55

PRI segment contains the price provided in your latest price file for this product. If this is outside of the agreedtolerance, we would expect our order to be rejected in line with the fill/kill flag i.e. if Partial ship is allowed, then wewould just expect the affected line rejected in a multiple line order

Example:PRI+CAL:8.55

Page 26: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

24

UNS SECTION CONTROL Pos: 2320 Max: 1Mandatory

Group: N/A Elements: 1

User Option (Usage): Must useFunction: To separate header, detail and summary sections of a message.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageUNS010 0081 Section identification

Description: Identification of theseparation of sections of a message.

M a 1/1 Must use

CodeList Summary (Total Codes: 2, Included: 1)Code NameS Detail/summary section separation

Description: To qualify the segment UNS, when separating the detail from thesummary section of a message.

Notes: 1. To be used by message designers only when required to avoid ambiguities.

Notes:Notes:Always present Example: UNS+S'

Always present Example: UNS+S'

Page 27: ORDERS Purchase order message - Insight Web Servers.nsit.com/.../en_GB/manage/edi/edifact-purchase-order-message.pdf · ORDERS Purchase order message ... Purchase order message -

Purchase order message - ORDERS

25

UNT MESSAGE TRAILER Pos: 2390 Max: 1Mandatory

Group: N/A Elements: 2

User Option (Usage): Must useFunction: To end and check the completeness of a message.

Element Summary: Ref Tag Element Name Status Type Min/Max UsageUNT010 0074 Number of segments in a message

Description: The number of segmentsin a message body, plus the messageheader segment and message trailersegment.

M n 1/10 Must use

UNT020 0062 Message reference number

Description: Unique messagereference assigned by the sender.

M an 1/14 Must use

Notes: 1. 0062, the value shall be identical to the value in 0062 in the corresponding UNH segment.

Notes:Notes:UNT+number segments UNH to UNT inclusive+message number in interchange

Example:

UNT+27+50'

UNT+number segments UNH to UNT inclusive+message number in interchange

Example:

UNT+27+50'