IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS RAW STEEL ORDER STATUS REPORT (870) TRANSACTION SET
|
|
- Nelson Maurice Wilkinson
- 6 years ago
- Views:
Transcription
1 IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS RAW STEEL ORDER STATUS REPORT (870) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE
2 870 Order Status Report Functional Group ID=RS Introduction: This Draft Standard for Trial contains the format and establishes the data contents of the Order Status Report Transaction Set (870) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report on the current status of a requirement forecast, an entire purchase order, selected line items on a purchase order, selected products/services on a purchase order, or purchase orders for a specific customer in their entirety or on a selection basis. The transaction set can also be used to report on the current status of single or multiple requisitions. The report format allows for the inclusion of "reasons" relative to the status. This transaction set may also be used to update the supplier's scheduled shipment or delivery dates. This transaction set can result from either an inquiry or a prearranged schedule agreed to by the trading partners. Notes: This convention provides the format and establishes the data content of an Order Status Report transaction set (870). The Order Status Report transaction set provides the ability to report on the current status of an entire purchase order, selected line items on a purchase order, selected products/services on a purchase order, or purchase orders for a specific customer in their entirety or on a selective basis. The report format allows for the inclusion of 'reasons' relative to the status of the purchase order(s). This transaction set may also be used to update the supplier's scheduled shipment or delivery date(s). This transaction set will result from a prearranged schedule agreed to by the trading partners. FCA will use the (outbound) Order Status Report (870) to transmit the status of current releases (open, closed and cancelled) for that supplier or warehouse. This will replace a printed Order Status report that was provided to the supplier. The (electronic) Order Status Report should be used by the supplier or warehouse to ship against the oldest open order. The release number should be included in the ASN release number element (PRF02). FCA will transmit the 870 Order Status Report six days a week, Monday through Saturday History of Change: 10/07/2010: Name change from DaimlerChrysler to Chrysler Updated Address 04/23/2015: Name Change To FCA US Heading: Page Pos. Seg. Base r Loop Notes and No. No. ID Name Guide Status Max. Repeat Comments 04/23/2015 V/R FCA US
3 5 010 ST Transaction Set Header M M BSR Beginning Segment for Order Status Report M M NTE Note/Special Instruction O Not REF Reference Numbers O Not TD3 Carrier Details (Equipment) O Not TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both) 044 TD5 Carrier Details (Routing Sequence/Transit Time) O Not 1 O Not 1 LOOP ID - N N1 Name O N2 Additional Name Information O Not N3 Address Information O Not N4 Geographic Location O Not REF Reference Numbers O Not PER Administrative Communications Contact O Not PWK Paperwork O Not DTM Date/Time/Period O Not 10 LOOP ID - LM LM Code Source Information O Not LQ Industry Code M Not 100 Detail: Page Pos. Seg. Base r Loop Notes and No. No. ID Name Guide Status Max. Repeat Comments LOOP ID - HL HL Hierarchical Level M M PRF Purchase Order Reference O Not 1 LOOP ID - ISR ISR Item Status Report O Not PID Product/Item Description O Not QTY Quantity O Not REF Reference Numbers O Not PER Administrative Communications Contact O Not DTM Date/Time/Period O Not CS Contract Summary O Not 3 n1 LOOP ID - N N1 Name O N2 Additional Name Information O Not N3 Address Information O Not N4 Geographic Location O Not REF Reference Numbers O Not PER Administrative Communications Contact O Not 3 04/23/2015 V/R FCA US
4 LOOP ID - LM LM Code Source Information O Not LQ Industry Code M Not 100 LOOP ID - PO PO1 Baseline Item Data O CUR Currency O Not SLN Subline Item Detail O Not PO3 Additional Item Detail O Not PID Product/Item Description O MEA Measurements O PKG Marking, Packaging, Loading O Not 25 LOOP ID - ISR ISR Item Status Report O PID Product/Item Description O Not QTY Quantity O DTM Date/Time/Period O N1 Name O N2 Additional Name Information O Not N3 Address Information O Not N4 Geographic Location O Not TD1 Carrier Details (Quantity and Weight) O Not TD5 Carrier Details (Routing Sequence/Transit Time) O Not TD3 Carrier Details (Equipment) O Not TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both) O Not REF Reference Numbers O SAC Service, Promotion, Allowance, or Charge Information O Not 25 LOOP ID - LM LM Code Source Information O Not LQ Industry Code M Not 100 LOOP ID - LX >1 340 LX Assigned Number O Not 1 n2 350 REF Reference Numbers O Not >1 360 N1 Name O Not DTM Date/Time/Period O Not 10 LOOP ID - LM LM Code Source Information O Not LQ Industry Code M Not 100 Summary: Page Pos. Seg. Base r Loop Notes and No. No. ID Name Guide Status Max. Repeat Comments CTT Transaction Totals O 1 n SE Transaction Set Trailer M M 1 04/23/2015 V/R FCA US
5 Transaction Set Notes 1. is limited to intra-organizational transactions. 2. The LX loop conveys serial number, lot number, and inventory data. 3. The number of line items (CTT01) is the accumulation of the number of HL segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment. 04/23/2015 V/R FCA US
6 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max : 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Comments: Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes ST Transaction Set Identifier Code M ID 3/3 M Code uniquely identifying a Transaction Set 870 X12.23 Order Status Report ST Transaction Set Control Number M AN 4/9 M Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 04/23/2015 V/R FCA US
7 Segment: BSR Beginning Segment for Order Status Report Position: 020 Loop: Level: Heading Usage: Mandatory Max : 1 Purpose: To indicate the beginning of an Order Status Report. Syntax Notes: Semantic Notes: 1 BSR03 indicates a status report document number assigned by the sender. 2 BSR04 indicates the date of this report from the sender. 3 BSR07 indicates the time of this report from the sender. 4 BSR08 indicates a status report document number assigned by the inquirer. 5 BSR09 indicates the date this report was requested from the sender by the inquirer. 6 BSR10 indicates the time this report was requested from the sender by the inquirer. Comments: Notes: This segment is used to uniquely identify this report from others that are transmitted during a year. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes BSR Status Report Code M ID 1/2 M Code indicating the reason for sending the report 2 Prearranged Schedule or Agreement BSR Order/Item Code M ID 1/2 M ID 2/2 Code identifying a group of orders and items PP Selected Orders - Selected Items BSR Reference Number M AN 1/30 M Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. A unique reference number for this transaction set that is not repeated within a 12 month period. BSR Date M DT 6/6 M Date (YYMMDD) The creation date of the report. BSR Product/Date Code O ID 1/2 Not BSR Location Code O ID 1/2 Not BSR Time O TM 4/8 Not BSR Reference Number O AN 1/30 Not 04/23/2015 V/R FCA US
8 BSR Date O DT 6/6 Not BSR Time O TM 4/8 Not BSR Transaction Set Purpose Code O ID 2/2 Not BSR Action Code O ID 1/2 Not 04/23/2015 V/R FCA US
9 Segment: N1 Name Position: 050 Loop: N1 Optional Level: Heading Usage: Optional Max : 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 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. Notes: Two N1 segments are always required in the Heading level: 'SU' for the FCA assigned supplier code for the released supplier. 'PK' for the FCA supplier or warehouse who is to receive the report. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes N Entity Identifier Code M ID 2/2 M Code identifying an organizational entity, a physical location, or an individual PK Party to Receive Copy SU Supplier/Manufacturer N Name X AN 1/35 Not N Identification Code Qualifier X ID 1/2 Must ID 2/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer or Buyer's Agent N Identification Code X AN 2/17 Must AN 5/7 Code identifying a party or other code If N101 = SU, the FCA assigned supplier code for the release supplier; If N101 = PK, the FCA assigned supplier code for the supplier or warehouse who receives the report; N Entity Relationship Code O ID 2/2 Not N Entity Identifier Code O ID 2/2 Not 04/23/2015 V/R FCA US
10 Segment: HL Hierarchical Level Position: 010 Loop: HL Mandatory Level: Detail Usage: Mandatory Max : 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments Syntax Notes: Semantic Notes: Comments: 1 The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data. 2 HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction. 3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 4 HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information. 5 HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Notes: The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line item data to order data. FCA only uses the order level in the 870. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes HL Hierarchical ID Number M AN 1/12 M A unique number assigned by the sender to identify a particular data segment in a hierarchical structure '1' for the initial HL segment and incremented by 1 in each subsequent HL segment within the transaction set. HL Hierarchical Parent ID Number O AN 1/12 Not HL Hierarchical Level Code M ID 1/2 M Code defining the characteristic of a level in a hierarchical structure O Order HL Hierarchical Child Code O ID 1/1 Not 04/23/2015 V/R FCA US
11 Segment: N1 Name Position: 090 Loop: N1 Optional Level: Detail Usage: Optional Max : 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 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. Notes: One N1 segment is required to show the FCA plant issuing the release. 'MI' for the FCA and the order status report. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes N Entity Identifier Code M ID 2/2 M Code identifying an organizational entity, a physical location, or an individual MI Planning Schedule/Material Release Issuer N Name X AN 1/35 Not N Identification Code Qualifier X ID 1/2 Must ID 2/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer or Buyer's Agent N Identification Code X AN 2/17 Must AN 5/5 Code identifying a party or other code '06203' = Warren Stamping '06204' = TwinsburgStamping '06215' = SterlingStamping '06219' = Toledo Stamping '06244' = Belvidere Stamping '08477' = Toluca Stamping '09127' = Bramalea Stamping N Entity Relationship Code O ID 2/2 Not N Entity Identifier Code O ID 2/2 Not 04/23/2015 V/R FCA US
12 Segment: PO1 Baseline Item Data Position: 150 Loop: PO1 Optional Level: Detail Usage: Optional Max : 1 Purpose: To specify basic and most frequently used line item data Syntax Notes: 1 If PO103 is present, then PO102 is required. 2 If PO105 is present, then PO104 is required. 3 If PO106 is present, then PO107 is required. 4 If PO108 is present, then PO109 is required. 5 If PO110 is present, then PO111 is required. 6 If PO112 is present, then PO113 is required. 7 If PO114 is present, then PO115 is required. 8 If PO116 is present, then PO117 is required. 9 If PO118 is present, then PO119 is required. 10 If PO120 is present, then PO121 is required. 11 If PO122 is present, then PO123 is required. 12 If PO124 is present, then PO125 is required. Semantic Notes: Comments: 1 See the Data Dictionary for a complete list of ID's. 2 PO101 is the line item identification. 3 PO106 through PO125 provide for ten (10) different product/service ID's per each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU. Notes: FCA uses the PO1 to show the quantity of material ordered for a particular FCA part number as shown in the Material Release (830). For coils, the material ordered is shown in actual pounds. For cut blanks, the material ordered is shown in pieces. Some material is ordered in theoretical pounds. Consult the FCA Material Release (830) for the ordered units. The PO1 segment may also be used to transmit the FCA Purchase Order number for the material. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes PO Assigned Identification O AN 1/11 Not PO Quantity Ordered X R 1/9 Quantity ordered The (original release) quantity of material ordered from the Material Release (830). PO Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken 01 Actual Pounds 04/23/2015 V/R FCA US
13 for coils only. 24 Theoretical Pounds only for material ordered in theoretical pounds on the release (830). PC Piece for cut blanks only. PO Unit Price X R 1/14 Not PO Basis of Unit Price Code O ID 2/2 Not PO Product/Service ID Qualifier O ID 2/2 Must Code identifying the type/source of the descriptive number used in Product/Service ID (234) BP Buyer's Part Number PO Product/Service ID X AN 1/30 Must Identifying number for a product or service The FCA Part Number from the Material Release PO Product/Service ID Qualifier O ID 2/2 Must Code identifying the type/source of the descriptive number used in Product/Service ID (234) PO Purchase Order Number PO Product/Service ID X AN 1/30 AN 1/13 Identifying number for a product or service The FCA Purchase Order Number from the Material Release PO Product/Service ID Qualifier O ID 2/2 Must Code identifying the type/source of the descriptive number used in Product/Service ID (234) EC Engineering Change Level PO Product/Service ID X AN 1/30 Must Identifying number for a product or service The FCA Engineering Control (Metal Specification Suffix) from the Material Release PO Product/Service ID Qualifier O ID 2/2 Not PO Product/Service ID X AN 1/30 Not PO Product/Service ID Qualifier O ID 2/2 Not 04/23/2015 V/R FCA US
14 PO Product/Service ID X AN 1/30 Not PO Product/Service ID Qualifier O ID 2/2 Not PO Product/Service ID X AN 1/30 Not PO Product/Service ID Qualifier O ID 2/2 Not PO Product/Service ID X AN 1/30 Not PO Product/Service ID Qualifier O ID 2/2 Not PO Product/Service ID X AN 1/30 Not PO Product/Service ID Qualifier O ID 2/2 Not PO Product/Service ID X AN 1/30 Not PO Product/Service ID Qualifier O ID 2/2 Not PO Product/Service ID X AN 1/30 Not 04/23/2015 V/R FCA US
15 Segment: PID Product/Item Description Position: 180 Loop: PO1 Optional Level: Detail Usage: Optional Max : 1000 Purpose: To describe a product or process in coded or free-form format Syntax Notes: 1 If PID04 is present, then PID03 is required. 2 At least one of PID04 or PID05 is required. 3 If PID07 is present, then PID03 is required. 4 If PID08 is present, then PID03 is required. Semantic Notes: 1 PID03 to indicate the organization that publishes the code list being referred to. 2 PID04 should be used for industry-specific product description codes. 3 PID08 describes the physical characteristics of the product identified in PID04. A ``Y'' indicates that the specified attribute applies to this item. A ``N'' indicates it does not apply. Any other value is indeterminate. Comments: 1 If PID01 = ``F'', then PID05 is used. If PID01 = ``S'', then PID04 is used. If PID01 = ``X'', then both PID04 and PID05 are used. 2 PID06 when necessary to refer to the product surface or layer being described in the segment. 3 PID07 specifies the individual code list of the agency specified in PID03. Notes: to show the FCA Material Standard Number for the FCA Part Number given in the PO1 segment. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes PID Item Description Type M ID 1/1 M Code indicating the format of a description F Free-form PID Product/Process Characteristic Code O ID 2/3 Code identifying the general class of a product or process characteristic 11 Society, Government, Customer Specifications PID Agency Qualifier Code X ID 2/2 Not PID Product Description Code X AN 1/12 Not PID Description X AN 1/80 Must AN 1/12 A free-form description to clarify the related data elements and their content FCA Material Specification Code from the Material Release (830) PID Surface/Layer/Position Code O ID 2/2 Not PID Source Subqualifier O AN 1/15 Not 04/23/2015 V/R FCA US
16 PID Yes/No Condition or Response Code O ID 1/1 Not 04/23/2015 V/R FCA US
17 Segment: MEA Measurements Position: 190 Loop: PO1 Optional Level: Detail Usage: Optional Max : 40 Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001) Syntax Notes: 1 At least one of MEA03 MEA05 MEA06 or MEA08 is required. 2 If MEA03 is present, then MEA04 is required. 3 If MEA05 is present, then MEA04 is required. 4 If MEA06 is present, then MEA04 is required. 5 If MEA07 is present, then at least one of MEA03 MEA05 or MEA06 is required. 6 Only one of MEA08 or MEA03 may be present. Semantic Notes: 1 MEA04 defines the unit of measure for MEA03, MEA05, and MEA06. Comments: 1 When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+) value. Notes: Coils require 2 MEA segments for thickness and width. Cut blanks require 3 MEA segments for length, thickness, and width. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes MEA Measurement Reference ID Code O ID 2/2 Code identifying the broad category to which a measurement applies PD Physical Dimensions MEA Measurement Qualifier O ID 1/3 Must ID 2/2 Code identifying a specific product or process characteristic to which a measurement applies LN Length TH Thickness WD Width MEA Measurement Value X R 1/10 Must R 2/6 The value of the measurement The value of the dimension specified in MEA02 MEA04 C001 Composite Unit of Measure X To identify a composite unit of measure (See Figures Appendix for examples of use) C Unit or Basis for Measurement Code M ID 2/2 M Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken 04/23/2015 V/R FCA US
18 IN Inch C Exponent O R 1/15 Not C Multiplier O R 1/10 Not C Unit or Basis for Measurement Code O ID 2/2 Not C Exponent O R 1/15 Not C Multiplier O R 1/10 Not C Unit or Basis for Measurement Code O ID 2/2 Not C Exponent O R 1/15 Not C Multiplier O R 1/10 Not C Unit or Basis for Measurement Code O ID 2/2 Not C Exponent O R 1/15 Not C Multiplier O R 1/10 Not C Unit or Basis for Measurement Code O ID 2/2 Not C Exponent O R 1/15 Not C Multiplier O R 1/10 Not MEA Range Minimum X R 1/10 Not MEA Range Maximum X R 1/10 Not MEA Measurement Significance Code O ID 2/2 Not MEA Measurement Attribute Code X ID 2/2 Not MEA Surface/Layer/Position Code O ID 2/2 Not MEA Measurement Method or Device O ID 2/4 Not 04/23/2015 V/R FCA US
19 Segment: ISR Item Status Report Position: 210 Loop: ISR Optional Level: Detail Usage: Optional Max : 1 Purpose: To specify detailed purchase order/item status Syntax Notes: Semantic Notes: 1 If ISR01 specifies a date, ISR02 is required. Comments: Notes: ISR is used to indicate the status of releases. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes ISR Shipment/Order Status Code M ID 2/2 M Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction CC Shipment Complete on (Date) IC Item Canceled SL Shipped - to - Date through (Date) ISR Date O DT 6/6 Not ISR Status Reason Code O ID 3/3 Not 04/23/2015 V/R FCA US
20 Segment: QTY Quantity Position: 230 Loop: ISR Optional Level: Detail Usage: Optional Max : 4 Purpose: To specify quantity information Syntax Notes: Semantic Notes: Comments: Notes: The QTY segment is used to show the quantity of material received against an order. The unit of measure code (QTY03) will match the unit of measure on the original Material Release (830). If the order has been cancelled (e.g. ISR01 = 'IC'), a QTY segment won't be transmitted for remaining quantity of the order. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes QTY Quantity Qualifier M ID 2/2 M Code specifying the type of quantity 87 Quantity Received QTY Quantity M R 1/15 M Numeric value of quantity QTY Unit or Basis for Measurement Code O ID 2/2 Must Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken 01 Actual Pounds 24 Theoretical Pounds PC Piece Cut blanks only. 04/23/2015 V/R FCA US
21 Segment: DTM Date/Time/Period Position: 240 Loop: ISR Optional Level: Detail Usage: Optional Max : 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM06 is required. 2 If either DTM06 or DTM07 is present, then the other is required. Semantic Notes: Comments: Notes: One DTM segment in the ISR loop is mandatory to provide the date the material was required from the FST04 element of the FCA Material Release (830). Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes DTM Date/Time Qualifier M ID 3/3 M Code specifying type of date or time, or both date and time 106 Required By DTM Date X DT 6/6 Must Date (YYMMDD) The release period start date as given in element FST04 of the FCA Material Release (830) DTM Time X TM 4/8 Not DTM Time Code O ID 2/2 Not DTM Century O N0 2/2 Not DTM Date Time Period Format Qualifier X ID 2/3 Not DTM Date Time Period X AN 1/35 Not 04/23/2015 V/R FCA US
22 Segment: N1 Name Position: 250 Loop: ISR Optional Level: Detail Usage: Optional Max : 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 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. Notes: The N1 segment in the ISR loop is used to show the FCA assigned location code of the warehouse or processor storing the material. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes N Entity Identifier Code M ID 2/2 M Code identifying an organizational entity, a physical location, or an individual WH Warehouse N Name X AN 1/35 Not N Identification Code Qualifier X ID 1/2 Must ID 2/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer or Buyer's Agent N Identification Code X AN 2/17 Must AN 5/5 Code identifying a party or other code The FCA assigned location code of the warehouse or processor storing the material N Entity Relationship Code O ID 2/2 Not N Entity Identifier Code O ID 2/2 Not 04/23/2015 V/R FCA US
23 Segment: REF Reference Numbers Position: 300 Loop: ISR Optional Level: Detail Usage: Optional Max : 12 Purpose: To specify identifying numbers. Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Notes: FCA will provide 1 REF segment in the ISR loop to show the FCA release number the material was shipped against. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes REF Reference Number Qualifier M ID 2/2 M Code qualifying the Reference Number. RE Release Number REF Reference Number X AN 1/30 Must AN 1/15 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. If REF01 = RE, this is the release number from the FST09 element of the FCA Material Release (830); REF Description X AN 1/80 Not 04/23/2015 V/R FCA US
24 Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Usage: Optional Max : 1 Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If CTT03 is present, then CTT04 is required. 2 If CTT05 is present, then CTT06 is required. Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness. Notes: to provide the total number of HL segments used. This total is used to cross check that the complete transaction set was received and that all report data is accounted for. Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes CTT Number of Line Items M N0 1/6 M Total number of line items in the transaction set Total number of HL segments. CTT Hash Total O R 1/10 Must 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. The total of all the quantities in the PO102 element of all the PO1 segments CTT03 81 Weight O R 1/10 Not CTT Unit or Basis for Measurement Code X ID 2/2 Not CTT Volume O R 1/8 Not CTT Unit or Basis for Measurement Code X ID 2/2 Not 04/23/2015 V/R FCA US
25 CTT Description O AN 1/80 Not 04/23/2015 V/R FCA US
26 Segment: SE Transaction Set Trailer Position: 020 Loop: Level: Summary Usage: Mandatory Max : 1 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). Syntax Notes: Semantic Notes: Comments: 1 SE is the last segment of each transaction set. Notes: The transaction set control number value in this trainer must match the same element value in the transaction set header (ST02). Data Element Summary Ref. Data Base r Des. Element Name Attributes Attributes SE01 96 Number of Included Segments M N0 1/10 M Total number of segments included in a transaction set including ST and SE segments SE Transaction Set Control Number M AN 4/9 M Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 04/23/2015 V/R FCA US
27 FCA US Raw Steel Order Status Report Example: Status of Raw Steel Orders EDI Format ST~870~ BSR~2~PP~00001~ N1~PK~~92~44313 N1~SU~~92~53154 Interpretation Transaction Set Identifier Code = 870 (X12.23 Order Status Report) Transaction Set Control Number = Status Report Code = 2 (Prearranged Schedule or Agreement) Order/Item code = PP (Selected Orders - Selected Items) Reference Number = Date = 10/13/2014 Entity Identifier Code = PK (Party to Receive Copy) Identification Code Qualifier = 92 (Assigned by Buyer or Buyer's Agent) Identification Code = Entity Identifier Code = SU (Supplier/Manufacturer) Identification Code Qualifier = 92 (Assigned by Buyer or Buyer's Agent) Identification Code = (The following HL loop illustrates a closed order) HL~1~~O Hierarchical ID Number = 1 Hierarchical Level Code = O (Order) N1~MI~~92~06203 Entity Identifier Code = MI (Planning Schedule/Material Release Issuer) Identification Code Qualifier = 92 (Assigned by Buyer or Buyer's Agent) Identification Code = PO1~~10000~01~~~BP~ AA~PO~A A~EC~2 Quantity Ordered = Unit or Basis for Measurement Code = 01 (Actual Pounds) Product/Service ID Qualifier = BP (Buyer's Part Number) Product/Service ID = AA Product/Service ID Qualifier = PO (Purchase Order Number) Product/Service ID = A A Product/Service ID Qualifier = EC (Engineering Change Level) Product/Service ID = 2 PID~F~11~~~1067 Item Description Type = F (Free-form) Product/Process Characteristic Code = 11 (Society, Government, Customer Specifications) Description = /23/2015 V/R FCA US
28 FCA US Raw Steel Order Status Report Example: EDI Format Status of Raw Steel Orders (continued) Interpretation MEA~PD~TH~.033~IN MEA~PD~WD~60~IN MEA~PD~LN~60~IN ISR~CC QTY~87~3000~01 DTM~106~ N1~WH~~92~44313 REF~RE~32131 Measurement Reference ID Code = PD (Physical Dimensions) Measurement Qualifier = TH (Thickness) Measurement Value =.033 Unit or Basis for Measurement Code = IN (Inch) Measurement Reference ID Code = PD (Physical Dimensions) Measurement Qualifier = WD (Width) Measurement Value = 60 Unit or Basis for Measurement Code = IN (Inch) Measurement Reference ID Code = PD (Physical Dimensions) Measurement Qualifier = LN (Length) Measurement Value = 60 Unit or Basis for Measurement Code = IN (Inch) Shipment/Order Status Code = CC (Shipment Complete on <Date>) Quantity Qualifier = 87 (Quantity Received) Quantity = 3000 Unit or Basis for Measurement Code = 01 (Actual Pounds) Date/Time Qualifier = 106 (Required By) Date = 07/16/2014 Entity Identifier Code = WH (Warehouse) Identification Code Qualifier = 92 (Assigned by Buyer or Buyer's Agent) Identification Code = Reference Number Qualifier = RE (Release Number) Reference Number = (The following HL loop illustrates a cancelled order.) HL~2~~O Hierarchical ID Number = 2 Hierarchical Level Code = O (Order) N1~MI~~92~06203 Entity Identifier Code = MI (Planning Schedule/Material Release Issuer) Identification Code Qualifier = 92 (Assigned by Buyer or Buyer's Agent) Identification Code = /23/2015 V/R FCA US
29 FCA US Raw Steel Order Status Report Example: EDI Format Status of Raw Steel Orders (continued) Interpretation PO1~~200000~01~~~BP~ AA~PO~A A~EC~1 Quantity Ordered = Unit or Basis for Measurement Code = 01 (Actual Pounds) Product/Service ID Qualifier = BP (Buyer's Part Number) Product/Service ID = AA Product/Service ID Qualifier = PO (Purchase Order Number) Product/Service ID = A A Product/Service ID Qualifier = EC (Engineering Change Level) Product/Service ID = 1 PID~F~11~~~1067 MEA~PD~TH~.033~IN MEA~PD~WD~60~IN ISR~IC QTY~87~3000~01 DTM~106~ N1~WH~~92~44313 REF~RE~32131 Item Description Type = F (Free-form) Product/Process Characteristic Code = 11 (Society, Government, Customer Specifications) Description = 1067 Measurement Reference ID Code = PD (Physical Dimensions) Measurement Qualifier = TH (Thickness) Measurement Value =.033 Unit or Basis for Measurement Code = IN (Inch) Measurement Reference ID Code = PD (Physical Dimensions) Measurement Qualifier = WD (Width) Measurement Value = 60 Unit or Basis for Measurement Code = IN (Inch) Shipment/Order Status Code = IC (Item Canceled) Quantity Qualifier = 87 (Quantity Received) Quantity = 3000 Unit or Basis for Measurement Code = 01 (Actual Pounds) Date/Time Qualifier = 106 (Required By) Date = 07/16/2014 Entity Identifier Code = WH (Warehouse) Identification Code Qualifier = 92 (Assigned by Buyer or Buyer's Agent) Identification Code = Reference Number Qualifier = RE (Release Number) Reference Number = /23/2015 V/R FCA US
30 FCA US Raw Steel Order Status Report Example: EDI Format Status of Raw Steel Orders (continued) Interpretation (The following HL loop illustrates an open order.) HL~3~~O Hierarchical ID Number = 3 Hierarchical Level Code = O (Order) N1~MI~~92~06203 Entity Identifier Code = MI (Planning Schedule/Material Release Issuer) Identification Code Qualifier = 92 (Assigned by Buyer or Buyer's Agent) Identification Code = PO1~~200000~01~~~BP~ AA~PO~A A~EC~3 Quantity Ordered = Unit or Basis for Measurement Code = 01 (Actual Pounds) Product/Service ID Qualifier = BP (Buyer's Part Number) Product/Service ID = AA Product/Service ID Qualifier = PO (Purchase Order Number) Product/Service ID = A A Product/Service ID Qualifier = EC (Engineering Change Level) Product/Service ID = 3 PID~F~11~~~1067 MEA~PD~TH~.033~IN MEA~PD~WD~60~IN ISR~SL QTY~87~3000~01 Item Description Type = F (Free-form) Product/Process Characteristic Code = 11 (Society, Government, Customer Specifications) Description = 1067 Measurement Reference ID Code = PD (Physical Dimensions) Measurement Qualifier = TH (Thickness) Measurement Value =.033 Unit or Basis for Measurement Code = IN (Inch) Measurement Reference ID Code = PD (Physical Dimensions) Measurement Qualifier = WD (Width) Measurement Value = 60 Unit or Basis for Measurement Code = IN (Inch) Shipment/Order Status Code = SL (Shipped - to - Date through <Date>) Quantity Qualifier = 87 (Quantity Received) Quantity = 3000 Unit or Basis for Measurement Code = 01 (Actual Pounds) 04/23/2015 V/R FCA US
31 FCA US Raw Steel Order Status Report Example: EDI Format Status of Raw Steel Orders (continued) Interpretation DTM~106~ N1~WH~~92~41772 REF~RE~31222 Date/Time Qualifier = 106 (Required By) Date = 07/16/2014 Entity Identifier Code = WH (Warehouse) Identification Code Qualifier = 92 (Assigned by Buyer or Buyer's Agent) Identification Code = Reference Number Qualifier = RE (Release Number) Reference Number = CTT~3~ Number of Line Items = 3 Hash Total = SE~39~ Total Number of Segments = 39 Transaction Set control Number = /23/2015 V/R FCA US
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 informationInternational Truck and Engine Corporation
International Truck and Engine Corporation EDI 870 -- Order Status Report VERSION: ANSI ASC X12 Version Release 3020 FINAL Publication Date: February 6, 2001 Trading Partner: Truck Marketing Created: January
More informationIMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR TIRE PROGRAM PRICE/SALES CATALOG (832) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR TIRE PROGRAM PRICE/SALES CATALOG (832) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE
More information846 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 information870 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 information830W (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 informationAn 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 information870 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 information870 Order Status Report
870 Order Status Report X12/V4010/870 : 870 Order Status Report Status: Final Company: CDW Publication: 7/19/2016 Table of Contents 870 Order Status Report.................................................................................................
More information850 - 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 information830 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 informationHCHETTE 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 information850 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 informationHACHETTE 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 information850 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 informationANSI 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 informationEDI Specifications Guide. 856 Customer Advance Ship Notice
856 Customer Advance Ship Notice 856 Ship Notice/Manifest - Functional Group=SH VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific
More information860 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 informationANSI 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 information860 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 information810 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 informationRCI 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 information850 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 information850 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 informationGolfsmith 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 information862 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 informationProduct 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 informationANSI 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 information861 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 information846 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 information855 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 information830 - 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 informationPlex 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 information867 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 informationModine Manufacturing Company. North America EDI Guidelines for Planning Schedules (830) v. 4010
Modine Manufacturing Company North America EDI Guidelines for Planning Schedules (830) v. 4010 Date: January 16, 2003 ISA Interchange Envelope Requirements ISA01 ID 2/2 M 00 ISA02 AN 10/10 M Not used ISA03
More information846 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 informationevo.com 855 Purchase Order Acknowledgment Author: SPS Commerce Company: evo.com Trading Partner: Created: 3/8/2013 Modified: 8/9/2017 Notes:
evo.com 855 Purchase Order Acknowledgment Author: SPS Commerce Company: evo.com Trading Partner: Created: 3/8/2013 Modified: 8/9/2017 Notes: 855 Purchase Order Acknowledgment Functional Group= PR Purpose:
More informationJR 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 information855 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 informationEDI 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 information850 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 informationDSW 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 information849 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 information816 Organizational Relationships
816 Organizational Relationships Functional Group ID=OR Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Organizational Relationships Transaction
More information850 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 informationEDI Implementation Guide Version
EDI Implementation Guide Version 004010 861 Receiving Advice/Acceptance Certificate Verizon Implementation Guide 1 04/20/17 861 Receiving Advice/Acceptance Certificate Introduction: Functional Group ID=RC
More information846 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 informationOrchard 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 information860 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 informationCVS/Caremark. Implementation Guide. 830 Planning Schedule with Release Capability. Version X
CVS/Caremark Implementation Guide 830 Planning Schedule with Release Capability Version X12-4010 Version 1.0 X12-4010 (004010) 1 September 21, 2017 Table of Contents Introduction:...3 ST Transaction Set
More information867 Product Transfer and Resale Report
867 Product Transfer and Resale Report Introduction: Functional Group ID=PT This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Transfer and Resale Report
More information869 Order Status Inquiry
869 Order Status Inquiry Functional Group ID=RS Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status Inquiry Transaction Set (869) for
More information940 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 informationJR 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 informationANSI 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 information846 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 information832 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 informationCVS/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 informationEDI Implementation Guide Version
EDI Implementation Guide Version 004010 867 Product Transfer and Resale Report Verizon Implementation Guide 1 04/12/17 867 Product Transfer and Resale Report Functional Group ID=PT Introduction: This Draft
More informationInternational Truck and Engine Corporation
International Truck and Engine Corporation EDI 824 - - Application Advice VERSION: ANSI ASC X12 Version Release 3040 FINAL Publication Date: April 20, 2000 Created: September 11, 1997 12:21 PM 824 Application
More informationPurchase 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 information867 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 information850 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 informationANSI 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 information850 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 informationEDI Specifications Guide. 855 Customer Purchase Order Acknowledgement
855 Customer Purchase Order Acknowledgement 855 Purchase Order Acknowledgement- Functional Group=PR VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the
More informationGovX 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 information810 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 informationIMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT ACCOUNT ANALYSIS (822) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT ACCOUNT ANALYSIS (822) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE
More informationEDI 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 information830 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 informationPLANNING SCHEDULE (830) SENT BY BLUE BIRD ANSI Segment Loop Construction
ANSI Segment Loop Construction SEG. SEGMENT REQ MAX LOOP ID / BLUE BIRD ID NAME USE USW LOOP COUNT USE ISA Interchange Control Segment M 1 YES GS Functional Group Header M 1 YES ST Transaction Set Header
More informationDLMS Implementation Convention (IC) 870L Special Program Requirements (SPR) Status or Notification ADC 287, 333, 400, 436 and 1043C DLM 4000.
870 Order Status Report Functional Group= RS Purpose: 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
More informationGovX 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 informationElectronic Data Interchange 832 Price/Sales Catalog (VICS Version ) March Powered By:
Electronic Data Interchange 832 Price/Sales Catalog (VICS Version - 4010) March 2011 Powered By: Purpose This document provides detailed guidelines and conventions for implementing electronic price/sales
More information824 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 information850 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 informationTRW Chassis Division
Material Release Transaction 830 ANSI X12 Version - 003040 Introduction 1. A release will not be issued unless a purchase order already exits which describes the contractual agreement between the supplier
More information832 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 information855 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 information850 Delhaize America Direct Store Delivery CAO Purchase Order Version 5010
850 Delhaize America Direct Store Delivery CAO Purchase Order Version 5010 Introduction: Functional Group ID=PO The transaction set can be used to provide for customary and established business and industry
More information846 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 informationOshkosh 860 Purchase Order Change Request - Buyer Initiated
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
More information875 - 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 information855 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 information12/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 information3. 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 information860 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 information855 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 information830 Planning Schedule with Release Capability
830 Planning Schedule with Release Capability X12/V4010/830: 830 Planning Schedule with Release Capability Version: Author: Abbott Nutrition ebusiness Company: Abbott Nutrition Created: 03/22/2012 Current:
More information812 Credit/Debit Adjustment
812 Credit/Debit Adjustment Functional Group ID=CD Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Credit/Debit Adjustment Transaction Set (812)
More information865 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 informationInbound 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 informationEDI Specifications Guide. 855 Supplier Purchase Order Acknowledgement. Last Update May 2016
855 Supplier Purchase Order Acknowledgement Last Update May 2016 855 Purchase Order Acknowledgment- Functional Group=PR VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the
More informationBaker & 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 information849 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 informationTransaction 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 information865 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 informationESIS. 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 informationDLMS Implementation Convention (IC) 888W Weapons System Data Change ADC 111, 167, 167A and 1043C DLM
888 Item Maintenance Functional Group= QG Purpose: This Draft Standard for Trial Use provides the format and establishes the data contents of the Item Maintenance Transaction Set (888) for use within the
More information