IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT MATERIAL CLAIM (847) TRANSACTION SET
|
|
- Gwendolyn O’Neal’
- 6 years ago
- Views:
Transcription
1 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
2 847 Material Claim Introduction: Functional Group ID=MX This Draft Standard for Trial Use contains the format and establishes the data contents of the Material Claim Transaction Set (847) for use within the context of an Electronic Data Interchange (EDI) environment. This standard provides trading partners a means to advise each other of costs and charges involved in fabricated or purchased material or both which has been deemed damaged, unusable, or obsolete. This transaction set is not to be used to submit claims against transportation or insurance carriers. The Material Claim Transaction Set (847) can be used in the following ways: (1) for a seller of material to advise the buyer of costs and charges resulting from order cancellation or change and must be based on the buyer's authorization to fabricate or purchase material or both; (2) for a buyer of material to advise the seller of costs and charges resulting from material which was deemed damaged or unusable. Notes: FCA US uses the Material Claim 847 transaction set for Commodity Procurement trading partners to charge back to FCA US various problem conditions with FCA US shipments. History of Change: 08/2008: Transition to Chrysler LLC with removal of references to Daimler 07/30/2010: Name change from Chrysler LLC to Chrysler Updated Address 02/24/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 BHT Beginning of Hierarchical Transaction M M AMT Monetary Amount M M NTE Note/Special Instruction O DTM Date/Time/Period O Not PER Administrative Communications O Not 3 Contact 070 CUR Currency O Not 1 LOOP ID - N N1 Name O N2 Additional Name Information O Not N3 Address Information O Not 2 02/24/2015 V/R FCA US
3 110 N4 Geographic Location O Not REF Reference Numbers O Not PER Administrative Communications Contact O Not 3 Detail: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments LOOP ID - HL > HL Hierarchical Level M M LIN Item Identification M M NTE Note/Special Instruction O Not PID Product/Item Description O Not QTY Quantity O Not MEA Measurements O SHP Shipped/Received Information O Not 5 n REF Reference Numbers O DTM Date/Time/Period O Not 10 n2 100 PKG Marking, Packaging, Loading O Not CTP Pricing Information O Not SAC Service, Promotion, Allowance, or Charge Information O 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 Numbers O Not PER Administrative Communications Contact O Not DTM Date/Time/Period O Not 10 c1 Summary: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments CTT Transaction Totals O 1 n SE Transaction Set Trailer M M 1 Transaction Set Notes 1. The SHP segment is used to show the material's shipped quantity in comparison to the authorization quantities. 2. The DTM segment is used to show dates for the authorization to fabricate or purchase materials. 3. Number of Line Items (CTT01) is the accumulation of the number of HL segments. Hash Total (CTT02) is not used. Transaction Set Comments 02/24/2015 V/R FCA US
4 1. The DTM segment is used to provide contact availability times. 02/24/2015 V/R FCA US
5 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 847 X12.63 Material Claim 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 02/24/2015 V/R FCA US
6 Segment: BHT Beginning of Hierarchical Transaction Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time Syntax Notes: Semantic Notes: 1 BHT03 is the number assigned by the originator to identify the transaction within the originator's business application system. 2 BHT04 is the date the transaction was created within the business application system. 3 BHT05 is the time the transaction was created within the business application system. Comments: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes BHT Hierarchical Structure Code M ID 4/4 M Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set 0002 Shipment, Order, Item, Packaging BHT Transaction Set Purpose Code M ID 2/2 M Code identifying purpose of transaction set 00 Original BHT 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. Original FCA US Invoice Number: invoice number from the BIG segment on the original FCA US 810 invoice. format: M AN 01/12 BHT Date M DT 6/6 M Date (YYMMDD) Transaction set creation date BHT Time O TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) Transaction set creation time 02/24/2015 V/R FCA US
7 Segment: AMT Monetary Amount Position: 030 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the total monetary amount Syntax Notes: Semantic Notes: Comments: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes AMT Amount Qualifier Code M ID 1/2 M Code to qualify amount CM Claimant Requested Total AMT Monetary Amount M R 1/15 M Monetary amount Total amount of claim 02/24/2015 V/R FCA US
8 Segment: NTE Note/Special Instruction Position: 040 Loop: Level: Heading Usage: Optional Max Use: 100 Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction Syntax Notes: Semantic Notes: Comments: 1 The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processable. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment. Notes: This segment should be used to tranmsit additional claim information and comments. FCA US requires at least one iteration with a max of four iterations of this segment. Upper case only. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes NTE Note Reference Code O ID 3/3 Code identifying the functional area or purpose for which the note applies ACI Additional Claim Information NTE02 3 Free Form Message M AN 1/60 M Free-form text 02/24/2015 V/R FCA US
9 Segment: N1 Name Position: 080 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: This segment will be used for transmission of the FCA US assigned supplier code. Data Element Summary Ref. Data Base User 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 SU Supplier/Manufacturer N Name X AN 1/35 Not N Identification Code Qualifier X ID 1/2 Must Use 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 Use Code identifying a party or other code FCA US assigned supplier code N Entity Relationship Code O ID 2/2 Not N Entity Identifier Code O ID 2/2 Not 02/24/2015 V/R FCA US
10 Segment: HL Hierarchical Level Position: 010 Loop: HL Mandatory Level: Detail Usage: Mandatory Max Use: 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. Data Element Summary Ref. Data Base User 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 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 9 Line Detail HL Hierarchical Child Code O ID 1/1 Code indicating whether if there are hierarchical child data segments subordinate to the level being described. 0 No Subordinate HL Segment in This Hierarchical Structure. 02/24/2015 V/R FCA US
11 Segment: LIN Item Identification Position: 020 Loop: HL Mandatory Level: Detail Usage: Mandatory Max Use: 1 Purpose: To specify basic item identification data Syntax Notes: 1 If LIN04 is present, then LIN05 is required. 2 If LIN06 is present, then LIN07 is required. 3 If LIN08 is present, then LIN09 is required. 4 If LIN10 is present, then LIN11 is required. 5 If LIN12 is present, then LIN13 is required. 6 If LIN14 is present, then LIN15 is required. 7 If LIN16 is present, then LIN17 is required. 8 If LIN18 is present, then LIN19 is required. 9 If LIN20 is present, then LIN21 is required. 10 If LIN22 is present, then LIN23 is required. 11 If LIN24 is present, then LIN25 is required. 12 If LIN26 is present, then LIN27 is required. 13 If LIN28 is present, then LIN29 is required. 14 If LIN30 is present, then LIN31 is required. Semantic Notes: 1 LIN01 is the line item identification Comments: 1 See the Data Dictionary for a complete list of ID's. 2 LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes LIN Assigned Identification O AN 1/11 Not LIN Product/Service ID Qualifier M ID 2/2 M Code identifying the type/source of the descriptive number used in Product/Service ID (234) CG Commodity Grouping LIN Product/Service ID M AN 1/30 M Identifying number for a product or service Commodity Type: 'S' = Steel 'P' = Plastic 'T' = Bar/Tube LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not 02/24/2015 V/R FCA US
12 LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not 02/24/2015 V/R FCA US
13 LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not LIN Product/Service ID Qualifier O ID 2/2 Not LIN Product/Service ID O AN 1/30 Not 02/24/2015 V/R FCA US
14 Segment: MEA Measurements Position: 060 Loop: HL Mandatory Level: Detail Usage: Optional Max Use: 10 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: Use to transmit total claim weight. 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 Code identifying a specific product or process characteristic to which a measurement applies WT Weight MEA Measurement Value X R 1/10 The value of the measurement Claim weight. Use two decimal positions with explicit decimal. If weight from original invoice is in Hundredweight, this value should be in Hundredweight. 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 Use unit of measure from original invoice. CW Hundred Pounds (CWT) LB Pound C Exponent O R 1/15 Not C Multiplier O R 1/10 Not 02/24/2015 V/R FCA US
15 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 02/24/2015 V/R FCA US
16 Segment: REF Reference Numbers Position: 080 Loop: HL Mandatory Level: Detail Usage: Optional Max Use: 12 Purpose: To specify identifying numbers. Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes REF Reference Number Qualifier M ID 2/2 M Code qualifying the Reference Number. 1X Complaint Code D9 Claim Number DL Debit Memo REF Reference Number X AN 1/30 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. If REF01 = '1X', one of the following two position codes: '23' = Miscellaneous '45' = Steel not removed from truck '51' = Defective Material '54' = Price Discrepancy '55' = Weight Discrepancy '57' = Duplicate Billing '58' = Proof of Delivery required '64' = Matl not received '67' = Billing error If REF01 = 'DL', the stamper assigned debit memo number; it must be unique and should be 10 positions or less with no embedded blanks. REF Description X AN 1/80 Not 02/24/2015 V/R FCA US
17 Segment: SAC Service, Promotion, Allowance, or Charge Information Position: 120 Loop: HL Mandatory Level: Detail Usage: Optional Max Use: 10 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. 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 SAC10 alone is used to indicate a specific quantity which could be a dollar amount, that is applicable to service, promotion, allowance or charge. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge. 4 SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used. 5 SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion. 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 a "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09. Notes: The following examples should be followed for each of the different charges: Base Charge: SAC~C~A520~~~ GST: SAC~C~D360~~~39939 Handling: SAC~C~D500~~~32580~~~10.00~DO~32.58 Other: SAC~C~F050~~~32580~~~18.00~DO~18.10 Scrap: SAC~C~G660~~~-31500~~~-4.5~CW~70.00 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 02/24/2015 V/R FCA US
18 SAC Service, Promotion, Allowance, or Charge Code X ID 4/4 Code identifying the service, promotion, allowance, or charge A520 D360 Base Charge Goods and Services Tax Charge D500 Handling F050 Other (See related description) G660 Scrap Allowance 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 If SAC02 = 'A520', the base charge for the material; If SAC02 = 'D360', the total amount of the Goods and Services Tax; If SAC02 = 'D500', the total handling charge (extended: SAC08 * SAC10); If SAC02 = 'F050', the total 'other' charges (extended: SAC08 * SAC10); If SAC02 = 'G660', the total scrap charge (extended: SAC08 * SAC10) SAC Allowance/Charge Percent Qualifier X ID 1/1 Not SAC Allowance or Charge Percent X R 1/6 Not SAC Allowance or Charge Rate O R 1/9 Allowance or Charge Rate per Unit If SAC02 = 'A520' or 'D360', this element should not be used; If SAC02 = 'D500', the Handling Rate; If SAC02 = 'F050', Other chargeable price; If SAC02 = 'G660', Scrap price SAC 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 If SAC02 = 'A520' or 'D360', this element should not be used. 01 Actual Pounds CW Hundred Pounds (CWT) DO Dollars, U.S. HR Hours SAC Allowance or Charge Quantity O R 1/10 Quantity basis when allowance or charge quantity is different from the purchase order or invoice quantity Use two decimal positions with actual decimal. If SAC02 = 'A520' or 'D360', this element should not be used. SAC Allowance or Charge Quantity O R 1/10 Not 02/24/2015 V/R FCA US
19 SAC Allowance or Charge Method of Handling Code O ID 2/2 Not SAC Reference Number X AN 1/30 Not SAC Option Number O AN 1/20 Not SAC Description O AN 1/80 Not 02/24/2015 V/R FCA US
20 Segment: CTT Transaction Totals Position: 010 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 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. 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 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. 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 CTT Description O AN 1/80 Not 02/24/2015 V/R FCA US
21 Segment: SE Transaction Set Trailer Position: 020 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 02/24/2015 V/R FCA US
22 FCA US Commodity Procurement Material Claim Example 1: EDI Format ST~847~0001 Steel Chargeback for Defective Material Interpretation Transaction Set Identifier Code = 847 (X12.63 Material Claim) Transaction Set Control Number = 0001 BHT~0002~00~ ~050823~1430 AMT~CM~ Hierarchical Structure Code = 0002 (Shipment, Order, Item, Packaging) Transaction Set Purpose Code = 00 (Original) Reference Number = Date = 08/23/2005 Time = 2:30 PM Amount Qualifier Code = CM (Claimant Requested Total) Monetary Amount = NTE~ACI~THIS SEGMENT SHOULD BE USED TO CONVEY ADDITIONAL INFORMATION Note Reference Code = ACI (Additional Claim Information) Free Form Message = THIS SEGMENT SHOULD BE USED TO CONVEY ADDITIONAL INFORMATION NTE~ACI~NOT CONTAINED IN THE NORMAL FORMAT OF THE TRANSACTION SET. Note Reference Code = ACI (Additional Claim Information) Free Form Message = NOT CONTAINED IN THE NORMAL FORMAT OF THE TRANSACTION SET. NTE~ACI~ITS PLACEMENT SHOULD BE AT THE HEADER LEVEL ONLY. THE Note Reference Code = ACI (Additional Claim Information) Free Form Message = ITS PLACEMENT SHOULD BE AT THE HEADER LEVEL ONLY. THE NTE~ACI~PRESENCE OF THIS SEGMENT COULD AID IN CLAIM PROCESSING. Note Reference Code = ACI (Additional Claim Information) Free Form Message = PRESENCE OF THIS SEGMENT COULD AID IN CLAIM PROCESSING. N1~SU~~92~24518 Entity Identifier Code = SU (Supplier/Manufacturer) Identification Code Qualifier = 92 (Assigned by Buyer or Buyer's Agent) Identification Code = /24/2015 V/R FCA US
23 FCA US Commodity Procurement Material Claim Example 1: EDI Format Steel Chargeback for Defective Material (continued) Interpretation HL~1~~9~0 Hierarchical ID Number = 1 Hierarchical Level Code = 9 (Line Detail) Hierarchical Child Code = 0 (No Subordinate HL Segment in This Hierarchical Structure.) LIN~~CG~S MEA~~WT~8.47~CW REF~1X~51 REF~D9~7391 REF~DL~711C700 SAC~C~A520~~~27400 SAC~C~F050~~~2000~~~20.00~DO~1.00 SAC~C~G660~~~-2541~~~-3.00~CW~8.47 Product/Service ID Qualifier = CG (Commodity Grouping) Product/Service ID = S Measurement Qualifier = WT (Weight) Measurement Value = 8.47 Unit or Basis for Measurement Code = CW (Hundred Pounds <CWT>) Reference Number Qualifier = 1X (Complaint Code) Reference Number = 51 Reference Number Qualifier = D9 (Claim Number) Reference Number = 7391 Reference Number Qualifier = DL (Debit Memo) Reference Number = 711C700 Allowance or Charge Indicator = C (Charge) Service, Promotion, Allowance, or Charge Code = A520 (Base Charge) Amount = Allowance or Charge Indicator = C (Charge) Service, Promotion, Allowance, or Charge Code = F050 (Other <See related description>) Amount = Allowance or Charge Rate= Unit or Basis for Measurement Code = DO (Dollars, U.S.) Allowance or Charge Quantity = 1.00 Allowance or Charge Indicator = C (Charge) Service, Promotion, Allowance, or Charge Code = G660 (Scrap Allowance) Amount = Allowance or Charge Rate= Unit or Basis for Measurement Code = CW (Hundred Pounds <CWT>) Allowance or Charge Quantity = 8.47 CTT~1~26859 Number of Line Items = 1 Hash Total = /24/2015 V/R FCA US
24 FCA US Commodity Procurement Material Claim Example 1: EDI Format Steel Chargeback for Defective Material (continued) Interpretation SE~19~0001 Number of Included Segments = 19 Transaction Set Control Number = /24/2015 V/R FCA US
25 FCA US Commodity Procurement Material Claim Example 2: EDI Format ST~847~0002 Plastic Chargeback (Weight discrepancy) Interpretation Transaction Set Identifier Code = 847 (X12.63 Material Claim) Transaction Set Control Number = 0002 BHT~0002~00~ ~050828~1615 AMT~CM~81.60 Hierarchical Structure Code = 0002 (Shipment, Order, Item, Packaging) Transaction Set Purpose Code = 00 (Original) Reference Number = Date = 08/28/2005 Time = 4:15 PM Amount Qualifier Code = CM (Claimant Requested Total) Monetary Amount = NTE~ACI~THIS SEGMENT SHOULD BE USED AT THE HEADER LEVEL TO CONVEY Note Reference Code = ACI (Additional Claim Information) Free Form Message = THIS SEGMENT SHOULD BE USED AT THE HEADER LEVEL TO CONVEY NTE~ACI~ADDITIONAL CLAIM INFORMATION. A MAX OF FOUR ITERATIONS Note Reference Code = ACI (Additional Claim Information) Free Form Message = ADDITIONAL CLAIM INFORMATION. A MAX OF FOUR ITERATIONS NTE~ACI~MAY BE USED. THE USE OF THE NTE SEGMENT COULD POTENTIALLY Note Reference Code = ACI (Additional Claim Information) Free Form Message = MAY BE USED. THE USE OF THE NTE SEGMENT COULD POTENTIALLY NTE~ACI~AID IN CLAIMS PROCESSING. N1~SU~~92~66592 Note Reference Code = ACI (Additional Claim Information) Free Form Message = AID IN CLAIMS PROCESSING. Entity Identifier Code = SU (Supplier/Manufacturer) Identification Code Qualifier = 92 (Assigned by Buyer or Buyer's Agent) Identification Code = HL~1~~9~0 Hierarchical ID Number = 1 Hierarchical Level Code = 9 (Line Detail) Hierarchical Child Code = 0 (No Subordinate HL Segment in This Hierarchical Structure.) 02/24/2015 V/R FCA US
26 FCA US Commodity Procurement Material Claim Example 2: EDI Format LIN~~CG~P Plastic Chargeback (Weight discrepancy) (continued) Interpretation Product/Service ID Qualifier = CG (Commodity Grouping) Product/Service ID = P MEA~~WT~160.00~LB REF~1X~55 REF~DL~ SAC~C~A520~~~8160 Measurement Qualifier = WT (Weight) Measurement Value = Unit or Basis for Measurement Code = LB (Pound) Reference Number Qualifier = 1X (Complaint Code) Reference Number = 55 Reference Number Qualifier = DL (Debit Memo) Reference Number = Allowance or Charge Indicator = C (Charge) Service, Promotion, Allowance, or Charge Code = A520 (Base Charge) Amount = CTT~1~8160 Number of Line Items = 1 Hash Total = 8160 SE~16~0002 Number of Included Segments = 16 Transaction Set Control Number = /24/2015 V/R FCA US
862 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 informationIMPLEMENTATION 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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. 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 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 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 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 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 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 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 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 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. 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 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 informationContract Completion Status
S Implementation Convention (IC) 567C S Contract Completion Statement/ Unclosed Contract 567 Contract Completion Status Functional Group= D3 Purpose: This Draft Standard for Trial Use contains the format
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 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 informationEDI 830 Planning Schedule with Release Capability. VERSION: ANSI ASC X12 Version Release 4010
Navistar, Inc. EDI 830 Planning Schedule with Release Capability VERSION: ANSI ASC X12 Version Release 4010 EDI 830 Implementation Guide Document Number: Revision: Revision Date: PUR-2004 3.4 June 30,
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 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 information862: Shipping Schedule Outbound from TMD to Vendor
Toledo Molding & Die, Inc. EDI Document Specification 862: Shipping Schedule Outbound from TMD to Vendor Please note the following additions/changes: BSS09 this d.e.# will now be used (contract number)
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 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 information830 Planning Schedule with Release Capability SUPPLIER version
830 Planning Schedule with Release Capability SUPPLIER version Introduction: Functional Group ID=PS This Standard contains the format and establishes the data contents of the Planning Schedule with Release
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 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 informationLVS/ET Division. 862 Shipping Schedule
LVS/ET Division 862 Shipping Schedule ANSI X12 Version 004010 lvsedi@arvinmeritor.com 862v4010 Revised 3/20/2007 Page 1 of 19 862 Shipping Schedule Transaction Layout: Heading: Arm Req Pos No Seg ID Name
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 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 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 informationDoD Transportation Electronic Business (DTEB) Convention
Department of Defense DoD Transportation Electronic Business (DTEB) Convention ASC X12 Transaction Set 998 Rail Bill of Lading Cancellation (Version 004010) FINAL DRAFT December 2007 20071215 Department
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 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 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 information820 Payment Order/Remittance Advice DRAFT
820 Payment Order/Remittance Advice DRAFT Introduction: Functional Group ID=RA This Draft Standard for Trial Use contains the format and establishes the data contents of the Payment Order/Remittance Advice
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 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 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 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 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 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 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 informationEMPIRE ELECTRONICS, INC. Address Qualifier: 12 EDI Address: IMPLEMENTATION GUIDE
Address Qualifier: 12 EDI Address: 8105858130 ANSI X12 - Version 003060 AIAG 830 IMPLEMENTATION GUIDE Empire Electronics, Inc has produced this guide. All rights reserved. EDI Implementation Guide 1 TABLE
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 information945 Warehouse Shipping Advice
945 Warehouse Shipping Advice X12/V4010/945 Company: JR Simplot Company Modified: 11/24/2015 Notes: edi@simplot.com Table of Contents 945 Warehouse Shipping Advice............................................................................................................
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 informationKOHLER COMPANY VENDOR SHIP NOTICE LAYOUT (856) Kohler Description Number M = Mandatory O = Optional C = Conditional
ISA Field ISA Field Description M = Mandatory O = Optional C = Conditional M = Mandatory O = Optional C = Conditional ISA - Interchange Control Header ISA01 101 Authorization Info. Qualifier M ID 2/2 M
More informationCSI EDI ASN 856 specification Version /21/ ASN Advance Shipping Notice. Version: ANSI X /21/2012 V 1.
Charming Technology Services EDI Specification 856 - ASN Advance Shipping Notice Version: ANSI X12 004030 07/21/2012 V 1.2 From domestic vendor to CSI From Domestic Vendors to CSI 1 of 51 Table of Content
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 information315 Status Details (Ocean)
OCEAN TRANSPORTATION INDUSTRY GUIDE TO 004010 315 9 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 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 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 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 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 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 informationEDI Implementation Guide for SAP ASN
EDI Implementation Guide for SAP ASN March 2015 TRANSACTION SET 856 Advanced Ship Notice ANSI X.12 Table of Contents 856 Advanced Ship Notice Usage Convention...1 ANSI X.12 Version...2 H-D EDI Qualifier
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 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 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 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 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 informationMartinrea International s EDI Specifications. AIAG version 4010 ANSI X (Planning Schedule)
Martinrea International s EDI Specifications AIAG version 4010 ANSI X12 830 (Planning Schedule) Segment: ST Transaction Set Header Position: 010 Purpose: To indicate the start of a transaction set 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 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 informationEDI Implementation Guide 856 Advance Ship Notice Version 4010
EDI Implementation Guide 856 Advance Ship Notice Version 4010 Stores, Inc. and Subsidiaries and Affiliates 8000 Bent Branch Dr. Irving, TX 75063 (972) 409-1300 856 Ship Notice/Manifest 4010 Functional
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 informationPayment Order/Remittance Advice
820 Payment Order/Remittance Advice Functional Group= RA Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Payment Order/Remittance Advice Transaction
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 informationEDI Specifications Version 4010 / Transaction Set 210 Carrier Truckload Shipments
EDI Specifications Version 4010 / Transaction Set 210 Carrier Truckload Shipments Copyright 1995-2003 Transportation Solutions Inc; all rights reserved. This document and all intellectual property including
More informationa. Defense Logistics Management Standards Office (DLMSO)
Approved DLMS Change 168 New DLMS Supplement 4010 567C, Contract Completion Status (DLMS Contract Completion Statement/Unclosed Contract Status/Contract Close-out Extension) 1. ORIGINATOR a. Defense Logistics
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 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 information830 Planning Schedule EDI Implementation Guide
830 Planning Schedule EDI Implementation Guide Revision 1.3 02 / 2011 edi-team@behrgroup.com Behr Group EDI Team Page 2 Behr Group 830 Planning Schedule EDI Implementation Guide 830 Planning Schedule 1
More information856 Ship Notice/Manifest Standard Carton Pack Structure
856 Ship Notice/Manifest Standard Carton Pack Structure Macy s VICS Version 5010 VICS Document Mapping Effective 06/12/09 The following is an outline of what is expected when receiving VICS 856 Ship Notice
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 informationPUBNET 2000 Version 3060 IMPLEMENTATION GUIDELINE FOR EDI 850
850 Purchase Orer Functional Group=PO This Draft Stanar for Trial Use contains the format an establishes the ata contents of the Purchase Orer Transaction Set (850) for use within the context of an Electronic
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 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 informationReceiving Advice/Acceptance Certificate
861 Receiving Advice/Acceptance Certificate Functional Group= RC Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Receiving Advice/Acceptance Certificate
More information