ANSI X12 version Receiving Advice/ Acceptance Certificate

Similar documents
Functional Acknowledgment

861 Receiving Advice/Acceptance Certificate

DSW Designer Shoe Warehouse

Functional Acknowledgment - 997

X Envelops. University Hospitals Health Systems University Hospitals of Cleveland ASNI X12 Envelops Version Functional Group ID=

EDI Functional Acknowledgment

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

824 Application Advice X12/V4010/824: 824 Application Advice Version: 1.3

Functional Acknowledgment - 997

870 Order Status Report

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

860 Purchase Order Change Request - Buyer Initiated

JR Simplot Food Group Purchase Order Acknowledgment

Customer EDI Guidelines 997 Functional Acknowledgment

Freightliner Corporation Interchange Envelope Structure

855 Purchase Order Acknowledgment

ICS Interchange Control Structures

990 Response to a Load Tender

997 - Functional Acknowledgment Author: DOT FOODS, INC. Publication: March 3, 2005

ADOBE Inbound 997 ANSI X Version: 1.0

EFS 997 Functional Acknowledgment X12/V4010/997: 997 Functional Acknowledgment Version: 1.3

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct

990 Response to a Load Tender

Ver 2 Rel 2 Envelope Segments -

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

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

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

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

Product Transfer and Resale Report - 867

824 Application Advice

855 Purchase Order Acknowledgment

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

Purchase Order Change Request - Buyer Initiated

997 Functional Acknowledgment

990 Response to a Load Tender

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

846 Inventory Inquiry/Advice

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

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

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

JR Simplot Agribusiness Ship Notice/Manifest

852 Product Activity Data Functional Group=PD

12/19/2017 Purchase Order Acknowledgment - 855

850 Purchase Order. Version: X12

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

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

Electronic Data Interchange 832 Price/Sales Catalog (VICS Version ) March Powered By:

EDI Implementation Guide Version

850 Purchase Order - v4030

820 Payment Order/Remittance Advice

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

Inbound ANSI X Version 04010

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications

879 - Price Information

824 Application Advice

Rite Aid Corporation 875 Grocery Products Purchase Order Version UCS

Inbound X Version 04010

EDI Specification. 997 Functional Acknowledgement. For all Trading Partners. Version: ANSI X /21/2011 V 1.0

DoD Transportation Electronic Business (DTEB) Convention

JR Simplot Corporate 810 Invoice

850 Purchase Order

860 Purchase Order Change Request - Buyer Initiated

ZF Group North American Operations. EDI Implementation Guide

846 Inventory Inquiry/Advice - v4010

846 Inventory Inquiry/Advice

Remittance Advice

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

To: Electronic Data Interchange (EDI) Partners:

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

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

International Truck and Engine Corporation

997 Functional Acknowledgement X12 Version 4010

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

846 Inventory Inquiry/Advice

850 Purchase Order X12 Version Version: 2.0

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

Amazon Purchase Order Acknowledgment

824 Application Advice

831 Application Control Totals

990 RESPONSE TO A LOAD TENDER. Version:

824 Application Advice

Status Updates Auto Push Table of Contents

Oshkosh 860 Purchase Order Change Request - Buyer Initiated

HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 4010 IMPLEMENTATION GUIDE

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

830 - Material Release VERSION: 1.2

Revised 11/15/17 Booking Confirmation EDI 301. Booking Confirmation. ANSI X Revised 11/15/17

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

Document Version FUNCTIONAL ACKNOWLEDGEMENT (ANSI X12 VERSION 4040) 10/10/2008. X12V General Parts, Inc./CARQUEST

810 Invoice Service Parts Version:

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

855 Purchase Order Acknowledgment

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

870 Order Status Report

816 Organizational Relationships

832 Price/Sales Catalog

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

849 Response to Product Transfer

EDI 860 Mapping. Instructions. Version 1.0 September 16, 2016

Transcription:

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

861 Receiving Advice/Acceptance Certificate Functional Group=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 within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be d to provide for customary and established business and industry practice relative to the notification of receipt or formal acceptance of goods and services. Segments: Pos Id Segment Name Req Max Repeat Notes Usage Use ISA Interchange Control Header M 1 Used GS Functional Group Header M 1 Used Heading: Pos Id Segment Name Req Max Repeat Notes Usage Use 010 ST Transaction Set Header M 1 Must 020 BRA Beginning Segment for Receiving Advice or M 1 N1/020 Must Acceptance Certificate 050 REF Reference Identification O >1 Used 070 DTM Date/Time Reference M 10 Must LOOP ID - N1 200 130 N1 Name O 1 Used Detail: Pos Id Segment Name Req Max Use Repeat Notes Usage LOOP ID - RCD 200000 010 RCD Receiving Conditions M 1 Must 020 SN1 Item Detail (Shipment) O 1 Used 040 LIN Item Identification M 100 Must Summary: Pos Id Segment Name Req Max Use Repeat Notes Usage 020 SE Transaction Set Trailer M 1 Must Segments: Notes: Pos Id Segment Name Req Max Use Repeat Notes Usage GE Functional Group Trailer M 1 Used IEA Interchange Control Trailer M 1 Used 1/020 This transaction set is a Receiving Advice unless BRA04 contains a value of "8". When BRA04 contains a value of "8", the transaction set is an Acceptance Certificate and the units received is the units accepted. 861 All Partners 4010 Inbound.rtf 2 Superior Essex

ISA Interchange Control Header Pos: Max: 1 - Mandatory Loop: N/A Elements: 16 To start and identify an interchange of zero or more functional groups and interchange-related control segments ISA01 I01 Authorization Information Qualifier Description: Code to identify the type of information in the Authorization Information 00 No Authorization Information Present (No Meaningful Information in I02) ISA02 I02 Authorization Information Description: Information d for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01) ISA03 I03 Security Information Qualifier Description: Code to identify the type of information in the Security Information 00 No Security Information Present (No Meaningful Information in I04) ISA04 I04 Security Information Description: This is d for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03) ISA05 I05 Interchange ID Qualifier Description: Qualifier to designate the system/method of code structure d to designate the sender or receiver ID element being qualified 01 Duns (Dun & Bradstreet) 09 X.121 (CCITT) 12 Phone (Telephone Companies) ZZ Mutually Defined ISA06 I06 Interchange Sender ID Description: Identification code published by the sender for other parties to as the receiver ID to route data to them; the sender always codes this value in the sender ID element M AN 10/10 Must M AN 10/10 Must M AN 15/15 Must 861 All Partners 4010 Inbound.rtf 3 Superior Essex

ISA07 I05 Interchange ID Qualifier Description: Qualifier to designate the system/method of code structure d to designate the sender or receiver ID element being qualified 12 Phone (Telephone Companies) ISA08 I07 Interchange Receiver ID Description: Identification code published by the receiver of the data; When sending, it is d by the sender as their sending ID, thus other parties sending to them will this as a receiving ID to route data to them User Note 1: 2194614000 Production 2194614462 Test ISA09 I08 Interchange Date Description: Date of the interchange ISA10 I09 Interchange Time Description: Time of the interchange ISA11 I10 Interchange Control Standards Identifier Description: Code to identify the agency responsible for the control standard d by the message that is enclosed by the interchange header and trailer All valid standard codes are d. ISA12 I11 Interchange Control Version Number Description: This version number covers the interchange control segments Code Name 00401 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997 ISA13 I12 Interchange Control Number Description: A control number assigned by the interchange sender M AN 15/15 Must M DT 6/6 Must M TM 4/4 Must M ID 1/1 Must M ID 5/5 Must M N0 9/9 Must ISA14 I13 Acknowledgment Requested Description: Code sent by the sender to request an interchange acknowledgment (TA1) 0 No Acknowledgment Requested M ID 1/1 Must ISA15 I14 Usage Indicator Description: Code to indicate whether data enclosed by this interchange envelope is test, production or information P Production Data T Test Data ISA16 I15 Component Element Separator Description: Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter d to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator M ID 1/1 Must M 1/1 Must 861 All Partners 4010 Inbound.rtf 4 Superior Essex

GS Functional Group Header Pos: Max: 1 - Mandatory Loop: N/A Elements: 8 To indicate the beginning of a functional group and to provide control information GS01 479 Functional Identifier Code Description: Code identifying a group of application related transaction sets RC Receiving Advice/Acceptance Certificate (861) GS02 142 Application Sender's Code Description: Code identifying party sending transmission; codes agreed to by trading partners GS03 124 Application Receiver's Code Description: Code identifying party receiving transmission. Codes agreed to by trading partners GS04 373 Date Description: Date expressed as CCYYMMDD GS05 337 Time Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) GS06 28 Group Control Number Description: Assigned number originated and maintained by the sender GS07 455 Responsible Agency Code Description: Code d in conjunction with Data Element 480 to identify the issuer of the standard X Accredited Standards Committee X12 GS08 480 Version / Release / Industry Identifier Code Description: Code indicating the version, release, subrelease, and industry identifier of the EDI standard being d, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by r); if code in DE455 in GS segment is T, then other formats are allowed Code Name 004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997 Semantics: M AN 2/15 Must M AN 2/15 Must M DT 8/8 Must M TM 4/8 Must M N0 1/9 Must M ID 1/2 Must M AN 1/12 Must 1. GS04 is the group date. 2. GS05 is the group time. 3. The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. Comments: 1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer. 861 All Partners 4010 Inbound.rtf 5 Superior Essex

ST Transaction Set Header Pos: 010 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 To indicate the start of a transaction set and to assign a control number ST01 143 Transaction Set Identifier Code Description: Code uniquely identifying a Transaction Set 861 Receiving Advice/Acceptance Certificate M ID 3/3 Must ST02 329 Transaction Set Control Number Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set M AN 4/9 Must Semantics: 1. The transaction set identifier (ST01) d by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). BRA Beginning Segment for Receiving Advice or Acceptance Certificate Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 3 To indicate the beginning of a Receiving Advice or Acceptance Certificate Transaction Set and transmit an identifying number, date, and time BRA01 127 Reference Identification Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier M AN 1/30 Must BRA02 373 Date Description: Date expressed as CCYYMMDD M DT 8/8 Must BRA03 353 Transaction Set Purpose Code Description: Code identifying purpose of transaction set 00 Original Semantics: 1. BRA02 is the date that the receiving advice transaction set is created. 2. BRA05 is the time that the receiving advice transaction set is created. 861 All Partners 4010 Inbound.rtf 6 Superior Essex

REF Reference Identification Pos: 050 Max: >1 Heading - Optional Loop: N/A Elements: 4 To specify identifying information REF01 128 Reference Identification Qualifier Description: Code qualifying the Reference Identification All valid standard codes are d. REF02 127 Reference Identification Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier M ID 2/3 Must C AN 1/30 Used REF03 352 Description Description: A free-form description to clarify the related data elements and their content C AN 1/80 Used Syntax: 1. REF02 R0203 -- At least one of REF02 or REF03 is required. DTM Date/Time Reference Pos: 070 Max: 10 Heading - Mandatory Loop: N/A Elements: 2 To specify pertinent dates and times DTM01 374 Date/Time Qualifier M ID 3/3 Must Description: Code specifying type of date or time, or both date and time 011 Shipped 050 Received DTM02 373 Date Description: Date expressed as CCYYMMDD C DT 8/8 Used Syntax: 1. DTM02 R020305 -- At least one of DTM02, DTM03 or DTM05 is required. 861 All Partners 4010 Inbound.rtf 7 Superior Essex

N1 Name Pos: 130 Max: 1 Heading - Optional Loop: N1 Elements: 4 To identify a party by type of organization, name, and code N101 98 Entity Identifier Code Description: Code identifying an organizational entity, a physical location, property or an individual All valid standard codes are d. N102 93 Name Description: Free-form name M ID 2/3 Must C AN 1/60 Used N103 66 Identification Code Qualifier Description: Code designating the system/method of code structure d for Identification Code (67) All valid standard codes are d. N104 67 Identification Code Description: Code identifying a party or other code C ID 1/2 Used C AN 2/80 Used Syntax: 1. N102 R0203 -- At least one of N102 or N103 is required. 2. N103 P0304 -- If either N103 or N104 are present, then the others are required. Comments: 1. This segment, d 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. 861 All Partners 4010 Inbound.rtf 8 Superior Essex

RCD Receiving Conditions Pos: 010 Max: 1 Detail - Mandatory Loop: RCD Elements: 4 To report receiving conditions and specify contested quantities RCD02 663 Quantity Units Received or Accepted Description: Number of Units Received or Accepted M R 1/9 Must RCD03 C001 Composite Unit of Measure Description: To identify a composite unit of measure(see Figures Appendix for examples of ) 355 Unit or Basis for Measurement Code Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken All valid standard codes are d. RCD04 664 Quantity Units Returned Description: Number of units returned RCD05 C001 Composite Unit of Measure Description: To identify a composite unit of measure(see Figures Appendix for examples of ) 355 Unit or Basis for Measurement Code Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken All valid standard codes are d. C Comp Used C R 1/9 Used C Comp Used Syntax: 1. RCD02 R020406 -- At least one of RCD02, RCD04 or RCD06 is required. 2. RCD02 P0203 -- If either RCD02 or RCD03 are present, then the others are required. 3. RCD04 P0405 -- If either RCD04 or RCD05 are present, then the others are required. Semantics: 1. RCD01 is the receiving advice line item identification. 2 Comments: 1. See the Data Element Dictionary for a complete list of receiving condition IDs. 861 All Partners 4010 Inbound.rtf 9 Superior Essex

SN1 Item Detail (Shipment) Pos: 020 Max: 1 Detail - Optional Loop: RCD Elements: 2 To specify line-item detail relative to shipment SN102 382 Number of Units Shipped Description: Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set M R 1/10 Must SN103 355 Unit or Basis for Measurement Code Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken All valid standard codes are d. Syntax: 1. SN105 P0506 -- If either SN105 or SN106 are present, then the others are required. Semantics: 1. SN101 is the ship notice line-item identification. Comments: 1. SN103 defines the unit of measurement for both SN102 and SN104. 861 All Partners 4010 Inbound.rtf 10 Superior Essex

LIN Item Identification Pos: 040 Max: 100 Detail - Mandatory Loop: RCD Elements: 2 To specify basic item identification data LIN02 235 Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number d in Product/Service ID (234) All valid standard codes are d. LIN03 234 Product/Service ID Description: Identifying number for a product or service User Note 1: This should be the buyer or customer part and the qualifier can be whatever is appropriate for that number. M AN 1/48 Must SE Transaction Set Trailer Pos: 020 Max: 1 Summary - Mandatory Loop: N/A Elements: 2 To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) SE01 96 Number of Included Segments Description: Total number of segments included in a transaction set including ST and SE segments M N0 1/10 Must SE02 329 Transaction Set Control Number Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set M AN 4/9 Must Comments: 1. SE is the last segment of each transaction set. 861 All Partners 4010 Inbound.rtf 11 Superior Essex

GE Functional Group Trailer Pos: Max: 1 - Mandatory Loop: N/A Elements: 2 To indicate the end of a functional group and to provide control information GE01 97 Number of Transaction Sets Included Description: Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element M N0 1/6 Must GE02 28 Group Control Number Description: Assigned number originated and maintained by the sender M N0 1/9 Must Semantics: 1. The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06. Comments: 1. The of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that d in the corresponding header. IEA Interchange Control Trailer Pos: Max: 1 - Mandatory Loop: N/A Elements: 2 To define the end of an interchange of zero or more functional groups and interchange-related control segments IEA01 I16 Number of Included Functional Groups Description: A count of the number of functional groups included in an interchange M N0 1/5 Must IEA02 I12 Interchange Control Number Description: A control number assigned by the interchange sender M N0 9/9 Must 861 All Partners 4010 Inbound.rtf 12 Superior Essex