DTIC ADA263353: DoD Electronic Data Interchange (EDI) Convention: ASC X12 Transaction Set 856 Ship Notice/Manifest (Version 003030)

60 Pages·1.5 MB·English

by  Defense Technical Information Center

DEPARTMENT OF DEFENSE SHIP NOTICE/MANIFEST
EDI CONVENTION 856.003030
Draft
*AD-A263 353
Department
"of
1
1993
SA PR~j
DoD
Electronic Data
Interchange (EDI)
* Convention
ASC X12 Transaction Set 856
Ship Notice/Manifest
(Version 003030)
ThI documet wa prepated by the Lo.sti, Managerant Intgitute for the Defense Finrance and
ActintingServtce -Cohibubas Center and the Defense Lvgwat Agency under Task DF1Ol. The task was
performed under Contra MDAg03-9O.C4-X06 with the Department of Defense. Permisason to quote or
reproduoe any pan of this dom uwit except for Governmnt purposes mun be obtained from the
Department of Defense Ecutive Agent for Elctronic Com(cid:127)(cid:127)rce/Electronic Data interrrhange/Ped~on
of Logisti Unc.iaassfed/fen-une Systers.
Executive Agent for EC/EDI/PLUS
Defense Logistics Agency
Cameron Station
Alexandria, VA 22304-6100 ,93-0)8758
BASELINE AS OF: 13 JANUARY 1993
nr~
SW SHIP NOTICE MANIFEST
ANSI ASC X12 VERSION/RELEASE 003M
10.0 DoD EDI CONVENTION
ASC X12 TRANSACTION SET 856
SHIP NOTICE MANIFEST
(VERSION 003030)
FORMATTING SHIP NOTICE MANIFEST INFORMATION FOR
THE DoD PAYMENT SYSTEM USING THE ASC X12 TRANS-
ACTION SET 16 SHIP NOTICE MANIFEST.
0
DT03 JANUARY 13 1993 10.0.1
MG SHIP NOTICE MANIFEST
ANSI ASC X12 VERSIONELEASE 003030
{BLANK PAGE)
10.0.2 UT03 JANUARY 13 Ies
REPORT DOCUMENTATION PAGE Form Approved
OPM No. 0704-0188
.
P~~ikI nregl.p-o ring hwden for this collection of information is estimated to average I hour per response. including the time for reviewung instructions. searching eist*" daw sources
- and snaintaining the data needed, and reiewig the collection of information. Send comments regarding this buriden estimate or any other aspect of this collection of
kbfumation. including suggestions for reducing this burdien.fto Washington Headquarters Services. Directorate for information operations and Reports. 1215 lefferson Davis Highway. Suite
12MArlingtn,.V A f202M-430 and to the Office of Information and Regulatory Affairs. Office of Management and Budget. Washington. DC2 05013.
1. AGENCY USE ONLY (gLave Blank) 2. REPORT DATE 3. REPORT TYPE AND DATES COVERED
January 1993 Draft
4. TITLE AND SUBTITLE 5. FUNDING NUMBERS
DoD Electronic Data Interchange (EDt) Convention: C MDA9O3-90-C -0006
ASC X12 Transaction Set 856 Ship Notice/Manifest (Version 003030) PE 0902198D
6. AUThOR(S)
Stephen Luster
Richard Modrowaki
William T. James
7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8, PERFORMING ORGANIZATION
Logistics M4anagement Institute REPORT NUMBER
6400 Goldsboro Road LMI-DL203-LN13
Bethesda, ND 2M8'7 %88N
9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORINGIMONITORING
DoD Executive Agent for ECIEDIIPLUS AGENCY REPORT NUMBER
Defense Logistics Agency
DLA-ZIE, Cameron Station
Alexandria. VA 22304
11. SUPPLEMENTARY NOTES
Prepared in cooperation with Data Interchange Standards Association, the Secretariat and administrative arm of the Accredited Standards
Committee X12
12a. DISTRIBUTION/AVAILABILITY STATEMENT 12b. DISTRIBUTION CODE
A: Approved for public release; distribution unlimited
13. ABSTRACT (Maximum 200 words)
This is an Electronic Data Interchange (EDT) systems design document that describes the standards or "convention" the Department of
Defense (DoD) will use to accept or transmit a ship notice/manifest using the ASC X12 Transaction Set 856 Ship Notice/Manifest (003030).
'documents;,
14. SUBJECITERMS 15. NUMBER OF PAGES
Electronic Data Interchange; EDT; DoD EDT Convention: Electronic Commerce; ANSI X12, X12; 62
electronic standards, electronic business standards; computer-to-computer exchange of data; electronic 16. PRICECODE
electronic records; paperless environment; conventions
L17. SOECFRU ERPITOYR TC LASSIFICATION 18. SOEF CTUHRISIT YP ACGLEA SSIFICATION 19. SOEFC AUBRSITTRYA CCLTA SSIFICATION 20. LUILMITATION OF ABSTRACT
Unclassified Unclassified Unclassified
NSN 7546-01-ZmSO-S0 Standard Form 298. (Rev 2- 89)
Pmacrib~d byA NSI Std M18-1
&WS6H IP NOTICE MANIFEST
___________________ANSI SC X1 2 VERSIOW/RELEASE 00303
Contents
FORMATTING SHIP NOTICE MANIFEST INFORMATION FOR
THE DOD PAYMENT SYSTEM USING THE ASC X12 TRANS-
AC71ON SET 886 SHIP NOTICE MANIFEST.
10.1 Introduction
10.1 Reserved
10.2 control Segments
10.3 Reserved
10.4 Resered
10.5 Reserved
10.6 Resered
10.7 DoD Conventions
10A Reserved
10.13 Reserved
10.C Example - Ship Notice Manifest Information From
Invoicng Party to DFAS Using ASC X12 856A
10.1) Reserved
10.E Reserved CQVU AMYT r7 4
10O.F Reserved__
______
Accession For
NTIS CFAkI
DIIC' 7-4,3 El
C dot~c
F'AW3Lind/ar
DT03 JANUARY 1233 10ON0.3~
656 SHIP NOTICE MANIFEST
ANSI A1C X12 VERSIOWRELEASE 003030
{BLANK PAGE)
10.0.4 DMTs JANUAR 13 1614
856 SHIP NOTICE MAN WEST
ANSI AXC X12 VERSION/RELEASE 003M
10.i INTRODUCTION
This is an Electronic Data Interchange (EDI) systems design
document that describes the standard or Oconvention' the
Department of Defense (DoD) will use to accept a Ship Notice
Manifest using the ASC X12 Transaction Set 856 Ship Notice
Manifest (003030). It contains information for the design of
interface computer programs that serve to link systems applica-
tion computer programs and an EDI translator computer pro-
gram.
Who Needs to Use This Document
Computer programmers can use this document to identify the
data in a populated EDI transaction with data requirements of
their specific application database. Conversely, programmers
can identify where their applications data requirement should
be carried in an EDI transaction.
Why Use a Convention
There are more ways to populate an EDI transaction than there
are ways to fill out a blank form. A convention defines the rules
for filling in or "populating" an EDI transaction with a specific
data set. Following a convention ensures the integrity of data
that is produced and processed by EDI capable computer sys-
* tems.
Contents
Three sections are included in this document.
"* Section 10., Control Segments, identifies the specific data
requirements for formatting the EDI interchange control
segments when sending and receiving EDI transactions.
"* Section 10.7, DoD Conventions, lists the layout of the target
transaction set by segment and data element. This section
can be used to interpret segments and data elements of a
populated transaction set.
"* Appendices contain examples of populated transaction sets,
trading partner data element matrix, and other items that
serve as references for software developers.
DT03 JANUARY 13 ION I0±1
S56 SHIP NOTICE WMAIFEST
ANSN AXC XI 2 VERSMOIOWELLEAS 003030
{BLANK PAGE}
10.3.2 003 JANUA~rY 1313SM
666 SHIP NOTICE MANIFEST
ANSI ASC X12 WEROWRELEASE 00300
10.2 Control Segme
,As
Overview
This chapter describes the Electronic Data Interchange (EDI)
control segments (interchange control segments and functional
group segments). The control segment information was derived
from the ASC X12 Standards Draft Version 3 Release 3
(ooo).
Purpose
This chapter identifies specific data requirement for formatting
the EDI control segments when transmitting and receiving EDI
transactions. The format and data content of the control seg-
ments is usually managed by EDI translation software. The data
requirement described herein should be used to set control
segment format when installing or initializing translation
software for transmission and reception of EDI transaction.
Contents
Two items are included in this chapter.
* Table 10.2-1, Interchange Control Segment Hierarchy
describes the control segments in their order of occurrence
in an EDi communications interchange.
* Table 10.2-2, DoD Convention ASC X12 Control Segments
is a detailed description of the Department of Defense data
conventions for formatting EDI standard control segments.
All segments identified in Table 10.2-1 are broken down and
described by their discrete data elements.
DT03 JANUARY 13 1963 10,1
6U SHIP NOTICE MANIFEST
ANNI ASC X1 2 VERSIOWNELEASE 003030
{BLANK PAGE)
102.2 0T33 JANUARY 13 IM