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



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

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

AMTEX IMPLEMENTATION GUIDELINES FOR EDI CONVENTIONS

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

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

856 Advanced Shipping Notices (ASN)

824 Application Advice

Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

Electronic Data Interchange

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

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

810 Invoice ANSI ASC X12 Version 4010

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

ANSI X12 version Advance Ship Notice

KANSAS CITY SOUTHERN EDI On-Boarding Guide

CSX EDI 824 Application Advice Version:

DoD Transportation Electronic Data Interchange (EDI) Convention

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

ANSI X12 version Text Message

997 Functional Acknowledgment

EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message

ANSI X12 version Remittance Advice

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

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

ANSI X12 version Planning Schedule with Release Capability

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

Ultramar Ltd IMPLEMENTATION GUIDE

Detail SE Transaction Set Trailer Summary GE Functional Group Trailer Summary IEA Interchange Control Trailer Summary. ISA Interchange Control Header

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

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

214 Transportation Carrier Shipment Status Message - LTL

EDI GUIDELINES INVOICE 810 VERSION 4010

VERSION: ANSI X

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

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

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

BLUE CROSS AND BLUE SHIELD OF LOUISIANA DENTAL CLAIMS COMPANION GUIDE

810 Invoice Revised 01/26/15

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

Supply Chain Merchandise Logistics E-Commerce Purchase Order

810 Invoice ANSI X.12 Version 5010

Staples Supplier Electronic Data Interchange Implementation Guide

Purpose of the 270/271 Health Care Eligibility Benefit Inquiry and Response

CREDIT CARD BULK PROVIDER REQUIREMENTS

State of Tennessee Department of Revenue

Mazda North American Operations EDI Supplier Documentation October 20, 2015

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION

Unified Grocers 820 EFT Specifications Remittance Advice Document Structure

999 Implementation Acknowledgment. Version: 1.0 Draft

860 Purchase Order Change Request Buyer Initiated

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

ANSI X Product Transfer and Resale Report

Electronic Data Interchange

State of Nebraska. Motor Fuels Division. EDI Implementation Guide. Revised May ANSI ASC X12 V.4030

The information in this document will be common for all X12N implementation guides.

Transaction Set Application Advice

ANSI X12 ASN 856 Version

Arkansas Blue Cross Blue Shield EDI Report User Guide. May 15, 2013

Electronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy

Portland General Electric Implementation Standard

VDP Program Vendor Guidelines

820 Payroll Deducted and Other Group Premium Payment for Insurance Products

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

Customer EDI Guidelines United States 810 Invoice

NEXCOM EDI 753 / 754 Supplier Shipping Instructions

ADOBE ANSI X Version: 1.0

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

HIPAA EDI Companion Guide for 835 Electronic Remittance Advice

Implementation Guide to. Application Advice - Freight Bill EDI 824. In Response to CN Invoices. December 31, 2010

820 Payroll Deducted and Other Group Premium Payment for Insurance Products

DRS Defect Report Inbound 322. DRS Defect Report from Trading partner to Chassis.Com IB 322 Implementation Guide Prepared by Advent Inc for OCEMA

856 Ship Notice/Manifest - R US CANADA

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

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

Florida. Department of Revenue. Motor Fuels EDI Technical Implementation Guide. July 2015 ANSI ASC X12 V.4030

835 Claim Payment/Advice

EDI GUIDELINES PURCHASE ORDER 850 VERSION 4010

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

214 Transportation Carrier Shipment Status Message

835 Health Care Claim Payment/Advice Functional Group=HP

VOLVO Dealer Programs 810 Invoice EDI Guideline

Commonwealth of Kentucky Department of Revenue

835 Transaction Companion Guide Healthcare Claim Payment/Advice. Version X91A1 (Addendum)

HP SYSTEMS UNIT. Companion Guide: Electronic Data Interchange Reports and Acknowledgements

EDI SPECIFICATIONS 4050VICS VERSION

837 Professional Health Care Claim

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

276/277 HIPAA Transaction Companion Guide HIPAA/V005010X212 VERSION: 1.0 DATE: 02/05/2014

MERITOR. EDI Business Process Guide

Geisinger Health Plan

ACH Implementation Guide for Electronic Funds Transfer: Industry

322 TERMINAL OPERATIONS AND INTERMODAL RAMP ACTIVITY

837 Health Care Claim: Institutional Companion Guide. HIPAA version 5010

Implementation Guideline

Ford Customer Service Division SDS (Supplier Direct Ship) EDI Manual

EDI Specifications Advance Ship Notice (Supplier v4010)

Electronic Document Interchange Standards Version 5050

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

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010

California Solar Initiative

Transcription:

Implementation Guidelines: ANSI X12 Transaction Set 824 DOCUMENT NUMBER: ICS 004010 824 S ESSAR Steel Algoma Inc. Information Systems and Business Process Improvement Author: Greg Masters Effective Date: 2001-04-24

ESSAR Steel Algoma Inc. PAGE NO.: i TABLE OF CONTENTS SECTION 1. REVISION STATUS... 1.1 SECTION 2. PREFACE... 2.1 SECTION 3. SUMMARY... 3.1 SECTION 4. INTERCHANGE ENVELOP... 4.1 ISA - Interchange Control Header... 4.2 4.1 Element separators and segment terminator... 4.4 4.2 IEA - Interchange Control Trailer... 4.5 SECTION 5. FUNCTIONAL GROUP ENVELOPE... 5.1 GS - Functional Group Header... 5.2 5.1 GE - Functional Group Trailer... 5.3 SECTION 6. 824 TRANSACTION SET... 6.1 Data Segment Sequence... 6.2 6.1 ST - Transaction Set Header... 6.3 6.2 BGN - Beginning Segment for... 6.4 6.3 N1 - Name... 6.5 6.4 OTI - Original Transaction Identification... 6.6 6.5 REF - Reference Numbers... 6.8 SECTION 7. DATA ELEMENT DICTIONARY... 7.1 SECTION 8. 824 SAMPLE TRANSACTION... 8.1

ESSAR Steel Algoma Inc. PAGE NO.: 1.1 SECTION 1. REVISION STATUS

ESSAR Steel Algoma Inc. PAGE NO.: 1.2 REVISION DATE PAGES AUTHOR NUMBER ========================================================== R00/A 1995 12 05 original draft G. Masters R00 1995 12 12 original G. Masters R01 1995 12 22 fixed GS elements G. Masters R02 1996 01 31 revised N1 segment G. Masters R03 1998 09 04 added 080 to DTM01 G. Masters R04 2000 03 07 revised summary G. Masters R05 2000 03 22 converted to 4010 G. Masters R06 2001 01 15 added REF~SE G. Masters R07 2001 04 24 for suppliers RMR G. Masters R08 2003 04 04 Revised element & G. Masters sub-element separator. R09 2008 06 23 Name change G. Masters

ESSAR Steel Algoma Inc. PAGE NO.: 2.1 SECTION 2. PREFACE

ESSAR Steel Algoma Inc. PAGE NO.: 2.2 This document is intended to provide the details on the construct of an electronic 824 transaction set to satisfy Algoma's requirements. Essar Steel Algoma Inc. is committed to supporting and using the American National Standards Institute (ANSI) X12 national standards. However, the standards are broad in scope and flexible in methods of implementing. These are the Algoma specific requirements for the. Any questions or concerns regarding the Algoma application advice or electronic data communication with Algoma may be directed to: ESSAR Steel Algoma Inc. IS & BPI 105 West Street Sault Ste. Marie, ON P6A 7B4 Kathy Rathwell 705 945-3058 krathwel@algoma.com Greg Masters 705 945-2981 gmasters@algoma.com Fax 705 945-2366

ESSAR Steel Algoma Inc. PAGE NO.: 3.1 SECTION 3. SUMMARY

ESSAR Steel Algoma Inc. PAGE NO.: 3.2 In order for Essar Steel Algoma Inc. to efficiently service its customers, Algoma has implemented the ANSI X12 824 transaction set. This transaction set will be used to report errors found in the data content edit of inbound transactions (856, 861 and 870). It is very important not to confuse the (824) with the Functional Acknowledgement (997). The 997 only provides the results of a syntactical check of the incoming transaction and is not concerned with the data content. The 824 reports on the results of the analysis of the actual data as processed by Algoma. All data fields on the inbound transaction are checked for validity and adherence to Algoma's requirements. Any discrepancies in the inbound data will be reported via the 824. The supplier of the inbound transaction must use this information to resolve the discrepancies and retransmit corrected data immediately. NOTE: If any one piece of information is rejected on an ASN, the entire ASN is rejected. The ASN must be corrected and the complete ASN must be resent to Algoma. All 824 transactions must be acknowledged with a Functional Acknowledgement (997). Essar Steel Algoma Inc. uses the GXS network for electronic data interchange. Algoma's DUNS number is 201495124.

ESSAR Steel Algoma Inc. PAGE NO.: 4.1 SECTION 4. INTERCHANGE ENVELOP

ESSAR Steel Algoma Inc. PAGE NO.: 4.2 ISA - Interchange Control Header Segment: Level: Max Use/Loops: Purpose: General Information: ISA - Interchange Control Header n/a 1 per interchange/none To start and identify an interchange of one or more functional groups and interchange related control segments. None Example: ISA~00~ ~00~ ~01~201495124 ~ 01~999999999 ~940901~1312~U~00401~000000001~1~ P~` N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- ISA01 744 Authorization M ID 02/02 "00" (Zeros) Information Qual No authorization information present ISA02 745 Authorization M AN 10/10 Use 10 spaces Information ISA03 746 Security M ID 02/02 "00" (Zeros) Information Qual No security information present ISA04 747 Security M AN 10/10 Use 10 spaces Information ISA05 704 Interchange Sender M ID 02/02 "01" for DUNS number. ID Qualifier ISA06 705 Interchange Sender M ID 15/15 "201495124" ID left justified. ISA07 704 Interchange Receiver M ID 02/02 "01" for DUNS number. ID Qualifier "09" for phone number. "ZZ" for mutually defined. ISA08 706 Interchange Receiver M ID 15/15 Receiver's ID number ID left justified. ISA09 373 Interchange Date M DT 06/06 Date of Transmission (YYMMDD) ISA10 337 Interchange Time M TM 04/04 Time of Transmission (HHMM) 24 hour clock

ESSAR Steel Algoma Inc. PAGE NO.: 4.3 Segment: ISA - Interchange Control Header Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- ISA11 726 Interchange Standard M ID 01/01 "U" for USA ID ISA12 703 Interchange Version M ID 05/05 "00401" ID ISA13 709 Interchange Control M N0 09/09 Sequential Number ID starting with 1 and incremented by 1 for each ISA sent. ISA14 749 Acknowledgement M ID 01/01 "0" for acknowledge- ID ment not required. ISA15 748 Test Indicator M ID 01/01 "P" for production "T" for test ISA16 701 Sub Element M AN 01/01 Must be different Separator then the element separator.

ESSAR Steel Algoma Inc. PAGE NO.: 4.4 4.1 Element separators and segment terminator Algoma uses the following characters: Segment terminator EBCDIC Hex "1C" Element separator EBCDIC Hex "5C" Sub element separator EBCDIC Hex "A1"

ESSAR Steel Algoma Inc. PAGE NO.: 4.5 4.2 IEA - Interchange Control Trailer Segment: Level: Max Use/Loops: Purpose: General Information: Example: IEA - Interchange Control Trailer n/a 1 per interchange/none To define the end of an interchange of one or more functional groups and interchange related control segments. None IEA~3~000000001 N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- IEA01 405 Number of Included M N0 01/05 Number of GS Groups segments included between ISA and this IEA IEA02 709 Interchange Control M N0 09/09 Must match ISA13 Number

ESSAR Steel Algoma Inc. PAGE NO.: 5.1 SECTION 5. FUNCTIONAL GROUP ENVELOPE

ESSAR Steel Algoma Inc. PAGE NO.: 5.2 GS - Functional Group Header Segment: Level: GS - Functional Group Header n/a Max Usage/Loops: 1/None Purpose: General Information: Example: The GS segment is used to indicate the beginning of a functional group and to provide control information None GS~AG~201495124~999999999~20010420~1312~1~X~004010 N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- GS01 479 Functional ID M ID 02/02 "AG" GS02 142 Application Sender M ID 02/12 Sender s ID number. Code GS03 124 Application M ID 02/12 Receiver s ID Receiver Code number. GS04 29 Data Interchange M DT 08/08 Date created Date (CCYYMMDD) GS05 30 Data Interchange M TM 04/04 Time created Time (HHMM) GS06 28 Data Interchange M N0 01/09 Start with 1 and Control Number increment by 1 for each subsequent GS between interchanges GS07 455 Responsibility M ID 01/02 Use "X" for ANSI Agency X12 code formats GS08 480 Version M ID 01/12 "004010"

ESSAR Steel Algoma Inc. PAGE NO.: 5.3 5.1 GE - Functional Group Trailer Segment: Level: GE - Functional Group Trailer n/a Max Usage/Loops: 1 per functional group/none Purpose: General Information: Example: To define (specify) the end of a functional group of related transaction sets. None GE~3~1 N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- GE01 97 Number of Included M N0 01/06 Total count of Transaction Sets transaction sets in functional group GE02 28 Data Interchange M N0 01/09 Same as GS06 in the Control Number associated group header

ESSAR Steel Algoma Inc. PAGE NO.: 6.1 SECTION 6. 824 TRANSACTION SET

ESSAR Steel Algoma Inc. PAGE NO.: 6.2 Data Segment Sequence ST BGN N1 OTI REF DTM TED SE Transaction Set Header Beginning Segment for Name Original Transaction Identification Reference Numbers Date/Time Reference Technical Error Description Transaction Set Trailer

ESSAR Steel Algoma Inc. PAGE NO.: 6.3 6.1 ST - Transaction Set Header Segment: Level: ST - Transaction Set Header Header Max Usage/Loops: 1/None Purpose: General Information: Example: To indicate the start of a transaction set and to assign a control number. This segment is required. The transaction set control number (ST02) in this header must match the transaction set control number (SE02) in the transaction set trailer (SE). ST~824~0001 N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- ST01 143 Transaction Set M ID 03/03 Use "824" ID Code ST02 329 Transaction Set M AN 04/09 A unique number Control Number assigned to each transaction set within a functional group.

ESSAR Steel Algoma Inc. PAGE NO.: 6.4 6.2 BGN - Beginning Segment for Segment: Level: BGN - Beginning Segment for Header Max Usage/Loops: 1/None Purpose: General Information: Example: To indicate the beginning of an Transaction Set and to transmit an identifying number, date and other basic data relating to the transaction set. The date and time are the date and local time of the creation of the transaction. BGN~00~123456~19940916~1421 N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- BGN01 353 Transaction Set M ID 02/02 "00" - original Purpose Code BGN02 127 Reference Number M AN 01/30 A unique number generated by the receiver of the original document. BGN03 373 Date M DT 08/08 Creation date (CCYYMMDD) BGN04 337 Time C TM 04/08 Creation time (HHMM) 24 hour clock. BGN05 623 Time Code O ID 02/02 Not used. BGN06 127 Reference O AN 01/30 Not used. Identification BGN07 640 Transaction Type O ID 02/02 Not used. Code BGN08 306 Action Code O ID 01/02 Not used. BGN09 786 Security Level Code O ID 02/02 Not used.

ESSAR Steel Algoma Inc. PAGE NO.: 6.5 6.3 N1 - Name Segment: Level: N1 - Name Header Max Usage/Loops: 1 per N1 loop whose max usage is 2. Purpose: General Information: Example: To identify a party by type of organization, name and code. Ship-to and consignor or ship-to and ship-from segments will be sent. N1~CI~ACME~1~745942164 N/L N1~ST~ACCURIDE N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- N101 98 Entity Identifier M AN 02/03 "ST" for ship-to Code "CI" for consignor "SF" for ship-from N102 93 Name M AN 01/60 Organization's name. N103 66 ID Code Qualifier O ID 01/02 "1" for DUNS number. "ZZ" for mutually defined. N104 67 ID Code O AN 02/80 DUNS number. N105 706 Entity Relationship O ID 02/02 Not used. Code N106 98 Entity Identifier O AN 02/03 Not used. Code

ESSAR Steel Algoma Inc. PAGE NO.: 6.6 6.4 OTI - Original Transaction Identification Segment: Level: OTI - Original Transaction Identification Detail Max Usage/Loops: 1/10,000 Purpose: General Information: Example: 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 results. One OTI loop is generated for each line item. OTI~IR~SI~123456~~~~~3452~3452~856 N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- OTI01 110 Application M ID 01/02 "IA" item accepted. Acknowledgement Code "IE" item accepted with error. "IR" item rejected: re-check transaction set to insure accuracy before resending. OTI02 128 Reference Number M ID 02/02 "SI" Shipper's Qualifier Identification (SID) number. See Data Element Dictionary section for complete list of values. OTI03 127 Reference Number M AN 01/30 Based on the value of OTI02. OTI04 142 Application Sender's O AN 02/12 Not used. Code OTI05 124 Application O AN 02/12 Not used. Receiver's Code OTI06 373 Date O DT 08/08 Not used. OTI07 337 Time O TM 04/08 Not used. OTI08 28 Group Control O N0 01/09 GS06 from original Number transaction. OTI09 329 Transaction Set O AN 04/09 ST02 from original Control Number transaction OTI10 143 Transaction Set O ID 03/03 Original transaction set Identifier Code ID.

ESSAR Steel Algoma Inc. PAGE NO.: 6.7 Segment: OTI - Original Transaction Identification Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- OTI11 480 Version/Release/ O ID 01/12 Original transaction Industry ID Code version. OTI12 353 Transaction Set O ID 02/02 Not used. Purpose Code OTI13 640 Transaction Type O ID 02/02 Not used. Code OTI14 346 Application Type O ID 02/02 Not used. Code OTI15 306 Action Code O ID 01/02 Not used. OTI16 305 Transaction Handling O ID 01/02 Not used. Code OTI17 641 Status Reason Code O ID 03/03 Not used.

ESSAR Steel Algoma Inc. PAGE NO.: 6.8 6.5 REF - Reference Numbers Segment: Level: REF - Reference Numbers Detail Max Usage/Loops: 12 per OTI loop. Purpose: General Information: Example: To transmit identifying numbers. Used to specify reference numbers from the original transaction (i.e. bill of lading, heat, mill order item, processor piece ID, Algoma's mill/tag number). REF~BM~32418 N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- REF01 128 Reference Number M AN 02/03 "BM" for BOL. Qualifier "HC" for heat. See Data Element Dictionary section for a complete list of values. REF02 127 Reference Number M AN 01/30 Based on REF01. REF03 352 Description O AN 01/80 Not used.

ESSAR Steel Algoma Inc. PAGE NO.: 6.9 DTM - Date/Time Reference Segment: Level: DTM - Date/Time Reference Detail Max Usage/Loops: 2 per OTI loop Purpose: General Information: Example: To specify pertinent dates and times. At least one occurrence of the DTM segment will be sent. DTM01 will be 011 when in response to a shipment. DTM01 will be 080 when in response to a ready status ASN. DTM~011~19940916~1421 N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- DTM01 374 Date/Time M AN 03/03 "011" for ASN ship Qualifier date/time. "009" Algoma process date/time. "080" for date/time from ready status ASN DTM02 373 Date M DT 08/08 Date (CCYYMMDD) DTM03 337 Time M TM 04/08 Time (HHMM) 24 hour clock. DTM04 623 Time Code O ID 02/02 Not used. DTM05 1250 Date Time Period O ID 02/03 Not used. Format Qualifier DTM06 1251 Date Time Period O AN 01/35 Not used.

ESSAR Steel Algoma Inc. PAGE NO.: 6.10 TED - Technical Error Description Segment: Level: TED - Technical Error Description Detail Max Usage/Loops: 1/TED 10,000/OTI Purpose: General Information: Example: To identify the error and, if feasible, the erroneous segment, or data element, or both. This segment will only be sent when an error is encountered. TED~003~INVALID ORDER NUMBER~~~~~33212 N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- TED01 647 Application Error M ID 01/03 Algoma assigned error Condition Code number. TED02 3 Free Form Message O AN 01/60 Error message. TED03 721 Segment ID Code O ID 02/03 Not used. TED04 719 Segment Position in O N0 01/06 Not used. Transaction Set TED05 722 Element Position in O N0 01/02 Not used. Segment TED06 725 Data Element O N0 01/04 Not used. Reference Number TED07 724 Copy of Bad Data O AN 01/99 Copy of bad element. Element TED08 961 Data Element New O AN 01/99 Not used. Content

ESSAR Steel Algoma Inc. PAGE NO.: 6.11 SE - Transaction Set Trailer Segment: Level: SE - Transaction Set Trailer Summary Max Usage/Loops: 1/none. Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segment). General Information: Example: SE~23~0001 N/L Elem ID Elem# Name Features Comments ------- ----- ------------------ -------- -------- SE01 96 Number of Included M N0 01/06 Segments SE02 329 Transaction Set M AN 04/09 Same as ST02 Control Number

ESSAR Steel Algoma Inc. PAGE NO.: 7.1 SECTION 7. DATA ELEMENT DICTIONARY

ESSAR Steel Algoma Inc. PAGE NO.: 7.2 66 ID Code Qualifier 1 DUNS number 98 Entity Identifier Code CI Consignor SF Ship from ST Ship to 110 Application Acknowledgement Code IA Item accepted IE Item accepted with error IR Item rejected 128 Reference Number Qualifier BM Bill of lading F8 Reference identification HC Heat number LS Mill/tag number MI Mill order item SI Shipper's Identification (SID) number SE Serial Number (Processor piece ID.) 353 Transaction Set Purpose Code 00 Original 374 Date/Time Qualifier 009 Receiver process date/time 011 ASN ship date/time 647 Application Error Condition Code 006 Duplicate 007 Missing data 009 Invalid date 011 Not matching 012 Invalid combination 024 Other unlisted reason 848 Incorrect data H Missing or invalid processing MQT Missing quantity ZZZ Mutually defined

ESSAR Steel Algoma Inc. PAGE NO.: 8.1 SECTION 8. 824 SAMPLE TRANSACTION

ESSAR Steel Algoma Inc. PAGE NO.: 8.2 ISA~00~ ~00~ ~01~201495124 ~01~ 207663412 ~940901~1312~U~00302~000000001~1~P~` GS~AG~207663412~201495124~20010420~1312~1~X~004010 ST~824~0001 BGN~00~20030401043000001~20030401~0430 N1~ST~MISSING DATA~ZZ~ABCDEFG 00 N1~CI~MISSING DATA~ZZ~ABCDEFG 00 OTI~IR~SI~J425984~~~~~24~000240002~856~004010 REF~BM~13097000 DTM~011~20030331~0000 DTM~009~20030401~0409 TED~011~PO LINE ITEM DOES NOT EXIST ON PO/RLSE.~~~~~215472 0000 004 TED~ZZZ~~~~~~CORRECT AND RESEND ENTIRE ASN SE~21~0001 ST~824~0002 BGN~00~20030329050100001~20030329~0501 N1~ST~ESSAR Steel Algoma Inc~1~201495124 N1~SF~ANY COMPANY~ZZ~ABCDEFG 00 OTI~IR~SI~J415383~~~~~22~000220002~856~004010 REF~PK~J415383 REF~BV~000 DTM~011~20030328~0000 DTM~009~20030329~0432 TED~007~MISSING PART NUMBER TED~ZZZ~~~~~~CORRECT AND RESEND ENTIRE ASN SE~12~0002 GE~2~1 IEA~1~000000001