DoD Transportation Electronic Business (DTEB) Convention
Department of Defense
DoD Transportation Electronic Business (DTEB) Convention
ASC X12 Transaction Set 315 Transportation Node Status Report (Version 004010)
VERSION 1
August 2016
20160829
DEPARTMENT OF DEFENSE TRANSPORTATION EDI CONVENTION
TRANSPORTATION NODE STATUS REPORT
315.N.004010
Department of Defense
DoD Transportation Electronic Business (DTEB) Convention
ASC X12 Transaction Set 315 TRANSPORTATION NODE STATUS REPORT (Version 004010)
VERSION 1
20160829
ii
DEPARTMENT OF DEFENSE TRANSPORTATION EDI CONVENTION
TRANSPORTATION NODE STATUS REPORT
315.N.004010
CONTENTS
1.0 INTRODUCTION
2.0 CONTROL SEGMENTS
3.0 STANDARD IMPLEMENTATION CONVENTION
4.0 IC ELEMENT MATRIX
5.0 RESERVED
6.0 IC CODE LISTS
7.0 RESERVED
8.0 RESERVED
9.0 RESERVED
20160829
VERSION 1
i.1
DEPARTMENT OF DEFENSE TRANSPORTATION EDI CONVENTION
TRANSPORTATION NODE STATUS REPORT
315.N.004010
(Blank Page)
i.2
VERSION 1
20160829
DEPARTMENT OF DEFENSE TRANSPORTATION EDI CONVENTION
TRANSPORTATION NODE STATUS REPORT
315.N.004010
Section 1.0
INTRODUCTION
This implementation convention (IC) describes the standard or convention the Department of Defense will use to exchange Transportation Node Status Report data in support of the Defense Transportation Electronic Business (DTEB) program. For further information about the DTEB program, contact the following: United States Transportation Command TCJ6-CA 508 Scott Drive Scott Air Force Base, IL 62225-7001 To view the current convention, go to [Note: To access publication, you must have an ITS account.]
Who Needs to Use This Document?
Computer programmers use this document to identify the data requirements for populating an EDI transaction.
Why Use a Convention?
A convention defines the rules for populating an EDI transaction. Following a convention ensures that trading partners will encounter fewer data quality problems during development and maintenance of EDI systems.
20160829
VERSION 1
1.1
DEPARTMENT OF DEFENSE TRANSPORTATION EDI CONVENTION
TRANSPORTATION NODE STATUS REPORT
315.N.004010
Contents
Additional sections are included in this document.
? Section 2.0, Control Segments, identifies the specific data requirements for formatting the EDI interchange control segments that envelop all EDI transactions.
? Section 3.0, Standard Implementation Convention, lists the layout of the target transaction set by segment and data element. Identified along side each transaction set data element is the IC Element Matrix index number from Section 4.0.
? Section 4.0, IC Element Matrix, identifies the application data elements trading partners need to exchange. This section can be used to map an existing application database into the transaction set.
? Section 5.0 , when present, contains an example of the EDI transactions.
? Section 6.0, Application Code Lists, when present, identifies the DoD codes that trading partners need to exchange. This section augments the matrix presented in Section 4.0.
? Other Sections contain examples of hard copy documents, examples of EDI transaction sets, segment looping logic tables, and other items that serve as references for software developers.
1.2
VERSION 1
20160829
Department of Defense Transportation EDI Convention
Transportation Node Status Report
315.N.004010
What's New In Version 1
Added in Version 1 DM Number DM Description
1236
In Section 6 for the code list for the B411, DE 310, at index 2-11 change code value 'INC' DOD definition from 'In-checked for onward processing' to 'In-checked at final destination'. Add code value 'ARI' with DOD definition of "In-checked for onward processing". Add usage note to new code 'ARI' that reads: "Use this code to indicate a REPSHIP reportable shipment has been inchecked at an in-transit location other than the final destination."
Approval Date
8/29/2016
20160829
VERSION 1
1.3
DEPARTMENT OF DEFENSE TRANSPORTATION EDI CONVENTION
STATUS DETAILS (OCEAN)
315.A.004010
Section 2.0
CONTROL SEGMENTS
Instruction
For detailed description of DoD data conventions for formatting Interchange Control and Functional Group segments for use among Defense Transportation Electronic Business (DTEB) trading partners refer to the DoD Transportation Electronic Business (DTEB) Convention, ASC X12 Control Segments (Version 004010), located at: [Note: To access publication, you must have an ITS account.] Commercial Trading Partners and DoD personnel that do not hold an ITS account may view the Convention at:
20160829
VERSION 1
2.1
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- pdc 274 borrowed um dlms codes3 defense logistics
- chapter 12 intragovernmental transactions table
- dod financial management regulation volume 5 chapter 24
- mil
- department of defense
- dod 7000 14 r financial management regulation volume 6b
- dodi 8320 06 september 26 2012 incorporating change 1
- dod transportation electronic business dteb convention
- mar 0 8 2012
Related searches
- dod 7000.14 r dod financial management regulation
- transportation business plan sample pdf
- dod business partner number lookup
- electronic commerce business model
- business plan for transportation business
- dod business case analysis example
- dod business case analysis guide
- dod business case analysis template
- dod business case analysis
- dod product support business case analysis guidebook
- senior transportation business opportunities
- electronic state business daily texas