Freightliner LLC Paragon Inbound 855 Purchase Order Acknowledgment

Transcription

1 Freightliner LLC Paragon Inbound 855 Purchase Order Acknowledgment VERSION: ANSI ASC X DRAFT Created: September 21, 2000 Modified: May 18, 2006 IB855PAR (004010) 1 May 18, 2006

2 This page intentionally left blank IB855PAR (004010) 2 May 18, 2006

3 855 Purchase Order Acknowledgment Functional Group ID=PR Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership. Notes: Purpose: To acknowledge the receipt of a Freightliner purchase order transaction (850). This transaction will echo the information received within the purchase order. It will also indicate how and when the supplier plans to fill each line item. This transaction also allows the supplier to modify ship quantities and dates but does not allow supplies to split scheduled ship dates. Contents/Organization: An EDI 855 transmission (ISA through IEA segment) will consist of multiple transaction sets, and contain only one purchase order number per transaction set (ST through SE segment). Transmission Frequency: The purchase order acknowledgment must be transmitted within 2 working days upon receipt of a Freightliner purchase order. Currently, Freightliner Aftermarket retrieves these documents multiple times daily. Error Handling Each 855 transaction received by Freightliner will be edited for conformance to requirements as described in this section of the manual. Errors will be reported to the Freightliner Aftermarket Material Planner and EDI Coordinator if segments/elements required are missing or element values are invalid. Here are some common errors found in an Aftermarket 855: 1. Invalid Item Number. The Item Number in a PO1 or ACK segment was not found on Freightliner's database; this is a hard error which prevents an acknowledgment record from being created for the item on Freightliner's Purchasing System. 2. Invalid Purchase Order/Line Number. The Purchase Order (P.O.) and/or Line Number in a PO1 or ACK segment was not found on Freightliner's database or was found but not associated with the supplier. This is a hard error which prevents an acknowledgment record from being created for the item. 3. Invalid Ship-to Location Code. The Ship-to Location Code in the N1*ST segment is not valid this is a hard error IB855PAR (004010) 3 May 18, 2006

4 which prevents acknowledgment records from being created for all item(s) in the transaction. If one or more of the above errors (among others) are detected in an 855 by Freightliner's system, the supplier will be notified via an 824 Application Advice transaction. The supplier will then be advised of the error condition(s) with an expectation that they will not be repeated in subsequent transmissions; corrective action may be requested as well, e.g. retransmit the 855 with corrected values. IMPORTANT NOTE(S): 1. Only one ACK segment per PO1 segment. 2. Date changes should be reflected in the SCH09. Any date changes listed in the ACK05 will not be recognized. 3. The estimated ship date in SCH09 will reflect the date that all quantities of the purchase order line will have completed shipment. 4. Quantity changes should be reflected in the SCH01. Example: ST*855* BAK*00*AC* * N1*ST**92*07A. N1*SU**92*CUM1. PO1*10*51*EA*2.23**BP*CUM ACK*DR*51*EA. SCH*51*EA***010* **139* PO1*20*3*EA*5.60**BP*CUM ACK*IA*3*EA. SCH*1*EA***010* **139* SCH*2*EA***010* **139* PO1*30*17*EA*15.49**BP*A ACK*IR*0*EA. SCH*0*EA***010* PO1*40*11*EA*101.23**BP*SP X. ACK*IQ*11*EA. SCH*12*EA***010* **139* CTT*4*82. SE*14* Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 ST Transaction Set Header M 1 M 020 BAK Beginning Segment for Purchase Order M 1 Acknowledgm ent LOOP ID - N1 200 M 300 N1 Name M 1 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - PO IB855PAR (004010) 4 May 18, 2006

5 M 010 PO1 Baseline Item Data M 1 n1 LOOP ID - ACK 1 M 270 ACK Line Item Acknowledgment M 1 LOOP ID - SCH 1 M 310 SCH Line Item Schedule M 1 n2 Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - CTT CTT Transaction Totals O 1 n3 M 030 SE Transaction Set Trailer M 1 Transaction Set Notes 1. PO102 is required. 2. The SCH segment is used to specify various quantities of items ordered that are to be scheduled. When this segment is used the unit of measurement code (SCH02) should always be identical to the unit of measurement code in the associated PO1 segment (PO103) and the sum of values of quantity (SCH01) should always equal the quantity ordered (PO102) in the PO1 segment. 3. The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment. IB855PAR (004010) 5 May 18, 2006

6 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Purpose: To indicate the start of a transaction set and to assign a control number M ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 855 Purchase Order Acknowledgment M ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set IB855PAR (004010) 6 May 18, 2006

7 Segment: BAK Beginning Segment for Purchase Order Acknowledgment Position: 020 Loop: Level: Heading Purpose: To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates M BAK Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set 00 Original 05 Replace M BAK Acknowledgment Type M ID 2/2 Code specifying the type of acknowledgment AC AD RJ Acknowledge - With Detail and Change Acknowledge With Detail and No Change Rejected With Detail M BAK Purchase Order Number M AN 1/22 Identifying number for Purchase Order assigned by the purchaser M BAK Date M DT 8/8 Date expressed as CCYYMMDD IB855PAR (004010) 7 May 18, 2006

8 Segment: N1 Name Position: 300 Loop: N1 Mandatory Level: Heading Purpose: To identify a party by type of organization, name, and code M N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual ST Ship To SU Supplier/Manufacturer M N Identification Code Qualifier M ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer or Buyer's Agent M N Identification Code M AN 2/80 Code identifying a party or other code IB855PAR (004010) 8 May 18, 2006

9 Segment: PO1 Baseline Item Data Position: 010 Loop: PO1 Mandatory Level: Detail Purpose: To specify basic and most frequently used line item data M PO Assigned Identification M AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set Purchase order line number. M PO Quantity Ordered M R 1/15 Quantity ordered M PO Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken EA Each M PO Unit Price M R 1/17 Price per unit of product, service, commodity, etc. M PO Product/Service ID Qualifier M ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) BP Buyer's Part Number M PO Product/Service ID M AN 1/48 Identifying number for a product or service IB855PAR (004010) 9 May 18, 2006

10 Segment: ACK Line Item Acknowledgment Position: 270 Loop: ACK Mandatory Level: Detail Purpose: To acknowledge the ordered quantities and specify the ready date for a specific line item M ACK Line Item Status Code M ID 2/2 Code specifying the action taken by the seller on a line item requested by the buyer IA IC ID IQ IR DR Item Accepted Item Accepted Changes Made Item Deleted Item Accepted Quantity Changed Item Rejected Item Accepted Date Rescheduled ACK Quantity M R 1/15 Numeric value of quantity ACK Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken EA Each ACK Date/Time Qualifier O ID 3/3 Code specifying type of date or time, or both date and time 010 Requested Ship ACK Date X DT 8/8 Date expressed as CCYYMMDD ACK Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) BP Buyer's Part Number ACK Product/Service ID X AN 1/48 Identifying number for a product or service ACK Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) VP Buyer's Part Number ACK Product/Service ID X AN 1/48 Identifying number for a product or service IB855PAR (004010) 10 May 18, 2006

11 Segment: SCH Line Item Schedule Position: 310 Loop: SCH Mandatory Level: Detail Purpose: To specify the data for scheduling a specific line-item M SCH Quantity M R 1/15 Numeric value of quantity M SCH Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken EA Each M SCH Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 010 Requested Ship M SCH Date M DT 8/8 Date expressed as CCYYMMDD Direct ship orders this will be the order date M SCH Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 139 Estimated Ship Date M SCH Date M DT 8/8 Date expressed as CCYYMMDD IB855PAR (004010) 11 May 18, 2006

12 Segment: CTT Transaction Totals Position: 010 Loop: CTT Optional Level: Summary Usage: Optional Purpose: To transmit a hash total for a specific element in the transaction set M CTT Number of Line Items M N0 1/6 Total number of line items in the transaction set CTT Hash Total O R 1/10 Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element. Example: First occurrence of value being hashed..18 Second occurrence of value being hashed. 1.8 Third occurrence of value being hashed Fourth occurrence of value being hashed Hash total prior to truncation. 855 Hash total after truncation to three-digit field. IB855PAR (004010) 12 May 18, 2006

13 Segment: SE Transaction Set Trailer Position: 030 Loop: Level: Summary Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) M SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments M SE Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set IB855PAR (004010) 13 May 18, 2006