Implementation Guidelines for EDI Conventions Transaction set 824 Application Advice Ver. 3060 REQUIREMENTS 1/17
Introduction This draft standard for trial contains the format and establishes the data contents of the Application Advice transaction set (824) for within the context of an Electronic Data Interchange (EDI) also know as Electronic Commerce(EC) environment. The transaction set can be d to provide the ability to report the results of an application system's data content edits of transaction sets. The results of editing transaction sets can be reported at the functional group and transaction set level, in either coded or free-form format. It is designed to accommodate the business need of reporting the acceptance, rejection or acceptance with change of any transaction set. The Application Advice should not be d in place of a transaction set designed as a specific response to another transaction set (e.g., purchase order acknowledgment sent in response to a purchase order). HTNA s this transaction to return acknowledgement or error information for all 856 Advanced Ship Notices received from our suppliers. If there is an error in the line items of the ASN while checking the line items, it will ca the whole ASN to fail. 2/17
DEFINITION Hayashi Telempu North America Corp. Abbreviations in the usage column headed REQ. /ATTRIBUTES. (Requirements/Attributes) have the following definitions and will appear, as indicated, in all IGEC (Implementation Guidelines for EDI Conventions). The ANSI usage requirements have been provided in the table for reference purposes only. Condition Designator Segments: M Mandatory. This data segment must be included in the Transaction set. O Optional. The presence of this data segment is at the option of the sending party. Data Elements: C Conditional. The data element conditions are of three types: mandatory, optional, and relational, and define the circumstances under which a simple data element, composite data structure or component data element may be required to be present or absent in a particular segment or composite data structure. M Mandatory. The element must be d. (Note: If a segment is defined as optional, and if the segment is d, one or more data elements may be listed as mandatory.) O Optional. The presence of this data element is at the option of the sending party. X Relational. The presence of this item is related to the presence or absence of other item(s). See Conditional. Data Element Type The follow types of data elements appear in this guide. Each data element is assigned a minimum and maximum length. The length of the data element value is the number of character positions d except as noted for numeric, and decimal elements. Numeric Decimal Number Identifier String Date Time Nn (n indicates implied decimal positions) R ID AN (alpha-numeric) DT (YYMMDD) TM (HHMM 24hour clock) Numeric (Nn) and decimal (R) fields are assumed to be positive unless a leading minus sign indicating a negative value is transmitted. A plus sign is never transmitted. The minus sign (-) and the decimal point are not counted as part of the data element s length. HTNA Required Abbreviations in the usage column headed Usage (HTNA Usage) have the following definitions and will appear, as indicated, in all IGEC (Implementation Guidelines for EDI Conventions). Must Used Not d HTNA require a data segment/element. HTNA require a data segment/element s at the option. HTNA require a data segment/element des not. Required Delimiter Element * Sub Element : Segment Terminator ~ 3/17
824 SEGMENT USAGE OVERVIEW Functional Group=AG Heading: POS ID SEGMENT NAME REQ MAX LOOP USAGE USAGE 010 ST Transaction Set Header M 1 Must 020 BGN Beginning Segment For Application Advice M 1 Must LOOP ID N1 2 030 N1 Name O 1 Must 040 N2 Additional Name Information O 2 Not d 050 N3 Address Information O 2 Not d 060 N4 Geographic Location O 1 Not d 070 REF Reference Number O 12 Not d 080 PER Administrative Communications Contact O 3 Not d Detail: POS ID SEGMENT NAME REQ MAX USAGE LOOP USAGE LOOP ID OTI 10000 010 OTI Original Transaction Identification M 1 Must 020 REF Reference Number O 12 Must 030 DTM Date/Time Reference O 2 Must 040 PER Administrative Communications Contact O 3 Not d 050 AMT Monetary Amount O 10 Not d 060 QTY Quantity O 10 Not d LOOP ID OTI/TED 10000 070 TED Technical Error Description O 1 Used 080 NTE Note/Special Instruction O 100 Used 090 SE Transaction Set Trailer M 1 Must 4/17
SEGMENT: ST - TRANSACTION SET HEADER LEVEL/POSITION: Heading / 010 MAX USAGE/LOOPS: EXAMPLES: 1 / None To indicate the beginning of a transaction set and to assign a control number The transaction set control number (ST02) in this header must match the transaction set control number (SE02) in the transaction set trailer (SE) segment. ST*824*994091616~ ST01 143 Transaction Set ID Code M ID 03/03 Must ST02 329 Transaction Set Control M AN 04/09 Must Use 824 for Application Advice A unique control number (same as SE02) 5/17
SEGMENT: BGN - BEGINNING SEGMENT FOR APPLICATION ADVICE LEVEL/POSITION: Heading / 020 MAX USAGE/LOOPS: EXAMPLES: 1 / None To indicate the beginning of an application advice This segment is intended to provide information for the entire transaction. The reference number will be a uniquely generated identification number by the receiver of the original document. BGN*00*187827*090722*163500~ BGN01 353 Transaction Set Purpose M ID 02/02 Must BGN02 127 Reference Number X AN 01/30 Must BGN03 373 Date M DT 06/06 Must BGN04 337 Time X TM 04/06 Must BGN05 623 Time Code O ID 02/02 Not d 00 = Original HTNA reference number for the Application Advice Date (YYMMDD) Time (HHMM) 6/17
SEGMENT: N1 - NAME LEVEL/POSITION: Heading / 030 MAX USAGE/LOOPS: 1 / N1/2 To identify the party by type of organization, name, and code The N1 loop in the heading area is d to identify the ship-to code, and the ship-from code from the original ASN. EXAMPLES: N1*SF**92**5111~ (Ship from) N1*ST**92**17~ (Ship to) N101 98 Entity Identifier Code M ID 02/02 Must N102 93 Organization Name X AN 01/35 Not d N103 66 Identification Code Qualifier X ID 01/02 Must N104 67 Identification Code X AN 02/17 Must ST = SF = Ship to Location Ship from Location 92 = Assigned by buyer ** See list below Assigned Ship from code: Assigned Ship to code: Vendor number will be assigned by HTNA from EDI Profile. ** Please see HTNA EDI Profile 17 = HTNA Lebanon Plant 47 = HTNA Jasper Plant 21 = Hayashi Canada Plant 7/17
SEGEMENT: OTI ORIGINAL TRANSACTION IDENTIFICATION LEVEL/POSITION: Detail / 010 MAX USAGE/LOOPS: 1 / OTI/10000 To identify the edited transaction set, the level at which the results of the edit are reported, and to indicate the accepted, rejected or accepted with change edit result One OTI loop is generated for each ASN line item, whether accepted or rejected by HTNA. HTNA s multiple TED loops to convey multiple error messages for a line item. If OTI01 = "IA", line item was accepted without errors. If OTI01 = "IE", line item had one or more non-fatal errors (warnings) but no fatal errors. It was accepted as submitted and should not be resent. If OTI01 = "IR", line item had one or more fatal errors and was rejected. It must be corrected and resent. EXAMPLE: OTI*IA*SI*1278085*******856~ (Accepted) OTI*IE*SI*2331376*******856~ (Accepted w/ Error) OTI*IR*SI*2331376*******856~ (Rejected) OTI01 110 Application Acknowledgment Code M ID 01/02 Must OTI02 128 Reference Number Qualifier M ID 02/02 Must OTI03 127 Reference Number M AN 01/30 Must OTI04 142 Application Sender's Code O AN 02/15 Not d OTI05 124 Application Receiver's Code O AN 02/15 Not d OTI06 373 Date O DT 06/06 Not d OTI07 337 Time O TM 04/06 Not d OTI08 28 Group Control Number X N0 01/09 Must "IA" = Accepted "IE" = Accepted with Error "IR" = Rejected "SI" = ASN number Value referred to by OTI02 GS Control Number 8/17
OTI09 329 Transaction Set Control Number O AN 04/09 Must OTI10 143 Transaction Set Identifier Code O ID 03/03 Must OTI11 480 Version/Release/Industry Identifier O AN 01/12 Not Code d Transaction Control Number 856 = ASN transaction set ** If there is an error (OTI01= IR : Rejected) in the line items of the ASN, it will ca the whole ASN to fail. The ASN sender must fix what is wrong with the ASN and resend it. 9/17
SEGMENT: REF - REFERENCE NUMBER LEVEL/POSITION: Detail / 020 MAX USAGE/LOOP: 12 / OTI To transmit identifying numbers associated with the item identified in the OTI record This segment is d to identify the packing slip number or parts number processed. EXAMPLES: REF*PK*2331126 ~ (Packing Slip number) REF*PM*0070345~ (Part number) REF01 128 Reference Number Qualifier M ID 02/02 Must REF02 127 Reference Number X AN 01/30 Must REF03 352 Description X AN 01/80 Not d PK = Packing Slip number PM = Part number Value referred to by REF01 10/17
SEGMENT: DTM - DATE / TIME REFERENCE LEVEL/POSITION: Detail / 030 MAX USAGE/LOOPS: 2 / OTI To specify pertinent dates and times To specify HTNA system process date/time, and ship date/time from the original ASN. EXAMPLES: DTM*009*090928*083700~ (Shipped Date/Time) DTM*011*091005*143500~ (Process Date/Time) DTM01 374 Date/Time Qualifier M ID 03/03 Must "009 = Shipped Date/Time from original ASN 011 = Process Date/Time in HTNA Date (YYMMDD) DTM02 373 Date X DT 06/06 Must DTM03 337 Time X TM 04/06 Used Time (HHMMSS) DTM04 623 Time Code O ID 02/02 Not d DTM05 624 Century O N0 02/02 Not d 11/17
SEGMENT: TED TECHNICAL ERROR DESCRIPTION LEVEL/POSITION: Detail / 070 MAX USAGE/LOOP: EXAMPLE: 1 / OTI/TED/10000 To identify the error This segment is only generated in the Detail area when the ASN (856) is accepted with errors or rejected (OTI01 = IE", or "IR"). In the the event of multiple error conditions per line item a separate TED loop will be generated for each error condition. TED01 will contain "ZZZ" indicating the of a HTNA proprietary error code as the first three positions of TED02 followed by a generic description of the error. TED07 will contain a copy of the data in error. TED*ZZZ*076PO DOES NOT MATCH CUSTOMER RELEASE*****0070345~ ** This segment is optional. TED01 647 Application Error Condition Code M ID 01/03 Must TED02 3 Free Form Message O AN 01/60 Must TED03 721 Segment ID Code O ID 02/03 Not d TED04 719 Segment Position in Transaction Set O N0 01/06 Not d TED05 722 Element Position in Segment O N0 01/02 Not d TED06 725 Data Element Reference Number O N0 01/04 Not d TED07 724 Copy of Bad Data Element O AN 01/99 Must TED08 961 Data Element New Content O AN 01/99 Not d Error code assigned by HTNA Value referred to by TED01 Key data for bad data ** Please refer to IGEC.9 (824 Error codes-msgs).xls for more information. 12/17
SEGMENT: NTE NOTE/SPECIAL INSTRUCTION LEVEL/POSITION: Detail / 080 MAX USAGE/LOOP: EXAMPLE: 100 / OTI/TED To transmit information in a free-format, if necessary, for comment or special instruction The NTE segment contains the brief error message generated by HTNA which corresponds to the error code in the first 3 positions of TED02. NTE**INVALID PO/50000~ ** This segment is optional. NTE01 363 Note Reference Code O ID 03/03 Not d NTE02 3 Message (Free-Format) M AN 01/60 Must ** Please refer to IGEC.9 (824 Error codes-msgs).xls for more information. 13/17
SEGMENT: SE - TRANSACTION SET TRAILER LEVEL: Summary / 010 MAX USAGE/LOOPS: EXAMPLE: 1/None To indicate the end of a transaction set and provide the count of the transmitted segments including the SE and ST segments The number of included segments is the total of all segments d 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*5*0001~ SE01 96 Number Of Included Segments M N0 01/10 Must SE02 329 Transaction Set Control Number M AN 04/09 Must Total number of segments Same as corresponding ST02 14/17
Examples of 824 Transaction Set EXAMPLE 1: All ASN Data Accepted Without Error Hayashi Telempu North America Corp. EDI FORMAT INTERPRETATION ------------------------------------------------------------- ---------------------------------------------------------------------------- ST*824*000000001~ ANSI Transaction Set Control No. = 000000001 BGN*00*053145101*940222*1451~ Transaction Purpose = 00 (Original) Reference No. = 053145101 Generation Date = 02/22/94 Generation Time = 2:51 p.m. N1*SF**92*12345~ ASN Ship-From Location = 12345 N1*ST**92*01~ ASN Ship-To Location = 01 OTI*IA*SI*123456*******856~ REF*PK*123456~ REF*PM*XXXXXXXXXA~ Application Ack Code = IA (Accepted) Reference Number Qualifier = SI Reference Number = 123456 (ASN#) Transaction Set ID Code = 856 (ASN) Reference Number Qualifier = PK Reference Number = 123456 (Packing List) Reference Number Qualifier = PM Reference Number = XXXXXXXXXA (Part No.) DTM*009*940222*1130~ ASN Shipped Date = 02/22/94 ASN Shipped Time = 11:30 a.m. DTM*011*940222*1136~ HTNA ASN Process Date = 02/22/94 HTNA ASN Process Time = 11:36 a.m. SE*10*000000001~ Total Number of Segements = 10 Transaction Set Control No. = 000000001 15/17
EXAMPLE 2 : One Line Item Accepted with Error, and One Rejected EDI FORMAT INTERPRETATION ------------------------------------------------------------- ---------------------------------------------------------------------------- ST*824*000000001~ ANSI Transaction Set Control No. = 000000001 BGN*00*053145101*940222*1451~ Transaction Purpose = 00 (Original) Reference No. = 053145101 Generation Date = 02/22/94 Generation Time = 2:51 p.m. N1*SF**92*12345~ ASN Ship-From Location = 12345 N1*ST**92*01~ ASN Ship-To Location = 01 OTI*IE*SI*123456*******856~ REF*PK*123456~ REF*PM*XXXXXXXXXA~ Application Ack Code = IE (Accepted with Error) Reference Number Qualifier = SI Reference Number = 123456 (ASN#) Transaction Set ID Code = 856 (ASN) Reference Number Qualifier = PK Reference Number = 123456 (Packing List) Reference Number Qualifier = PM Reference Number = XXXXXXXXXA (Part No.) DTM*009*940222*1130~ ASN Shipped Date = 02/22/94 ASN Shipped Time = 11:30 a.m. DTM*011*940222*1136~ HTNA ASN Process Date = 02/22/94 HTNA ASN Process Time = 11:36 a.m. TED*070*DATE SHIPPED IS AFTER CUSTOMER RELEASE DATE*****37765~ HTNA Error Code = 010 HTNA Error Desc = " DATE SHIPPED IS AFTER CUSTOMER RELEASE DATE " Key data for bad data = 37765 (Order number) NTE**ACCEPTED WITH ERROR/090713~ OTI*IR*SI*123456*******856~ REF*PK*123456~ Error Message = ACCEPTED WITH ERROR/090713 Application Ack Code = IR (Rejected) Reference Number Qualifier = SI Reference Number = 123456 (ASN#) Transaction Set ID Code = 856 (ASN) Reference Number Qualifier = PK Reference Number = 123456 (Packing List) 16/17
REF*PM*ZZZZZZZZZB~ Reference Number Qualifier = PM Reference Number = ZZZZZZZZZB (Part No.) DTM*009*940222*1130~ ASN Shipped Date = 02/22/94 ASN Shipped Time = 11:30 a.m. DTM*011*940222*1136~ HTNA ASN Process Date = 02/22/94 HTNA ASN Process Time = 11:36 a.m. TED*076*PO DOES NOT MATCH CUSTOMER RELEASE***** ZZZZZZZZZB~ HTNA Error Code = 076 HTNA Error Desc = " PO DOES NOT MATCH CUSTOMER RELEASE " Key data for bad data = ZZZZZZZZZB (Part number) NTE**INVALID PO/50000~ Error Message = INVALID PO/50000 SE*19*000000001~ Total Number of Segements = 19 Transaction Set Control No. = 000000001 ** In this example, it will ca the whole ASN to fail beca there is an error (OTI01= IR : Rejected) in the line items of the ASN. The ASN sender must fix what is wrong with the ASN and resend it. 17/17