DoD DTIC- Electronic Data____ DoD DTIC- Electronic Data S NO0919 Interchange (EDI) F Convention ASC...

AD-A286 076

S)/

Department

bi Defense

____ DoDDTIC- Electronic Data

S NO0919 Interchange (EDI)F Convention

ASC X12 Transaction Set 410Rail Carrier Invoice(Version 003020)

This clod • 7,sbeao• dve-lob pdbliec z-•eiese oncd sa e; it3 DF1O1LN7distributio,3 is uniijaited- t

94-34576 ,March 1993

9 I 1 11 11111111 1 19 4lii 1 117 0 71930315 94 11 7 071

DEPARTMENT OF DEFENSE RAIL CARRIER INVOICEEDI CONVENTION 410.003020

' , Department

L k-Defense

DoDElectronic Data

S--: -I Interchange (EDI)_____.._ _ ......_ . ConventionBy..............Distribution_ ASC X 12 Transaction Set 410

Av,:Thty oRail Carrier InvoiceAvail a: c , or

Dit Special (Version 003020)

This damsmcnt was prepared by the Lagigia M•aageswwu Ir ute for the ' RuuFace amndActounting Semvic - Iblumahs- Cenum and the Dekin Lqeis Agency under TUak DI01. The tubwas pwerfw d uuder contract MDADM0-90C.O with th DeLpmbtut of Dom. pmlan to quate oeproduce Amy pon of this dowuu l m p- f-r Gowummt pu sm I uad be chauud hu the

Dpaputnwat of Deiraw Emuiv AVu for D mcokra Coanmtm/Ekhdrok Data hbIneuhap/Pn•idmmeof(LAginia Unwaid/Smomi S,,Syew ,

Executive Agent for EC/EDI/PLUSDefense Logistics AgencyCameron StationAlexandria. VA 22304-6100

930315

DIPARTFA OF DGM RAIL CARRIER INVOICEsI CoNVUeION 410.003020

10.0 DoD EDI CONVENTION

ASC X12 TRANSACTION SET 410 RAILCARRIER INVOICE (VERSION 003020)

FORMATTING INVOICE INFORMATION FOR THE DoDTRANSPORTATION PAYMBEIT SYSTEM USING THE Xl 2.139TRANSACTION SET 410 RAIL CARRIER INVOICE

93021S 10.0

DWARTWET OF DOOMhE RAIL CARRIER NVOICE0 CONVO•M 410.003020

(BLANK AAGE)

10.0 930315

DEPARTMENT OF DEFENSE RAIL CARRIER INVOICE

EDI CONVENIlON 410.003020

Contents

FORMATTING INVOICE INFORMATION FOR THE DoDTRANSPORTATION PAYMENT SYSTEM USING THE X1 2.139TRANSACTION SET 410 RAIL CARRIER INVOICE.

10.i Introduction

10.1 Reserved

10.2 Control Segments

10.3 Reserved

10.4 Reserved

10.5 Data Element Cross-Reference Matrix

10.6 Reserved

10.7 DoD Convention

10.A Reserved

10.8 Reserved

10.C Examples - Invoice Information From Carrier toDFAS-IN Using ASC X12 410

1O.D Reserved

10.E Reserved

10 .F Additional Government Code UWts

93031S 10.0.1

DEPARTMENT OF DE RAIL CARRIER INVOICE

EDI CONVEdTION 410.003020

(BLANK PAGE)

10.0.1 930315

DEPART1MRE OF DW-: E RAIL CARRIER NVOICE

EDI CONVEWNION 410.003020

10.i INTRODUCTION

This is an Electronic Data Interchange (EDI) systems designdocument that describes the standard or "convention" the Depart-ment of Defense (DoD) will use to accept a transportation invoiceusing the ASC X12.139 Transaction Set 410 Rail Carrier Invoice(003020). It contains information for the design of interfacecomputer programs that serve to link systems application com-puter programs and an EDI translator computer program.

Who Needs to Use This DocumentComputer programmers can use this document to identify thedata in a populated EDI transaction with data requirements oftheir specific application database. Conversely, programmers canidentify where their applications data requirement should becarried in an EDI transaction.

Why Use a ConventionThere are more ways to populate an EDI transaction than thereare ways to fill out a blank form. A convention defines the rulesfor filling in or "populating" an EDI transaction with a specificdata set. Following a convention ensures the integrity of datathat is produced and processed by EDI capable computer systems.

ContentsFour sections are included in this document.

"* Section 10.2, Control Segments, identifies the specific datarequirements for formatting the EDI interchange controlsegments needed to send and receive EDI transactions.

" Section 10.5, Data Element Cross-Reference Matrix, lists thedata requirements of DoD and specifies where each dataelement should be carried in the transaction set. This sectioncan be used to map an existing application database into thetransaction set.

" Section 10.7, DoD Conventions, lists the layout of the targettransaction set by segment and data element. Identified alongside each transaction set data element is the cross-referencedata element from Section 10.5. This section can be used tointerpret segments and data elements of a populated transac-tion set.

"* Appendices contain examples of populated transaction sets,trading partner data element matrix, and other items thatserve as references for software developers.

9320315 10.i

RAIL CARRIER INVOICE DEPARTMENT OF D:IFENSE410.003020 EDl CONVENTION

(Blank Page)

10.1 930315

DEPARWTN• OF DENSE RAIL CARRIER INVOICEEDI CONVENTION 410.003020

10.2 Control Segments

OverviewThis chapter describes the Electronic Data Interchange (EDI)comtrol segments (interchange control segments and functionalgroup segments). The control segment information was derivedfrom the ASC X12 Standards Draft Version 3 Release 2(003020).

PurposeThis chapter identifies specific data requirement for formattingthe EDI control segments when transmitting and receiving EDItransactions. The format and data content of the control segmentsis usually managed by EDI translation software. The data re-quirement described herein should be used to set control segmentformat when installing or initializing translation software fortransmission and reception of EDI transaction.

ContentsTwo items are included in this chapter.

"* Table 10.2-1, Interchange Control Segment Hierarchydescribes the control segments in their order of occurrencein an EDI communications interchange.

" Table 10.2-2, DoD Convention ASC X12 Control Segmentsis a detailed description of the Department of Defense dataconventions for formatting EDI standard control segments.All segments identified in Table 10.2-1 are broken down anddescribed by their discrete data elements.

330315 10.2.1

RAIL CARRIER NVOICE DEPARTM9IJT OF DB=EWE410.003020 EDI CONVBNTICN

(Blank Page)

10.2.2 930315

DEPARTAMM OF D699M RAIL CARRIER NVOICE

0I CONVwEamON 410,003020

TABLE 10.2-1

Control Segment Hierarchy

930315 10.2.3

RAIL CARRIER INVOICE DEPARTMENT OF DEBENSE410.003020 EDI CONVBETION

(Blank Page)

10.2.4 930315

DEPAR1W•E OF DUeWMs RAIL CARRIER JVOICEEl CONVBE0N 410.003020

Interchange Control EnvelopeControl Segments

Poe Seg ReqIndustry No. ID Name Des Use Loop

USE 10 ISA Interchange Control Header M 1

USE 20 GS Functional Group Header M 1

* Grouped Transactions

USE 30 GE Functional Group Trailer M 1

USE 40 IEA Interchange Control Trailer M 1

930315 10.2.5

RAIL CARRIER INOICE DEPARTMENT OF DENSe410.003020 EDI CONVENTION

(Blank Page)

10.2.6 930315

DEPARTMET OF DEFOU RAIL CARRIER INVOCEEDI CONVENTION 410.003020

TABLE 10.2-2

DoD Convention

ASC X12 Control Segments

930315 10.2.7

RAL CAIý WV(MDEAR1IAN OF 0SO416 ~N2S w CONV3IOON

(BLANK PAGE)

10.2.8 930315

SWA1T OF ONO RAML CARRIER IMVOICEW CO€NV hITIC 410.003020

Segwmnt: ISA Interchange Control Headerusae: M

Purpom: To start and identify an interchange of oneor more functUonal groups and interchange-related control segments. The actual valuesof the data element separator and the seg-ment terminator for this interchange are setby the interchange control header. For a par-ticular interchange, the value at the fourthcharacter position is the data elementseparator, and the value of the last charposition is the value of the segment ter-minator.

Note: The interchange control number value in thisheader must match the value in the same dataelement in the corresponding interchange con-trol trailer.

Data Element SumnaryRef. DataDes. Elment Name Attributs

ISA01 101 Authorization Information M ID 2/2QualifierCode to identify the type of information in theAuthorization Information.

Authorization Qualifier1001 1 Code Definition

00 No Authorization Information Present

ISA02 102 Authorization Information M ANI 0/10Information used for additional identification orauthorization of the sender or the data in the inter-change.

Authorization Info1002 1

If no authorization information isagreed to by trading partners, fill

field with zeroes.

ISA03 103 Security Information Qualifier M ID 2/2Code to identify the type of information in thesecurity information.

930316 10.2.9

RAIL CARRIER INVOICE DEPARTM4T OF DEFEIE410.003020 EDI CONV9ETOt

Security Qualifier1003 1 Code Definition

00 No security information prewet.

ISA04 104 Security Infoimarion M AM10/10This is used for identifying the security informationabout the sender or the data in the interchange.

Security Info1004 ]

If no security information isagreed to by trading partners, fill

field with zeroes.

ISAO5 105 Interchange Id Oualifier M ID 2/2Qualifier to designate the system/method of codestructure used to designate the sender ID elementbeing qualified.

Sender Qualifier1005 1

Use authorized X 12 code list.

ISA06 106 Interchange Senders Id M AN 5/15Identification code published by the sender for otherparties to use as the receiver ID to route data tothem.

Sender Id1006 1

DoD activities use Department ofDefense Activity Address

Code (DoDAAC) or other codecoordinated with the Defense

Transportation EDI Administrator.Non-DoD activities use identifica-tion code qualified by ISAOS andcoordinated with the value-added

network (VAN).

ISA07 105 Interchange Id Qualifier M ID 2/2

Code to identify the type of information in theAuthorization Information.

Interchange Qualifier[007 1

Use authorized X12 code list.

10.2.10 930315

DWPARAn1W OF DOW E RAIL CARRIER INVOICE8M4 0imVWeTrmN 410.003020

ISA08 107 Interchange Receiver's id M AN15/15Identification code published by the receiver of thedata.

Receiver Id1008 1

For DoD activities. use Depart-ment of Defense Activity Addrem

Code (DoDAAC) or other codecoordinated with the Defense

Transportation EDI Administrator.For Non-DoD activites, use iden-tification code qualified by ISA07

and co mrinated with the VAN.

ISA09 108 Interchange Data M DT 616

Date of the interchange.Date

1009 1Assiwd by transiation saftwaen.

ISA10 109 Interchange Tim M TM 4/4

Time of the interchange.Time

10101

Assigned by translation software.

ISAI 1 110 Interchange Control Standerd M ID 1/1klentifierCode to identify the agency responsible for the con-trol standard used by the message that is enclosed bythe interchange header and trailer.

Standards Id1011 1 Code Definition

U U.S. EDI Community of ASC Xl 2, TDCC, andUCS

ISA12 111 Interchange Control Version M ID 5/5

This version number covers the interchange controlsegments and the functional group control segments.

930315 10.2.11

RAIL CAMR NVOICE DEPARTMBET OF DOMM410.002020 EDI CONVBCTMII

Version Id1012 1

Version ID as defined or agreedupon by the trading partners.

Code Definition00302 Draft Standard for Trial Use Approved for

"Publication by ASC X 12 Procedur ReviewBoard Through October 1591

ISA13 112 Interchange Control Numer M NO 9/9This number uniquely identifies the interchange datato the sender.

Interchange Control Number(013 1


ISA14 113 Acknowledgment Requested M ID 1/1Code sent by the sender to request an interchange ac-knowledgement.

Acknowledgment Request1014 1

Code value agreed upon by trad-ing partners.

Code Defknitom0 No Acknowledgment Requested1 interchange Acknowledgement Requested

ISAI5 114 Test Indicator M ID 1/1

Code to indicate whether data enclosed by this inter-change envelope is test or production.

Test Indicator(015 1

Code value agreed upon by trad-ing parters.

Code DefinitionP Production DataT Test Data

ISA16 115 SubelementSeparator M AN 1/1

This is a field reserved for future expansion inseparating data element subgroups.

10.2.12 930315

w~m~y F D~ERAE. CARR1R IdVOWEDE V4ITMWO DO 410.003020

Suboloment Separator10161

930315 10.2. 13

RAIL CARRIER IVOICE DEPARTMET OF DEFUSE410.003020 EDI CONVBNTlON

Segment: GS Functional Group HeaderUsage: M

Purpose: To indicate the beginning of a functionalgroup and to provide control information

Comnuient: A. A functional group of related transactionsets, within the scope of X12 standards,consists of a collection of simila transac-tion sets enclosed by a functional groupheader and a functional group trailer.

Syntax Notes: 01 The data interchange control number(GS06) in this header must be identicalto the same data element in the as-sociated Functional Group Trailer(GE02).

Data Element SmanmmyRef. DataD". 8m1t Name Atnimrs

(3S01 479 Functional id Code M ID 2/2

Code identifying a group of application related Trans-action Sets.

Functional Id1020 1 Code Defilon

IA 110 - Air Freight Details nd InvoiceIM 210 - Freight Details and Invoice (Motor)MI 213 - Carrier Shipnent Statue nrqiryQM 214 - Shipment Status MessageIR 410 - Freight Details and Invoice (Ma)RA 820 - Payment Orderfemnittanoe AdviceSl 868 - Shipment InformationFS 869 - Freight Invoice (Generic Mode)CG 994 - Administrative MessageFA 997 - Functional Acknowledgement

Choos the code value pop upateto the information content of the

functional group. See X1 2 Diction-ay for source code list.

GS02 142 Application Sender's Code M AN 2112

Code identifying party sending transmission. Codesagreed to by trading partners.

10.2.14 930315

DEART& T OF O8WM RAIL CARRIER INVOICEWM CONVWNTION 410.003020

Sender's Code10211

DoD activities use Departmnnt ofDefense Activity Address Code(DoDAAC). Non-DoD activities

use identification code asigned byDoD activity. Recommend for mn-

creasd security that non-DoDcode differ from that used in

ISA06.

GS03 124 Application Receiver's Code M AN 2/12Code identifying party rec':iving transmission. Codesagreed to by trading paruirs.

Receiver's Code(0221

DoD activities use Department ofDefense Activity Address Code(DoDAAC). Non-DoD activities

use identification code assigned byDoD activity. Recommend for in-

creased security that non-DoDcode differ from that used in

ISA08.

GS04 29 Group Date M DT 6/6Date sender generated a functional group of ransac-tion sets.

Date[0231


GS05 30 Group Time M TM 4/4Time (HHMM) when the sender generated a func-tional group of transaction sets (local time atsender's location).

Time1024 1


GS06 28 Group Control Number M NO 1/9Assigned number originated and maintained by thesender.

Group Control Number1025 1


930315 10.2.15

RAL CAR INVOICE DEPARTMBET OF DW:dSE410.00O20 EDI CONVENTION

GS07 455 Responsible Agency Code M ID 1/2Code used in conjunction with Data Element 480 toidentify the issuer of the standard.

Agency Code1026 1

Indicates that an ANSI X12 stand-ord is being transmitted.

Code DefinitionX Accredited Standards Conmittee X1 2

GS08 480 Version/Release/Industry Id Code M ID 1/12Code indicating the version, release, subrelease andindustry identifier of the EDI standard being used.(See X12 Dictionary)

Version/Release[027 1

Code value agreed to by tradingpartners. See X12 Dictionary for

aource code list.Code Definition

003020 Draft Standards Approved By ASC Xl 2Through October 1991

10.2.16 930315

DEPARTMENT OF Di MSE RAIL CARRIER INVOICEEDI CONVIETION 410.003020

Segment: GE Functional Group Trailer

Usage: MPurpose: To indicate the end of a functional group

and to provide control information

Comment: A. The use of identical data interchange con-trol numbers in the associat-4 functionalgroup header and trailer is designed tomaximize functional group integrity. Thecontrol number is the same as that usedin the corresponding header.

Syntax Notes: 01 The data interchange control number(GE02) in this trailer must be identicalto the same data element in the as-sociated Functional Group Header(GS06).

Data Element SumnaryRef. DataDes. Elenmet Name Attrbutes

GEO0 97 Number of Included Sets M NO 1/6Total number of transaction sets included in the func-tional group or interchange (transmission) group ter-minated by the trailer containing this data element.

Number of Segments1028 1

Assigned by the translationsoftware.

GE02 28 Group Control Number M NO 1/9Assigned number originated and maintained by thesender.

Group Control Number[029 1

Assigned by the translationsoftware. This control number

must match the control number ofthe preceding GS06 control num-

ber.

930315 10.2.17

RAIL CARRIER INVOICE DEPARTIWIT OF DEFBSE410.003020 EDI CONVENTION

Segment: lEA Interchange Control TrailerUsige: M

Pupose: To define the end of an interchange of oneor more functional groups and interchangerelated control segments.

Note: The interchange control number in this trailermust match the value in the same data ele-ment in the corresponding interchangeheader.

Data Bement SummyRef. DataDoe. Element Name Attributes

IEA01 116 Number of Included Functional M NO 1/5GroupsA count of the number of functional groups includedin a transmission.

Functional Group Count1040 1


IEA02 112 Interchange Control Number M NO 9/9This number uniquely identifies the interchange datato the sender.

Interchange Control Number[041 1

Assigned by translation software.This number must match the num-

ber that occurs in !SA13.

10.2.18 930315

DEPARTIMET OF DBISE RAIL CARRIER IVOICEEDI CONV=dTION 410.003020

10.5 DATA ELEMENTCROSS-REFERENCE MATRIX

OverviewThis chapter lists the data element cross-reference between theDepartment of Defense (DoD) ASC X12.139 Transaction Set 410Rail Carrier Invoice (003020). We derived the cross-referencefrom the following:

"* Examination of DoD transportation invoice information datarequirements.

"* Analysis of ASC X12.139 Transaction Set 410 Rail CarrierInvoice.

"* Comments submitted by DoD activities and commercial car-riers involved in the DoD electronic data interchange effort.

PurposeThis chapter identifies specific data in an application and theircorresponding EDI mapping into the Transaction Set 410. Dataelements from an existing application database can be identifiedwith elements in this cross-reference. If no application exists,the cross-reference provides enough information to develop adatabase design to automate the application. With an applicationin place, this cross-reference will expedite mapping of thedatabase into a commercial EDI translation package. All tradingpartners who plan to exchange the 410 with DoD can use thisdocument as a reference for the development of theirdatabase/EDI translator interface program.

ContentsOne table is included in this chapter. Table 10.5-1, Data ElementCross-Reference lists all the discrete data elements of the DoDinvoice data requirements and their corresponding segment anddata element of the ASC X12.139 Transaction Set 410 RailCarrier Invoice.

930315 10.5.1

DEPARTMET OF D MISE RAIL CARRIER INVOICEEDI CONVENTION 410.003020

(BLANK PAGE)

10.6.2 930315

DEPARTIENT OF DMMBSE RAIL CARRIER NVOICEWI CONVENTION 410.003020

TABLE 10.5-1

DATA ELEMENT CROSS-REFERENCE

DoD Transportation Invoice Data Using ASCX 12.139 Transaction Set 410 Rail Carrier Invoice.

How To Read This TableTable 10.5-1 cross-references discrete DoD invoice data require-ments to the corresponding segment and data elements of theTransaction Set 410. The following definitions explain bow table10.5-1 is organized. Understanding the information in this tablerequires familiarity with EDI standards.

Government ReferencesThe first three columns on the left in Table 10.5-1 identify thespecific invoice data element.

" INVOICE DATA NAME: Lists individual data elementsrequired to send a transportation invoice. The user shouldidentify these elements with a data name in their internaldatabase system.

"* INDEX: Three entries may appear in this column andrepresent various levels of indexing used to sort the datanames in a data dictionary.

"* Q: An asterisk (*) in this column identifies the data as aqualifier code.

EDI ReferencesThe remaining seven columns identify the detailed mapping ofeach data name into Transaction Set 410. Using these referencesis explained below in "How To Use This Table".

"* AREA: The area of the transaction set where the data ismapped. A = header, B = detail, C = summary.

"* POS: The sequential position of a specific segment withinthe area of the transaction set.

" REF DES: The first two or three alphanumeric charactersidentify a transaction set segment; the last two numericcharacters in the column identify a data element position inthe segment.

"* DE #: The EDI data element number that appears at thatposition in the segment.

"* VALUE: The recommended code value(s) that should beused.

930315 10.5.3

DEPARTMBNIT OF DEFESE RAIL CARRIER INVOICEEDI CONVINTION 410.003020

DoD CONVENTIONS: Additional information about thedata as they apply to Department of Defense use.

How To Use This TableThis table maps a data element to a specific data element in anEDI transaction set.

1. Select any data element from the INVOICE DATA NAMElist,

2. Identify the AREA, POS, and REF DES for that DATA

NAME,

3. Go to Table 10.7-2 DoD Segment Hierarchy,

4. Find the AREA (Table A = header, etc.) in the hierarchy,

5. Locate the segment that corresponds to the POS and the REFDES. NOTE: The POS may not appear in some hierarchy tables.In this case, use the segment id identified by the first 2-3characters in the REF DES,

6. In the left-hand column, identify the page number of the

segment Id,

7. Turn to that page number in Table 10.7-3,

8. Now in the convention table 10.7-3, find the REF DES fromstep, 2 under the Ref. Des. column on the right hand side ofthe page,

9. You have now mapped a data element from table 10.5-1 intothe convention table 10.7-3.

The INVOICE DATA NAME from Table 10.5-1 appears in theright hand column along with its INDEX and the DoD CON-VENTION. The EDI standard definition of the data elementappears in the right band column of the page.

Each INVOICE DATA NAME from Table 10.5-1 can be mappedinto the transaction set in this manner.

10.S.4 930315

DEPARTT OF DuEO RAIL CARRIER INVOICEED1 COWNV " 410.003020

(BLANK PAGE)

9320315 ¶0.5.5

DEPAR7IUG1T OF DEFENSE RAIL CARRIER INVOICEEDI CONIVENION 410.003020

aiU0 a

.E 3i

E --.50

CC 0

* 06

7 E

t a (2 E

0 L6

Sc 0

%i CL0

-u c

2:2cc - c -. 5

o a a fa a a a"

r - - - --- r

o 90 0 0 0 0 0

55 0

CS C

0

z 201

UU

0oc 0

m ! . ! .

(30 u93031S

DEPARTMET OF DEFENSE RAIL CARRIER INVOICEEDI CONVEdTION 410.003020

" x '

0

OE E>

1- °.5. . a

2!0 it

6. Q.

.7~

-o

CLS 0

0L. E'

0 0

- •; . • :0 b -- 00

S0 ab as a) 4

C13 zz z zz z z

C- -0 -

.3U . . .. U.. .--.

10

cc-

606 0. 0

SO OL .20 0 -2.0 F4 d CL IL Q. cl

-z --

t a0 a a a ccaQ. Q. CIL, aa

9331 10.5.7 2Z

DEPARTNIWIT OF DSWUM RAIL CARRIER INVOICESDI CONVITION 410.003020

7

.3 -- Am A:

US..

E 2

Cc

0 I I z z0o. 0 o

._cUUcc-- .5. C C 03C5

=> U U

M2w

w- Co.fInear ob-

0 0 t

E E

- 2

Fr

0 0 1U 0

10 . 93031

DEPARTNENT OF DEFRSE RAIL CARRIER HYVOMCDI CONVMWTIO 410.003020

0

J: 0

-'2

0 S

* 0 U

C)7

A G

400

40 3

q 0 0 m 01

z - E *z z .s z z

40 fa co 40 40 4 o t

U-~U U .).

0. 0~ 0 t. m- r-'iE

0

o m -u 0 Ur-m u r-.m * -- 0 0 0 0*~ 00 0 0

ft ~ 0 .2 .2 - f - ft '.2- ft2A 1! a fu 0 0 .21 .2 .0

*. - - C.) r ~'A Z Z Z "0 o "I o Z &

o~~~~t 0 8 0 0 0 0C

9221 0 0 0 00 0 059

DIEARMENT OF DOWEV RAIL CARRIER UJVOSCEEDI COP4VET1ON 410.003020

E

0 0 C0

Im

go - 0

19 .3 -2

x -sob

F- U) (

to q la a

V go

C.) 0) O ~

o C4

so

oOS1 93031

DVPARTA*T OF DOWSE RAIL CARRIER EVOICEWDI CONYBeamO 410.003020

c

SE U)

E o

0~

C; c0mae

rU

_.S.

FAU A

*su. a .UUJ

cp m

.P. 10 p..

VdP -0 .0 Lo i

0 44 -m em00

p..IS 1 0 ~ S z

8 Ig 0P

9331 100. 60 O 1

DEPARTMENT OF DER3M RAIL CARRIER IVOICEEDI CONVEiTION 410.003020

(Blank Page)

10.5.12 930315

DEPAiRTW T OF D09SE RAIL CARRIER INVOICE

EDI CONVBQTION 410003020

10.7 DoD CONVENTIONS

OverviewThis chapter is the convention for the ASC X12.139 TransactionSet 410 (Version 003020) as used by the Department of Defensefor accepting a transportation invoice. It was derived from:

"* Table 10.5-I, Data Element Cross-Reference Matrix thatdescribes the discrete DoD data requirements for invoices.

"* ASC X12.139 Transaction Set 410 Rail Carrier Invoice.

A relational database management system was used to merge theData Element Cross-Reference Matrix and a Transaction Set 410database into the subset of 410 segments described in table 10.7-3of this chapter.

PurposeThis chapter contains all necessary information for a DoD tradingpartner to map and translate a Transaction Set 410. AD tradingpartners who plan to exchange the Transaction Set 410 can usethis document as a reference for the development of their EDIdatabase/translator interface program.

ContentsThree tables are included in this chapter.

"* Table 10.7-1, ASC X12.139 Transaction Set 410 SegmentHierarchy describes the 410 segments as they appear in theASC X12 Standards Dictionary.

"* Table 10.7-2, DoD Model Transaction Set 410 SegmentHierarchy describes the subset of 410 segments used forsending transportation invoices.

" Table 10.7-3, Conventions is a detailed description of theDepartment of Defense conventions for transmitting Trans-action Set 410. All segments identified in Table 10.7-2 aredetailed in Table 10.7-3 by segment, position, and codevalue.

930315 10.7.1

DEPARTWMDT OF DER3SE RAIL CARRIER INVOICEEDI CONVENTION 410.003020

(BLANK, PAGE)

10.7.2 930315

DEP•ARTh OF DEUh RAIL CARRIER INVOICEEDI CONVdI11ON 410.003020

TABLE 10.7-1

SEGMENT HIERARCHY

ASC X12.139 TRANSACTION SET 410

RAIL CARRIER INVOICE(Version 003020)

93031S 10.7.3

DEPARTMEIT OF DEW-#JSE RAL CARRIER INVOICEEDI CONVENTION 410.003020

(Blank Page)

10.7.4 930315

DEPAITMENT OF DEENSE RAIL CARRIER INVOCEEDI CONVENnaN 410.003020

ASC X12.139 Transaction Set 410Rail Carrier Freight Details and Invoice

(Version 003020)Segment Hierarchy

Table 1 - Header Area

Pos Seg ReqIndustry No. ID Name Des Use Loop

USE 10 ST Transaction Set Header M 1

USE 20 B3B Beginning Segment for Carrier's M 1Invoice

30 C4 Alternate Amount Due 0 1

USE 40 N9 Reference Number 0 30

USE 50 N7 Equipment Details M 1 N7%25560 VC Motor Vehicle Control 0 21

70 G4 Scale Identification Segment 0 1

80 M7 Seal Numbers 0 5

90 N5 Equipment Ordered 0 1

100 IC Intermodal Chassis Equipment 0 1

110 IM Intermodal Movement Information 0 1

120 M12 In-bond Identifying Information 0 1

USE 130 NI Waybill Reference M 266

USE 140 F9 Origin Station M 1

USE 150 D9 Destination Station M 1

USE 160 NI Name 0 1 N1\10170 N3 Address information 0 2

180 N4 Geographic Location 0 1

190 F1 Consignor Name 0 1

200 F2 Consignor Address 0 2

210 F4 Consignor City 0 1

220 D1 Consignee Name 0 1

230 D2 Consignee Address 0 2

240 D4 Consignee City 0 1

250 Ul Ultimate Consignee Name 0 1

260 U2 Ultimate Consignee Address 0 1

270 U4 Ultimate Consignee City 0 1

280 US Prior Origin Name 0 1

290 US Prior Origin Address 0 1

300 U9 Prior Origin City 0 1

930315 10.7.5

DEPARTMET OF D =BSE RAIL CARRIER INVOICEEDI CONVENTIN 410.003020

310 FS Consignor's Third Party 0 1 FS\10

320 F6 Consignor's Third Party Address 0 1

330 F7 Consignor's Third Party City 0 1

340 DS Consignee's Third Party 0 1 DS\10

350 D6 Consignee's Third Party Address 0 1

360 D7 Consignee's Third Party City 0 1

370 S1 Stop-off Name 0 1 S1\6

380 S2 Stop-off Address 0 1

390 S9 Stop-off Station 0 1

400 R2 Route Information 0 13

410 RE Rebill At Interchange 0 1

420 PS Protective Service Instructions 0 3

USE 430 LX Assigned Number M I LX\25

USE 440 LS Description, Marks and Numbers M 15

USE 445 LS Loop Header M 1

USE 450 LX Assigned Number M I LX\26

USE 460 L0 Line Item - Quantity and Weight M 10

USE 470 Li Rate and Charges M 10

USE 475 LE Loop Trailer M 1

USE 430 L7 Tariff Reference 0 30

490 T1 Transit Inbound Origin 0 1 T1\64

SO0 T2 Transit Inbound Lading 0 30

510 T3 Transit Inbound Route 0 12

520 T6 Transit Inbound Rates 0 1

530 TS Free-form Transit Data 0 99

USE 540 L3 Total Weight and Charges M 1SSO X7 Customs Information 0 2

560 GA Canadian Grain Information 0 1

USE 570 SE Transaction Set Trailer M 1

10.7.6 930315

DEPARTMBNT OF DB:WASE RAIL CARRIER IVOICE

EDI CONVmeiIdm 410.003020

TABLE 10.7-2

SEGMENT HIERARCHY

DoD MODEL FOR TRANSACTION SET

410 RAIL CARRIER INVOICE

930315 10.7.7

DEPARTMBET OF DERME RAIL CARRIER INVOICEEDI CONVENTION 410.003020

(BLANK PAGE)

10.7.8 930315

DEPAR, WrrT OF WDO si RAL CAMRER VOCE01 CONVET1O 410.003020

DoD Model Transaction Set 410Rail Carrier InvoiceSegment Hierarchy

Table 1 - Header Area

Pos Seg ReqPage No. No. ID Name Des Use Loop

13 10 ST Transaction Set Header M 1

14 20 83B Beginning Segment for Carrier's M IInvoice

17 40 N9 Reference Number 0 30

20 50 N7 Equipment Details M I N7%25

22 130 NO Waybill Reference M 265

24 140 F9 Origin Station M 1

25 150 D9 Destination Station M 1

27 160 N1 Name 0 1 N14\10

30 430 LX Assigned Number M 1 LX\26

31 440 L5 Description, Marks and Numbers M 1s

33 445 LS Loop Header M 1

35 450 LX Assigned Number M 1 LX\25

36 460 L0 Line Item - Quantity and Weight M 10

38 470 L1 Rate and Charges M 10

40 475 LE Loop Trailer M 1

42 480 L7 Tariff Reference 0 30

44 540 L3 Total Weight and Charges M 1

46 570 SE Transaction Set Trailer M 1

930315 10.7.9

DEPARTMI OF DEESE RAIL CARRIER UIVOICE

EDI CONVENTION 410.003020

(Blank Page)

10.7.10 93031S

DEPARTMENT OF 009MSE RAIL CARRIER INVOICEEDI CONVId11ON 410.003020

TABLE 10.7-3

DoD 410 CONVENTION

How To Read This TableThis table contains two sets of references. ASC X12 referencesare contained in the right-hand column. Government referencesare contained in the left-hand column except for codes lists whichare included in the right-hand column.

Govenvnent ReferencesThe left-hand and middle columns in Table 10.7-3 describeDepartment of Defense conventions.

"* Left-hand column contains two general references.

"> INDEX: is enclosed in brackets and corresponds to aspecific INDEX from Table 10.5-1.

"> INVOICE DATA NAME: Appears above the INDEXand corresponds to a specific DATA NAME from Table10.5-1.

"* Middle column: Contains a less-than sign to indicate whereDepartment of Defense conventions vary from the ASC X12convention.

To help the user determine the source data, the INDEX can beused to trace data elements back to Table 10.5-1.

ASC X12 ReferencesThe right-hand column describes the ASC X12 conventions. Theinformation included at the beginning of a segment descriptionis standard ASC X12 information. The subheadings listed underData Element Summary describe conventions for each data ele-ment in the segment.

"> Ref Des, Data Element, Attributes: Three subheadingsdescribe the format of the segment as prescribed by ASCX12.

"> Name: Describes the ASC X12 data element and offersthe standard definition. It also lists the specific codevalues the Department of Defense prescribes and mayprovide other Department of Defense information.

How To Use This TableThis table can be used to identify the data contained in populatedTransaction Set 410.

930315 10.7.11

DEPARTMBET OF DEFESE RAIL CARRIER INVOICEEDI CONVEITION 410.003020

1. Identify a segment from a populated transaction set (SeeAppendix l0.C for examples of the 410).

2. Look up the segment in table 10.7-3.

3. Read the right-hand column to identify the Reference Desig-nator (Ref. Des.). The Reference Designator combines the seg-ment id and the data element position to form a single identifier.

4. Read the left-hand column immediately adjacent to the Ref-erence Designator to find the discrete DATA NAME, INDEX,and DoD CONVENTION from Tale 10.5-1 that is mapped tothat Reference Designator. When multiple DATA NAMEs appearfor a single Reference Designator, there is usually a codequalifier somewhere in the same segment that identifies the data.

10.7.12 930315

DEPARTITIAT OF DEFENSE RAIL CARRIER INVOICEEDI CONVi4mON 410.003020

Segment: ST Transaction Set HeaderLevel: 1

Sequence: 10Usage: M

Max Use: 1Loop:

Purpose: To indicate the start of a transaction set andto assign a control number

Comment: 01 The transaction set identifier (STO1) isintended for use by the translationroutines of the interchange partners toselect the appropriate transaction setdefinition (e.g., 810 selects the invoicetransaction set).

Data Element SunTmatyRef. DataDes. Element Name Atuitass

STO0 143 Transaction Set Identifler Code M ID 3/3Code uniquely identifying a Transaction Set.

Transaction Set Id1001 *1 Code Definition

410 Xl 2.139 Rail Carrier Freight Details and Invoice

ST02 329 Transaction Set Control Nunmber M AN 4/9Identifying control number assigned by the originatorfor a transaction seL

Transaction Set ControlNumber1002 1

The application and structure ofthe control number must be

agreed upon between DoD and itstrading partners. The first five

digits will indicate the interchangecontrol number. The last four

digits represent the sequence ofthe transaction within the func-

tional group.

930315 10.7.13

DiPART OF DEFRUE RAIL CARRIER iNVOiCEII COINVNI1N 410.003020

Segment: B3B Beginning Segment for Carrier'sInvoice

Level: 1Sequence: 20

Usage: M

Max Use: 1Loop:

Purpose: To transmit identifying numbers, dates andother basic data relating to the transactionset.

Comment: 03 B3B03 is the billing date.

05 B3B05 is the payment due date.09 B3B09 default value is pounds.

Data Elment SummaryRef. DataDes. Element Name Attribue

B3B01 76 Invoice Number M AN 1/22Identifying number assigned by issuer.

Invoice Number(003 1

Transportation service provider'suniqu invoice number.

B3B02 146 Shipment Method of Payment M ID 2/2

Code identifying payment terms for transportationcharges.

Shipment Method ofPayment[004 1 Code Definition

PP Prepaid

B3B03 373 Date M DT 6/6Date (YYMMDD).

Invoice Date1005 ]

Date the invoice is issued. Use for-mat YYMMDD.

13B04 193 Net Amount Due M N2 1/9Total charges to be paid by the receiver of this trans-action set expressed in the standard monetarydenomination for the currency specified.

10.7.14 930315

DEPAR0dTM OF DESISE RAL CARRIER IVOICEEDI CONVB4T1ON 410.003020

Total Charges1006 1

Total shipment charge includinglinehaui. accessorial, miscel-

laneous, and fuel charges. Implieddecimal at second position from

right.

B3B05 373 Date M DT 6/6

Date (YYMMDD).Payment Due Date

[007 1

Not used by DoD paymentcenters. Use format YYMMOD.

B3B06 140 Standard Carrier Alpha Code M ID 2/4Standard Carrier Alpha Code

Billing Carier SCAC(008 1

Use the SCAC of the carrier thatissues the invoice.

B3807 91 Transportation Method/Type M ID 12CodeCode specifying the method or type of transportationfor the shipment.

Transportation Method1009 1 Code Definition

R Rail

B3B08 145 Shipment Identification Number 0 AN 1/30Identification number assigned to the shipment bythe shipper that uniquely identifies the shipmentfrom origin to ultimate destination and is not subjectto modification. (Does not contain blanks or specialcharacters.)

GBL Number[010 1

DoD unique number representing ashipment. The number is made up

of one or two alpha characters fol-lowed by six or seven numbers.

Do not use any punctuation or spe-cial characters.

53509 188 Weight Unit Qualifier 0 ID 111

930315 10.7.15

DEPARTMEIT OF DEFENSE RAIL CARRIER INVOICEEDI CONVENTION 410.003020

B3B10 202 Correction Inicator 0 ID 2/2Code used to indicate that the transaction set con-

tains information which corrects a previous billing.Correction Indicator

(011 *I

If the invoice is submitted for thefirst time (original invoice), this op-

tioral data field is not used.

Code Definition

AD SupplementalCA Cancei

10.7.16 930315

DEPARTMWWT OF DOVU4E RAIL CARRIER WVOICEEDI CONVENTION 410.003020

Segment: N9 Reference Number

Level: 1

Sequence: 40

Usage: M

Max Use: 30

Loop:

Purpose: To transmit identifying numbers and descrip-tive information as specified by the refer-ence number qualifier

Syntax Notes: 02 R0203 - At least one of N902 or N903is required.

Data Element SummayRef. DataDes. Element Name Attribtts

N901 128 Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.Payee Code Qualifier

1012 *] Code Definition

PQ Payee Identification

Carrier Pickup Date Qualifier[014 *1 Code Definition

PS Pickup Reference Number

Carrier Delivery Date Qualifier[018 *1 Code Definition

DO Delivery Reference Number

Carrier Reference NumberQualifier

1021 *1 Code DefinitionCN Carrier Reference Number (PRO Number)

N902 127 Reference Number C AN 1/30

Reference number or identification number asdefined for a particular Transaction Set, or asspecified by the Reference Number Qualifier.

930315 10.7.17

DEPARTM T OF DEFESE RAIL CARRIER INVOICE


Payee Code[013 1

Identification assigned by DoD pay-ment center. Qualify in N901.

Carrier Reference Number1022 1

Qualify in N901.

N903 369 Free-form Description C AN 1/45

Free-form descriptive text.Payee Zip Code

1013010 1

Zip code of location that payeeauthorizes payment to be sent.

Must match payee information onfile at payment center.

Carrier Pickup Date Text1015 1

To satisfy Xl 2 syntax, fill thisdata element with 'PICKUP

DATE'.

Carrier Delivery Date Text(019 1

To satisfy X1 2 syntax, fill thisdata element with 'DELIVERY

DATE.'

N904 373 Date 0 DT 6/6

Date (YYMMDD).Carrier Pickup Date

1016 1

Date carrier picked up shipment.Not required for submission of sup-

plemental invoices. Use formatYYMMDD.

10.7.18 930315

DEPARTM1MT OF OIE RAIL CARRIER UNVOICEEO R CONVOF 410.003020

Carrier Delivery Date1020 1

Date carrier delivered shipment.Not required for submission of sup-

plemental invoices. Use formatYYMMDD.

N905 337 Time 0 TM 4/6

Time expressed in 24-hour clock time (HHMMSS)(Time range: 000000 through 235959)

Carrier Pickup Time[017 1

Time carrier picked up shipment.Use format HHMM.

930315 10.7.19

DEPARTMENT OF DEFENSE RAIL CARRIER INVOICEWI CONVENTION 410.003020

Segment: N7 Equipment Details

Level: 1

Sequence: 50Usage: 0

Max Use: 1Loop:

Purpose: To identify the equipment.

Comment: 01 N701 is mandatory for rail transactions.20 N720 and N721 are expressed in iches.

Syntax Notes: 03 C0304 - If N703 is present, then 04 isrequired.

05 P0516 - If either N705 or N716 ispresent, then the other is required.


Data Element SwnmaryRef. DataDes. Element Name Attributes

N701 206 Equipment Initial 0 AN 1/4

N702 207 Equipment Number M AN 1/10Sequencing or serial part of an equipment unit's iden-tifying number (pure numeric form for equipmentnumber is preferred).

Equipment Number(022010 1

Mandatory ANSI syntax field notrequired by DoD.

N703 81 Weight 0 R 1/8

N704 187 Weight Qualifier C ID 1/2

N705 167 Tare Weight C NO 3/8

N706 232 Weight Allowance 0 NO 2/6

N707 205 Dunnage 0 NO 1/6

10.7.20 930315

DEPARI1 OF DGE RAIL CARRIER INVOICE

EDI CONVINam 410.003020

N708 183 Volume C R 1/8

N709 184 Volume Unit Qualifier C ID 1/1

N710 102 Ownership Code 0 ID 1/1

N711 40 Equipment Description Code 0 ID 2/2

N712 307 Equipment Owner Code 0 ID 1/4

N713 319 Temperature Control 0 AN 3/6

N714 219 Position 0 AN 1/3

N715 567 Equipment Length 0 NO 4/5

N716 571 Tare Qualifier Code C ID 1/1

N717 188 Weight Unit Qualifier 0 ID III

N718 761 Equipment Nunber Check Digit 0 NO 1/1

N719 56 Type of Service Code ID 2/2

N720 65 Height 0 R 1/8

N721 189 Width 0 R 1/8

N722 24 Equipment Type 0 ID 4/4

930215 10.7.21

DEPARTMENT OF DO:SE RAIL CARRIER IVOICEEDI CONVBwTino 410.003020

Segment: N8 Waybill Reference

Level: 1

Sequence: 130Usage: M

Max Use: 255Loop:

Pwpose: To identify the waybill and to specify theequipment used and the destination details

Comment: 00 Waybill type should only be transmittedwhen the transaction set involves a multi-ple Car/TOFCICOFC shipment or a con-veymg flat car. Waybill type should notbe sent on a single Car/TOFC/COFC.

0 2 N802 is the Waybill Date.07 N807 is the Waybill Date.10 N8 10 will contain destination railroad ini-

tial (SCAC).11 N811 will contain railroad destination

(FSAC).Syntax Notes: 03 P030405 - If either N803,N804 or N8

are present, then the others are required.06 P0607 - If either N806 or N807 is

present, then the other is required.08 P0809 - If either N808 or N809 is

present, then the other is required.

Data Eement SwminaryRef. DataDes. Ehminat Name Attrbutss

N801 186 Waybil Nunter M NO 1/6Carrier accounting number of the waybill for the in-bound movement.

Waybill Number[022 100 1


N802 373 Date M DT 6/6

Date (YYMMDD).Waybill Date1022 110 1


10.7.22 930315

DEPARTMENT OF DOMYSE RAIL CARRIER INVOICE

EI CONVENTION 410.003020

N803 231 Cross Reference Type Code C ID 1/1

N804 206 Equipment Initial C AN 1/4

N805 207 Equipment Number C AN 1/10

N806 186 Waybill Number C NO 1/6

N807 373 Dam C DT 6/6

N808 300 Destination Station C AN 2/19

N809 156 State or Province Code C ID 2/2

N810 140 Standard Carrier Alpha Code 0 ID 2/4

N81 1 573 Freight Station Accounting Code 0 ID 1/5

930315 10.7.23

DIWARTU d OF DMWE RAIL CARRIER INVOICEWI CONVEWTIGN 410.003020

Segment: F9 Origin StationLevel: 1


Max Use: 1Loop:

Purpose: To identify the rail origin of this shipmenL

Data Bement SwnmyRef. DataDos. Elameit Namoe Attybte

F901 573 Freight Station Accounting Code 0 ID 1/5

F902 101 Origin Station M AN 2/19Railroad station at which the movement of goodsoriginated.

Origin Station1022 120 1

Mandatory ANSI sntax field notrequired by DoD.

F903 156 State or Province Code M ID 2/2Code (Standard State/Province) as defined by ap-propriate government agency.

Origin Station Code(022 130 1


F904 26 Country Code 0 ID 2/2

F905 194 Billed At Station Code 0 ID 1/6

F906 19 City Name 0 AN 2/19

F907 156 State or Province Code 0 ID 2/2

F908 154 Standard Point Location Code 0 ID 6/9

F909 116 Postal Code 0 ID 4/9

10.7.24 930315

DEPARTMENT OF D9 IJSE RAIL CARRIER INVOICEED[ CONVBETION 410.003020

Segment: D9 Destination StationLevel: 1

Sequence: 150

Usage: 0

Max Use: 1

Loop:

Purpose: To identify the rail destination of this ship-ment.

Data BEement SuwmaryRef. Dat.Des. Elemet Name Attribum

D901 573 Freight Station Accounting Code 0 ID 1/5

D902 300 Destination Station M AN 2/19Railroad station at which the movement of goods isto terminate.

Destination Station1022 140 1


D903 156 State or Province Code M ID 2/2Code (Standard State/Province) as defined by ap-propriate government agency.

Destination Station StateCode

[022 150 1Mandatory ANSI syntax field not

required by DoD.

D904 26 Country Code 0 ID 2/2

D905 194 Billed At Station Code 0 ID 1/6

D906 19 City Name 0 AN 2/19

D907 156 State or Province Code 0 ID 2/2

D908 154 Standard Point Location Code 0 ID 6/9

930315 10.7.25

DEPARTIENT OF DBEWESE RAIL CARRIER INVOICE

EDI CONVBETION 410.003020

D909 116 PostalCode 0 ID 4/9

10.7.26 930315

DEPARTMET OF DEiENSE RAIL CARRIER INVOICEEDI CONVBETION 410.003020

Segment: NI Name

Level: 1

Sequence: 160

Usage: MMax Use: 1

Loop:

Purpose: To identify a party by type of organization,name and code

Comment: 04 This segment, used alone, provides themost efficient method of providing or-ganizational identification. To obtain thisefficiency the "ID Code" (NI04) must

provide a key to the table maintained bythe transaction processing party.

Syntax Notes: 02 R0203 - At least one of N102 or N103is required.


Data Element SuwmnyRef. DataDes. Element Name Atm'ixtm

N101 98 Entity ldentifier Code M ID 2/2

Code identifying an organizational entity or a physi-cal location.

Issuing Office Qualifier1031 *1 Code Definition

IU Issuer

Tendered To Carrier Qualifier1034 *1 Code Definition

OC Origin Carier

Destination TransportationCompany Qualifier

[037 *1 Code Definition

DC Destination Carrier

Diversion/ReconsignmentFrom Qualifier

1043 *1 Code DefinitionT4 Transfer Point

930315 10.7.27

DEPARTMIMT OF DE=SE RAIL CARRIER INVOICEWI CONVENTION 410.003020

N102 93 Name C AN 1/35

N103 66 Identification Code Qualifier C ID 1/2Code designating the system/method of code struc-ture used for Identification Code (67).

Issuing Office GBLOCQualifier

1032 *1 Code Definition27 Government Bill Of Lading Office Code (GBLOC)

Tendered To Carrier SCACQualifier

1035 *1 Code Definition2 SCAC

Destination TransportationCompany SCAC Qualifier

[038 *1 Code Definition2 SCAC

DiversionlReconsignmentFrom SPLC Qualifier

(044 *1 Code Definition20 Standard Point Location Code (SPLC)

N104 67 Identification Code C AN 2117Code identifying a party.

Issuing Office GBLOC[033 1

Qualify in N103.

Tendered To Carrier SCAC1036 1

Use SCAC of billing company.

Destination TransportationCompany SCAC

1039 1

Use SCAC of delivering carrier.

10.7.28 930315

DEPARIIT OF WFEIM RAL CARRIER INVOICEEDI CONVENI" 410.003020

Diversion/ReconsignmentFrom SPLC

(045 1

Qualify in N103.

930315 10.7.29

DEPARTFhW OF DENSE RAIL CARRIER INVOICEEDI CONVBETION 410.003020

Segment: LX Assigned Number

Level: 1

Sequence: 430

Usage: M

Max Use: 1

Loop:Purpose: To reference a line number in a transaction

set.

Data lement SwmnawyRef. DataDes. ESiment Name Attibaus

LX01 554 Assigned Nunmer M NO 1/6

Number assigned for differentiation withi a transac-tion set.

Service Charge LoopIdentifier(046 *1

Assign a sequential number foreach charge. Charges include

transportation linehaul, accessorial,miscellaneous, and authorized sur-charges. Use one LX01 for each

L108 (service charge code).

10.7.30 930315

DEPARTMBN T OF DEFENSE RAIL CARRIER INVOICEUIN CONv~TI•IN 410.003020

Segrn~t: L5 Description, Marks and Numbers


Usage: 0

Max Use: 15

Loop:

Purpose: To specify the line item in terms of descrip-tion, quantity, packaging, and marks andnumbers.

Comment: 02 L502 may be used to send quantity infor-mation as part of the product descrip-tion.

03 L503 and L504 are "Paired" data ele-ments. If one is used, both must be usedexcept for rail transaction sets whereSTCC is understood.

Syntax Notes: 03 P0304 - If either L503 or L504 ispresent, then the other is required.

08 P0809 - If either L508 or L509 ispresent, then the other is required.

Data Eement SummaryRof. DataDes. emett Name Amtes

L501 213 Lading Une ltem Number 0 NO 1/3

Sequential line number for a lading item.Description, Marks, and

Numbers1046 010 1


L502 79 Lading Description 0 AN 1/50

L503 22 Commodity Code C AN 1/16

L504 23 Commodity Code Qualifier C ID 1/1

L505 103 Packaging Code 0 AN 5/5

L506 87 Marks and Numbers 0 AN 1/45

930315 10.7.31

DEPARTMENT OF DERNSE RAIL CARRIER INVOICEEDI CONVBNI'ON 410.003020

L507 88 Marks and Numbers Qualifier 0 ID 112

L508 23 Commodity Code Qualifier C ID 1/1

L509 22 Commodity Code C AN 1/16

L510 595 Compartment ID Code 0 ID 1/1

10.7.32 930315

DEPARTMWIT OF DEFENSE RAIL CARRIER IVOICEEDI CONVENTION 410.003020

Segment: LS Loop HeaderLevel: 1

Sequence: 445

Usage: M

Max Use: 1

Loop:

PurpK cae that the next segment begins awoup

Comment: 00 LS is a control segment. LS is alwaysused in conjunction with a correspondingloop trailer (end) - LE, as illustratedbelow. The LS and LE indicate the startand end of a loop but are not part of theiteration of the loop.LOOP NESTINGLoop "A" Header (LS "A-)Loop "B" Header (LS "B")

Loop "C" Header (LS "C")Loop "C" Trailer (LE "C")Loop "D" Header (LS "D")Loop "D" Trailer (LE "D")

Loop "B" Trailer (LE "B")Loop "A" Trailer (LE "A")

Neither LS nor LE is used if the datawithin the loop is not used.

Syntax Notes: 00 One loop may be nested containedwithin another loop, provided the innernested loop terminates before the outerloop. When specified by the standardsetting body as 'mandatory', this seg-ment in combination with "LE", must beused. It is not to be used if not specifi-cally set forth for use. The loopidentifier in the loop header and trailermust be identical. The value forthe identifier is the loop ID of the re-quired loop beginning segment. Theloop ID number is given on the transac-tion set diagram in the appropriateASC X12 version/release.

Data Element Summary

Ref. DataDes. Element Name Attributes

930315 10.7.33

DEPARTNMW OF DBbESE RAIL CARRIER INVOICEEDI CONVENTION 410.003020

LS01 447 Loop Identifier Code M AN 1/4

Code identifying a loop within the transaction setwhich is bounded by the related LS and LE seg-ments (corresponding LS and LE segments musthave the same value for loop identifier). (Note: Theloop ID number given on the transaction set diagramis recommended as the value for this data element insegments LS and LE.)

Loop Header1046 020 1


10.7.34 930315

DEPARTMBI OF DEFENSE RAIL CARRIER INVOICEEDI CONVBI'nON 41o.oo3o20

Segment: LX Assigned Number

Level: 1

Sequence: 450

Usage: M

Max Use: 1

Loop:

Purpose: To reference a line number in a transactionset.

Data Element SunmaryRef. DataDo*. Element Name Attribts

LXO1 554 Assigned Number M NO 1/6

Number assigned for differentiation within a transac-tion set.

Assigned Number[047 *1


930315 10.7.35

DEPARTNENT OF DEFESE RAIL CARRIER INVOICEEDI CONVWTMION 410.003020

Segment: L0 Line Item - Quantity and Weight


Usage: 0

Max Use: 10Loop:

Purpose: To specify quantity, weight, volume andtype of service for a line item including ap-plicable "quantity/rate-as" data.

Syntax Notes: 02 P0203 - If either L002 or L003 ispresent, then the other is required.




11 C1104 - If L01I is present, then 04 is re-quired.

Data Element SumrnayRef. DataDes. Element Name At

L001 213 Lading Line ItemNumb~er 0 NO 1/3Sequential line number for a lading item.

Line Item - Quantity and

Weight[047 010 1


L002 220 Billed/Rated-as Quantity C R 1/11

L003 221 Billed/Rated-as Qualifier C ID 2/2

L004 81 Weight C R 1/8

L005 187 Weight Qualifier C ID 1/2

L006 183 Volume C R 1/8

L007 184 Volume Unit Quai• C ID 1/1

10,7.36 930315

DEPARTMENT OF DEFENSE RAIL CARRIER INVOICEEI CONVENTION 410.003020

L008 80 Lading Quantity C NO 1/7

LO09 211 Packaging Form Code C ID 3/3

LOO 458 Dunnage Description 0 AN 2/25

L011 188 Weight Unit Qualifier 0 ID 1/1

L012 56 Type of Service Code 0 ID 2/2

930315 10.7.37

DEPARTMENT OF DEFENS RAIL CARRIER INVOICEEDI CONVEU -)ON 410.003020

Segment: L1 Rate and ChargesLevel: 1


Max Use: 10Loop:

Purpose: To specify rate and charges detail relative toa line item including freight charges, advan-ces, special charges, and entitlements

Syntax Notes: 04 R040506 - At least one of L104,L105 orL106 is required.

14 P1415 - If either L114 or Ll15 ispresent, then the other is required.


Data Bement SumwqyRef. DataDes. Eleuent Name AttribsUt"

LIO1 213 Lading Line ftenNunber 0 NO 1/3

L102 60 Freight Rate 0 R 1/9

L103 122 Rate/Value Qualifier 0 ID 2/2

L104 58 Charge C N2 1/9For a line item: freight or special charge; for thetotal invoice: the total charges -- expressed in thestandard monetary denomination for the currencyspecified.

Service Charge1048 1

Charge for each service identifiedin L108. Implied decimal atsecond position from right.

L105 191 Advances C N2 1/9

L106 117 Prepaid Amount C N2 1/9

L107 120 Rate Combination Point Code 0 AN 3/9

10.7.38 930315

DEPARTMENT OF DEFESE RAI. CARRIER INVOICEEDI CONVENTION 410.003020

Li 08 150 Special Charge or Allowance 0 ID 3/3CodeCode identifying type of special charge or al-lowance.

Service Charge Code[049 *1

Services regulated by the MilitaryTraffic Management Command

(MTMC). See Billing Instructionsavailable from DoD Payment Cen-ter for more information. See Ap-

pendix 10.F for cross referencefrom DoD codes to ASC X1 2

codes.

L109 121 Rate Class Code 0 ID 1/3

L110 39 EntitlementCode 0 ID 1/1

L01l 16 Charge Method of Payment 0 ID 1/1

Li 12 276 Special Charge Description 0 AN 2/25Identification of special charge. This data element isused whenever an applicable code cannot be foundin data element 150.

Service Charge Description[050 *1

Use free form description of anythird party or miscellaneous ser-

vice code identified in L108. SeeAppendix 1 O.F for application.

Ll13 257 Tariff Application Code 0 ID 1/1

L1i4 74 Declared Vase C N2 2/10

Li15 122 RateNalue Qualifier C ID 2/2

L116 372 Lading Liability Code 0 ID 1/1

L117 220 biI' d/Rated-as Quantity C R 1/11

L118 221 Billed/Rated-as Qualifier C ID 2/2

930315 10.7.39

DEPARTMBET OF DEPVdGE RAIL CARRIER INVOICEEDI CONViJtiON 410.003020

Segment: LE Loop TrailerLevel: 1

Sequence: 475

Usage: M

Max Use: 1Loop:

Purpose: To indicate that the loop immediately preced-ing this segment is complete

Comment: 00 LE is a control segment. LE is alwaysused in conjunction with a correspondingloop header (start) - LS, as illustratedbelow. The LS and LE indicate the startand end of a loop but are not part of theiteration of the loop.LOOP NESTINGLoop "A" Header (LS "A")Loop "B" Header (LS "B")

Loop -C- Header (LS -C-)Loop "C" Trailer (LE "C")Loop "D" Header (LS "D")Loop "D" Trailer (LE "D")

Loop "B" Trailer (LE "B")Loop "A" Trailer (LE "A")

Neither LS nor LE is used if the datawithin the loop is not used.

Syntax Notes: 00 One loop may be nested containedwithin another loop, provided the innernested loop terminates before the outerloop. When specified by the standardseting body as 'mandatory', this seg-ment, in combination with "LS", must beused. It is not to be used if not specifi-cally set forth for use. The loopidentifier in the loop header and trailermust be identical. The value forthe identifier is the loop ID of the re-quired loop beginning segment. Theloop ID number is given on the transac-tion set diagram in the appropriateASC X12 version/release.

Data Element SummayRef. DatDo. Element Name Atutgnst

10.7.40 930315

DEPARTNMWT OF DMSE RAIL CARRIER INVOICEEDI CONVNT1ION 410.003020

LE01 447 Loop Identifier Code M AN 1/4Code identifying a loop within the transaction setwhich is bounded by the related LS and LE seg-ments (corresponding LS and LE segments musthave the same value for loop identifier). (Note: Theloop ID number given on the transaction set diagramis recommended as the value for this data element insegments LS and LE.)

Loop Trailer1050010 1


930315 10.7.41

DPARTMBW OF DWFE RAIL CARRIER WVOICEOI CONVeaNOm 410.003020

Segment: L7 Tariff ReferenceLevel: 1


Max Use: 30Loop:

Purpose: To reference details of the tariff used to ar-rive at applicable rates or charge

Comment: 10 L710 is the Effective Date.15 "City" and "State" in L715 and L716

are used for rate combination city andstate.

Data Element SummaryRef. DabD"s. Eemet Nam Attlzfe

L701 213 Lading Une ftem Nmbier 0 NO 1/3

L702 168 Tariff Agency Code 0 ID 1/4

L703 171 Tariff Numrer o AN 1/7

L704 172 Tariff Section 0 AN 1/2

L705 169 Tariff Item Numner 0 AN 1116

L706 170 Tariff Item Part 0 NO 1/2

L707 59 Freight Class Code 0 AN 2/5

L708 173 Tariff Supplemnent Identifier 0 AN 1/4

1709 46 ExParte 0 AN 4/4

L710 373 Date 0 DT 6/6

L711 119 Rate Basis Nuntmer 0 AN 1/6

10.7.42 930315

DEPARThMB OF DEFESE RAIL CARRIER INVOICEWI CONVWTION 410.003020

L712 227 Tariff Colukm 0 AN 1.12

L713 294 Tariff Distance 0 NO 1iDistance on which the rate for a shipment is based.

Tariff/Tender Miles1051 1

Mileage used in calculatingnileage related charges. Qualify

in L714.

L714 295 Distance Qualifier 0 ID 1/1Code identifying the distance unit.

Tariff/Tender Miles Qualifier1052 *1 Code Definition

T Tariff/Tender Miles

L715 19 City Name 0 AN 2/19

L716 156 State or Province Code 0 ID 212

930315 10.7.43

DEPARTMNIT OF DFUM RAIL CARRIER NVOICEEDI CONvYBInN 410.003020

Segment: L3 Total Weight and ChargesLevel: 1

Sequence: 540Usage: C

Max Use: 1Loop:

Purpose: To specify the total shipment m terms ofweight, volume, rates, charges, advances,and prepaid amounts applicable to one ormore line items

Comment: 05 L305 is the total charges.Syntax Notes: 01 P0102 - If either L301 or L302 is

present, then the other is required.03 P0304 - If either L303 or L304 is



present, then the other is required.

Data Element SuwwnmyRef. DataDo&. Elemut Name Attrilbgs

L301 81 Weight C R 1/8Numeric value of weight.

Total Billed Weight1052 100 1

Total billed weight in poundsrounded to whole number. If not

applicable to invoice, enter 0.

1302 187 Weight Qualifier C ID 1/2Code defining the type of weighlt

Total Billed Weight Qualifier[052 110 *1 Code Definition

8 Billed Weight

1303 60 Freight Rate C R 1/9

L304 122 RateNalue Qualifier C ID 2/2

1305 58 Charge 0 N2 1/9

10.7.44 930315



L306 191 Advances 0 N2 1/9

L307 117 Prepaid Amount 0 N2 1/9

L308 150 Special Charge or Allowance 0 ID 3/3Code

L309 183 Volume C R 1/8

L310 184 Volume Unit Qualifier C ID 1/1

L311 80 Lading Quantity 0 NO 1/7

L312 188 Weight Unit Qualifier 0 ID 1/1

L313 171 TariffNumber 0 AN 1/7

L314 74 Declared Value C N2 2110

L31 5 122 Rate/Value Qualifier C ID 2/2

930315 10.7.45

DEPARTMENT OF DEFENSE RAIL CARRIER INVOICEED! CONVENTION 410.003020

Segment: SE Transaction Set Trailer


Usage: MMax Use: 1

Loop:Purpose: To indicate the end of the transaction set

and provide the count of the transmntted seg-ments (including the beginning (ST) and en-ding (SE) segments).

Comment: 00 SE is the last segment of each transac-tion set.

Data Element SwmwrayRef. DataDes. Element Name Attbibsm

SEO1 96 Number of Included Segments M NO 1/6Total number of segments included in a transactionset including ST and SE segments.

Included Number ofSegments

1053 1Total segments in this transaction

set including the ST and SE seg-ments.

SE02 329 Transaction Set Control Number M AN 4/9

Identifying control number assigned by the originatorfor a transaction set.

Transaction Set ControlNumber1054 1

This data element ends the trans-action set and should match the

number that appears in the ST02that begins the transaction set.

10.7.46 930315



10.C Examples - X12.139 TransactionSet 410 Rail Carrier Invoice

This appendix contains an example of Transaction Set 410 as itis used for transmitting invoice information to a DoD paymentcenter.

The example illustrates the use of a 410 to transmit invoiceinformation to the Defense Finance and Accounting Service -Indianapolis Center (DFAS-IN).

930316 10.C.1

DEPARTWMT OF DEFOYSE RAIL CARRIER NVOICEEDI CONVBInON 410.003020

(Blank Page)

¶o.C.2 930315

DEPARWGMWI" OF DBEFESE RAIL CARRIER INVOICE


Example - Invoice information from Carrier to DFAS-IN using ASC X12 410

ST*410*00001 nil Transaction set header

B3B*784682*PP*910630*99750*910723*CR*R*C0016115 nil Beginning segment

N9*PQ*1611"45421 nil Payee code

N9*P8**PICKUP DATE*910622*1230 nil Pickup date and time

N9*DO**DELIVERY DATE*910630 n/I Delivery date

N9*CN*827648 nil Cartier reference number

N7**000 n/il Equlpment number

N8*110201*910630 n/l Waybill number

F9**origin station*VA nil Origin station

D9**desination station*CA n/il Destination station

NI*IU**27*LNFL n/l Imsing Office GBLOC

NI*OC**2*AACS n/l Tendered To Carrier SCAC

NI*DC**2*CR nil Desutinat transportation company SCAC

LX* I nI1 Charge loop ID

L5* I n/l Description, marks, numbers

LS*1 nil Loop header

LX*I n/ Assigned number

LO* I nil Line Itenm- quantity and weight

L1****80000****LHS nil Transportation Unehaal charge

LE*I nil Loop trailer

L7*************1500*T n/l Tender miles

LX*2 n/l Charge loop ID

LX*1 nil Assigned number

L5*1 nil Description, marks, number

LS*I n/l Loop header

93031S 10.C.3


EDI CONVEIONa 410W003020

LX*2 ui1 Chae sub-loop ID

LO* 1 nil Line Item - quantity and weight

Ll***197.50***ARG n/l Accessoiral servtces charn

LE*I n/l Loop trailer

L3*120000*B n/l Total weight

SE*31*O001 n/l Transaction set trailer

10.C.4 930315

DEPARTMEIT OF DEFBIE RAIL CARRIER INVOICE

EDI CONVBE'ION 410.003020

10.F Additional DoD Code Lists

This appendix contains additional DoD code lists for formattinginvoice data to the ASC X12 210 transaction set. Please notethat DoD code definitions may not be exactly the same as thoseidentified in the ASC X12 Standards publications.

Code list includes:

[051 1 - Service Charge Code

Footnote definitions:

* Need new X12 code

** Code to be moved from DE 152 to DE 150

930315 10.F.1

RAIL CARRIER INVOICE DEPARTMENT OF DSM410.003020 EDI CONVBENION

(Blank Page)

10.F.2 930315


EDI CONVENITION 410.003020

[055 J Service Charge Code

Mapping: 2 120 L108 150

Accessorial Services for Freight il Shipments

DoD LI08 DoD

Code Value Definition

GS GSS** Greater Security

RG ARG** Rail Armed Guard

RS RMS* Rail Surveillance

"TS TSS** Tank Surveillance (one tank per car)

TS TMS* Tank Surveillance (two tanks per car)

DM DEM Demurrage

HR HR-* Heater/Refrigeration

RC RCC Reconsignment/Diversion

SO SOC Stop-Off

SO EXM* Stop-Off (Excess Mileage Charge)

SG SRG Storage

WV WTV Weight Verification

AC 045 Advancing Charges

DV DTB* Detention

FC FCS* Furnishing Chassis

HF HHB Handling Freight

LU URC Loading/Unloading

PD PUD Pickup/Delivery

PR PRL Prelodging

RD RCL Redelivery

RV RLS* Relocation of Vehicle

SP SPU Split Pickup

SV SVS* Storage of Vehicles

TM TMV* Tendering of Multiple Vehicles

VF VFN* Vehicles Furnished But Not Used

SS SFT Special Train Service

AA AAS* Attendants Accompanying

CG CSP* Government Caboose

CG GSP* Government Guard Cars

930315 10.F.3

DEPARTEM T OF DEFOISE RAIL CARRIER INVOICE

EDI CONVNT'OIN 410.003020

CG CCP" Carrier Caboose

CG GCP* Camer Guard Cars

CG CRS* Government Caboose/Guard Cars Returned

EC ECS Empty Cars Ordered But Not Used

10.F.4 930315

DEPARITET OF DOW-4SE RAIL CARRIER INVOICE

wI CONVeflTN• 410.003020

Third Party or Miscellaneous Services

DoD LI08 DoD L112Code Value Definition Value

PUC Pickup Service Furnished (air freight)

SPC Overdimension Permit

BRD Bridge TolLs

IHT Highway Tolls

TPS* Third Pany/Miscellaneous Service Description

Linehaul Services

DoD LI08 DoD L112Code Value Definition Value

LHS* iUnehaul service

Surcharges

DoD LI08 DoD L112

Code Value Definition Value

100 Air surcharge

405 Fuel surcharge

BSC Bunker surcharge

CON Port congestion surcharge

- WAR War risk surcharge

930315 10.F.5

Form ApprovedREPORT DOCUMENTATION PAGE OPM No. O7O4-O18

P& reloimng buwren for this coecion of informaoon is estumated wo averae" 1 hour per isapoms.. including the timfe for reviewing Mistructo•ns. searching existislangl saources

sa10ming. and maintaining the dte needed. and rqviewing the collecton of intoination Send coummnnta rega•ding this buroen estimate or any otther aspect Of thi• coeilctuon of

inemlation.ddiniig te r reduing tM bunden. to Washington Headquarter Sanns. Directorate for ntorinazon Operations and Reports. 1215 Jeflerson Davns Highway. Suite124. Aulingtoo.VA 2202-4302.and the Oftfkeof Inforesation ard Regulatory Affairs. Offthcof Managerment and Budget Washington. DC 20S03.

1. AGENCY USE ONLY (Leave Biank) 2. REPORT DATE 3. REPORT TYPE AND DATES COVERED

Mar 93 Final

4. TILE AND SUBTITLE S. FUNDING NUMBERS

DoD Electronic Data Interchange (EDI) Convention: C MDA903-90-C-0006ASC X12 Transaction Set 410 Rail Carrier Invoice (Version 003020) PE 0902198D

6. AUTHOR(S)W. Michael Bridges and Harold L. Frohman

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) B. PERFORMING ORGANIZATION

Lgitics Management Institute REPORT NUMBER

6400 Goldsboro Road LMI-DF1OILN7Bethesda, MD 20817-5886

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORING/MONITORINGChief RPTA Division AGENCY REPORT NUMBER

Defense Finance and Accounting Service - Indianapolis CenterInformation Systems Directorate, Building 1Fort Harrison, IN 46249-0901

11. SUPPLEMENTARY NOTES

Prepared in cooperation with Data Interchange Standards Association, the Secretariat and administrative arm of the Accredited StandardsCommittee X12.

12a. DISTRIBUTION/AVAILABILITY STATEMENT 12b. DISTRIBUTION CODEA: Approved for public release; distribution unlimited

13. ABSTRACT (Maximum 200 words)

This is an electronic data interchange (EDT) systems design document that describes the standard or "convention" the Department of Defense(DoD) will use to accept a transaction invoice using the ASC X12.139 Transaction Set 410 Rail Carrier Invoice (003020).

14. SUBJECTTERMS 15. NUMBER OF PAGES

Electronic Data Interchange; EDT; DoD EDT Convention; Electronic Commerce; ANSI X12, X12, electronic 96standards; electronic business standards; computer-to-computer exchange of data; electronic documents: 16. PRICE CODEelectronic records: paperless environment; conventions; invoice: rail carrier

17. SECURITY CLASSIFICATION 18. SECURITY CLASSIFICATION 18. SECURITY CLASSIFICATION 20. LIMITATION OF ABSTRACTOFREPORT OF THIS PAGE OF ABSTRACT ULUncl.s~ified Unclassified Unclassified

NSN 7540-01-280-5500 Standard Form 298, (Rev. 2-89)Prescribed by ANSI Std. 239-18299-01

DoD DTIC- Electronic Data____ DoD DTIC- Electronic Data S NO0919 Interchange (EDI) F Convention ASC...

Documents

Transcript of DoD DTIC- Electronic Data____ DoD DTIC- Electronic Data S NO0919 Interchange (EDI) F Convention ASC...