X12 Implementation Guidelines For Outbound Receiving Advice v002001 (861O)



Similar documents
Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

VERSION: ANSI X

Portland General Electric Implementation Standard

ANSI X12 version Advance Ship Notice

EDI IMPLEMENTATION GUIDE. 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel)

ANSI X12 version Planning Schedule with Release Capability

810 Invoice ANSI ASC X12 Version 4010

BORGWARNER IMPLEMENTATION GUIDELINE FOR V PLANNING SCHEDULE

AMTEX IMPLEMENTATION GUIDELINES FOR EDI CONVENTIONS

Electronic Data Interchange

944 Warehouse Stock Transfer Receipt Advice. X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice

CVS/Caremark. Implementation Guide. 810 RX DC Invoice. Version X

Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT IT1 Baseline Item Data M PID Product / Item Description M

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

856 Advanced Shipping Notices (ASN)

810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes:

Electronic Data Interchange

EDI Specifications Advance Ship Notice (Supplier v4010)

856 Ship Notice/Manifest - R US CANADA

810 Invoice Revised 01/26/15

X12 Implementation. Guidelines. For. Transfer Version (996o)

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION

Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira

ANSI X Product Transfer and Resale Report

Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010

Invoice. Transaction Set (810) (Outbound from TI)

CVS/Caremark. Implementation Guide. 852 Product Activity Data Warehouse Movement. Version X

997 Functional Acknowledgment

Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)

Implementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS S

VOLVO Dealer Programs 810 Invoice EDI Guideline

84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION August 21, 2007

Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN)

867 Product Transfer and Resale Report Ver/Rel Electronic Data I nterchange. Utility Industry Group Implementation Guideline.

ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.

Implementation Guideline

Mazda North American Operations EDI Supplier Documentation October 20, 2015

Transaction Set Application Advice

EDI Guide - Appendix T 861 Receiving Advice/Acceptance Certificate (From Navy ERP/ILSMIS to irapt)

ADOBE ANSI X Version: 1.0

997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.

Customer EDI Guidelines United States 810 Invoice

3/31/08 ALTRA INDUSTRIAL MOTION Invoice Inbound 810 X Page 1 Created by Ralph Lenoir

856 Advance Ship Notice Supplier Implementation Guide November 2015

ORDERS 92.1 EDI GUIDELINE. for. Message Type ORDERS, ORDCHG Version 1 Release 921. ORDERS, ORDCHG Version /2011 Page 1

EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message

PURCHASE ORDER RESPONSE

810 Invoice. Introduction: Heading: Functional Group ID=IN

Bill of Lading Number REF Reference Identification M AN 1/30 MustUse

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET

ANSI X12 ASN 856 Version

Supply Chain Merchandise Logistics E-Commerce Purchase Order

ASN. HDMA Electronic Data Interchange (EDI) Guidelines for the 856 Advance Ship Notice to Support Implementation of DSCSA

214 Transportation Carrier Shipment Status Message

RANDOM HOUSE. EDI Implementation Guide. 850 Purchase Order X12 Version 4010

To indicate the beginning of an invoice transaction set and to transmit identifying numbers and dates. BIG^ ^12345^ ^ ^

EDI Specifications Invoice (Supplier v4010)

ANSI X12 version Remittance Advice

824 Application Advice

ANSI X12 version Text Message

Note: The following information is required on all Merchandise Invoices:

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010

ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message

EDI GUIDELINES INVOICE 810 VERSION 4010

Implementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS S Supplier

Staples Supplier Electronic Data Interchange Implementation Guide

860 Purchase Order Change Request Buyer Initiated

EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X Draft

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007

945 Warehouse Shipping Advice

810 Invoice ANSI X.12 Version 5010

Unified Grocers 820 EFT Specifications Remittance Advice Document Structure

BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010

Now, suppliers can also select EDI as a method for receiving Change and Cancel Orders.

MERITOR. EDI Business Process Guide

VDP Program Vendor Guidelines

Electronic Document Interchange Standards Version 5050

Dart Container Corporation. EDI 810 Outbound Invoice Version 4010

810 - Invoice. Set Number Set Name - Invoice Functional Group - IN

LOOP ID - N N9 Reference Identification O MSG Message Text O 1000

999 Implementation Acknowledgment. Version: 1.0 Draft

Adobe - EDIFACT D97.A ORDERS

INTRODUCTION TO EDIFACT. presented by EIDX

Bulk EDIFACT ASN MESSAGE FORMAT

214 Transportation Carrier Shipment Status Message - LTL

KANSAS CITY SOUTHERN EDI On-Boarding Guide

EDI GUIDELINES PURCHASE ORDER 850 VERSION 4010

Media Saturn EDI Application Documentation

Price Information UCS & X12

DoD Transportation Electronic Data Interchange (EDI) Convention

Delivery/Return Acknowledgment or 895 Adjustment UCS

EDIFACT DELFOR D99B Guideline

Purchase Orders Message ORDERS (EDIFACT D97A)

S.2.2 CHARACTER SETS AND SERVICE STRING ADVICE: THE UNA SEGMENT

Hella EDIFACT INVRPT

The EDI 810 specification is separated into logically distinct groups, which are composed of particular segment types.

CSX EDI 824 Application Advice Version:

Transcription:

X12 Implementation Guidelines For Outbound Receiving Advice v002001 (861O)

861 Receiving Advice/Acceptance Certificate Introduction: Functional Group ID=RC This Draft Standard for Trial Use contains the format and establishes the data contents of the Receiving Advice/Acceptance Certificate Transaction Set (861) 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 notification of receipt or formal acceptance of goods and services. Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 ST Transaction Set Header M 1 M 020 BRA Beginning Segment for Receiving Advice or M 1 Acceptance Certificate M 050 REF Reference Numbers M 2 M 070 DTM Date/Time/Period M 1 LOOP ID - N1 200 M 130 N1 Name M 1 LOOP ID - RCD 200000 M 200 RCD Receiving Conditions M 1 M 210 SN1 Item Detail (Shipment) M 1 M 230 LIN Item Identification M 1 M 460 CTT Transaction Totals M 1 M 470 SE Transaction Set Trailer M 1 FD861O (002001) 1

Segment: ST Transaction Set Header Position: 010 Loop: Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Notes: The transaction set control number (ST02) in this header must match the transaction set control number (SE02) in the transaction set trailer (SE). ST*861*891230001' M ST01 143 Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 861 Receiving Advice/Acceptance Certificate M ST02 329 Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set A unique number assigned to each transaction set within a functional group. This number must match the value in SE02. FD861O (002001) 2

Segment: BRA Beginning Segment for Receiving Advice or Acceptance Certificate Position: 020 Loop: Purpose: To indicate the beginning of a Receiving Advice or Acceptance Certificate Transaction Set and transmit an identifying number, date, and time Syntax Notes: Notes: Ford only uses the transactions set purpose of original. BRA*890590001*030109*00' M BRA01 127 Reference Number M AN 1/30 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. A number assigned by Ford to uniquely identify the transaction set. M BRA02 373 Date M DT 6/6 Date (YYMMDD) Transaction creation date. M BRA03 353 Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set 00 Original FD861O (002001) 3

Segment: REF Reference Numbers Position: 050 Loop: Max Use: 2 Purpose: To specify identifying numbers. Syntax Notes: 1 At least one of REF02 or REF03 is required. Notes: Used to transmit shipment identification ASN and/or packing slip number. REF*SI*12345' M REF01 128 Reference Number Qualifier M ID 2/2 Code qualifying the Reference Number. PK Packing List Number SI Shipper's Identifying Number for Shipment (SID) A unique number (to the shipper) assigned by the shipper to identify the shipment REF02 127 Reference Number C AN 1/30 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Ford will send the supplier generated ASN number and/or packing slip number for the referenced shipment (BSN02). Ford will only provide up to the first 11 characters. FD861O (002001) 4

Segment: DTM Date/Time/Period Position: 070 Loop: Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Notes: Normally used to specify the receiving date. This segment will be used to specify the shipped date if return is indicated. DTM*050*030109' DTM*011*030106' M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time Will contain - "050" - material received on this date or "011" - material shipped on this date. Shipped date will be used when a return is indicated. 011 Shipped 050 Received DTM02 373 Date C DT 6/6 Date (YYMMDD) FD861O (002001) 5

Segment: N1 Name Position: 130 Loop: N1 Mandatory 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. Notes: Two occurrences of the N1 are required. One for the "ship from" location (N101 - "SF") and one for the "ship to" (N101 - "ST"). If a return is indicated, the "SF" will be Ford and "ST" will be the supplier. N1*ST**92*AP01A' N1*SF**92*A001A' M N101 98 Entity Identifier Code M ID 2/2 Code identifying an organizational entity, a physical location, or an individual SF Ship From ST Ship To N103 66 Identification Code Qualifier C ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer or Buyer's Agent N104 67 Identification Code C AN 2/17 Code identifying a party or other code Will contain Ford assigned code. FD861O (002001) 6

Segment: RCD Receiving Conditions Position: 200 Loop: RCD Mandatory Purpose: To report receiving conditions and specify contested quantities Syntax Notes: 1 At least one of RCD02 RCD04 or RCD06 is required. 2 If RCD02 is present, then RCD03 is required. 3 If RCD04 is present, then RCD05 is required. 4 If RCD06 is present, then both RCD07 and RCD08 are required. 5 If RCD09 is present, then both RCD10 and RCD11 are required. 6 If RCD12 is present, then both RCD13 and RCD14 are required. 7 If RCD15 is present, then both RCD16 and RCD17 are required. 8 If RCD18 is present, then both RCD19 and RCD20 are required. Notes: In each RCD loop Ford will send detail level information for all receipts, discrepancies and Assembly Division returns. RCD02 will contain the quantity received. RCD04 will contain the quantity returned. (Return quantity is used by Assembly Division only.) RCD08 will contain one of the following codes: "08" - Return, reject, do not adjust cum. "12" - Return, overshipment, adjust cum. (The cum adjustment quantity will be specified in the RCD09 - RCD11 discrepancy area with a RCD11 code of "11" and the adjust cum quantity in RCD09.) "13" - Quantity discrepancy, do not adjust cum. RCD**900*PC***100*PC*08' RCD02 663 Quantity Units Received or Accepted C R 1/9 Number of Units Received or Accepted RCD03 355 Unit or Basis for Measurement Code C ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Will contain the same unit of measure as Ford Material Release (830). Refer to 002001 Data Element Dictionary for acceptable code values. RCD04 664 Quantity Units Returned C R 1/9 Number of units returned Used by Assembly Division to indicate return quantity. RCD05 355 Unit or Basis for Measurement Code C ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Will contain the same unit of measure as Ford Material Release (830). Refer to 002001 Data Element Dictionary for acceptable code values. RCD06 667 Quantity in Question C R 1/9 Number of units contested because of physical condition or status of units Will contain difference between SN102 and RCD02. RCD07 355 Unit or Basis for Measurement Code C ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Will contain same unit of measure as Ford Material Release (830). Refer to 002001 Data Element Dictionary for acceptable code values. RCD08 412 Receiving Condition Code C ID 2/2 Code designating physical condition or status of units received in a specific FD861O (002001) 7

shipment 08 Rejected 12 Return Overshipment 13 Quantity Discrepancy RCD09 667 Quantity in Question C R 1/9 Number of units contested because of physical condition or status of units When used will contain cum adjustment quantity. RCD10 355 Unit or Basis for Measurement Code C ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Will contain same unit of measure as Ford Material Release (830). Refer to 002001 Data Element Dictionary for acceptable code values. RCD11 412 Receiving Condition Code C ID 2/2 Code designating physical condition or status of units received in a specific shipment Ford will use the RCD09 - RCD11 discrepancy set to show cum adjustment quantity only. 11 Cum Adjustment Quantity FD861O (002001) 8

Segment: SN1 Item Detail (Shipment) Position: 210 Loop: RCD Mandatory Purpose: To specify line-item detail relative to shipment Syntax Notes: 1 If SN105 is present, then SN106 is required. Notes: Used to show ASN quantity for the part referenced in the LIN segment. SN1**1000*PC' M SN102 382 Number of Units Shipped M R 1/10 Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set For Assembly Division, received quantity, otherwise ASN quantity. M SN103 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Will contain same unit of measure as Ford Material Release (830). Refer to 002001 Data Element Dictionary for acceptable code values. FD861O (002001) 9

Segment: LIN Item Identification Position: 230 Loop: RCD Mandatory 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. Notes: Use for Ford part number. Ford part number may consist of a prefix, base, suffix and control code. Any of these, except the base, may or may not be present. The portions of the part number are delimited by spaces. LIN**BP*E6SP 7E396 AA 040' (Part number with control code) LIN**BP*E6SP 7E396 AA 040*PO*FE 4397' (Part number with control code and PO number) LIN**BP* 7E396 AA 040' (Part number without prefix) LIN**BP*E6SP 7E396' (Part number with neither suffix nor control code) M LIN02 235 Product/Service ID Qualifier M ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) BP Buyer's Part Number M LIN03 234 Product/Service ID M AN 1/30 Identifying number for a product or service This field will contain the Ford part number. FD861O (002001) 10

Segment: CTT Transaction Totals Position: 460 Loop: 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. Notes: CTT*4*32951' M CTT01 354 Number of Line Items M N0 1/6 Total number of line items in the transaction set Total number of RCD segments. M CTT02 347 Hash Total M R 1/10 Sum of Quantity Received element (RCD02) of all RCD segements Accumulation of the quantity received element (RCD02) of all RCD segments. FD861O (002001) 11

Segment: SE Transaction Set Trailer Position: 470 Loop: Purpose: Syntax Notes: Notes: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments). The number of included segments is the total of all segments used in the transaction set including the ST and SE segments. The transaction set control number (SE02) in the trailer must match the transaction set control number (ST02) in the transaction set header segment (ST). SE*51*891230001' M SE01 96 Number of Included Segments M N0 1/6 Total number of segments included in a transaction set including ST and SE segments M SE02 329 Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Will contain value in ST02. FD861O (002001) 12