Oshkosh 860 Purchase Order Change Request - Buyer Initiated

Size: px
Start display at page:

Download "Oshkosh 860 Purchase Order Change Request - Buyer Initiated"

Transcription

1 Oshkosh 860 Purchase Order Change Request - Buyer Initiated AIAG X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated Version: 1.0 Final Company: Oshkosh Corporation Publication: 11/13/2015

2 Table of Contents 860 Purchase Order Change Request - Buyer Initiated.. <PH> ST Transaction Set Header.. <PH> BCH Beginning Segment for Purchase Order Change PER Administrative Communications Contact. <PH> <PH> N9 Loop Reference Identification... <PH> N9 Reference Identification.. <PH> DTM Date/Time Reference.. MSG Message Text... <PH> <PH> N1 Loop Name.. <PH> N1 Name. <PH> N2 Additional Name Information <PH> N3 Address Information.. <PH> N4 Geographic Location. <PH> POC Loop Line Item Change... POC Line Item Change.. <PH> <PH> PO4 Item Physical Details.. <PH> REF Reference Identification.. <PH> MSG Message Text... SCH Loop Line Item Schedule. SCH Line Item Schedule <PH> <PH> <PH> N9 Loop Reference Identification... <PH> N9 Reference Identification.. <PH> MSG Message Text <PH> 31 N1 Loop Name.. <PH> 32 N1 Name. <PH> 33 N2 Additional Name Information <PH> 35 N3 Address Information.. <PH> 36 N4 Geographic Location. <PH> 37 CTT Loop Transaction Totals. <PH> 38 CTT Transaction Totals <PH> 39 SE Transaction Set Trailer... <PH> 40 OSK_X12_860_4010 ECS.ecs i For internal use only

3 860 Purchase Order Change Request - Buyer Initiated Functional Group= PC Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Change Request - Buyer Initiated Transaction Set (860) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the information required for the customary and established business and industry practice relative to a purchase order change. This transaction can be used: (1) by a buyer to request a change to a previously submitted purchase order or (2) by a buyer to confirm acceptance of a purchase order change initiated by the seller or by mutual agreement of the two parties. Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage 010 ST Transaction Set Header M 1 Must use 020 BCH Beginning Segment for Purchase Order Change 060 PER Administrative Communications Contact LOOP ID - N M 1 Must use O 3 Used 285 N9 Reference Identification O 1 Used 287 DTM Date/Time Reference O >1 Used 290 MSG Message Text O 1000 Used LOOP ID - N N1 Name O 1 Used 310 N2 Additional Name Information O 2 Used 320 N3 Address Information O 2 Used 330 N4 Geographic Location O >1 Used Detail: Pos Id Segment Name Req Max Use Repeat Notes Usage LOOP ID - POC >1 010 POC Line Item Change O 1 Used 090 PO4 Item Physical Details O >1 Used 100 REF Reference Identification O >1 Used 292 MSG Message Text O >1 Used LOOP ID - SCH SCH Line Item Schedule O 1 Used LOOP ID - N N9 Reference Identification O 1 Used 330 MSG Message Text O 1000 Used LOOP ID - N N1 Name O 1 Used 350 N2 Additional Name Information O 2 Used 360 N3 Address Information O 2 Used OSK_X12_860_4010 ECS.ecs 1 For internal use only

4 Pos Id Segment Name Req Max Use Repeat Notes Usage 370 N4 Geographic Location O 1 Used Summary: Pos Id Segment Name Req Max Use Repeat Notes Usage LOOP ID - CTT 1 N3/010L 010 CTT Transaction Totals O 1 N3/010 Used 030 SE Transaction Set Trailer M 1 Must use Notes: 3/010L Number of line items (CTT01) is the accumulation of the number of POC segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (POC03) for each POC segment. 3/010 Number of line items (CTT01) is the accumulation of the number of POC segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (POC03) for each POC segment. OSK_X12_860_4010 ECS.ecs 2 For internal use only

5 ST Transaction Set Header Pos: 010 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must use Purpose: To indicate the start of a transaction set and to assign a control number ST Transaction Set Identifier Code M ID 3/3 Must use Description: Code uniquely identifying a Transaction Set CodeList Summary (Total Codes: 298, Included: 1) Code Name 860 Purchase Order Change Request - Buyer Initiated ST Transaction Set Control Number M AN 4/9 Must use Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). OSK_X12_860_4010 ECS.ecs 3 For internal use only

6 BCH Beginning Segment for Purchase Order Change Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 16 User Option (Usage): Must use Purpose: To indicate the beginning of the Purchase Order Change Transaction Set and transmit identifying numbers and dates BCH Transaction Set Purpose Code M ID 2/2 Must use Description: Code identifying purpose of transaction set CodeList Summary (Total Codes: 65, Included: 5) Code Name 00 Original 01 Cancellation 04 Change 05 Replace 06 Confirmation BCH02 92 Purchase Order Type Code M ID 2/2 Must use Description: Code specifying the type of Purchase Order CodeList Summary (Total Codes: 69, Included: 11) Code Name BE BK CF CP DS OS RL RO SA SP UE Blanket Order/Estimated Quantities (Not firm Commitment) Blanket Order (Quantity Firm) Confirmation Change to Purchase Order Dropship Special Order Release or Delivery Order Rush Order Stand-alone Order Sample Unit Exchange BCH Purchase Order Number M AN 1/22 Must use Description: Identifying number for Purchase Order assigned by the orderer/purchaser User Note 1: For a blanket PO, this will contain the blanket PO number For a Spot Buy PO, this will contain the complete PO/Release Number BCH Release Number O AN 1/30 Used Description: Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction User Note 1: For a Blanket PO, this will contain the Release number BCH Change Order Sequence Number M AN 1/8 Used OSK_X12_860_4010 ECS.ecs 4 For internal use only

7 Description: Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set BCH Date M DT 8/8 Must use Description: Date expressed as CCYYMMDD Semantics: 1. BCH06 is the date assigned by the purchaser to purchase order. 2. BCH09 is the seller's order number. 3. BCH10 is the date assigned by the sender to the acknowledgment. 4. BCH11 is the date of the purchase order change request. OSK_X12_860_4010 ECS.ecs 5 For internal use only

8 PER Administrative Communications Contact Pos: 060 Max: 3 Heading - Optional Loop: N/A Elements: 9 Purpose: To identify a person or office to whom administrative communications should be directed PER Contact Function Code M ID 2/2 Must use Description: Code identifying the major duty or responsibility of the person or group named All valid standard codes are used. (Total Codes: 230) PER02 93 Name O AN 1/60 Used Description: Free-form name PER Communication Number Qualifier X ID 2/2 Used Description: Code identifying the type of communication number CodeList Summary (Total Codes: 40, Included: 1) Code Name EM Electronic Mail PER Communication Number X AN 1/80 Used Description: Complete communications number including country or area code when applicable PER Communication Number Qualifier X ID 2/2 Used Description: Code identifying the type of communication number CodeList Summary (Total Codes: 40, Included: 1) Code Name TE Telephone PER Communication Number X AN 1/80 Used Syntax Rules: Description: Complete communications number including country or area code when applicable 1. P If either PER03 or PER04 is present, then the other is required. 2. P If either PER05 or PER06 is present, then the other is required. 3. P If either PER07 or PER08 is present, then the other is required. OSK_X12_860_4010 ECS.ecs 6 For internal use only

9 Loop Reference Identification Pos: 285 Repeat: 1000 Optional Loop: N9 Elements: N/A Purpose: To transmit identifying information as specified by the Reference Identification Qualifier Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 285 N9 Reference Identification O 1 Used 287 DTM Date/Time Reference O >1 Used 290 MSG Message Text O 1000 Used OSK_X12_860_4010 ECS.ecs 7 For internal use only

10 N9 Reference Identification Pos: 285 Max: 1 Heading - Optional Loop: N9 Elements: 7 Purpose: To transmit identifying information as specified by the Reference Identification Qualifier N Reference Identification Qualifier M ID 2/3 Must use Description: Code qualifying the Reference Identification All valid standard codes are used. (Total Codes: 1503) N Reference Identification X AN 1/30 Used Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Free-form Description X AN 1/45 Used Description: Free-form descriptive text N Date O DT 8/8 Used Description: Date expressed as CCYYMMDD N Time X TM 4/8 Used Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) N Time Code O ID 2/2 Used Description: Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow All valid standard codes are used. (Total Codes: 51) N907 C040 Reference Identifier O Comp Used Description: To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier N Reference Identification Qualifier M ID 2/3 Must use Description: Code qualifying the Reference Identification All valid standard codes are used. (Total Codes: 1503) N Reference Identification M AN 1/30 Must use Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Reference Identification Qualifier X ID 2/3 Used Description: Code qualifying the Reference Identification All valid standard codes are used. (Total Codes: 1503) OSK_X12_860_4010 ECS.ecs 8 For internal use only

11 N Reference Identification X AN 1/30 Used Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Reference Identification Qualifier X ID 2/3 Used Description: Code qualifying the Reference Identification All valid standard codes are used. (Total Codes: 1503) N Reference Identification X AN 1/30 Used Syntax Rules: Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 1. R At least one of N902 or N903 is required. 2. C If N906 is present, then N905 is required. Semantics: 1. N906 reflects the time zone which the time reflects. 2. N907 contains data relating to the value cited in N902. OSK_X12_860_4010 ECS.ecs 9 For internal use only

12 DTM Date/Time Reference Pos: 287 Max: >1 Heading - Optional Loop: N9 Elements: 6 Purpose: To specify pertinent dates and times DTM Date/Time Qualifier M ID 3/3 Must use Description: Code specifying type of date or time, or both date and time All valid standard codes are used. (Total Codes: 1112) DTM Date X DT 8/8 Used Description: Date expressed as CCYYMMDD DTM Time X TM 4/8 Used Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) DTM Time Code O ID 2/2 Used Description: Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow All valid standard codes are used. (Total Codes: 51) DTM Date Time Period Format Qualifier X ID 2/3 Used Description: Code indicating the date format, time format, or date and time format All valid standard codes are used. (Total Codes: 39) DTM Date Time Period X AN 1/35 Used Syntax Rules: Description: Expression of a date, a time, or range of dates, times or dates and times 1. R At least one of DTM02, DTM03 or DTM05 is required. 2. C If DTM04 is present, then DTM03 is required. 3. P If either DTM05 or DTM06 is present, then the other is required. OSK_X12_860_4010 ECS.ecs 10 For internal use only

13 MSG Message Text Pos: 290 Max: 1000 Heading - Optional Loop: N9 Elements: 3 Purpose: To provide a free-form format that allows the transmission of text information MSG Free-Form Message Text M AN 1/264 Must use Description: Free-form message text MSG Printer Carriage Control Code X ID 2/2 Used Description: A field to be used for the control of the line feed of the receiving printer All valid standard codes are used. (Total Codes: 7) MSG Number O N0 1/9 Used Description: A generic number Syntax Rules: 1. C If MSG03 is present, then MSG02 is required. Semantics: 1. MSG03 is the number of lines to advance before printing. Comments: 1. MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc. 2. If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required. OSK_X12_860_4010 ECS.ecs 11 For internal use only

14 Loop Name Pos: 300 Repeat: 200 Optional Loop: N1 Elements: N/A Purpose: To identify a party by type of organization, name, and code Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 300 N1 Name O 1 Used 310 N2 Additional Name Information O 2 Used 320 N3 Address Information O 2 Used 330 N4 Geographic Location O >1 Used OSK_X12_860_4010 ECS.ecs 12 For internal use only

15 N1 Name Pos: 300 Max: 1 Heading - Optional Loop: N1 Elements: 6 Purpose: To identify a party by type of organization, name, and code N Entity Identifier Code M ID 2/3 Must use Description: Code identifying an organizational entity, a physical location, property or an individual CodeList Summary (Total Codes: 1312, Included: 10) Code Name BT BY MA MI RE SE SF SP ST SU Bill-to-Party Buying Party (Purchaser) Party for whom Item is Ultimately Intended Planning Schedule/Material Release Issuer Party to receive commercial invoice remittance Selling Party Ship From Party filling Shipper's Order Ship To Supplier/Manufacturer N Name X AN 1/60 Used Description: Free-form name N Identification Code Qualifier X ID 1/2 Used Description: Code designating the system/method of code structure used for Identification Code (67) User Note 1: AIAG Recommends use of the DUNS Number, however, if no DUNS Number exists, or is unavailable, use code "92". CodeList Summary (Total Codes: 215, Included: 3) Code Name 1 D-U-N-S Number, Dun & Bradstreet 92 Assigned by Buyer or Buyer's Agent ZZ Mutually Defined N Identification Code X AN 2/80 Used Syntax Rules: Description: Code identifying a party or other code 1. R At least one of N102 or N103 is required. 2. P If either N103 or N104 is present, then the other is required. Comments: OSK_X12_860_4010 ECS.ecs 13 For internal use only

16 1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2. N105 and N106 further define the type of entity in N101. OSK_X12_860_4010 ECS.ecs 14 For internal use only

17 N2 Additional Name Information Pos: 310 Max: 2 Heading - Optional Loop: N1 Elements: 2 Purpose: To specify additional names or those longer than 35 characters in length N Name M AN 1/60 Must use Description: Free-form name N Name O AN 1/60 Used Description: Free-form name OSK_X12_860_4010 ECS.ecs 15 For internal use only

18 N3 Address Information Pos: 320 Max: 2 Heading - Optional Loop: N1 Elements: 2 Purpose: To specify the location of the named party N Address Information M AN 1/55 Must use Description: Address information N Address Information O AN 1/55 Used Description: Address information OSK_X12_860_4010 ECS.ecs 16 For internal use only

19 N4 Geographic Location Pos: 330 Max: >1 Heading - Optional Loop: N1 Elements: 6 Purpose: To specify the geographic place of the named party N City Name O AN 2/30 Used Description: Free-form text for city name N State or Province Code O ID 2/2 Used Description: Code (Standard State/Province) as defined by appropriate government agency N Postal Code O ID 3/15 Used Description: Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country Code O ID 2/3 Used Description: Code identifying the country N Location Qualifier X ID 1/2 Used Description: Code identifying type of location All valid standard codes are used. (Total Codes: 172) N Location Identifier O AN 1/30 Used Syntax Rules: Description: Code which identifies a specific location 1. C If N406 is present, then N405 is required. Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2. N402 is required only if city name (N401) is in the U.S. or Canada. OSK_X12_860_4010 ECS.ecs 17 For internal use only

20 Loop Line Item Change Pos: 010 Repeat: >1 Optional Loop: POC Elements: N/A Purpose: To specify changes to a line item Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 010 POC Line Item Change O 1 Used 090 PO4 Item Physical Details O >1 Used 100 REF Reference Identification O >1 Used 292 MSG Message Text O >1 Used 295 Loop SCH O 200 Used 320 Loop N9 O 1000 Used 340 Loop N1 O 200 Used OSK_X12_860_4010 ECS.ecs 18 For internal use only

21 POC Line Item Change Pos: 010 Max: 1 Detail - Optional Loop: POC Elements: 15 Purpose: To specify changes to a line item POC Assigned Identification M AN 1/20 Used Description: Alphanumeric characters assigned for differentiation within a transaction set User Note 1: Oshkosh will always send the PO Line number in this element. POC Change or Response Type Code M ID 2/2 Must use Description: Code specifying the type of change to the line item CodeList Summary (Total Codes: 29, Included: 9) Code Name AI DI MU NC PC PQ QD QI RS Add Additional Item(s) Delete Item(s) (Multiple) For Unit Price Quantity Reschedule Change Concurrent Item (No Change) Price Change Unit Price/Quantity Change Quantity Decrease Quantity Increase Reschedule POC Quantity Ordered O R 1/15 Used Description: Quantity ordered User Note 1: Quantity may equal zero POC Quantity Left to Receive X R 1/9 Used Description: Quantity left to receive as qualified by the unit of measure POC05 C001 Composite Unit of Measure X Comp Used Description: To identify a composite unit of measure(see Figures Appendix for examples of use) POC Unit or Basis for Measurement Code M ID 2/2 Must use Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken All valid standard codes are used. (Total Codes: 794) POC Unit Price X R 1/17 Used Description: Price per unit of product, service, commodity, etc. POC Basis of Unit Price Code O ID 2/2 Used Description: Code identifying the type of unit price for an item OSK_X12_860_4010 ECS.ecs 19 For internal use only

22 CodeList Summary (Total Codes: 91, Included: 9) Code Name AP CP CT NC NE NQ TC TE TM Advise Price Current Price (Subject to Change) Contract No Charge Not to Exceed No Quote Contract Price per Hundred Contract Price per Each Contract Price per Thousand POC Product/Service ID Qualifier X ID 2/2 Used Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) CodeList Summary (Total Codes: 477, Included: 6) Code Name BP CL DR DV PT VP Buyer's Part Number Color Drawing Revision Number Location Code Print or Drawing Vendor's (Seller's) Part Number POC Product/Service ID X AN 1/48 Used Description: Identifying number for a product or service User Note 1: POC10 through POC27 provide for 9 additional pairs of data elements 235 and 234 used in the same manner as POC08 and POC09 POC Product/Service ID Qualifier X ID 2/2 Used Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) All valid standard codes are used. (Total Codes: 477) POC Product/Service ID X AN 1/48 Used Description: Identifying number for a product or service POC Product/Service ID Qualifier X ID 2/2 Used Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) All valid standard codes are used. (Total Codes: 477) POC Product/Service ID X AN 1/48 Used Description: Identifying number for a product or service POC Product/Service ID Qualifier X ID 2/2 Used Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) All valid standard codes are used. (Total Codes: 477) OSK_X12_860_4010 ECS.ecs 20 For internal use only

23 POC Product/Service ID X AN 1/48 Used Description: Identifying number for a product or service Syntax Rules: 1. C If POC03 is present, then POC04 and POC05 are required. 2. C If POC07 is present, then POC06 is required. 3. P If either POC08 or POC09 is present, then the other is required. 4. P If either POC10 or POC11 is present, then the other is required. 5. P If either POC12 or POC13 is present, then the other is required. 6. P If either POC14 or POC15 is present, then the other is required. 7. P If either POC16 or POC17 is present, then the other is required. 8. P If either POC18 or POC19 is present, then the other is required. 9. P If either POC20 or POC21 is present, then the other is required. 10. P If either POC22 or POC23 is present, then the other is required. 11. P If either POC24 or POC25 is present, then the other is required. 12. P If either POC26 or POC27 is present, then the other is required. Semantics: 1. POC01 is the purchase order line item identification. OSK_X12_860_4010 ECS.ecs 21 For internal use only

24 PO4 Item Physical Details Pos: 090 Max: >1 Detail - Optional Loop: POC Elements: 1 Purpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item PO Pack O N0 1/6 Used Syntax Rules: Description: The number of inner containers, or number of eaches if there are no inner containers, per outer container 1. P If either PO402 or PO403 is present, then the other is required. 2. C If PO405 is present, then PO406 is required. 3. P If either PO406 or PO407 is present, then the other is required. 4. P If either PO408 or PO409 is present, then the other is required. 5. C If PO410 is present, then PO413 is required. 6. C If PO411 is present, then PO413 is required. 7. C If PO412 is present, then PO413 is required. 8. L If PO413 is present, then at least one of PO410, PO411 or PO412 is required. 9. C If PO417 is present, then PO416 is required. 10. C If PO418 is present, then PO404 is required. Semantics: 1. PO415 is used to indicate the relative layer of this package or range of packages within the layers of packaging. Relative Position 1 (value R1) is the innermost package. 2. PO416 is the package identifier or the beginning package identifier in a range of identifiers. 3. PO417 is the ending package identifier in a range of identifiers. 4. PO418 is the number of packages in this layer. Comments: 1. PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack (PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the carton contains Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ". 2. PO413 defines the unit of measure for PO410, PO411, and PO412. OSK_X12_860_4010 ECS.ecs 22 For internal use only

25 REF Reference Identification Pos: 100 Max: >1 Detail - Optional Loop: POC Elements: 4 Purpose: To specify identifying information REF Reference Identification Qualifier M ID 2/3 Must use Description: Code qualifying the Reference Identification CodeList Summary (Total Codes: 1503, Included: 1) Code Name RS Returnable Container Serial Number REF Reference Identification X AN 1/30 Used Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier REF Description X AN 1/80 Used Description: A free-form description to clarify the related data elements and their content REF04 C040 Reference Identifier O Comp Used Description: To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier REF Reference Identification Qualifier M ID 2/3 Must use Description: Code qualifying the Reference Identification CodeList Summary (Total Codes: 1503, Included: 1) Code Name ZZ Mutually Defined REF Reference Identification M AN 1/30 Must use Syntax Rules: Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 1. R At least one of REF02 or REF03 is required. Semantics: 1. REF04 contains data relating to the value cited in REF02. OSK_X12_860_4010 ECS.ecs 23 For internal use only

26 MSG Message Text Pos: 292 Max: >1 Detail - Optional Loop: POC Elements: 3 Purpose: To provide a free-form format that allows the transmission of text information MSG Free-Form Message Text M AN 1/264 Must use Description: Free-form message text MSG Printer Carriage Control Code X ID 2/2 Used Description: A field to be used for the control of the line feed of the receiving printer All valid standard codes are used. (Total Codes: 7) MSG Number O N0 1/9 Used Description: A generic number Syntax Rules: 1. C If MSG03 is present, then MSG02 is required. Semantics: 1. MSG03 is the number of lines to advance before printing. Comments: 1. MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc. 2. If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required. OSK_X12_860_4010 ECS.ecs 24 For internal use only

27 Loop Line Item Schedule Pos: 295 Repeat: 200 Optional Loop: SCH Elements: N/A Purpose: To specify the data for scheduling a specific line-item Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 295 SCH Line Item Schedule O 1 Used OSK_X12_860_4010 ECS.ecs 25 For internal use only

28 SCH Line Item Schedule Pos: 295 Max: 1 Detail - Optional Loop: SCH Elements: 12 Purpose: To specify the data for scheduling a specific line-item SCH Quantity M R 1/15 Must use Description: Numeric value of quantity SCH Unit or Basis for Measurement Code M ID 2/2 Must use Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken All valid standard codes are used. (Total Codes: 794) SCH03 98 Entity Identifier Code O ID 2/3 Used Description: Code identifying an organizational entity, a physical location, property or an individual CodeList Summary (Total Codes: 1312, Included: 1) Code Name ST Ship To SCH04 93 Name X AN 1/60 Used Description: Free-form name SCH Date/Time Qualifier M ID 3/3 Must use Description: Code specifying type of date or time, or both date and time CodeList Summary (Total Codes: 1112, Included: 2) Code Name 002 Delivery Requested 106 Required By SCH Date M DT 8/8 Must use Description: Date expressed as CCYYMMDD SCH Time O TM 4/8 Used Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) SCH Date/Time Qualifier X ID 3/3 Used Description: Code specifying type of date or time, or both date and time All valid standard codes are used. (Total Codes: 1112) SCH Date X DT 8/8 Used Description: Date expressed as CCYYMMDD OSK_X12_860_4010 ECS.ecs 26 For internal use only

29 SCH Time X TM 4/8 Used Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) SCH Request Reference Number O AN 1/45 Used Description: Reference number or RFQ number to use to identify a particular transaction set and query (additional reference number or description which can be used with contract number) SCH Assigned Identification M AN 1/20 Used Syntax Rules: Description: Alphanumeric characters assigned for differentiation within a transaction set User Note 1: Oshkosh will always require the Item Line number in this element. 1. C If SCH03 is present, then SCH04 is required. 2. L If SCH08 is present, then at least one of SCH09 or SCH10 is required. 3. C If SCH09 is present, then SCH08 is required. 4. C If SCH10 is present, then SCH08 is required. Semantics: 1. SCH12 is the schedule identification. Comments: 1. SCH05 specifies the interpretation to be used for SCH06 and SCH07. OSK_X12_860_4010 ECS.ecs 27 For internal use only

30 Loop Reference Identification Pos: 320 Repeat: 1000 Optional Loop: N9 Elements: N/A Purpose: To transmit identifying information as specified by the Reference Identification Qualifier Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 320 N9 Reference Identification O 1 Used 330 MSG Message Text O 1000 Used OSK_X12_860_4010 ECS.ecs 28 For internal use only

31 N9 Reference Identification Pos: 320 Max: 1 Detail - Optional Loop: N9 Elements: 7 Purpose: To transmit identifying information as specified by the Reference Identification Qualifier N Reference Identification Qualifier M ID 2/3 Must use Description: Code qualifying the Reference Identification All valid standard codes are used. (Total Codes: 1503) N Reference Identification X AN 1/30 Used Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Free-form Description X AN 1/45 Used Description: Free-form descriptive text N Date O DT 8/8 Used Description: Date expressed as CCYYMMDD N Time X TM 4/8 Used Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) N Time Code O ID 2/2 Used Description: Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow All valid standard codes are used. (Total Codes: 51) N907 C040 Reference Identifier O Comp Used Description: To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier N Reference Identification Qualifier M ID 2/3 Must use Description: Code qualifying the Reference Identification All valid standard codes are used. (Total Codes: 1503) N Reference Identification M AN 1/30 Must use Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Reference Identification Qualifier X ID 2/3 Used Description: Code qualifying the Reference Identification All valid standard codes are used. (Total Codes: 1503) OSK_X12_860_4010 ECS.ecs 29 For internal use only

32 N Reference Identification X AN 1/30 Used Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Reference Identification Qualifier X ID 2/3 Used Description: Code qualifying the Reference Identification All valid standard codes are used. (Total Codes: 1503) N Reference Identification X AN 1/30 Used Syntax Rules: Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 1. R At least one of N902 or N903 is required. 2. C If N906 is present, then N905 is required. Semantics: 1. N906 reflects the time zone which the time reflects. 2. N907 contains data relating to the value cited in N902. OSK_X12_860_4010 ECS.ecs 30 For internal use only

33 MSG Message Text Pos: 330 Max: 1000 Detail - Optional Loop: N9 Elements: 3 Purpose: To provide a free-form format that allows the transmission of text information MSG Free-Form Message Text M AN 1/264 Must use Description: Free-form message text MSG Printer Carriage Control Code X ID 2/2 Used Description: A field to be used for the control of the line feed of the receiving printer All valid standard codes are used. (Total Codes: 7) MSG Number O N0 1/9 Used Description: A generic number Syntax Rules: 1. C If MSG03 is present, then MSG02 is required. Semantics: 1. MSG03 is the number of lines to advance before printing. Comments: 1. MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc. 2. If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required. OSK_X12_860_4010 ECS.ecs 31 For internal use only

34 Loop Name Pos: 340 Repeat: 200 Optional Loop: N1 Elements: N/A Purpose: To identify a party by type of organization, name, and code Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 340 N1 Name O 1 Used 350 N2 Additional Name Information O 2 Used 360 N3 Address Information O 2 Used 370 N4 Geographic Location O 1 Used OSK_X12_860_4010 ECS.ecs 32 For internal use only

35 N1 Name Pos: 340 Max: 1 Detail - Optional Loop: N1 Elements: 6 Purpose: To identify a party by type of organization, name, and code N Entity Identifier Code M ID 2/3 Must use Description: Code identifying an organizational entity, a physical location, property or an individual CodeList Summary (Total Codes: 1312, Included: 8) Code Name 16 Plant BT BY MA SE SF ST SU Bill-to-Party Buying Party (Purchaser) Party for whom Item is Ultimately Intended Selling Party Ship From Ship To Supplier/Manufacturer N Name X AN 1/60 Used Description: Free-form name N Identification Code Qualifier X ID 1/2 Used Description: Code designating the system/method of code structure used for Identification Code (67) All valid standard codes are used. (Total Codes: 215) N Identification Code X AN 2/80 Used Description: Code identifying a party or other code N Entity Relationship Code O ID 2/2 Used Description: Code describing entity relationship All valid standard codes are used. (Total Codes: 96) N Entity Identifier Code O ID 2/3 Used Syntax Rules: Description: Code identifying an organizational entity, a physical location, property or an individual All valid standard codes are used. (Total Codes: 1312) 1. R At least one of N102 or N103 is required. 2. P If either N103 or N104 is present, then the other is required. Comments: OSK_X12_860_4010 ECS.ecs 33 For internal use only

36 1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2. N105 and N106 further define the type of entity in N101. OSK_X12_860_4010 ECS.ecs 34 For internal use only

37 N2 Additional Name Information Pos: 350 Max: 2 Detail - Optional Loop: N1 Elements: 2 Purpose: To specify additional names or those longer than 35 characters in length N Name M AN 1/60 Must use Description: Free-form name N Name O AN 1/60 Used Description: Free-form name OSK_X12_860_4010 ECS.ecs 35 For internal use only

38 N3 Address Information Pos: 360 Max: 2 Detail - Optional Loop: N1 Elements: 2 Purpose: To specify the location of the named party N Address Information M AN 1/55 Must use Description: Address information N Address Information O AN 1/55 Used Description: Address information OSK_X12_860_4010 ECS.ecs 36 For internal use only

39 N4 Geographic Location Pos: 370 Max: 1 Detail - Optional Loop: N1 Elements: 6 Purpose: To specify the geographic place of the named party N City Name O AN 2/30 Used Description: Free-form text for city name N State or Province Code O ID 2/2 Used Description: Code (Standard State/Province) as defined by appropriate government agency N Postal Code O ID 3/15 Used Description: Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country Code O ID 2/3 Used Description: Code identifying the country N Location Qualifier X ID 1/2 Used Description: Code identifying type of location All valid standard codes are used. (Total Codes: 172) N Location Identifier O AN 1/30 Used Syntax Rules: Description: Code which identifies a specific location 1. C If N406 is present, then N405 is required. Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2. N402 is required only if city name (N401) is in the U.S. or Canada. OSK_X12_860_4010 ECS.ecs 37 For internal use only

40 Loop Transaction Totals Pos: 010 Repeat: 1 Optional Loop: CTT Elements: N/A Purpose: To transmit a hash total for a specific element in the transaction set Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 010 CTT Transaction Totals O 1 Used OSK_X12_860_4010 ECS.ecs 38 For internal use only

41 CTT Transaction Totals Pos: 010 Max: 1 Summary - Optional Loop: CTT Elements: 7 Purpose: To transmit a hash total for a specific element in the transaction set CTT Number of Line Items M N0 1/6 Must use Description: Total number of line items in the transaction set Syntax Rules: 1. P If either CTT03 or CTT04 is present, then the other is required. 2. P If either CTT05 or CTT06 is present, then the other is required. Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness. OSK_X12_860_4010 ECS.ecs 39 For internal use only

42 SE Transaction Set Trailer Pos: 030 Max: 1 Summary - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must use 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) SE01 96 Number of Included Segments M N0 1/10 Must use Description: Total number of segments included in a transaction set including ST and SE segments SE Transaction Set Control Number M AN 4/9 Must use Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Comments: 1. SE is the last segment of each transaction set. OSK_X12_860_4010 ECS.ecs 40 For internal use only

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes:

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes: 850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes: Table of Contents 850 Purchase Order...1 ISA Interchange Control Header...3 GS Functional Group Header...5

More information

860 Purchase Order Change Request - Buyer Initiated

860 Purchase Order Change Request - Buyer Initiated 860 Purchase Order Change Request - Buyer Initiated X12/V4010/860 :860 Purchase Order Change Request - Buyer Initiated Company: General Mills Modified: 1/7/2016 Notes: Table of Contents 860 Purchase Order

More information

850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008

850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008 850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008 850 Purchase Order Functional Group=PO Purpose: This Draft Standard for Trial Use contains the format and establishes the data

More information

860 Purchase Order Change Request - Buyer Initiated

860 Purchase Order Change Request - Buyer Initiated 860 Purchase Order Change Request - Buyer Initiated X12/V4010/860 :860 Purchase Order Change Request - Buyer Initiated Company: General Mills Modified: 1/11/2018 Notes: Table of Contents 860 Purchase Order

More information

Oshkosh 855 Purchase Order Acknowledgment

Oshkosh 855 Purchase Order Acknowledgment Oshkosh 855 Purchase Order Acknowledgment AIAG X12/V4010/855: 855 Purchase Order Acknowledgment Version: 1.0 Final Company: Oshkosh Corporation Publication: 11/13/2015 Notes: Please Note: The EDI 855 with

More information

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

865 Purchase Order Change Acknowledgment/Request - Seller Initiated Purchase Order Change Acknowledgment/Request - Seller Initiated X12/V4010/ : Purchase Order Change Acknowledgment/Request - Seller Initiated Version: 1.1 Final Author: Advance Auto Parts Company: Advance

More information

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

865 Purchase Order Change Acknowledgment/Request - Seller Initiated 865 Purchase Order Change Acknowledgment/Request - Seller Initiated X12/V4010/865: 865 Purchase Order Change Acknowledgment/Request - Seller Initiated Version: 1.0 Final Company: Oshkosh Corporation Created:

More information

816 Organizational Relationships

816 Organizational Relationships 816 Organizational Relationships X12/V4010/816: 816 Organizational Relationships Version: 1.0 Final Company: Oshkosh Corporation Publication: 7/8/2015 Modified: 7/8/2015 Table of Contents 816 Organizational

More information

ANSI X (Purchase Order) Inbound (to Eclipse) Version 4010

ANSI X (Purchase Order) Inbound (to Eclipse) Version 4010 ANSI X12 850 (Purchase Order) Inbound (to Eclipse) Version 4010 Eclipse 850 4010 (Customer) 1 10/11/2012 850 Purchase Order Functional Group=PO Purpose: This Draft Standard for Trial Use contains the format

More information

RCI 855 Purchase Order Acknowledgment

RCI 855 Purchase Order Acknowledgment RCI 855 Purchase Order Acknowledgment X12/V4030/855 : 855 Purchase Order Acknowledgment Version: 1.0 Draft Company: DiCentral Publication: 8/18/2017 Notes Table of Contents 855 Purchase Order Acknowledgment.....................................................................................................

More information

HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 4010 IMPLEMENTATION GUIDE

HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 4010 IMPLEMENTATION GUIDE HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 400 IMPLEMENTATION GUIDE Purchase Order 850 Functional Group PO 400 This Draft Standard for Trial Use contains the format and establishes the data contents

More information

ANSI X (Advance Shipment Notification) Inbound (to Eclipse) Version 4010

ANSI X (Advance Shipment Notification) Inbound (to Eclipse) Version 4010 ANSI X12 856 (Advance Shipment Notification) Inbound (to Eclipse) Version 4010 Eclipse 856 4010 (Vendor) 1 10/12/2012 856 Ship Notice/Manifest Functional Group=SH Purpose: This Draft Standard for Trial

More information

ANSI X (Product Transfer and Resale Report) Outbound (from Eclipse) Version 4010

ANSI X (Product Transfer and Resale Report) Outbound (from Eclipse) Version 4010 ANSI X12 867 (Product Transfer and Resale Report) Outbound (from Eclipse) Version 4010 Eclipse 867 4010 (Vendor) 1 10/12/2012 867 Product Transfer and Resale Report Functional Group=PT Purpose: This Draft

More information

850 Purchase Order. Version: X12

850 Purchase Order. Version: X12 850 Purchase Order Version: 004010 X12 Company: DOT FOODS, INC. Publication: 5/18/2012 850 Purchase Order Functional Group= PO Purpose: This Draft Standard for Trial Use contains the format and establishes

More information

816 Organizational Relationships

816 Organizational Relationships 816 Organizational Relationships X12/V4010/816: 816 Organizational Relationships Version: 1.0 Final Company: Oshkosh Corporation Publication: 3/1/2013 Modified: 2/24/2013 2/24/2013 Oshkosh Corporation

More information

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

GovX Purchase Order. X12/V5010/850: 850 Purchase Order 850 Purchase Order X12/V5010/850: 850 Purchase Order Company: GovX.com 1 4/12/2013 Purchase Order - 850 10/16/2015 Added TD5 segment 1/7/2016 9/19/2018 Added new value UP in PO106 Added TD512 segment Table

More information

Purchase Order Change Request - Buyer Initiated

Purchase Order Change Request - Buyer Initiated 860 Purchase Order Change Request - Buyer Initiated Functional Group= PC Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Change Request

More information

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

GovX Purchase Order. X12/V5010/850: 850 Purchase Order 850 Purchase Order X12/V5010/850: 850 Purchase Order Company: GovX.com 1 4/12/2013 Purchase Order - 850 10/16/2015 Added TD5 segment 1/7/2016 Added new value UP in PO106 2 Table of Contents 850 Purchase

More information

BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 865 VERSION 4010 FROM SUPPLIER. Document version 1.5

BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 865 VERSION 4010 FROM SUPPLIER. Document version 1.5 BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 865 VERSION 4010 FROM SUPPLIER Document version 1.5 The following guide is intended to facilitate the user in implementing Electronic Data

More information

Inbound ANSI X Version 04010

Inbound ANSI X Version 04010 Inbound ANSI X12 850 Version 04010 For CLP License Ordering Version: ANSI X12 850 4010 Author: Adobe EDI Modified: 06/09/2010 CLP_X12_ANSI8504010_060910.ecs 1 For internal use only 850 Purchase Order Functional

More information

867 Bill Back itradenetwork OMS

867 Bill Back itradenetwork OMS 867 Bill Back itradenetwork OMS X12/V4010/867: 867 Product Transfer and Resale Report Version: 1.3 Final Company: itradenetwork Publication: 12/23/2013 Trading Partner: Current: 4/3/2015 Table of Contents

More information

850 Purchase Order X12/V4010/850 Version: 1.0 Company: JR Simplot Company Modified: 11/24/2015 Notes:

850 Purchase Order X12/V4010/850 Version: 1.0 Company: JR Simplot Company Modified: 11/24/2015 Notes: 850 Purchase Order X12/V4010/850 Version: 1.0 Company: JR Simplot Company Modified: 11/24/2015 Notes: edi@simplot.com Table of Contents 850 Purchase Order...........................................................................................................................

More information

860 Purchase Order Change Request (Buyer Initiated) X12 Version Version: 2.0

860 Purchase Order Change Request (Buyer Initiated) X12 Version Version: 2.0 860 Purchase Order Change Request (Buyer Initiated) X12 Version 4010 Version: 2.0 Author: Advance Auto Parts Company: Advance Auto Parts Publication: 02/08/2017 1/26/2017 Purchase Order Change Request

More information

EDI Guideline. Version: 2.2. X12/V4010/832 : 832 Price/Sales Catalog. Publication: 1/21/2019 Trading Partner: Quebec EDI Healthcare Program

EDI Guideline. Version: 2.2. X12/V4010/832 : 832 Price/Sales Catalog. Publication: 1/21/2019 Trading Partner: Quebec EDI Healthcare Program EDI Guideline X12/V4010/832 : 832 Price/Sales Catalog Version: 2.2 Author: InterTrade Publication: 1/21/2019 Trading Partner: Quebec EDI Healthcare Program Document Change Log Notes Version Date Previous

More information

867 Product Transfer and Resale Report Functional Group=PT

867 Product Transfer and Resale Report Functional Group=PT 867 Product Transfer and Resale Report Functional Group=PT This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Transfer and Resale Report Transaction

More information

846 Inventory Inquiry/Advice

846 Inventory Inquiry/Advice 846 Inventory Inquiry/Advice Status: Final Author: Margie Waggoner Publication: 06/17/2013 Notes: Table of Contents 846 Inventory Inquiry/Advice............................................................................................

More information

832 Price/Sales Catalog

832 Price/Sales Catalog 832 Price/Sales Catalog Status: Final Author: Margie Waggoner Publication: 09/25/2007 Notes: This transaction set is used to send information to fulfillment customers about Ingram Entertainmen Inc. products

More information

JR Simplot Corporate 810 Invoice

JR Simplot Corporate 810 Invoice JR Simplot Corporate 810 Invoice X12/V4010/810: 810 Invoice Version: 1.0 Company: JR Simplot Company Modified: 3/2/2018 Notes: edi@simplot.com Table of Contents 810 Invoice.......................................................................................................................................

More information

850 Purchase Order - v4030

850 Purchase Order - v4030 850 Purchase Order - v4030 X12/V4030/850 Version: 1.0 Final Author: Inovis Publication: April 1, 2008 PepBoys850_4030_FINAL.ecs 1 Ver 1.0 Revision History Date Version Revision Approved By April 1, 2008

More information

846 RAPID Inventory Inquiry/Advice Standard

846 RAPID Inventory Inquiry/Advice Standard 846 RAPID Inventory Inquiry/Advice Standard Functional Group ID=IB Introduction: This Standard contains the format and establishes the data contents of the Inventory Inquiry/Advice Transaction Set (846)

More information

855 Purchase Order Acknowledgment. United Natural Foods

855 Purchase Order Acknowledgment. United Natural Foods 855 Purchase Order Acknowledgment Company: United Natural Foods Table of Contents 855 Purchase Order Acknowledgment... 1 ST Transaction Set Header... 2 BAK Beginning Segment for Purchase Order Acknowledgment...

More information

ANSI X (Purchase Order Acknowledgment) Inbound (to Eclipse) Version 4010

ANSI X (Purchase Order Acknowledgment) Inbound (to Eclipse) Version 4010 ANSI X12 855 (Purchase Order Acknowledgment) Inbound (to Eclipse) Version 4010 Eclipse 855 4010 (Vendor) 1 10/12/2012 855 Purchase Order Acknowledgment Functional Group=PR Purpose: This Draft Standard

More information

875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005

875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005 875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005 DOT FOODS, INC. Distributor 875 Page 1 875 Grocery Products Purchase Order Functional Group=OG This Draft Standard

More information

Product Transfer and Resale Report - 867

Product Transfer and Resale Report - 867 867 Product Transfer and Resale Report - 4010 Version: 1.0 Author: Land O' Lakes, Inc. V4010 1 867 Product Transfer and Resale Report Functional Group=PT This Draft Standard for Trial Use contains the

More information

Inbound X Version 04010

Inbound X Version 04010 Inbound X12 850 Version 04010 For Value Incentive Plan (VIP) License Ordering Version: ANSI ASC X12 850 4010 Author: Adobe EDI Company: Adobe Systems Inc Modified: 8/31/2015 850 Purchase Order Functional

More information

Introduction: Heading: Detail: Summary: Functional Group ID=TX

Introduction: Heading: Detail: Summary: Functional Group ID=TX 864 Text Message Functional Group ID=TX Introduction: This Draft Standard for Trial Use contains the format and establishes the data content of the Text Message Transaction Set (864) for use within the

More information

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications EDI 850 Version 4010 ANSI X12 Purchase Order Specifications Coupa Software, Inc. 1855 S. Grant St. 5 th Floor San Mateo, CA 94402 www.coupa.com Contents Purchase Order Details 3 Introduction 3 File Format

More information

860 Purchase Order Change v.4 (4010) Hubbell to Supplier Outbound Transaction

860 Purchase Order Change v.4 (4010) Hubbell to Supplier Outbound Transaction 860 Purchase Order Change v.4 (4010) Hubbell to Supplier Outbound Transaction Functional Group ID=PC Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents

More information

870 Order Status Report

870 Order Status Report 870 Order Status Report X12/V4010/870: 870 Order Status Report Version: 2.1 Final Author: Insight Direct USA, Inc. Modified: 10/12/2006 870 Order Status Report Functional Group=RS This Draft Standard for

More information

JR Simplot Food Group Purchase Order Acknowledgment

JR Simplot Food Group Purchase Order Acknowledgment JR Simplot Food Group - 855 Purchase Order Acknowledgment UCS/V4010/855: 855 Purchase Order Acknowledgment Version: 1.0 Company: JR Simplot Company Publication: 6/1/2016 Notes: edi@simplot.com Table of

More information

850 Purchase Order. X12/V4010/850: 850 Purchase Order

850 Purchase Order. X12/V4010/850: 850 Purchase Order 850 Purchase Order X12/V4010/850: 850 Purchase Order Company: General Mills Modified: 1/11/2018 Notes: Production Orders for copack and warehousing partners. Table of Contents 850 Purchase Order............................................................................................................................

More information

844 Product Transfer Account

844 Product Transfer Account 844 Product Transfer Account Adjustment Functional Group=CF This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Transfer Account Adjustment Transaction

More information

870 Order Status Report

870 Order Status Report 870 Order Status Report Functional Group=RS This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status Report Transaction Set (870) for use within the context

More information

846 Inventory Inquiry/Advice

846 Inventory Inquiry/Advice 846 Inventory Inquiry/Advice X12/V5010/846: 846 Inventory Inquiry/Advice Company: Contact: GovX.com integrations@govx.com 846 Inventory Inquiry/Advice Functional Group=IB Purpose: This X12 Transaction

More information

ESIS. EDI Implementation Guide. Purchase Order Change X Version 4010 Release 8.0. EDI_Guide_Change_Order_X12_860_Version_4010_Release_8-0.

ESIS. EDI Implementation Guide. Purchase Order Change X Version 4010 Release 8.0. EDI_Guide_Change_Order_X12_860_Version_4010_Release_8-0. EDI Implementation Guide ESIS Purchase Order Change X12 860 Version 4010 Release 8.0 Page 1 of 37 EDI Implementation Support Information EDI Contact Name: ESIS, E-Commerce Provider of Raytheon EDI Contact

More information

JR Simplot Agribusiness Ship Notice/Manifest

JR Simplot Agribusiness Ship Notice/Manifest JR Simplot Agribusiness - 856 Ship Notice/Manifest X12/V4010/856: 856 Ship Notice/Manifest Version: 1.0 Company: JR Simplot Modified: 8/28/2018 Table of Contents 856 Ship Notice/Manifest.....................................................................................................................

More information

850 Purchase Order. X12/V4010/850 : 850 Purchase Order Version: 2.0 Final

850 Purchase Order. X12/V4010/850 : 850 Purchase Order Version: 2.0 Final 850 Purchase Order X12/V4010/850 : 850 Purchase Order Version: 2.0 Final Author: D&H Distributors Company: D&H Distributors Publication: 8/15/2016 Trading Partner: Modified: 8/12/2016 Notes EDI notes The

More information

855 Purchase Order Acknowledgment

855 Purchase Order Acknowledgment 855 Purchase Order Acknowledgment X12/V4010/855 : 855 Purchase Order Acknowledgment Version: 2.0 Final Author: EDI Department Company: D&H Distributors Publication: 8/26/2016 Modified: 8/25/2016 Notes

More information

Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS. 830 TRANSACTION SET MATERIAL RELEASE Version Revised November 18, 2009

Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS. 830 TRANSACTION SET MATERIAL RELEASE Version Revised November 18, 2009 Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS 830 TRANSACTION SET MATERIAL RELEASE Version 004010 Revised November 18, 2009 2 P a g e 830 Material Release Functional Group ID=PS Introduction:

More information

862 Shipping Schedule

862 Shipping Schedule AN AIAG IMPLEMENTATION GUIDELINE VERSION 004 RELEASE 010 862 862 Shipping Schedule PREFACE This is the AIAG s recommended usage for the 862 - Shipping Schedule for ASC X12 version release 004010. Prior

More information

850 Purchase Order

850 Purchase Order 850 Purchase Order - 4010 Version: 1.0 Author: Land O' Lakes Inc. V4010 1 850 Purchase Order Functional Group=PO This Draft Standard for Trial Use contains the format and establishes the data contents

More information

850 Purchase Order X12 Version Version: 2.0

850 Purchase Order X12 Version Version: 2.0 850 Purchase Order X12 Version 4010 Version: 2.0 Author: Advance Auto Parts Company: Advance Auto Parts Publication: 12/03/2016 Revision History Date Version Description Author 1/15/2013 NA Original publication

More information

Zappos EDI Guideline. X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated. Version: 1.0

Zappos EDI Guideline. X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated. Version: 1.0 Zappos EDI Guideline X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated Version: 1.0 Author: Zappos Created: 07/06/2011 Last updated: 01/15/2014 Electronic Data Interchange 860 Purchase

More information

Orchard Supply Hardware Direct to Consumer 850 Purchase Order

Orchard Supply Hardware Direct to Consumer 850 Purchase Order Orchard Supply Hardware Direct to Consumer 850 Purchase Order X12/V4010/850: 850 Purchase Order Author: Orchard Supply Hardware Trading Partner: Created: May 25, 2011 Modified: June 9, 2011 Notes: ISA/GS

More information

861 Receiving Advice/Acceptance Certificate

861 Receiving Advice/Acceptance Certificate 861 Receiving Advice/Acceptance Certificate X12/V4010/511 Version: 1.1 Publication: 01.24.2013 www.flextronics.com Version Number Version Date Description of Change Reason of Change Author Change Reference

More information

846 Inventory Inquiry/Advice. X12/V5010/846: 846 Inventory Inquiry/Advice

846 Inventory Inquiry/Advice. X12/V5010/846: 846 Inventory Inquiry/Advice 846 Inventory Inquiry/Advice X12/V5010/846: 846 Inventory Inquiry/Advice Author: SPS Commerce Company: Shoe Sensation Publication: 9/7/2016 846 Inventory Inquiry/Advice Functional Group= IB Purpose: This

More information

ANSI X12 version Receiving Advice/ Acceptance Certificate

ANSI X12 version Receiving Advice/ Acceptance Certificate ANSI X12 version 4010 861 Receiving Advice/ Acceptance Certificate VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 8/22/00 Trading Partner: All Partners 861 All Partners 4010 Inbound.rtf 1

More information

12/19/2017 Purchase Order Acknowledgment - 855

12/19/2017 Purchase Order Acknowledgment - 855 855 Purchase Order Acknowledgment Functional Group= PR Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction

More information

855 Purchase Order Acknowledgment

855 Purchase Order Acknowledgment 855 Purchase Order Acknowledgment X12/V4010/855: 855 Purchase Order Acknowledgment Version: 2.0 Final Author: Insight Direct USA, Inc. Modified: 01/17/2014 855 Purchase Order Acknowledgment Functional

More information

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

865 Purchase Order Change Acknowledgment/Request - Seller Initiated Changes 5/2011: SCH11 Schedule line identifier 865 Purchase Order Change Acknowledgment/Request - Seller Initiated Introduction: Functional Group ID=CA This standard provides for the format and establishes

More information

940 Warehouse Shipping Order

940 Warehouse Shipping Order 940 Warehouse Shipping Order X12/V4030/940: 940 Warehouse Shipping Order Version: 1.0 Author: Abbott Nutrition ebusiness Company: Abbott Nutrition Created: 03/21/2012 Current: 03/21/2012 Table of Contents

More information

879 - Price Information

879 - Price Information 879 - Price Information Author: DOT FOODS, INC. Publication: September 24, 2008 879 Price Information Functional Group=QG Purpose: This Draft Standard for Trial Use contains the format and establishes

More information

Baker & Taylor 850 EDI Specifications

Baker & Taylor 850 EDI Specifications Baker & Taylor 850 EDI Specifications Version: 1.4 Final Created: 07/31/2003 Notes: Implementation Guide for Vendors 850 Purchase Order Version 4010 850 Purchase Order Functional Group=PO This Draft Standard

More information

810 Invoice. Version: 1.0 Final. X12/V4010/810: 810 Invoice. Company: Baker & Taylor Modified: 10/26/2010 Notes:

810 Invoice. Version: 1.0 Final. X12/V4010/810: 810 Invoice. Company: Baker & Taylor Modified: 10/26/2010 Notes: 810 Invoice X12/V4010/810: 810 Invoice Version: 1.0 Final Author: Baker & Taylor Company: Baker & Taylor Modified: 10/26/2010 Notes: Table of Contents 810 Invoice... 1 ISA Interchange Control Header...

More information

830 - Material Release VERSION: 1.2

830 - Material Release VERSION: 1.2 830 - Material Release VERSION: 1.2 Dura, LLC March 24, 2011 830 Planning Schedule with Release Capability Functional Group=PS This standard contains the format and establishes the data contents of the

More information

855 Purchase Order Acknowledgement X12/V4010/855: 855 Purchase Order Acknowledgement Version: 1.1

855 Purchase Order Acknowledgement X12/V4010/855: 855 Purchase Order Acknowledgement Version: 1.1 855 Purchase Order Acknowledgement X12/V4010/855: 855 Purchase Order Acknowledgement Version: 1.1 1 CHANGE LOG Chg# Date Noted Description of Change Change By Version Num. 1 Original 1.0 2 9/1/2017 Updated

More information

CVS/Caremark. Implementation Guide. 810 DSD Invoice. Version X

CVS/Caremark. Implementation Guide. 810 DSD Invoice. Version X CVS/Caremark Implementation Guide 810 DSD Invoice Version X12-4010 810 Mapping Specifications v4010 i Table of Contents 810 Invoice... 1 ISA Interchange Control Header... 2 GS Functional Group Header...

More information

855 Purchase Order Acknowledgment

855 Purchase Order Acknowledgment Changes 9/2009: PO1 Segment is mandatory PO1 segment 02 position is mandatory Changes 5/2011: SCH11 Schedule line identifier 855 Purchase Order Acknowledgment Functional Group ID=PR Introduction: This

More information

849 Response to Product Transfer

849 Response to Product Transfer 849 Response to Product Transfer Account Adjustment Functional Group=CF This Draft Standard for Trial Use contains the format and establishes the data contents of the Response to Product Transfer Account

More information

LOOP ID - PO PO1 Baseline Item Data M 1 N2/ REF Reference Identification O >1

LOOP ID - PO PO1 Baseline Item Data M 1 N2/ REF Reference Identification O >1 850 Purchase Order Functional Group=PO This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of

More information

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct X12/V4010/832: 832 Price/Sales Catalog Version: 1.0 Final Author: Publication: Trading Partner: All Notes: Brand Technology Services Table of Contents

More information

846 Inventory Inquiry / Advice _Outbound

846 Inventory Inquiry / Advice _Outbound 846 Inventory Inquiry / Advice _Outbound 846 ANSI X12 004010 Version: 1.1 Publication: 02.09.2014 Version Version Date Description of Change Reason of Change Author Change Reference Number 1.0 09.02.2014

More information

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Company: JR Simplot Company Publication: 6/1/2016 Notes:

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Company: JR Simplot Company Publication: 6/1/2016 Notes: 850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Company: JR Simplot Company Publication: 6/1/2016 Notes: edi@simplot.com Table of Contents 850 Purchase Order............................................................................................................................

More information

810 Invoice. X12/V4010/810 : 810 Invoice Version: 2.0 Final

810 Invoice. X12/V4010/810 : 810 Invoice Version: 2.0 Final 810 Invoice X12/V4010/810 : 810 Invoice Version: 2.0 Final Author: D&H Distributors Company: D&H Distributors Publication: 8/15/2016 Modified: 8/12/2016 Notes EDI notes The EDI messages use UTF8/Unicode

More information

850 Purchase Order. X12/V4010/850: 850 Purchase Order

850 Purchase Order. X12/V4010/850: 850 Purchase Order 850 Purchase Order X12/V4010/850: 850 Purchase Order Author: Abbott Nutrition ebusiness Company: Abbott Nutrition Created: 02/14/2012 Current: 02/14/2012 Table of Contents 850 Purchase Order. BEG

More information

JR Simplot Food Group Grocery Products Purchase Order. UCS/V4010/875: 875 Grocery Products Purchase Order Version: 1.0

JR Simplot Food Group Grocery Products Purchase Order. UCS/V4010/875: 875 Grocery Products Purchase Order Version: 1.0 JR Simplot Food Group - 875 Grocery Products Purchase Order UCS/V4010/875: 875 Grocery Products Purchase Order Version: 1.0 Company: JR Simplot Company Modified: 9/4/2018 Table of Contents 875 Grocery

More information

850 Purchase Order. X12/V4010/850: 850 Purchase Order. Version: 2.5 Final

850 Purchase Order. X12/V4010/850: 850 Purchase Order. Version: 2.5 Final 850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 2.5 Final Author: Insight Direct USA, Inc. Modified: 07/24/2008 850 Purchase Order Functional Group=PO This Draft Standard for Trial Use contains

More information

824 Application Advice

824 Application Advice 824 Application Advice Functional Group ID=AG Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use

More information

HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE

HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE 1 Purchase Order Acknowledgement 855 4010 Functional Group PR This Draft Standard for Trial Use contains the

More information

Purchase Order Change Request. Transaction Set (860) (Inbound to TI)

Purchase Order Change Request. Transaction Set (860) (Inbound to TI) Purchase Order Change Request Transaction Set (860) (Inbound to TI) ANSI X12 Version Format: 3020 Date: December 15, 1994 Copyright 1994 Texas Instruments Inc. All Rights Reserved The information and/or

More information

846 Inventory Inquiry/Advice

846 Inventory Inquiry/Advice 846 Inventory Inquiry/Advice X12/V4010/846 : 846 Inventory Inquiry/Advice Version: 1.0 Final Author: EDI Department Company: D&H Distributing Publication: 01/23/2016 Created: 01/19/2016 Modified: 02/29/2016

More information

3. When the transaction set is accepted with data content change, the corrected data MUST be provided.

3. When the transaction set is accepted with data content change, the corrected data MUST be provided. 824 Application Advice Functional Group ID=AG Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use

More information

870 Order Status Report

870 Order Status Report 870 Order Status Report Introduction: Functional Group ID=RS This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status Report Transaction Set (870) for

More information

855 Purchase Order Acknowledgment

855 Purchase Order Acknowledgment 855 Purchase Order Acknowledgment Version: 004010 CNH_855v4010.ecs 1 Table of Contents 855 Purchase Order Acknowledgment... 4 ISA Interchange Control Header... 7 GS Functional Group Header... 9 ST Transaction

More information

855 Purchase Order Acknowledgement v Supplier to Hubbell Inbound Transaction

855 Purchase Order Acknowledgement v Supplier to Hubbell Inbound Transaction HUBBELL855_Inbound_V4 (004010) Septemember 15, 2016 855 Purchase Order Acknowledgement v. 4010 Supplier to Hubbell Inbound Transaction Introduction: Functional Group ID=PR This Draft Standard for Trial

More information

846 Inventory Inquiry/Advice

846 Inventory Inquiry/Advice 846 Inventory Inquiry/Advice UCS/V4010/846: 846 Inventory Inquiry/Advice Company: General Mills Modified: 1/11/2018 Notes: Daily Inventory Snapshot Table of Contents 846 Inventory Inquiry/Advice.................................................................................................................

More information

830 Planning Schedule with Release Capability

830 Planning Schedule with Release Capability AN AIAG IMPLEMENTATION GUIDELINE VERSION 004 RELEASE 010 830 830 Planning Schedule with Release Capability PREFACE This is the AIAG s recommended usage for the 830 - Planning Schedule with Release Capability

More information

Golfsmith 846 EDI Guidelines

Golfsmith 846 EDI Guidelines Golfsmith 846 EDI Guidelines X12/V4050/846: 846 Inventory Inquiry/Advice Author: SPS Commerce Trading Partner: Created: 10/19/2010 Modified: 04/19/2011 Notes: 846 Inventory Inquiry/Advice Functional Group=IB

More information

849 Response to Product Transfer Account Adjustment

849 Response to Product Transfer Account Adjustment 849 Response to Product Transfer Account Adjustment X12/V4010/849: 849 Response to Product Transfer Account Adjustment Company: Abbott Nutrition 849_4010_from_Abbott_Nutrition.ecs 1 Abbott Nutrition Table

More information

Transaction Set 849 Response to Product Transfer Account Adjustment

Transaction Set 849 Response to Product Transfer Account Adjustment The Global Network for B2B Integration in High Tech Industries Transaction Set 849 Response to Product Transfer Account Adjustment Functional Group ID = CF X12 Version 004 Release 010 December 2002 2 Revision

More information

824 Application Advice

824 Application Advice 824 Application Advice X12/V4010/824: 824 Application Advice Version: 1.0 Final Author: IBM Publication: Trading Partner: P2P Modified: 08/17/2006 Notes: Table of Contents 824 Application Advice.................................................................................................

More information

830W (R1) War Material Requirements 830 Planning Schedule with Release Capability

830W (R1) War Material Requirements 830 Planning Schedule with Release Capability 830 Planning Schedule with Release Capability Introduction: Functional Group ID=PS This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with

More information

An example of a paper copy Planning Schedules with Release Capability and its ASC X12 interpretation can be found at the back of this guideline.

An example of a paper copy Planning Schedules with Release Capability and its ASC X12 interpretation can be found at the back of this guideline. Introduction This guideline provides a description and technical layout of the data segments used when creating 3M s EDI Planning Schedules with Release Capability (Forecast) (ASC X12 transaction set 830)

More information

810 IBM Subset - Invoice To Customer - (004010)

810 IBM Subset - Invoice To Customer - (004010) 810 IBM Subset - Invoice To Customer - (004010) Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set

More information

NAPM RAIL INDUSTRY FORUM Application Advice IMPLEMENTATION GUIDELINE FOR EDI

NAPM RAIL INDUSTRY FORUM Application Advice IMPLEMENTATION GUIDELINE FOR EDI 824 Application Advice Functional Group=AG This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use within the context

More information

850 Purchase Order. Version: 1.0 Final. X12/V4010/850 : 850 Purchase Order. Advance Auto Parts

850 Purchase Order. Version: 1.0 Final. X12/V4010/850 : 850 Purchase Order. Advance Auto Parts 850 Purchase Order X12/V4010/850 : 850 Purchase Order Version: 1.0 Final Author: Advance Auto Parts Company: Advance Auto Parts Publication: 1/15/2013 Current: 10/10/2013 Table of Contents 850 Purchase

More information

810 Invoice Service Parts Version:

810 Invoice Service Parts Version: 810 Invoice Service Parts Version: 004010 CNH_810v4010_ServiceParts.ecs 1 Table of Contents 810 Invoice... 4 ISA Interchange Control Header... 7 GS Functional Group Header... 9 ST Transaction Set Header...

More information

ANSI X (Purchase Order Acknowledgment) Outbound (from Eclipse) Version 4010

ANSI X (Purchase Order Acknowledgment) Outbound (from Eclipse) Version 4010 ANSI X12 855 (Purchase Order Acknowledgment) Outbound (from Eclipse) Version 4010 Eclipse 855 4010 (Customer) 1 10/11/2012 855 Purchase Order Acknowledgment Functional Group=PR Purpose: This Draft Standard

More information

832 Price/Sales Catalog

832 Price/Sales Catalog 832 Price/Sales Catalog Functional Group ID=SC Transaction Layout: Heading: ARM Pos. Seg. Req. Loop Notes and Required No. ID Name Des. Max.Use Repeat Comments Required 010 ST Transaction Set Header M

More information

ANSI X (Advance Shipment Notification) Outbound (from Eclipse) Version 4010

ANSI X (Advance Shipment Notification) Outbound (from Eclipse) Version 4010 ANSI X12 856 (Advance Shipment Notification) Outbound (from Eclipse) Version 4010 Eclipse 856 4010 (Customer) 1 10/11/2012 856 Ship Notice/Manifest Functional Group=SH Purpose: This Draft Standard for

More information