IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS SERVICE NET AND SPRINTER INVOICE (810) TRANSACTION SET
|
|
- Kelley Glenn
- 6 years ago
- Views:
Transcription
1 IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS SERVICE NET AND SPRINTER INVOICE (810) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE
2 810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided. Notes: FCA US will use the Invoice (810) Transaction Set to invoice customers for parts for Service Net and Sprinter vehicles. History of Change: 11/03/2005: Move part description from IT1 to PID with expansion of description to length 80. Note: elements used in the IT1 for part description have been marked not used. In order to not disrupt the use/mapping of IT110/IT111, these elements remain as is. 10/05/2006: Add total discount amount to TDS (TDS04) 07/13/2010: Name change from DaimlerChrysler to Chrysler Updated Address 01/10/2011: Added GT (Goods and Service Tax ID) and 4G (Provincial Tax ID) in the REF segment. Added SP (State/Provincial Tax amount) and GS (Goods and Service Tax amount) in the TXI segment. 01/26/2015: Name Change To FCA US Heading: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments ST Transaction Set Header M M BIG Beginning Segment for Invoice M M NTE Note/Special Instruction O Not CUR Currency O Not REF Reference Identification O YNQ Yes/No Question O Not PER Administrative Communications O Not 3 01/26/2015 V/R FCA US
3 Contact LOOP ID - N N1 Name O N2 Additional Name Information O Not N3 Address Information O N4 Geographic Location O REF Reference Identification O Not PER Administrative Communications Contact O Not DMG Demographic Information O Not ITD Terms of Sale/Deferred Terms of Sale O > DTM Date/Time Reference O FOB F.O.B. Related Instructions O Not PID Product/Item Description O MEA Measurements O PWK Paperwork O Not PKG Marking, Packaging, Loading O Not L7 Tariff Reference O Not BAL Balance Detail O Not >1 213 INC Installment Information O Not PAM Period Amount O Not >1 LOOP ID - LM LM Code Source Information O Not LQ Industry Code M Not 100 LOOP ID - N N9 Reference Identification O Not MSG Message Text M Not 10 LOOP ID - V1 >1 260 V1 Vessel Identification O Not R4 Port or Terminal O Not >1 280 DTM Date/Time Reference O Not >1 LOOP ID - FA1 >1 290 FA1 Type of Financial Accounting Data O Not FA2 Accounting Data M Not >1 Detail: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments LOOP ID - IT IT1 Baseline Item Data (Invoice) O CRC Conditions Indicator O Not QTY Quantity O Not 5 n1 020 CUR Currency O Not IT3 Additional Item Data O Not TXI Tax Information O Not CTP Pricing Information O Not 25 01/26/2015 V/R FCA US
4 055 PAM Period Amount O Not MEA Measurements O Not 40 LOOP ID - PID PID Product/Item Description O MEA Measurements O Not PWK Paperwork O Not PKG Marking, Packaging, Loading O Not PO4 Item Physical Details O Not ITD Terms of Sale/Deferred Terms of Sale O REF Reference Identification O Not >1 125 YNQ Yes/No Question O Not PER Administrative Communications Contact O Not SDQ Destination Quantity O Not DTM Date/Time Reference O Not CAD Carrier Detail O Not >1 170 L7 Tariff Reference O Not >1 175 SR Requested Service Schedule O Not 1 LOOP ID - SAC SAC Service, Promotion, Allowance, or Charge Information O Not TXI Tax Information O Not 10 LOOP ID - SLN SLN Subline Item Detail O DTM Date/Time Reference O Not REF Reference Identification O Not >1 220 PID Product/Item Description O Not SAC Service, Promotion, Allowance, or Charge Information O Not TC2 Commodity O Not TXI Tax Information O Not 10 LOOP ID - N N1 Name O Not N2 Additional Name Information O Not N3 Address Information O Not N4 Geographic Location O Not REF Reference Identification O Not PER Administrative Communications Contact O Not DMG Demographic Information O Not 1 LOOP ID - LM LM Code Source Information O Not LQ Industry Code M Not 100 LOOP ID - V1 >1 320 V1 Vessel Identification O Not R4 Port or Terminal O Not >1 01/26/2015 V/R FCA US
5 340 DTM Date/Time Reference O Not >1 LOOP ID - FA1 >1 350 FA1 Type of Financial Accounting Data O Not FA2 Accounting Data M Not >1 Summary: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments TDS Total Monetary Value Summary M M TXI Tax Information O CAD Carrier Detail O AMT Monetary Amount O Not >1 LOOP ID - SAC SAC Service, Promotion, Allowance, or O 1 Charge Information TXI Tax Information O 10 LOOP ID - ISS >1 060 ISS Invoice Shipment Summary O Not PID Product/Item Description O Not CTT Transaction Totals O 1 n SE Transaction Set Trailer M M 1 Transaction Set Notes 1. The QTY segment is used to specify a quantity of units which are expected as payments, e.g., trade -ins or returns. 2. Number of line items (CTT01) is the accumulation of the number of IT1 segments. If used, hash total (CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment. 01/26/2015 V/R FCA US
6 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 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 User Des. Element Name Attributes Attributes ST Transaction Set Identifier Code M ID 3/3 M Code uniquely identifying a Transaction Set 810 Invoice 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 01/26/2015 V/R FCA US
7 Segment: BIG Beginning Segment for Invoice Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates Syntax Notes: Semantic Notes: 1 BIG01 is the invoice issue date. 2 BIG03 is the date assigned by the purchaser to purchase order. 3 BIG10 indicates the consolidated invoice number. When BIG07 contains code CI, BIG10 is not used. Comments: 1 BIG07 is used only to further define the type of invoice when needed. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes BIG Date M DT 8/8 M Date expressed as CCYYMMDD Transaction Set Create Date BIG02 76 Invoice Number M AN 1/22 M Identifying number assigned by issuer Invoice Number BIG Date O DT 8/8 Not BIG Purchase Order Number O AN 1/22 Not BIG Release Number O AN 1/30 Not BIG Change Order Sequence Number O AN 1/8 Not BIG Transaction Type Code O ID 2/2 Code specifying the type of transaction CN Credit Invoice CR Credit Memo DI Debit Invoice DR Debit Memo BIG Transaction Set Purpose Code O ID 2/2 Not BIG Action Code O ID 1/2 Not 01/26/2015 V/R FCA US
8 BIG10 76 Invoice Number O AN 1/22 Not 01/26/2015 V/R FCA US
9 Segment: REF Reference Identification Position: 050 Loop: Level: Heading Usage: Optional Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes REF Reference Identification Qualifier M ID 2/3 M Code qualifying the Reference Identification 19 Division Identifier 4G Provincial Tax Identification AW Air Waybill Number BB Authorization Number BF Billing Center Identification FQ Form Number GT Goods and Service Tax Registration Number QQ Unit Number VT Motor Vehicle ID Number REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier If REF01 = '19', the division identifier; If REF01 = 'AW', the tracking ID number; If REF01 = 'BB', the authorization number; If REF01 = 'BF', billing center ID number; If REF01 = 'FQ', the repair order number; If REF01 = 'QQ', the fleet unit number; If REF01 = 'VT', the VIN number. If REF01 = 'GT', Goods and Service Tax Number. If REF01 = '4G', Provincial Tax ID. REF Description X AN 1/80 Not REF04 C040 Reference Identifier O Not 01/26/2015 V/R FCA US
10 Use d To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier C Reference Identification Qualifier M ID 2/3 Not Code qualifying the Reference Identification C Reference Identification M AN 1/30 Not Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier C Reference Identification Qualifier X ID 2/3 Not Code qualifying the Reference Identification C Reference Identification X AN 1/30 Not Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier C Reference Identification Qualifier X ID 2/3 Not Code qualifying the Reference Identification C Reference Identification X AN 1/30 Not Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 01/26/2015 V/R FCA US
11 Segment: N1 Name Position: 070 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 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: Up to four possible of the N1 will be used. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N Entity Identifier Code M ID 2/3 M Code identifying an organizational entity, a physical location, property or an individual EY Employee Name SF Ship From ST Ship To VN Vendor N Name X AN 1/60 Free-form name N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 24 Employer's Identification Number Will be used only when N101 = 'EY'. 92 Assigned by Buyer or Buyer's Agent N Identification Code X AN 2/80 Code identifying a party or other code N Entity Relationship Code O ID 2/2 Not N Entity Identifier Code O ID 2/3 Not 01/26/2015 V/R FCA US
12 Segment: N3 Address Information Position: 090 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments: Notes: The N3 will be used to specify address information for ship from and ship to locations. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N Address Information M AN 1/55 M Address information N Address Information O AN 1/55 Address information 01/26/2015 V/R FCA US
13 Segment: N4 Geographic Location Position: 100 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is required. Semantic Notes: 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. Notes: The N4 will be used to specify address information for ship from and ship to locations. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N City Name O AN 2/30 Free-form text for city name N State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government agency N Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country Code O ID 2/3 Not N Location Qualifier X ID 1/2 Not N Location Identifier O AN 1/30 Not 01/26/2015 V/R FCA US
14 Segment: ITD Terms of Sale/Deferred Terms of Sale Position: 130 Loop: Level: Heading Usage: Optional Max Use: >1 Purpose: To specify terms of sale Syntax Notes: 1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD13 is required. 2 If ITD08 is present, then at least one of ITD04 ITD05 or ITD13 is required. 3 If ITD09 is present, then at least one of ITD10 or ITD11 is required. Semantic Notes: 1 ITD15 is the percentage applied to a base amount used to determine a late payment charge. Comments: 1 If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ITD Terms Type Code O ID 2/2 Code identifying type of payment terms 14 Previously agreed upon ITD Terms Basis Date Code O ID 1/2 Not ITD Terms Discount Percent O R 1/6 Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date Discount Percent for all items at this level, if applicable. ITD Terms Discount Due Date X DT 8/8 Date payment is due if discount is to be earned expressed in format CCYYMMDD Date invoice must be paid if taking a discount. ITD Terms Discount Days Due X N0 1/3 Not ITD Terms Net Due Date O DT 8/8 Date when total invoice amount becomes due expressed in format CCYYMMDD Date invoice must be paid if not using any discounts. ITD Terms Net Days O N0 1/3 Not ITD Terms Discount Amount O N2 1/10 Not ITD Terms Deferred Due Date O DT 8/8 Not ITD Deferred Amount Due X N2 1/10 Not 01/26/2015 V/R FCA US
15 ITD Percent of Invoice Payable X R 1/5 Not ITD Description O AN 1/80 Not ITD Day of Month X N0 1/2 Not ITD Payment Method Code O ID 1/2 Not ITD Percent O R 1/10 Not 01/26/2015 V/R FCA US
16 Segment: DTM Date/Time Reference Position: 140 Loop: Level: Heading Usage: Optional Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments: Data Element Summary Ref. Data Base User 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 214 Date of Repair/Service DTM Date X DT 8/8 Date expressed as CCYYMMDD If DTM01 = '214', the date of repair. DTM Time X TM 4/8 Not DTM Time Code O ID 2/2 Not DTM Date Time Period Format Qualifier X ID 2/3 Not DTM Date Time Period X AN 1/35 Not 01/26/2015 V/R FCA US
17 Segment: PID Product/Item Description Position: 160 Loop: Level: Heading Usage: Optional Max Use: 200 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 PID04 is required. 5 If PID09 is present, then PID05 is required. Semantic Notes: 1 Use 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; an "N" indicates it does not apply. Any other value is indeterminate. 4 PID09 is used to identify the language being used in PID05. Comments: 1 If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used. 2 Use 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. Data Element Summary Ref. Data Base User 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 GEN General Description SE Services PID Agency Qualifier Code X ID 2/2 Not PID Product Description Code X AN 1/12 Not PID Description X AN 1/80 A free-form description to clarify the related data elements and their content If PID02 = 'GEN', the repair requested from customer; If PID02 = 'SE', description of the repair. PID Surface/Layer/Position Code O ID 2/2 Not 01/26/2015 V/R FCA US
18 PID Source Subqualifier O AN 1/15 Not PID Yes/No Condition or Response Code O ID 1/1 Not PID Language Code O ID 2/3 Not 01/26/2015 V/R FCA US
19 Segment: MEA Measurements Position: 170 Loop: Level: Heading Usage: Optional Max Use: 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 MEA05 is present, then MEA04 is required. 3 If MEA06 is present, then MEA04 is required. 4 If MEA07 is present, then at least one of MEA03 MEA05 or MEA06 is required. 5 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. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes MEA Measurement Reference ID Code O ID 2/2 Not MEA Measurement Qualifier O ID 1/3 Not MEA Measurement Value X R 1/20 The value of the measurement Vehicle Mileage 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 DH Miles 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 01/26/2015 V/R FCA US
20 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/20 Not MEA Range Maximum X R 1/20 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 01/26/2015 V/R FCA US
21 Segment: IT1 Baseline Item Data (Invoice) Position: 010 Loop: IT1 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify the basic and most frequently used line item data for the invoice and related transactions Syntax Notes: 1 If any of IT102 IT103 or IT104 is present, then all are required. 2 If either IT106 or IT107 is present, then the other is required. 3 If either IT108 or IT109 is present, then the other is required. 4 If either IT110 or IT111 is present, then the other is required. 5 If either IT112 or IT113 is present, then the other is required. 6 If either IT114 or IT115 is present, then the other is required. 7 If either IT116 or IT117 is present, then the other is required. 8 If either IT118 or IT119 is present, then the other is required. 9 If either IT120 or IT121 is present, then the other is required. 10 If either IT122 or IT123 is present, then the other is required. 11 If either IT124 or IT125 is present, then the other is required. Semantic Notes: 1 IT101 is the purchase order line item identification. Comments: 1 Element 235/234 combinations should be interpreted to include products and/or services. See the Data Dictionary for a complete list of IDs. 2 IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes IT Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set Sequential line item number IT Quantity Invoiced X R 1/10 Number of units invoiced (supplier units) IT Unit or Basis for Measurement Code X ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Appropriate unit of measure will be used, typically 'EA'. IT Unit Price X R 1/17 Price per unit of product, service, commodity, etc. IT Basis of Unit Price Code O ID 2/2 Not IT Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service 01/26/2015 V/R FCA US
22 ID (234) VP Vendor's (Seller's) Part Number IT Product/Service ID X AN 1/48 Identifying number for a product or service FCA US part number IT Product/Service ID Qualifier X ID 2/2 Not IT Product/Service ID X AN 1/48 Not IT Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) A3 Locally Assigned Control Number PO Purchase Order Number IT Product/Service ID X AN 1/48 Identifying number for a product or service IT Product/Service ID Qualifier X ID 2/2 Not IT Product/Service ID X AN 1/48 Not IT Product/Service ID Qualifier X ID 2/2 Not IT Product/Service ID X AN 1/48 Not IT Product/Service ID Qualifier X ID 2/2 Not IT Product/Service ID X AN 1/48 Not IT Product/Service ID Qualifier X ID 2/2 Not IT Product/Service ID X AN 1/48 Not IT Product/Service ID Qualifier X ID 2/2 Not IT Product/Service ID X AN 1/48 Not IT Product/Service ID Qualifier X ID 2/2 Not IT Product/Service ID X AN 1/48 Not IT Product/Service ID Qualifier X ID 2/2 Not 01/26/2015 V/R FCA US
23 IT Product/Service ID X AN 1/48 Not 01/26/2015 V/R FCA US
24 Segment: PID Product/Item Description Position: 060 Loop: PID Optional Level: Detail Usage: Optional Max Use: 1 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 PID04 is required. 5 If PID09 is present, then PID05 is required. Semantic Notes: 1 Use 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; an "N" indicates it does not apply. Any other value is indeterminate. 4 PID09 is used to identify the language being used in PID05. Comments: 1 If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used. 2 Use 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. Data Element Summary Ref. Data Base User 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 08 Product PID Agency Qualifier Code X ID 2/2 Not PID Product Description Code X AN 1/12 Not PID Description X AN 1/80 A free-form description to clarify the related data elements and their content Part Description PID Surface/Layer/Position Code O ID 2/2 Not PID Source Subqualifier O AN 1/15 Not 01/26/2015 V/R FCA US
25 PID Yes/No Condition or Response Code O ID 1/1 Not PID Language Code O ID 2/3 Not 01/26/2015 V/R FCA US
26 Segment: ITD Terms of Sale/Deferred Terms of Sale Position: 110 Loop: IT1 Optional Level: Detail Usage: Optional Max Use: 2 Purpose: To specify terms of sale Syntax Notes: 1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD13 is required. 2 If ITD08 is present, then at least one of ITD04 ITD05 or ITD13 is required. 3 If ITD09 is present, then at least one of ITD10 or ITD11 is required. Semantic Notes: 1 ITD15 is the percentage applied to a base amount used to determine a late payment charge. Comments: 1 If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ITD Terms Type Code O ID 2/2 Code identifying type of payment terms 14 Previously agreed upon ITD Terms Basis Date Code O ID 1/2 Not ITD Terms Discount Percent O R 1/6 Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date Discount percent for this item. ITD Terms Discount Due Date X DT 8/8 Date payment is due if discount is to be earned expressed in format CCYYMMDD ITD Terms Discount Days Due X N0 1/3 Not ITD Terms Net Due Date O DT 8/8 Not ITD Terms Net Days O N0 1/3 Not ITD Terms Discount Amount O N2 1/10 Not ITD Terms Deferred Due Date O DT 8/8 Not ITD Deferred Amount Due X N2 1/10 Not ITD Percent of Invoice Payable X R 1/5 Not 01/26/2015 V/R FCA US
27 ITD Description O AN 1/80 Not ITD Day of Month X N0 1/2 Not ITD Payment Method Code O ID 1/2 Not ITD Percent O R 1/10 Not 01/26/2015 V/R FCA US
28 Segment: SLN Subline Item Detail Position: 200 Loop: SLN Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify product subline detail item data Syntax Notes: 1 If either SLN04 or SLN05 is present, then the other is required. 2 If SLN07 is present, then SLN06 is required. 3 If SLN08 is present, then SLN06 is required. 4 If either SLN09 or SLN10 is present, then the other is required. 5 If either SLN11 or SLN12 is present, then the other is required. 6 If either SLN13 or SLN14 is present, then the other is required. 7 If either SLN15 or SLN16 is present, then the other is required. 8 If either SLN17 or SLN18 is present, then the other is required. 9 If either SLN19 or SLN20 is present, then the other is required. 10 If either SLN21 or SLN22 is present, then the other is required. 11 If either SLN23 or SLN24 is present, then the other is required. 12 If either SLN25 or SLN26 is present, then the other is required. 13 If either SLN27 or SLN28 is present, then the other is required. Semantic Notes: 1 SLN01 is the identifying number for the subline item. 2 SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials. 3 SLN03 is the configuration code indicating the relationship of the subline item to the baseline item. 4 SLN08 is a code indicating the relationship of the price or amount to the associated segment. Comments: 1 See the Data Element Dictionary for a complete list of IDs. 2 SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1. 3 SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU. Notes: Iterations of SLN will be used as necessary for ATA/VMRS codes. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes SLN Assigned Identification M AN 1/20 M Alphanumeric characters assigned for differentiation within a transaction set SLN Assigned Identification O AN 1/20 Not SLN Relationship Code M ID 1/1 M Code indicating the relationship between entities O Information Only 01/26/2015 V/R FCA US
29 SLN Quantity X R 1/15 Not SLN05 C001 Composite Unit of Measure X Not Use d 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 Not Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken C Exponent O R 1/15 Not Power to which a unit is raised C Multiplier O R 1/10 Not Value to be used as a multiplier to obtain a new value C Unit or Basis for Measurement Code O ID 2/2 Not Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken C Exponent O R 1/15 Not Power to which a unit is raised C Multiplier O R 1/10 Not Value to be used as a multiplier to obtain a new value C Unit or Basis for Measurement Code O ID 2/2 Not Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken C Exponent O R 1/15 Not Power to which a unit is raised C Multiplier O R 1/10 Not Value to be used as a multiplier to obtain a new value C Unit or Basis for Measurement Code O ID 2/2 Not Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken C Exponent O R 1/15 Not 01/26/2015 V/R FCA US
30 Power to which a unit is raised C Multiplier O R 1/10 Not Value to be used as a multiplier to obtain a new value C Unit or Basis for Measurement Code O ID 2/2 Not Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken C Exponent O R 1/15 Not Power to which a unit is raised C Multiplier O R 1/10 Not Value to be used as a multiplier to obtain a new value SLN Unit Price X R 1/17 Not SLN Basis of Unit Price Code O ID 2/2 Not SLN Relationship Code O ID 1/1 Not SLN Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) VM Vehicle Maintenance Reporting Standards SLN Product/Service ID X AN 1/48 Identifying number for a product or service Combination of ATA/VMRS code keys 31,32 and 33. SLN Product/Service ID Qualifier X ID 2/2 Not SLN Product/Service ID X AN 1/48 Not SLN Product/Service ID Qualifier X ID 2/2 Not SLN Product/Service ID X AN 1/48 Not SLN Product/Service ID Qualifier X ID 2/2 Not SLN Product/Service ID X AN 1/48 Not SLN Product/Service ID Qualifier X ID 2/2 Not SLN Product/Service ID X AN 1/48 Not 01/26/2015 V/R FCA US
31 SLN Product/Service ID Qualifier X ID 2/2 Not SLN Product/Service ID X AN 1/48 Not SLN Product/Service ID Qualifier X ID 2/2 Not SLN Product/Service ID X AN 1/48 Not SLN Product/Service ID Qualifier X ID 2/2 Not SLN Product/Service ID X AN 1/48 Not SLN Product/Service ID Qualifier X ID 2/2 Not SLN Product/Service ID X AN 1/48 Not SLN Product/Service ID Qualifier X ID 2/2 Not SLN Product/Service ID X AN 1/48 Not 01/26/2015 V/R FCA US
32 Segment: TDS Total Monetary Value Summary Position: 010 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To specify the total invoice discounts and amounts Syntax Notes: Semantic Notes: 1 TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable). 2 TDS02 indicates the amount upon which the terms discount amount is calculated. 3 TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount less cash discount). 4 TDS04 indicates the total amount of terms discount. Comments: 1 TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes TDS Amount M N2 1/15 M Monetary amount Total invoice amount TDS Amount O N2 1/15 Not TDS Amount O N2 1/15 Not TDS Amount O N2 1/15 Monetary amount Total Discount Amount 01/26/2015 V/R FCA US
33 Segment: TXI Tax Information Position: 020 Loop: Level: Summary Usage: Optional Max Use: 10 Purpose: To specify tax information Syntax Notes: 1 At least one of TXI02 TXI03 or TXI06 is required. 2 If either TXI04 or TXI05 is present, then the other is required. 3 If TXI08 is present, then TXI03 is required. Semantic Notes: 1 TXI02 is the monetary amount of the tax. 2 TXI03 is the tax percent expressed as a decimal. 3 TXI07 is a code indicating the relationship of the price or amount to the associated segment. Comments: Notes: The TXI segment will be used when taxes apply. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes TXI Tax Type Code M ID 2/2 M Code specifying the type of tax GS Goods and Services Tax SP State/Provincial Tax SU Sales and Use Tax TXI Monetary Amount X R 1/18 Monetary amount Tax Amount TXI Percent X R 1/10 Not TXI Tax Jurisdiction Code Qualifier X ID 2/2 Not TXI Tax Jurisdiction Code X AN 1/10 Not TXI Tax Exempt Code X ID 1/1 Not TXI Relationship Code O ID 1/1 Not TXI Dollar Basis For Percent O R 1/9 Not TXI Tax Identification Number O AN 1/20 Not TXI Assigned Identification O AN 1/20 Not 01/26/2015 V/R FCA US
34 Segment: CAD Carrier Detail Position: 030 Loop: Level: Summary Usage: Optional Max Use: 1 Purpose: To specify transportation details for the transaction Syntax Notes: 1 At least one of CAD05 or CAD04 is required. 2 If CAD07 is present, then CAD08 is required. Semantic Notes: Comments: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes CAD01 91 Transportation Method/Type Code O ID 1/2 Code specifying the method or type of transportation for the shipment P Private Carrier CAD Equipment Initial O AN 1/4 Not CAD Equipment Number O AN 1/10 Not CAD Standard Carrier Alpha Code X ID 2/4 Not CAD Routing X AN 1/35 Free-form description of the routing or requested routing for shipment, or the originating carrier's identity CAD Shipment/Order Status Code O ID 2/2 Not CAD Reference Identification Qualifier O ID 2/3 Not CAD Reference Identification X AN 1/30 Not CAD Service Level Code O ID 2/2 Not 01/26/2015 V/R FCA US
35 Segment: SAC Service, Promotion, Allowance, or Charge Information Position: 040 Loop: SAC Optional Level: Summary Usage: Optional Max Use: 1 Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge Syntax Notes: 1 At least one of SAC02 or SAC03 is required. 2 If either SAC03 or SAC04 is present, then the other is required. 3 If either SAC06 or SAC07 is present, then the other is required. 4 If either SAC09 or SAC10 is present, then the other is required. 5 If SAC11 is present, then SAC10 is required. 6 If SAC13 is present, then at least one of SAC02 or SAC04 is required. 7 If SAC14 is present, then SAC13 is required. 8 If SAC16 is present, then SAC15 is required. Semantic Notes: 1 If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required. 2 SAC05 is the total amount for the service, promotion, allowance, or charge. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence. 3 SAC08 is the allowance or charge rate per unit. 4 SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge. 5 SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used. 6 SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion. 7 SAC16 is used to identify the language being used in SAC15. Comments: 1 SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction to further the code in SAC02. 2 In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes SAC Allowance or Charge Indicator M ID 1/1 M Code which indicates an allowance or charge for the service specified C Charge SAC Service, Promotion, Allowance, or Charge Code X ID 4/4 Code identifying the service, promotion, allowance, or charge 01/26/2015 V/R FCA US
36 C040 D240 Delivery Freight SAC Agency Qualifier Code X ID 2/2 Not SAC Agency Service, Promotion, Allowance, or Charge Code X AN 1/10 Not SAC Amount O N2 1/15 Monetary amount Total amount of charge SAC Allowance/Charge Percent Qualifier X ID 1/1 Not SAC Percent X R 1/6 Not SAC Rate O R 1/9 Not SAC Unit or Basis for Measurement Code X ID 2/2 Not SAC Quantity X R 1/15 Not SAC Quantity O R 1/15 Not SAC Allowance or Charge Method of Handling Code O ID 2/2 Not SAC Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Description of miscellaneous charge SAC Option Number O AN 1/20 Not SAC Description X AN 1/80 Not SAC Language Code O ID 2/3 Not 01/26/2015 V/R FCA US
37 Segment: TXI Tax Information Position: 050 Loop: SAC Optional Level: Summary Usage: Optional Max Use: 10 Purpose: To specify tax information Syntax Notes: 1 At least one of TXI02 TXI03 or TXI06 is required. 2 If either TXI04 or TXI05 is present, then the other is required. 3 If TXI08 is present, then TXI03 is required. Semantic Notes: 1 TXI02 is the monetary amount of the tax. 2 TXI03 is the tax percent expressed as a decimal. 3 TXI07 is a code indicating the relationship of the price or amount to the associated segment. Comments: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes TXI Tax Type Code M ID 2/2 M Code specifying the type of tax TXI Monetary Amount X R 1/18 Monetary amount TXI Percent X R 1/10 Percentage expressed as a decimal TXI Tax Jurisdiction Code Qualifier X ID 2/2 Code identifying the source of the data used in tax jurisdiction code TXI Tax Jurisdiction Code X AN 1/10 Code identifying the taxing jurisdiction TXI Tax Exempt Code X ID 1/1 Code identifying exemption status from sales and use tax TXI Relationship Code O ID 1/1 Code indicating the relationship between entities TXI Dollar Basis For Percent O R 1/9 Dollar basis to be used in the percent calculation of the allowance, charge or tax TXI Tax Identification Number O AN 1/20 Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state, county, etc.); often called a tax exemption number or certificate number TXI Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set 01/26/2015 V/R FCA US
38 Segment: CTT Transaction Totals Position: 070 Loop: Level: Summary Usage: Optional Max Use: 1 Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If either CTT03 or CTT04 is present, then the other is required. 2 If either CTT05 or CTT06 is present, then the other is required. Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes CTT Number of Line Items M N0 1/6 M Total number of line items in the transaction set CTT Hash Total O R 1/10 Not CTT03 81 Weight X R 1/10 Not CTT Unit or Basis for Measurement Code X ID 2/2 Not CTT Volume X R 1/8 Not CTT Unit or Basis for Measurement Code X ID 2/2 Not CTT Description O AN 1/80 Not 01/26/2015 V/R FCA US
39 Segment: SE Transaction Set Trailer Position: 080 Loop: Level: Summary Usage: Mandatory Max Use: 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. Data Element Summary Ref. Data Base User 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 01/26/2015 V/R FCA US
40 FCA US Service Net and Sprinter Invoice Example 1: EDI Format ST~810~0001 Interpretation Transaction Set Identifier Code = 810 (Invoice) Transaction Set Control Number = 0001 BIG~ ~53808~~~~~CN Date = 10/16/2004 Invoice Number = Transaction Type Code = CN (Credit Invoice) REF~AW~TRACKINGID REF~BF~ REF~19~DIV REF~BB~AUTHNUM REF~FQ~REPAIRORDER REF~VT~WD2YD REF~QQ~03-A REF~GT~C REF~4G~C N1~VN~FCA~92~ N1~EY~~24~ Reference Identification Qualifier = AW (Air Waybill Number) Reference Identification = TRACKINGID Reference Identification Qualifier = BF (Billing Center Identification) Reference Identification = Reference Identification Qualifier = 19 (Division Identifier) Reference Identification = DIV Reference Identification Qualifier = BB (Authorization Number) Reference Identification = AUTHNUM Reference Identification Qualifier = FQ (Form Number) Reference Identification = REPAIRORDER Reference Identification Qualifier = VT (Motor Vehicle ID Number) Reference Identification = D2YD Reference Identification Qualifier = QQ (Unit Number) Reference Identification = 03-A Reference Identification Qualifier = GT (Goods and Service Tax Registration Number) Reference Identification = C Reference Identification Qualifier = 4G (Provincial Tax Identification) Reference Identification = C Entity Identifier Code = VN (Vendor) Name = FCA Identification Code Qualifier = 92 (Assigned by Buyer or Buyer's Agent) Identification Code = Entity Identifier Code = EY (Employee Name) Identification Code Qualifier = 24 (Employer's Identification Number) Identification Code = /26/2015 V/R FCA US
41 FCA US Service Net and Sprinter Invoice Example 1: (continued) EDI Format N1~SF~ELMHURST DODGE INC Interpretation Entity Identifier Code = SF (Ship From) Name = ELMHURST DODGE INC N3~750 NORTH YORK ROAD Address Information = 750 NORTH YORK ROAD N4~ELMHURST~IL~ N1~ST~FDX EXP/CHICAGO- NORTH LOOP City Name = ELMHURST State or Province Code = IL Postal Code = Entity Identifier Code = ST (Ship To) Name = FDX EXP/CHICAGO- NORTH LOOP N3~3747 W HOWARD Address Information = 3747 W HOWARD N4~SKOKIE~IL~60076 DTM~214~ PID~F~GEN~~~REQUESTED REPAIR TEXT PID~F~SE~~~PARTS REPLACED City Name = SKOKIE State or Province Code = IL Postal Code = Date/Time Qualifier = 214 (Date of Repair/Service) Date = 10/13/2004 Item Description Type = F (Free-Form) Product/Process Characteristic Code = GEN (General Description) Description = REQUESTED REPAIR TEXT Item Description Type = F (Free-Form) Product/Process Characteristic Code = SE (Services) Description = PARTS REPLACED MEA~~~16740~DH Measurement Value = Unit or Basis for Measurement Code = DH (Miles) IT1~001~1~EA~-4.07~~VP~ AA~~~A3~ Assigned Identification = 001 Quantity Invoiced= 1 Unit or Basis for Measurement Code = EA Unit Price = Product/Service ID Qualifier = VP (Vendor's <Seller's> Part Number) Product/Service ID = AA Product/Service ID Qualifier = A3 (Locally Assigned Control Number) Product/Service ID = PID~F~08~~~SENSOR Item Description Type = F (Free-Form) Product/Process Characteristic Code = 08 (Product) Description = SENSOR 01/26/2015 V/R FCA US
42 FCA US Service Net and Sprinter Invoice Example 1: (continued) EDI Format ITD~14 Interpretation Terms Type Code = 14 (Previously agreed upon) SLN~1~~O~~~~~~ Assigned Identification = 1 Relationship Code = O (Information Only) Product/Service ID = TDS~-457~~~50 Amount = Amount =.50 TXI~GS~5 TXI~SP~5 Tax Type Code = GS (Goods and Services Tax) Monetary Amount = 5 Tax Type Code = SP (State/Provincial Tax) Monetary Amount = 5 CTT~1 Number of Line Items = 1 SE~28~0001 Number of Included Segments = 28 Transaction Set Control Number = /26/2015 V/R FCA US
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MARKET CENTER PROGRAM INVOICE (810) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MARKET CENTER PROGRAM INVOICE (810) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 004010
More informationARMY & AIR FORCE EXCHANGE SERVICE 810 Invoice
ARMY & AIR FORCE EXCHANGE SERVICE 810 Invoice 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 informationIMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR DISTRIBUTOR PURCHASE ORDER (850) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR DISTRIBUTOR PURCHASE ORDER (850) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 004010
More information810 Invoice. Introduction: Heading: Functional Group ID=IN
810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
More informationIMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS PAY AS BUILT INVENTORY ADVICE (846) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS PAY AS BUILT INVENTORY ADVICE (846) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 005020
More informationPittsburgh Glass Works. X Purchase Order Specifications
X-12 850 Purchase Order Specifications Contents 850 - Generic Purchase Order... 4 Introduction... 4 Heading... 4 Detail... 6 Summary... 6 Transaction Set Notes... 7 Segment: ST Transaction Set Header...
More informationAT&T Corporate Standard Specifications for New Horizons Wireline EDI 810 Invoice
810 Invoice Introduction: Functional Group ID=IN This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
More informationANSI X12 version Invoice
ANSI X12 version 4010 810 Invoice VERSION: 01.00.04 Author: EDI Administration Team Publication Date: 09/21/2007 Trading Partner: All Contact Information: O. C. Tanner Company EDI Administration Team 1930
More information810 Invoice Functional Group ID=IN
Health Industry Business Communications Council - ebusiness Committee 810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents
More informationIMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT MATERIAL CLAIM (847) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT MATERIAL CLAIM (847) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE
More informationARVINMERITOR P.O.'S 850 TRANSACTION SET WILL BE UTILIZED TO COMMUNICATE CONTRACTUAL INFORMATION REGARDING PART AND PRICE
ArvinMeritor 850 Purchase Order Functional Group ID=PO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850)
More informationNAPM RAIL INDUSTRY FORUM PURCHASE ORDER IMPLEMENTATION GUIDELINE FOR EDI
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 information810 Invoice. Introduction: Notes: Heading: Detail: Functional Group ID=IN
810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
More informationGENERAL MOTORS IMPLEMENTATION GUIDELINES FOR ANSI X12 TRANSACTION SET 850 PURCHASE ORDER
Corporate Information Standards GENERAL MOTORS IMPLEMENTATION GUIDELINES FOR ANSI X12 TRANSACTION SET 850 PURCHASE ORDER CORPORATE INFORMATION STANDARDS INFORMATION SYSTEMS & SERVICES GENERAL MOTORS CORPORATION
More informationX12 Implementation Guidelines For Outbound Purchase Order v2001 (850O)
X12 Implementation Guidelines For Outbound Purchase Order v2001 (850O) 850 Purchase Order Functional Group ID=PO Introduction: This Draft Standard for Trial Use contains the format and establishes the
More information810 Invoice. Introduction: Heading: Functional Group ID=IN
810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
More information810 Invoice. X12/V4010/810 : 810 Invoice. Version: 1.0 Final
810 Invoice X12/V4010/810 : 810 Invoice Version: 1.0 Final Author: EDI Department Company: D&H Distributors Publication: 03/01/2015 Trading Partner: Modified: 03/03/2016 Current: 03/03/2016 Notes EDI notes
More informationThis document defines the AAFES Business Requirements for the Purchase Order (REV 1).
850 Purchase Order Functional Group ID=PO Introduction: This X12 Transaction Set contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context
More informationElectronic Commerce Customer Guide
Electronic Commerce Customer Guide 811 Transaction Set (Version/Release 004010) Electronic Data Interchange - Electronic Funds Transfer AT&T Trading Partners Business Customers Value Added Networks Payment
More information812 Credit/Debit Adjustment. Author: Margie Waggoner Publication: 06/14/2013 Notes:
812 Credit/Debit Adjustment Author: Margie Waggoner Publication: 06/14/2013 Notes: Table of Contents 812 Credit/Debit Adjustment............................................................................................
More informationX12 Implementation Guidelines For. Outbound Non-Production (CPARS) Purchase Order Change Request (860)
X12 Implementation Guidelines For Outbound Non-Production (CPARS) Purchase Order Change Request (860) 860 Purchase Order Change Request - Buyer Initiated Introduction: Functional Group ID=PC This Draft
More informationFunctional information for outbound Invoice EDIFACT - INVOIC ANSI X12-810
Functional information for outbound Invoice EDIFACT - INVOIC ANSI X12-810 Micron has created a standard electronic invoice document format. This standard format includes specific details from the purchase
More information850 Purchase Order. Introduction: Heading: Functional Group ID=PO
850 Purchase Order Functional Group ID=PO Introduction: This Acquisition Instruction (AI) provides guidance specific to Defense Logistics Agency issued awards. This AI does not include anything that is
More informationInquiry/Advice 060 REF Reference Identification O 12. Detail: Pos.Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID LIN 10000
Inventory/Inquiry Advice EDI Guideline Version 4010 846 Inventory Inquiry/Advice Version 4010 Revised: February 2011 846 Inventory Inquiry/Advice Functional Group ID=IB Introduction: This Draft Standard
More information945 Warehouse Shipping Advice
945 Warehouse Shipping Advice Functional Group ID=SW Introduction: This transaction set is used to confirm shipment of product from a public warehouse. The transaction should always include the full order
More information850 Purchase Order. Introduction: Heading: Functional Group ID=PO
850 Purchase Order Functional Group ID=PO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within
More information843 Response to Request for Quotation
843 Response to Request for Quotation Functional Group ID=RR Introduction: This standard provides the format and establishes the data contents of a response to request for quotation transaction set.the
More information05/11/1998 Ingram Book Company Purchase Order INGRAM BOOK COMPANY Electronic Data Interchange Mapping Requirements PURCHASE ORDER (850)
INGRAM BOOK COMPANY Electronic Data Interchange Mapping Requirements PURCHASE ORDER (850) 1 2 850 Purchase Order Functional Group=PO This standard provides the format and establishes the data contents
More informationBERGEN BRUNSWIG DRUG COMPANY
810 Invoice BERGEN BRUNSWIG DRUG COMPANY Introduction: Functional Group ID=IN This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810)
More informationEDI X Implementation Guide. Advanced Ship Notice
EDI X12 004010 856 Implementation Guide Advanced Ship Notice Issued by: AM General Date: July 15, 2009 The information disclosed herein is proprietary to AM GENERAL and is not to be used or disclosed to
More information325 Consolidation of Goods In Container
325 Consolidation of Goods In Container Functional Group ID=SO Introduction: This Draft Standard for Trial Use contains the format and establishes the data content of the Consolidation of Goods in Container
More informationIMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS SHIPPING INSTRUCTIONS (304) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS SHIPPING INSTRUCTIONS (304) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE T.D.C.C. Ocean
More informationElectronic Data Interchange 850 Pre-Pack Purchase Order (VICS Version ) March Powered By:
Electronic Data Interchange 850 Pre-Pack Purchase Order (VICS Version - 4010) March 2011 Powered By: Purpose This document provides detailed guidelines and conventions for implementing electronic purchase
More information862 Shipping Schedule
862 Shipping Schedule Functional Group ID=SS Introduction: This standard provides the format and establishes the data contents of a shipping schedule transaction set within the context of an electronic
More informationEDI Specifications Guide. 850 Supplier Purchase Order
850 Supplier Purchase Order 850 Purchase Order - Functional Group=PO VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific Supplier Purchase
More information944 Warehouse Stock Transfer Receipt Advice
944 Warehouse Stock Transfer Receipt Advice Introduction: Functional Group ID=RE This Draft Standard for Trial Use contains the format and establishes the data contents of the Warehouse Stock Transfer
More information830 Planning Schedule with Release Capability
Changes made to specs on 07/20/11 Identified FST05 as the Need Date from Honeywell (Mandatory from Honeywell) Changes made to specs on 11/01/08 Replacing the NTE segment with REF segment. Upgrading to
More informationFunctional information for inbound EDI purchase order (PO) EDIFACT - ORDERS ANSI X12-850
Functional information for inbound EDI purchase order (PO) EDIFACT - ORDERS ANSI X12-850 In order for Micron to best automate the processing of inbound orders from our customers, we have created a standard
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 informationWeis Markets, Inc. Mapping Specifications 810 Invoice
Weis Markets, Inc. Mapping Specifications 810 Invoice SEG ID REQ.DES TYPE DESCRIPTION BIG M H Beginning Segment for Invoice N1 O H Name N2 O H Additional Name Information N3 O H Address Information N4
More informationX12 Implementation Guidelines For Inbound Price Catalog v (832I)
X12 Implementation Guidelines For Inbound Price Catalog v003010 (832I) 832 Price/Sales Catalog Functional Group ID=SC Introduction: This standard provides the format and establishes the data contents of
More information945 Warehouse Shipping Advice
945 Warehouse Shipping Advice X12/V4030/945: 945 Warehouse Shipping Advice Version: 1.1 Author: Abbott Nutrition ebusiness Company: Abbott Nutrition Created: 11/29/2012 Current: 11/29/2012 Notes: Table
More informationEDI Implementation Guide 850 Purchase Orders Version 4010 Effective Date: 25 July 2008
EDI Implementation Guide 850 Purchase Orders Version 4010 Effective Date: 25 July 2008 Michaels Stores, Inc. and Subsidiaries and Affiliates 8000 Bent Branch Dr. Irving, TX 75063 (972) 409-1300 850 Purchase
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 information846 Inventory Availability
846 Inventory Availability X12/V4010/846: 846 Inventory Availability Version: 4.0 Final Author: John Parkhill Company: Burlington Stores Publication: 6/16/2017 Trading Partner: Direct to Consumer Notes:
More informationIntroduction to the DLMS 810L, Logistics Bill
Introduction to the DLMS 810L, This briefing provides basic training on how to interpret the DLMS 810L IC, including an understanding of the table and looping structure concepts. The intent of the briefing
More informationEDI Implementation Guide 810 Invoice Accounting ANSI X12 Version 3010
810 Invoice Accounting ANSI X12 Version 3010 Transaction: 810 Page: 810-000 Description: Invoice Release Date: 05/30/97 Transaction Description Page No. 810 Invoice Purpose.................................
More information811 Consolidated Service Invoice/Statement
811 Consolidated Service Invoice/Statement Introduction: Functional Group ID=CI This Draft Standard for Trial Use contains the format and establishes the data contents of the Consolidated Service Invoice/Statement
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 information945 Warehouse Shipping Advice Version X12 Functional Group=SW
945 Warehouse Shipping Advice Version 005010 X12 Functional Group=SW All X12 Standards, required and conditional segments / elements must be mapped. W06 Warehouse Shipment Identification Pos: 020 Max:
More informationEDI Implementation Guide 860 Purchase Order Changes Version 4010 Effective Date: 25 July 2008
EDI Implementation Guide 860 Purchase Order Changes Version 4010 Effective Date: 25 July 2008 Michaels Stores, Inc. and Subsidiaries and Affiliates 8000 Bent Branch Dr. Irving, TX 75063 (972) 409-1300
More information856 Ship Notice/Manifest
856 Ship Notice/Manifest X12/V4010/856: 856 Ship Notice/Manifest Version: 5.0 4010 Draft Company: itradenetwork -dc Publication: 6/19/2015 Trading Partner: itn Supplier Version Notes: Universal 856 Draft
More informationAdvanced Ship Notice Message 856 X12/V3040/856: 856 Advanced Ship notice
Advanced Ship Notice Message 856 X12/V3040/856: 856 Advanced Ship notice Author: Publication: Trading Partner: Notes: Seagate B2B Outbound from Seagate to trading partner Cust856 1 2012 Seagate Technology
More informationElectronic Data Interchange. 850 Purchase Order. Version 4030
Electronic Interchange 850 Purchase Order Version 4030 March 2005 Table of Contents ISA Interchange Control Header... 2 GS Functional Group Header... 3 ST Transaction Set Header... 4 BEG Beginning Segment
More information870 Order Status Report (Version 4010) Target Corporation Common
870 Order Status Report (Version 4010) Target Corporation Common Revised: August 26, 2003 Introduction: Functional Group ID=RS This Draft Standard for Trial Use contains the format and establishes the
More informationMenards Implementation Guidelines
Menards Implementation Guidelines 810 Invoice 3/17/2006 Table of Contents q Menard, Inc. Electronic Commerce Information General contact and setup information you will need to properly set up Menards in
More informationCOMMERCIAL AIRPLANES GROUP. SUPPLIER NETWORK Electronic Data Interchange. PCOS (Purchasing/Control On-line System) EDI Implementation Guide
COMMERCIAL AIRPLANES GROUP SUPPLIER NETWORK Electronic Data Interchange PCOS (Purchasing/Control On-line System) EDI Implementation Guide Revision Number 4 Issued: January 28, 2001 . Telephone Contact
More information211 Motor Carrier Bill of Lading
211 Motor Carrier Bill of Lading Functional Group ID=BL Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Motor Carrier Bill of Lading Transaction
More informationDSD Invoice TRANSACTION SET 810 VERSION 4010
DSD Invoice TRANSACTION SET 810 VERSION 4010 EDI provides an efficient means for our trading partner to submit invoices for payment. Receipt of the invoices, as well as an indication of any EDI-related
More information820 Payment Order/Remittance Advice
820 Payment Order/Remittance Advice Functional Group ID=RA Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Payment Order/Remittance Advice Transaction
More informationLOOP-ID SAC LOOP REPEAT 25 LOOP-ID N9 LOOP REPEAT 1000 LOOP-ID N1 LOOP REPEAT 200 LOOP-ID PO1 LOOP REPEAT LOOP-ID CTP LOOP REPEAT >1
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 AN ELECTRONIC DATA
More information810 Invoice ANSI X.12 Version 5010
810 Invoice SI X.12 Version 5010 *** HEADE AEA *** SEG SEGMENT EQ MAX LOOP NAME DES USE EPEAT ISA Interchange Control Header M 1 GS Functional Group Header M 1 ST Transaction Set Header M 1 BIG Beginning
More informationEDI Specifications Version 4010 / Transaction Set 858 Shipment Information
EDI Specifications Version 4010 / Transaction Set 858 Shipment Information Copyright 1995-2003 Transportation Solutions Inc; all rights reserved. This document and all intellectual property including but
More informationInbound 855 (P.O. Acknowledgment) X12 Specification for Release
Inbound 855 (P.O. Acknowledgment) X12 Specification for Release 003040 The purpose of this document is to describe the suggested X12 specification to be used to transport Purchase Order Acknowledgment
More information211 Motor Carrier Bill of Lading
211 Motor Carrier Bill of Lading X12/V4060/211 : 211 Motor Carrier Bill of Lading Version: 2.0 Final Author: Thomas A. Smith Company: Burlington Coat Factory Publication: 12/26/2012 Trading Partner: Notes:
More informationSome optional segments or data elements may not be present in this documentation.
The goal of this documentation is to present the utilization of EDI 850 as an efficiency tool in the placement of product orders between trading partners in adherence to the retail industry standards.
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 information850 - Purchase Order. Caterpillar Inc.
850 - Purchase Order Caterpillar Inc. PREFACE... 3 TRANSACTION SEQUENCE WITH LEVELS... 4 ASC X12 REQUIRED CONTROL DATA... 5 SEGMENT/ELEMENT DEFINITION EXPLANATION... 6 ISA-INTERCHANGE CONTROL HEADER SEGMENT...
More informationWarehouse Inventory Adjustment Advice - 947
947 Warehouse Inventory Adjustment Advice - 4010 Version: 1.0 Author: V4010 1 947 Warehouse Inventory Adjustment Advice Functional Group=AW This Draft Standard for Trial Use contains the format and establishes
More information852 Product Activity Data Version 04010
1830 Route 130 North Burlington, NJ 08016 Phone: (609) 387-7800 Fax: (609) 387-2764 852 Product Activity Version 04010 Table of Content Introduction...1 ST Transaction Set Header...1 XQ Reporting Date/Action...2
More informationThis document defines the AAFES Business Requirements for the Ship Notice/Manifest.
856 Ship Notice/Manifest Functional Group ID=SH Introduction: This X12 Transaction Set contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within
More information810 Invoice Ver/Rel Electronic Data I nterchange. Utility Industry Group Implementation Standard. For
Utility Industry Group Implementation Standard For Electronic Data I nterchange TRANSACTION SET 810 Invoice Ver/Rel 004010 Outbound to Customer or Energy Service Provider 810 VERSION 004 RELEASE 010 A
More informationElectronic Data Interchange Implementation Guide
Electronic Data Interchange Implementation Guide ANSI X12 Page 1 of 12 Hill- Rom EDI Trading Partner Information Hill-Rom EDI Contact: Judy Murrell Phone Number: 812-934-1372 Email Address: judy.murrell@hill-rom.com
More informationLowe's EDI. 860 Purchase Order Change Request for PROCUREMENT Version: 5040
Lowe's EDI 860 Purchase Order Change Request for PROCUREMENT Version: 5040 Modified: 7/16/2013 Table of Contents 860 Purchase Order Change Request - Buyer Initiated... 3 ISA Interchange Control Header...
More information855 PO Acknowledgment X12 Version 4010
855 PO Acknowledgment X12 Version 4010 Functional Group ID = PR Use: JIT PO Acknowledgments Transaction Description This standard provides the format and establishes the data contents of a purchase order
More informationEDI Implementation Guide
TECO Energy EDI Implementation Guide Transaction Set 810 - Utility to Customer Version 4010.3 Jan 17, 2017 TECO Energy 1 Summary of Changes August 24, 2001 Version 1.0 - Initial Release 810 y. 4010 May
More informationK&G System Migration EDI SPECIFICATION
K&G System Migration EDI SPECIFICATION 850 PURCHASE ORDER Version 4010VICS Qualifier Type: 12 Qualifier : 4043517987 Transaction Sets Transaction sets must be enclosed in X.12 standard interchange (ISA-IEA)
More information940 Warehouse Shipping Order
940 Warehouse Shipping Order UCS/V4010/940: 940 Warehouse Shipping Order Company: General Mills Modified: 9/9/2017 Notes: Table of Contents 940 Warehouse Shipping Order.............................................................................................................
More information880 Grocery Products Invoice
880 Grocery Products Invoice Control Segments ISA Interchange Control Header ISA*00* *00* *08*9269070010 *08*YOUR ID*199880911*1954*U*00401*000026764*0*P*> ISA01 M Author Info Qualifier 00 No Authorization
More informationFILE LAYOUT FOR 855 EDI TRANSACTION (OUTBOUND)
FILE LAYOUT FOR 855 EDI TRANSACTION (OUTBOUND) VERSION 4010 Page 1 of 29 OVERVIEW PURPOSE OF TRANSACTION Inbound (Hubbell to Trading Partner) Purchase Order Acknowledgement VERSION Version 1 SUPPLIER Hubbell
More information180 Return Merchandise Authorization and Notification
180 Return Merchandise Authorization and Notification Functional Group ID=AN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the return Merchandise
More informationWarehouse Shipping Advice - 945
945 Warehouse Shipping Advice - 4010 INBOUND Version: 1.0 Author: Modified: 01/15/2004 V4010 1 945 Warehouse Shipping Advice Functional Group=SW This Draft Standard for Trial Use contains the format and
More informationLOOP-ID SAC LOOP REPEAT 25 LOOP-ID N9 LOOP REPEAT 1000 LOOP-ID N1 LOOP REPEAT 200 LOOP-ID PO1 LOOP REPEAT LOOP-ID CTP LOOP REPEAT >1
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 AN ELECTRONIC DATA
More information211 Motor Carrier Bill of Lading
211 Motor Carrier Bill of Lading X12/V4010/211 : 211 Motor Carrier Bill of Lading Version: 4.0 Final Author: Thomas A. Smith Company: Burlington Stores Publication: 10/24/2014 Trading Partner: Carrier
More informationX12 Implementation Guidelines For. Inbound Primary Metals Advance Ship Notice V002002FORD. (856i Primary Metals)
X12 Implementation Guidelines For Inbound Primary etals Advance Ship Notice V002002FORD (856i Primary etals) FD856PI (002002FORD) 1 January 6, 2010 856 Ship Notice/anifest Functional Group ID=SH Introduction:
More informationThyssenKrupp Presta Danville, LLC. EDI Implementation Guidelines for 830 Planning Schedule with Release Capability ANSI X-12 version/release
ThyssenKrupp Presta Danville, LLC EDI Implementation Guidelines for 830 Planning Schedule with Release Capability ANSI X-12 version/release 004010 Issued by: IT SAP Team Revision Date: 02/05/2010 Subject:
More informationEDI Specifications Version 4010 / Transaction Set 110 Air Freight Details and Invoice
EDI Specifications Version 4010 / Transaction Set 110 Air Freight Details and Invoice Copyright 1995-2003 Transportation Solutions Inc; all rights reserved. This document and all intellectual property
More informationACE HARDWARE 856 ADVANCED SHIP NOTICE ANSI X
ACE HARDWARE 856 ADVANCED SHIP NOTICE ANSI X12 4010 *NOTES: PLEASE REFERENCE 1 PO PER 856 TRANSACTION SET (ST-SE ENVELOPE). THE 856 SHOULD BE SENT THE SAME DAY THE ORDER IS SHIPPED. MAKE SURE ALL SHIP
More information856 Ship Notice/Manifest
856 Ship Notice/Manifest Functional Group ID=SH Introduction: KOSTAL 4010 Inbound 856 Trading Partner Specs Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments Must Use 010
More information204 Motor Carrier Load Tender X12 Version 4010 Outbound from Advance Auto
204 Motor Carrier Load Tender X12 Version 4010 Outbound from Advance Auto Version: 2.0 Author: Advance Auto Parts Company: Advance Auto Parts Publication: 2/16/16 i Publication Record Rev. Date Author
More informationPurchase Order (850) Transaction Set
Purchase Order (850) Transaction Set EDI IMPLEMENTATION GUIDE X12 VERSION 4010 September 2, 2008 Document Status Document Number etoys 850 4010 IG 1_0 Version 1.0 File Name Issue Date June 12, 2003 Owner
More information315 Status Details (Ocean)
OCEAN TRANSPORTATION INDUSTRY GUIDE TO 004010 315 APRIL 1998 004010 315 315 Status Details (Ocean) FUNCTIONAL GROUP ID = QO This Draft Standard for Trial Use contains the format and establishes the data
More informationJCPenney 856 Ship Notice/Manifest Version 4030
TABLE OF CONTENTS JCPenney Mapping Differences between Versions 3060 and 4030... 1.2 Transaction Set Purpose... 1.3 Pick Pack Shipment Segment Hierarchy... 1.3 Standard Pack Shipment Segment Hierarchy...
More information947 Warehouse Inventory Adjustment Advice
947 Warehouse Inventory Adjustment Advice Introduction: Functional Group ID=AW This Draft Standard for Trial Use contains the format and establishes the data contents of the Warehouse Inventory Adjustment
More informationEDI Specifications Version 4010 / Transaction Set 310 Freight Receipt and Invoice (Ocean)
EDI Specifications Version 4010 / Transaction Set 310 Freight Receipt and Invoice (Ocean) Copyright 1995-2003 Transportation Solutions Inc; all rights reserved. This document and all intellectual property
More information856 Advance Ship Notice/ Supplier Implementation Guide Getting Started with EDI
856 Advance Ship Notice/ Supplier Implementation Guide Getting Started with EDI 1 Contents Introduction to EDI 856 Advance Ship Notice / 824 Application Advice...2 Introduction.. 3 What is EDI...4 What
More informationEDI 214 Carrier Shipment Status Message Version
Ryder Transportation Management 1 Ryder Transportation EDI Electronic Data Interchange EDI 214 Carrier Shipment Status Message Version 004010 Document: Version: 3.0 Document Date: Nov. 2, 2015 Ryder Transportation
More informationCSX 322 Intermodal Event Report. Version:
CSX 322 Intermodal Event Report Version: 004010 Created: 10/5/2005 Modified: 11/5/2009 Current: 11/5/2009 Table of Contents 322 Terminal Operations and Intermodal Ramp Activity... 1 ISA Interchange Control
More informationMAGNA. ANSI X12 - Version AIAG. Advanced Shipping Notice / Manifest [856] IMPLEMENTATION GUIDE
MAGNA ANSI X12 - Version 003060 AIAG Advanced Shipping Notice / Manifest [856] IMPLEMENTATION GUIDE This guide has been produced by Magna International Inc. This Guideline is developed to be compliant
More informationEDI IMPLEMENTATION GUIDE FOR DOMESTIC VENDORS VALUE ADDED NETWORK: GXS INTERCHANGE ID QUAL: 12 INTERCHANGE ID #:
EDI IMPLEMENTATION GUIDE FOR DOMESTIC VENDORS VALUE ADDED NETWORK: GXS INTERCHANGE ID QUAL: 12 INTERCHANGE ID #: 2816465200 EDI DEPARTMENT: EDISupport@academy.com 1 TRANSACTION SET: 850 Purchase Order
More information