ANSI X12 version 4010 864 Text Message



Similar documents
ANSI X12 version Remittance Advice

ANSI X12 version Advance Ship Notice

824 Application Advice

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

810 Invoice ANSI ASC X12 Version 4010

ANSI X12 version Planning Schedule with Release Capability

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

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

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

Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

ANSI X Product Transfer and Resale Report

EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message

999 Implementation Acknowledgment. Version: 1.0 Draft

810 Invoice Revised 01/26/15

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

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

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION

214 Transportation Carrier Shipment Status Message

VERSION: ANSI X

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

ADOBE ANSI X Version: 1.0

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

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

Transaction Set Application Advice

214 Transportation Carrier Shipment Status Message - LTL

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

997 Functional Acknowledgment

DoD Transportation Electronic Data Interchange (EDI) Convention

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

CSX EDI 824 Application Advice Version:

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

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

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

BORGWARNER IMPLEMENTATION GUIDELINE FOR V PLANNING SCHEDULE

Portland General Electric Implementation Standard

EDI GUIDELINES INVOICE 810 VERSION 4010

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

856 Advance Ship Notice Supplier Implementation Guide November 2015

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

Electronic Data Interchange

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

945 Warehouse Shipping Advice

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

Implementation Guideline

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

810 Invoice ANSI X.12 Version 5010

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

KANSAS CITY SOUTHERN EDI On-Boarding Guide

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

Electronic Data Interchange

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

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

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

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

860 Purchase Order Change Request Buyer Initiated

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

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

ANSI ASC X12 SHIPMENT STATUS (214) VERSION

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

Electronic Document Interchange Standards Version 5050

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

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

WPS Health Solutions

EDI GUIDELINES PURCHASE ORDER 850 VERSION 4010

HIPAA EDI Companion Guide for 835 Electronic Remittance Advice

856 Ship Notice/Manifest - R US CANADA

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

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

Unified Grocers 820 EFT Specifications Remittance Advice Document Structure

HIPAA - ASC X12N Outbound EDI 835 Electronic Remittance Advice Transaction

MV-STAR. I/O Reference Guide

Supply Chain Merchandise Logistics E-Commerce Purchase Order

835 Health Care Payment/ Remittance Advice Companion Guide

820 Payroll Deducted and Other Group Premium Payment for Insurance Products

Adobe - EDIFACT D97.A ORDERS

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

Combined Insurance Company of America

835 Health Care Claim Payment/Advice Functional Group=HP

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010

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

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

Geisinger Health Plan

PURCHASE ORDER RESPONSE

BLUE CROSS AND BLUE SHIELD OF LOUISIANA DENTAL CLAIMS COMPANION GUIDE

820 ANSI X12 Version

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

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

835 Claim Payment/Advice

WPS Health Insurance

Ultramar Ltd IMPLEMENTATION GUIDE

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

ASC X12 Finance Subcommittee. Consumer Service Provider (CSP) Billing and Payment Guide

856 Advanced Shipping Notices (ASN)

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

DLMS Supplement to Federal IC 996H GENCOMM / XML ADC 416 DoD M

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

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

Transcription:

ANSI X12 version 4010 864 Text Message VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 08/22/00 Trading Partner: All Partners 864 All Partners 4010 Inbound.rtf 1 Superior Essex

864 Text Message Functional Group=TX This Draft Standard for Trial Use contains the format and establishes the data content of the Text Message Transaction Set (864) for within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be d to provide rs with a capability to electronically move messages, contracts, explanations, and other one-time communications.it is the intent of this transaction set to provide electronic communication (messages) for people, not for computer processing. The of the transaction set to transmit quasi or unique transaction set standards is discouraged.the of the Text Message transaction set demands of the sender certain detailed information about the recipient. The transaction set's purpose is to provide communication to the recipient in some human-readable form. The recipient's network will dictate what capabilities are available for delivery of the information. It is the responsibility of the sender to obtain this information and include it in the transmission. 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 BMG Beginning Segment For Text Message M 1 Must 030 DTM Date/Time Reference O 10 Used LOOP ID - N1 200 040 N1 Name O 1 Used 050 N2 Additional Name Information O 2 Used 060 N3 Address Information O 2 Used 070 N4 Geographic Location O 1 Used 090 PER Administrative Communications Contact O 3 Used Detail: Pos Id Segment Name Req Max Use Repeat Notes Usage LOOP ID - MIT >1 010 MIT Message Identification M 1 Must 080 MSG Message Text M 10000 0 Must Summary: Pos Id Segment Name Req Max Use Repeat Notes Usage 010 SE Transaction Set Trailer M 1 Must Segments: Pos Id Segment Name Req Max Repeat Notes Usage Use GE Functional Group Trailer M 1 Used IEA Interchange Control Trailer M 1 Used 864 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 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 M ID 2/2 Must M AN 10/10 Must M ID 2/2 Must M AN 10/10 Must M ID 2/2 Must M AN 15/15 Must M ID 2/2 Must M AN 15/15 Must 864 All Partners 4010 Inbound.rtf 3 Superior Essex

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 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 864 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 TX Text Message (864) 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 Descriptin: 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 ID 2/2 Must 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. 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. 864 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 864 Text Message 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). BMG Beginning Segment For Text Message Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 To indicate the beginning of a Text Message Transaction Set BMG01 353 Transaction Set Purpose Code Description: Code identifying purpose of transaction set 00 Original M ID 2/2 Must BMG02 352 Description Description: A free-form description to clarify the related data elements and their content O AN 1/80 Used 1. BMG02 contains the message subject. 864 All Partners 4010 Inbound.rtf 6 Superior Essex

DTM Date/Time Reference Pos: 030 Max: 10 Heading - Optional Loop: N/A Elements: 6 To specify pertinent dates and times DTM01 374 Date/Time Qualifier Description: Code specifying type of date or time, or both date and time All valid standard codes are d. DTM02 373 Date Description: Date expressed as CCYYMMDD M ID 3/3 Must C DT 8/8 Used DTM03 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) DTM04 623 Time Code Description: Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow All valid standard codes are d. DTM05 1250 Date Time Period Format Qualifier Description: Code indicating the date format, time format, or date and time format All valid standard codes are d. DTM06 1251 Date Time Period Description: Expression of a date, a time, or range of dates, times or dates and times C TM 4/8 Used O ID 2/2 Used C ID 2/3 Used C AN 1/35 Used Syntax: 1. DTM02 R020305 -- At least one of DTM02, DTM03 or DTM05 is required. 2. DTM04 C0403 -- If DTM04 is present, then DTM03 is required 3. DTM05 P0506 -- If either DTM05 or DTM06 are present, then the others are required. 864 All Partners 4010 Inbound.rtf 7 Superior Essex

N1 Name Pos: 040 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. 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. 864 All Partners 4010 Inbound.rtf 8 Superior Essex

N2 Additional Name Information Pos: 050 Max: 2 Heading - Optional Loop: N1 Elements: 2 To specify additional names or those longer than 35 characters in length N201 93 Name Description: Free-form name M AN 1/60 Must N202 93 Name Description: Free-form name O AN 1/60 Used N3 Address Information Pos: 060 Max: 2 Heading - Optional Loop: N1 Elements: 2 To specify the location of the named party N301 166 Address Information Description: Address information M AN 1/55 Must N302 166 Address Information Description: Address information O AN 1/55 Used 864 All Partners 4010 Inbound.rtf 9 Superior Essex

N4 Geographic Location Pos: 070 Max: 1 Heading - Optional Loop: N1 Elements: 4 To specify the geographic place of the named party N401 19 City Name O AN 2/30 Used Description: Free-form text for city name N402 156 State or Province Code Description: Code (Standard State/Province) as defined by appropriate government agency O ID 2/2 Used N403 116 Postal Code Description: Code defining international postal zone code excluding punctuation and blanks (zip code for United States) O ID 3/15 Used N404 26 Country Code Description: Code identifying the country O ID 2/3 Used Syntax: 1. N406 C0605 -- If N406 is present, then N405 is required 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2. N402 is required only if city name (N401) is in the U.S. or Canada. 864 All Partners 4010 Inbound.rtf 10 Superior Essex

PER Administrative Communications Contact Pos: 090 Max: 3 Heading - Optional Loop: N1 Elements: 6 To identify a person or office to whom administrative communications should be directed PER01 366 Contact Function Code Description: Code identifying the major duty or responsibility of the person or group named All valid standard codes are d. PER02 93 Name Description: Free-form name M ID 2/2 Must O AN 1/60 Used PER03 365 Communication Number Qualifier Description: Code identifying the type of communication number All valid standard codes are d. PER04 364 Communication Number Description: Complete communications number including country or area code when applicable PER05 365 Communication Number Qualifier Description: Code identifying the type of communication number All valid standard codes are d. PER06 364 Communication Number Description: Complete communications number including country or area code when applicable C ID 2/2 Used C AN 1/80 Used C ID 2/2 Used C AN 1/80 Used Syntax: 1. PER03 P0304 -- If either PER03 or PER04 are present, then the others are required. 2. PER05 P0506 -- If either PER05 or PER06 are present, then the others are required. 3. PER07 P0708 -- If either PER07 or PER08 are present, then the others are required. 864 All Partners 4010 Inbound.rtf 11 Superior Essex

MIT Message Identification Pos: 010 Max: 1 Detail - Mandatory Loop: MIT Elements: 4 To identify the beginning of a specific message and to allow the identification of a subject for the message MIT01 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 MIT02 352 Description Description: A free-form description to clarify the related data elements and their content O AN 1/80 Used MIT03 931 Page Width Description: Definition of the maximum number of characters per line that can be expected in the message text O N0 1/3 Used MIT04 932 Page Length Lines Description: Definition of the maximum number of lines per page that can be expected in the message text O N0 1/3 Used Semantics: 1. MIT01 contains the message number. 2. MIT02 contains the message subject. 1. MIT03 default is 80 characters. 2. MIT04 default is 66 lines. 864 All Partners 4010 Inbound.rtf 12 Superior Essex

MSG Message Text Pos: 080 Max: 100000 Detail - Mandatory Loop: MIT Elements: 3 To provide a free-form format that allows the transmission of text information MSG01 933 Free-Form Message Text Description: Free-form message text M AN 1/264 Must MSG02 934 Printer Carriage Control Code Description: A field to be d for the control of the line feed of the receiving printer All valid standard codes are d. MSG03 1470 Number Description: A generic number C ID 2/2 Used O N0 1/9 Used Syntax: 1. MSG03 C0302 -- If MSG03 is present, then MSG02 is required Semantics: 1. MSG03 is the number of lines to advance before printing. 1. MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc. 2. If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required. 864 All Partners 4010 Inbound.rtf 13 Superior Essex

SE Transaction Set Trailer Pos: 010 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 1. SE is the last segment of each transaction set. 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. 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. 864 All Partners 4010 Inbound.rtf 14 Superior Essex

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 864 All Partners 4010 Inbound.rtf 15 Superior Essex