dod electronic data interchange (edi) · dod electronic data interchange (edi) * convention asc x12...

"DTIC

AD-A264 469 ELECTEM AY• 17 1993lli~B{Uill!!mlil~ll! . C D- D raft

DepartmentofDefense

DoDElectronic Data

* Interchange (EDI)ConventionASC X 12 Transaction Set 843Response to Requestfor Quotation(Version 003010)

DL203LN18

January 1993

93-10838B N A O: . J 1499BASELINE AS OF: JANUARY 29, 1993 ..

DEPARTMENT OF DEFENSE RESPONSE TO REQUEST FOR QUOTATION

DRAFT IMPLEMENTATION CONVENTION 843.0030 1DoD_

DraftDepartment

L k-b Defense

DoD

Electronic DataInterchange (EDI)

* ConventionASC X12 Transaction Set 843Response to Requestfor Quotation(Version 003010)

This docurnent was prepared by the Logitics Management Insitute forthe Defense Loa itic Agency underTask DL20. The task was performed under Contract MDA9•3-90-C-1006 with the Department of DefensePermission to quote or reproduce any part of this docurnwt except for Government purposes must beobtained from the Department of Defense .•xecutive Agent for Flectronc Commerce/Electronic DlauInterchange/Protection of Loglstics Unclassified/Sensitive Systerm

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

BASELINE AS OF: JANUARY 29, 1993

DEPARTMENT OF DEFENSEDRAFT IMPLEMENTATION CONVENTION

TABLE OF CONTENTS

1.0 INTRODUCTION ..................... 1.01

1.1 PURPOSE OF THE CONVENTION .. 1.0.1

1.2 SCOPE ..................... 1.0.1

1.3 RESPONSIBLE ENTITY ........... 1.0.1

1.4 HOW TO USE THE IMPLEMENTATIONCONVENTION ................... 1.0.2

1.4.1 Conventions, Standards, and Guidelines . . 1.0.21.4.2Documentation of Conventions ........ 1.0.3

2.0 MAINTENANCE ..................... 2.01

2.1 MAINTAINING CONVENTIONS ...... 2.0.1

2.2 VERSION/RELEASE TIMING ........ 2.0.1

3.0 DoD CONVENTIONS FOR USING ASC X12TRANSACTION SETS 3.01

3.1 INTRODUCTION ................ 3.0.1

3.2 CONTROL SEGMENTS ........... 3.0.1

3.2.1 Description of Use ................ 3.0.23.2.2Control Segment Specifications ....... 3.0.5

3.3 EXAMPLE OF CONVENTION USE .... 3.0.15

3.4 DoD CONVENTION ............. 3.0.19

4.0 ASC X 12 FORMS .................... 4.01

5.0 GLOSSARY ......................... 5.01

5.1 X12 GLOSSARY . ............... 5.C.1

5.2 DoD GLOSSARY ................ 5.0.6

SAccecjjý for

NfiS CRA&II:;: " .-• ,3 5UIC TAB o

I 1 •yI -Olst'iblstion I

BASEUNE A.; OF: JANUARY 2, 1993 -0aii

Avtl _ _ _ _ r IDi';t Soccial


0

0

0iv BASEUNE AS OF: JANUARY 29,1993

DEPARTMENT OF DEFENSE

DRAFT IMPLEMENTATION CONVENTION

* 1.0 INTRODUCTION

"This chapter explains ihe purpose of the convention, the scope ofthe guidance, and provides an explanation of how to use theconvention.

1.1 PURPOSE OF THE CONVENTIONThe convention provides general guidance on the implementationof American National Standards Institute (ANSI) Accredited Stand-ards Committee (ASC) X12 electronic data interchange (EDI)standards within automated information systems (AIS) and infor-mation interchange procedures that require the collection, report-ing, and/or exchange of data needed to perform defense missions.

1.2 SCOPEThe guidance is provided for two components. First. it may beused by organizational elements of the DoD community. It mayalso be useful to organizations external to DoD that exchange datawith the DoD community in the course of their business relation-ships.

The DoD community encompasses the Military Services, Organiza-tions of the Joint Chicfs of Staff. Unified and Specified Commands.Office of the Secretary of Defense, and the Defense agencies. (Thatcommunity is collectively referred to as the DoD Components.)

Organizational entities external to DoD include (a) non-Govern-ment organizations, both commercial and nonprofit; (b) Federalagencies of the United States Government other than DoD;(c) local and state governments; (d) foreign national governments:and (e) international government organizations.

The draft convention published in this document is for trial useand comment. DoD Components must submit to the DoD EDIExecutive Agent (EA) their data requirements that are not coveredin the conventions as soon as possible, as indicated in Chapter 2.0.Section 2.1.

1.3 RESPONSIBLE ENTITYThe Defense Logistics Agency (DLA) is DoD's Executive Agentfor implementing and maintaining Defense-wide programs for(a) EDI in accordance with DepSecDef memorandum of May 24,1988, Subject: Electronic Data Interchange of Business-RelatedTransactions; and (b) Protection of Logistics Unclassified/Sensi-tive Systems (PLUS) in accordance with Assistant Secretary ofDefense (Production and Logistics) [ASD(P&L)] memorandum ofNovember 21, 1989. Subject: Production and Logistics TaskGroup for Data Protection. Publication of these conventions isbased upon this authol:,y. See Chapter 2.0 ,jatin'tnan-:. SectiOi 2.1for office point of contact.

BASEUNE AS OF: JANUARY 29,1993 1.0.1



1.4 HOW TO USE THE IMPLEMENTATIONCONVENTIONThe main topics and structures of this document conform to theEDI Implem!ntation Reference Manual Guidelines document thatwas developed by a task group of the subcommittee on educationand implementation of the ASC X12. The purpose of havingagreed-upon topics and structure is to facilitate reference by themany industry and DoD personnel who are involved in implement-ing the uniform standards for electronic interchange of businesstransactions.

1.4.1 Conventions, Standards, and GuidelinesThe terms conventions, standards, and guidelines are usedthroughout the document and are defined as follows:

* Conventions are the common practices and/or interpretationsof the use of ASC X12 standards. Conventions define what isincluded in a specific implementation of an ASC X 12 standard.

" Standards are the technical documentation approved byASC X12; specifically, transaction sets, segments, data ele-ments. code sets, and interchange control structure. Standardsprovide the structure for each ASC X12 document.

" Guidelines are instructions on the use of EDI. They provideadditional information to assist in conducting EDI. Guidelinesare intended to provide assistance and should not be your solesource of information.

1.4.1.1 Who Develops the Conventions?Conventions result from a joint effort between business, technical.and EDI ASC X12 standards experts. The business data require-ment is defined, a transaction set is selected, and the data require-ment is then identified with data elements in the transaction set.A convention is usually developed before any computer EDI sys-tems development work and serves as a design document when thedevelopment process begins.

1.4.1.2 Why Use a Convention?To create an ASC X12 transaction, a user must know the datarequirements, understand the ASC X12 standard, and be able touse that information to develop an interface program between thecomputer application and the ASC X12 translator. The necessaryinformation to perform this task is contained in the conventiondocument. Users who follow the convention will create a transac-tion set that all DoD users understand.

1.4.1.3 Who Needs a Convention?System analysts and application programmers who plan to createor read ASC X12 transactions use a convention to aid in interfacesoftware design. The convention will help the programmer andanalyst identify where their application data requirement should becarried in an ASC X12 transaction set.

1.0.2 BASELINE AS OF: JANUARY 29,1993


1.4.4.4 Can I Develop a Convention?Conventions already exist for some of the most common businesspractices. Copies of existing conventiuns cawi be acquired throughyour organization's EDI coordinator at the start of an EDI project.If you find no conventions for the business practice you are aboutto implement, your EDI coordinator should contact the DoD Ex-ecutive Agent for EDI. See Chapter 2.0, Maintenance, Section 2.1for the point of contact,

1.4.2 Documentation of ConventionsConventions are adopted from, and are intended to be in confor-mance with, ANSI ASC X12 standards or ASC X12 Draft Stand-ards for Trial Use (DSTU).

1.4.2.1 Transaction SetFigure 1.4-1 provides an example of a transaction set table. Thetransaction set defines information of business or strategic sig-nificance jid consists of a transaction set header segment, one ormore data segments in a specified order, and a transaction settrailer segment. The actual ASC X12 standard as it appears in theofficial ASC X12 standards manual is presented on the right sideof the page. This standard also includes both syntax notes andcomments, The specific DoD usage designator is presented on theleft side of the page.

The designation "N/U" appears in the left column if DoD does notuse the specific segment. A page number will appear if the segmentis used.

1.4.2.2 Transaction Set SegmentFigure 1.4-2 is an example of a transaction set segment.

DoD usage is specified on the left side of the page. For identifier(ID) - type data elements, acceptable code values are listed onthe right side of the page under the definitions of the element.

DoD notes, reflecting how the convention is to be used appear onthe right side of the page at the segment level or the data elementlevel.

The following definitions are for use in interpreting the dataelement requirement designators in the DoD-specific segmentdirectory section of the convention. For ASC X12 usage, see thedefinitions in X12.6 Application Control Structure.

* MandatoryMandatory data elements are defined by ASC X12,

OptionalOptional data elements are used at the discretion of the sendingparty or are based upon mutual agreement between tradingpartners.

BASEUNE AS OF: JANUARY 29, 1993 1.0.3


DEPARTWIENT OF DEFENSEDRAFT MPLEMENTATION CONVENTION

124 -APPUCATION ADVICE ANSI ASC; X12 YERSIO4WREL.EASE 003010O00_

824 Application AdviceThis standard provides the format and establishes the data contents of theApplication Advice Transaction Set (824) within the context of an ElectronicData Interchange (EDI) environment. This transaction set provides the abilityto report the results of an application system's data content edits oftransaction sets. The results of editing transaction sets can be reported at thefunctional group and transaction set level, in either coded or tree-form formatIt is designed to accomodate the business need of reporting the acceptance,rejection or acceptance with change of any transaction set. The ApplicationAdvice should not be used in place of a transaction set designed as aspecific response to another transaction set (e.g., purchase orderacknowledgement sent in response to a purchase order).

Table 1PAQS# PC& a W&. 10 MAASaM. Ot AX UN LOOPMqIEAT

2 010 ST Transaction Set Header M 13 020 BGN Beginning Segment M I

LOOPlu-Ri 214 030 NI Name 0 15 040 N2 Additional Name tnformation 0 26 050 N3 Address Information 0 27 060 N4 Geographic Location 0 18 070 REF Reference Numbers 0 129 060 PER Administrative Communications Contact 0 3

Table 2PAMGE, P•O., UG•.i MA NlE• a. IM, tUBl iJDOPIAIm~

LOOP•-O.n 100W10 010 OTI Original Transaction Identification M 112 020 REF Reference Numbers 0 1213 030 DTM Date/Time Reference 0 2N/U 040 PER Administrative Conmiunications Contact 0 3N/U 050 AMT Monetary Amount 0 10N/U 060 OTY Quantity 0 10

LOOP ID-TD 1000- 014 070 TED Technical Error Description 0 115 080 NTE Note/Special Instruction 0 10016 090 SE Transaction Set Trailer M 1

1 DA01 • JANUARY 29l M

Figure 1.4-1 Example of a Transaction Set Table


DEPAINNT OF DUBEEORAFT WPLE1WTATMOE COIVEUVrnON

DEPARTMENT OF DEFENSEDRAFT IMPLEMENTATION CONW."NTION

824 • APPUCATION ADVICE8(-N • BEGINNING SEGMENT ANSI ASC X12 VERSIONWRELEASE 0030. )DOD0

Segment: BGN Beginning SegmentLevel: Header

Loop: -

Mandatory Usage: Mandatory

Max Use: 1

Purpose: To indicate the beginning of a transaction set.

Syntax: If BGN05 is used. BGN04 is required.

Comments: 1. BGN02 is the Transaction Set Reference Numtlr.

2. BGN03 is the Transaction Set Date.

3. BGN04 is the Transaction Set Time.

4. BGN05 is the transaction set time qualifier.

Data Element SummaryMW OAA

Mandatory BGN01 353 Transaction Set Purpose Code M 10 22Code identifying purpose of transaction set.

00 Original01 Cancellation04 Change12 Not Processed

Mandatory BGN02 127 Reference Number M AN 1/30Reference number or identification number as defined for a particularTransaction Set, or as specified by the Reference Number Qualifier.

Mandatory BGNO3 373 Date M OT 6/6Date (YYMMDD).

Conditonal BGN04 337 Time C TM 4/4Time expressed in 24-hour clock time (HHMM, time range: 0000 though 2359).

Implementtlion Note:Use HHMM.

Not Ueed BGN0S 623 Time Code 0 ID 2/2

3 DAOi -JANUARY 29 1993

Figure 1.4-2 Example of a Trnsaction Set Segment

BASELUNE AS OF: JANUARY 29, 1M 1.6.S


" RequiredRequired data elements are considered optional underASC X12 rules, but are required by DoD decision.

" RecommendedRecommended data elements are considered optional underASC X12 rules and by the DoD. but the industry recommendstheir use to facilitate EDI. Most companies in the industryare expected to use this data element.

"* Not Used"Not Used" data elements are those that the DoD does notuse.

• ConditionalConditional data elements depend on the presence of other dataelements in the transaction set.

1.0.6 BASEUNE AS OF: JANUARY 29,1993


DRAFT IMPLEMENTATION CONVENTj.,

* 2.0 MAINTENANCE

This chapter describes the procedures for maintaining the DoDconventions. It also presents a section on version/release timing.

2.1 MAINTAINING CONVENTIONSThe DLA, as DoD's Executive Agent for EDI and PLUS, hasestablished a joint program office to oversee implementation ofEDI. Some of the functions of this program office are to maintainconfiguration control of related standards and common supportpackages (e.g., versions of ASC X12 standards and PLUS algo-rithms employed), participate in the standards-setting process, andensure compliance with approved EDI standards.

To accomplish these functions, the joint program office has estab-lished .t conventions and standards development and maintenanceprocess whose objectives are: (1) to obtain ASC X12 data require-ments from the DoD Components and present the requirements tothe ASC X12 for consideration as ANSI standards, and (2) todevelop and maintain conventions for use by DoD Componentsand their potential trading partners.

To take advantage of, and not duplicate, existing data stan-dardization proccsses. the EA has established focal pointswithin the ASD Offices, the Military Services, and the DefenseAgencies from which LDl information is obtained and dissemi-nated.

The EA's primary source of information a.out DoD's data require-ments is the EDI User.

Changes to this publication and recommended changes to ANSIASC X12 should be forwarded through your organizational pointof contact for data standardization to:

EDI Standards CoordinatorA'TTN: DLA-ZCCameron StationAlexandria, VA 22304-6100

See Chapter 4 for reproducible ASC X12 Work Request forms.

2.2 VERSION/RELEASE TIMINGIdentification of the official "vesion" of a standard is critical tothe successful interchange of information. Each participant mustbe able to send and receive the same version to ensure the accuracyof the information exchanged.

The version is transmitted as a 12-character code in the FunctionalGroup Header segment (GS) in Data Element #480, Ver-sion/Release/Industry ID. This 12-character code is used bvASC X12 as follows:




1-3 Version number4-5 Release level of version

6 Subrelease7-12 DoD/Industry or Trade Association ID

ASC X12 assigns the codes in positions 1 through 6.

A major version (1-3) will change only after an official publicreview cycle, leading to republication of a new American NationalStandard.

Release level of each new major version (4-6) will begin at "000"and incremented by I for each new ASC X12 approved publicationcycle, usually once a year. The fifth character designates therelease and the sixth character designates the subrelease.

DoD/Industry/Trade Association ID (7-12) is used to identifyconventions. For this suffix, DoD will use "DoD_- with the 10thcharacter identifying successive publications. The llth and 12thcharacters may be used by the Military Departments or DefenseAgencies.

DoD conventions for using ASC X12 standards are publishedannually. Conventions developed for each release will be main-tained for 4 years. Military Services and DoD Agencies willdetermine which release to use on the basis of business need butwill not use any release more than 4 years old without approvalof the DoD EA.



843 RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSI'nNIRELEASE 003010DOD

3.0 DoD CONVENTIONS FOR USINGASC X12 TRANSACTION SETS

This chapter defines the DD transaction set conventions. Itincludes the instructions tor implementing the control structure anddefinitions of the usage indicators and applicable codes.

3.1 INTRODUCTIONThe power of the ASC X12 standard is in its building blockconcept, which standardizes the essential elements of businesstransactions. It is analogous to a "standard bill of materials andthe construction specifications," which gives the architectflexibility in what can be designed with standardized materials andprocedures. The EDI system designer, like the architect, uses theASC X12 standards to build business transactions that are oftendifferent because of their function and yet utilize the ASC X12standards. The "bill of materials and the construction specification�of ASC X12 are the standards found in the published technicaldocumentation.

ASC X12.3 - The Data Element Dictionarv specifies the dataelements used in the construction of the segments that comprisethe transaction sets developed by ASC X12.

ASC X12.5 - The Interchange Control Structure provides theinterchange conf-ol segment (also called an envelope) of a headerand trailer foi the electronic interchange through a data transmis-sion; it also provide a structure to acknowledge the receipt andprocessing of the envelope.

ASC X12.6 - The Application Control Structure defines the basiccontrol structures, syntax rules, and semantics of EDI.

ASC X12.22 - The Data Segment Directory provides the defini-tions and specifications of the segments used in the constructionof transaction sets developed by ASC X12.

The DoD convention in Section 3.4 conform to the above standardsand each transaction set is a complete document to the extentpossible. For further clarification of acronyms. abbreviations, andcodes, refer to ASC X 12 published technical documentation. Cottact the DoD EDI Executive Agent for copies or the Data Inter-change Standards Association, Inc., Suite 355, 1800 DiagonalRoad, Alexandria, VA 22314.

3.2 CONTROL SEGMENTSIn addition to the communication control structure, the EDI structureprovides the standards user with multiple levels of control to ensuredata integrity. It does so by using header and trailer control segments

SASEUNE AS OF: JANUARY 29, 1993 3.0.1


843 - RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD_

designed to identify uniquely the start and end of the interchange

functional groups and transaction sets. The relationship of thesecontrol segments is shown in Figure 3.2-1. Control Segmentspecifications are defined in Section 3.2.2.

3.2.1 Description of UseThe interchange header and trailer segments surround one or morefunctional groups or interchange-related control segments and per-form the following functions:

* Define the data element separators and data segment ter-minators

• Identify the sender and receiver

* Provide conrol information

* Allow for authorization and security information.

The Interchange Acknolwedgment Segment is used to acknowledgeone interchange header and trailer envelope where the envelopesurrounds one or more functional groups. (No acknowledgment ismade for the interchange acknowledgment.)

The interchange control number value in the acknowledgment(TAI segment) is the same as that for the ISA segment that isbeing acknowledged. The control number serves as a link betweenthe interchange header and trailer and the acknowledgment of thatheader and trailer.

The interchange acknowledgment does not report any status on thefunctional groups contained in the interchange and is separatefrom the communication system's error procedures.

The preparer of the interchange header and trailer indicates thelevel of acknowledgment in Data Element 113, AcknowledgmentRequested. If an acknowledgment is requested, then the recipientmust return an acknowledgment. If not requested, none should begiven.

The interchange acknowledgment control segments are placed afterthe interchange header and before the first functional group orbefore the interchange trailer if there are no functional groups.

Control segments are standard for all implementation conventionsproduced for the Department of Defense. Some codes associatedwith individual data elements within the control segments areunique to the individual transaction set. Others, identify the ANSIversion and release in which the convention is written.




843 • RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD

-Communications Transport ProtocolIA/- interchange control Header

GS /-Functional Group Header

ST,/Transaction Set H eacler

Detail Segments 1(e.g.. Purchase Order) J

SE Transaction Set Trailer (D

ST Transaction Set Heade I

Detail Segments : ] 3(e.g.. Purchase Order)

SE Transaction Set Trailer

GE Functional Group Trailer

GS Functional Group Header -

ST / Transaction Set Header

Detail Segments -(e.g., Receiving Advice)

SE Transaction Set Trailer

GE Functional Group Trailer

lEA interchange control Trailer

Communications Transport Protocol

Figure 3.2-1. Hierarchical Structure



843• RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD_

0

3.0.4 BASELINE AS OF: JANUARY 29, 1993 I


843 RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSIONIRELEASE 003010DOD_

3.2.2 Control Segment Specifications



843 • RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD___

3.0.6 BASEUNE AS OF: JANUARY 29, 1993


001 CONTROL SEGMENTS 843 RESPONSE TO REQUEST FOR QUOTATIONISAo INTERCHANGE CONTROL HEADER ANSI ASC X12 VERSION!RELEASE 003010DOD

Segment: ISA Interchange Control HeaderPurpose: To start and identify an interchange of one or more functional groups

and interchange-related control segments.

Data Element SummaryREP. DATADES. ELEMIEW NAME ATTRIBUTES

Mandatory ISA01 101 Authorization Information Qualifier M ID 2-/2Code to identify the type of information in the Authorization Information.

00 No Authorization Information Present (No Meaningful Information in 102)

Mandatory ISA02 102 Authorization Information M AN 10/10Information used for additional identification or authorization of the sender or thedata in the interchange. The type of information is set by the AuthorizationInformation Qualifier.

Implementation Note:If no authorization information is agreed to by trading partners, fill field with blanks.

Mandatory ISA03 103 Security Information Qualifier M ID 2/2

Code to identify the type of information in the Security Information.

01 Password

Mandatory ISA04 104 Security Information M AN 10/10

This is used for identifying the security information about the sender or the datain the interchange. The type of information is set by the Security InformationQualifier.

Implementation Note:An agreed upon password. If no security information is agreed to by trading partners, fill field with blanks.

Mandatory ISA05 105 Interchange ID Qualifier M ID 212Qualifier to designate the system/method of code structure used to designate thesender or receiver ID element being qualified.

ZZ Mutually DefinedCode Value Implementation Note:An agreed upon designation of DoD Activity Address Code (DoDAAC) or other code coordinatedwith the value-added network (VAN).

Mandatory ISA06 106 Interchange Sender ID M ID 15/15Identification code published by the sender for other parties to use as thereceiver ID to route data to them. The sender always codes this number in thesender ID element.

Implementation Note:DoD activities use Department of Defense Activity Address Code (DoDAAC) or other code coordinated withthe value-added network (VAN). Non-DoD activities use identification code qualified by ISA05 andcoordinated with the VAN.

Mandatory ISA07 105 Interchange I Qualifier M ID 2/2Qualifier to designate the system/method of code structure used to designate thesender or receiver ID element being qualified.

ZZ Mutually Defined

BASEUNE AS OF: JANUARY 29,1993 DI08 3.0.7


843 RESPONSE TO REQUEST FOR QUOTATION 001 -CONTROL SEGMENTSANSI ASC X12 VERSIONJRELEASE 003010DOD ISA INTERCHANGE CONTROL HEADER

Code Value Implementation Note:An agreed upon designation of DoD Activity Address Code (DoDA4C) or other code coordinatedwith the value-added network (VAN).

Mandatory ISA08 107 Interchange Receiver ID M ID 15'15Identification code published by the receiver of the data. When sending, it isused by the sender as their sending ID, thus other parties sending to them willuse this as a receiving ID to route data to them.

Implementation Note:DoD activities use Department of Defense Activity Address Code (DoDAAC) or other code coordinated withthe value-added network (VAN). Non-DoD activities use identification code qualified by ISA05 andcoordinated with the VAN.

Mandatory ISA09 108 Interchange Date M DT 6/6Date of the interchange.

Implementation Note:Assigned by translation software. YYMMDD

Mandatory ISA10 109 Interchange Time M TM 4/4Time of the interchange.

Implementation Note:Assigned by translation software. HHMM

Mandatory ISAI1 110 Interchange Control Standards Identifier M ID 1/1Code to identify the agency responsible for the control standard used by themessage that is enclosed by the interchange header and trailer.

U U.S. EDI Community of ASC Xl 2, TDCC, and UCS

Mandatory ISA12 Ill Interchange Control Version Number M ID 5/5This version number covers the interchange control segments and the functionalgroup control segments.

00301 Draft Standard for Trial Use Approved for Publication by ASC X1 2 ProceduresReview Board Through October 1990

Code Value Implementation Note:Version ID as defined or agreed upon by the trading partners.

Mandatory ISA13 112 Interchange Control Number M NO 9/9This number uniquely identifies the interchange data to the sender. It is assignedby the sender. Together with the sender ID it uniquely identifies the interchangedata to the receiver. It is suggested that the sender, receiver, and all third partiesbe able to maintain an audit trail of interchanges using this number.

Mandatory ISA14 113 Acknowledgment Requested M ID 1/1

Code sent by the sender to request an interchange acknowledgment,

0 No Acknowledgment Requested

1 Interchange Acknowledgment Requested

Mandatory ISA1S 114 Test Indicator M ID 1/1Code to indicate whether data enclosed by this interchange envelope is test orproduction.

P Production Data

T Test Data

3.0.8 BASELINE AS OF: JANUARY 29, 1993. DI08

DEPARTMIENT OF DEFENSEDRAFT IMPLEMENTATION CONVENTION

001 - CONTROL SEGMENTS 843 RESPONSE TO REQUEST FOR QUOTATION.ISA -INTERCHANGE CONTROL HEADER ANSI ASC X12 VERSION/RELEASE 00301 ODOD_Code Value Implementation Note:Assigned by translation software.

Mandatory ISA16 115 Subelement Separator M AN 1/1This is a field reserved for future expansion in separating data elementsubgroups. (in the interest of a migration to international standards, this shouldbe different from the data element separator).

Implementation Note:Use character".

BASELINE AS OF: JANUARY 29,1993 * DIOS 3.0.9


843 RESPONSE TO REQUEST FOR QUOTATION 001 . CONTROL SEGMENTSANSI ASC X12 VERSION/RELEASE 003010DOD GS FUNCTIONAL GROUP HEADER

Segment: GS Functional Group HeaderPurpose: To indicate the beginning of a functional group and to provide control

information

Syntax: The data interchange control number (GS06) in this header must beidentical to the same data element in the associated Functional GroupTrailer (GE02).

Comment: A functional group of related transaction sets, within the scope of X1 2standards, consists of a collection of similar transaction sets enclosed bya functional group header and a functional group trailer.

Data Element SummaryREF. DATADES. ELEMENT NAME ATTRIOUTES

Mandatory GSO1 479 Functional Identifier Code M ID 2/2Code identifying a group of application related Transaction Sets.

Implementation Note:Choose the code value appropriate to the information content of the functional group. See X12 Dictionary forsource code list.

RR Response to Request For Quotation (843)

Mandatory GS02 142 Application Sender's Code M AN 2/15Code identifying party sending transmission. Codes agreed to by tradingpartners.

Implementation Note:DoD activities use Department of Defense Activity Address Code (DoDAAC). Non-DoD activities useidentification code assigned by DoD activity. Recommend for increased security that non-DoD code differfrom that used in ISA06.

Mandatory GS03 124 Application Receiver's Code M AN 2/15Code identifying party receiving transmission. Codes agreed to by tradingpartners.

Implementation Note:DoD activities use Department of Defense Activity Address Code (DoDAA C). Non-DoD activities useidentification code assigned by DoD activity. Recommend for increased security that non-DoD code differfrom that used in ISA08.

Mandatory GS04 29 Group Date M DT 6/6Date sender generated a functional group of transaction sets.

Implementation Note:Assigned by translation software.

Mandatory GS05 30 Group Time M TM 4/4Time (HHMM) when the sender generated a functional group of transaction sets(local time at sender's location).


Mandatory GS06 28 Group Contrr NJumber M NO 1/9Assigned number originated and maintained by the sender.

3.0.10 BASEUNE AS OF: JANUARY 29, 1993 . D108


001 -CONTROL SEGMENTS 843 RESPONSE TO REQUEST FOR QUOTATION.GS • FUNCTIONAL GROUP HEADER ANSI ASC X12 VERSION/RELEASE 00301 ODOD_


Mandatory GS07 455 Responsible Agency Code M ID 1/2Code used in conjunction with Data Element 480 to identify the issuer of thestandard.

X Accredited Standards Committee X12

Code Value Implementation Note:Indicates that an ANSI X12 standard is being transmitted.

Mandatory GS08 480 Version/Release/Industry ID Code M ID 1/12Code indicating the version, release, subrelease and industry identifier of the EDIstandard being used. Positions 1-3, version number; positions 4-6, release andsubrelease level of version; positions 7-12, industry or trade association identifier(optionally assigned by user).

003010 Draft Standards Approved By ASC X12 Through June 1990.

Code Value Implementation Note:Code value agreed to by trading partners. See X12 Dictionary for source code list.

BASELINE AS OF: JANUARY 29,1993 • D108 3.0.11

DEPARTMENT OF DEFENSEDRAFT IMPLEMENTATION COI VENTION

843 RESPONSE TO REQUEST FOR 2UOTATION 001 . CONTROL SEGMENTSANSI ASC X12 VERSIONIRELEASE 00301 ODOD_ GE. FtNCTIONAL GROUP TRAILER

Segment: GE Func;tlonal Group TrailerPurpose: To indicate the end of a functional group and to provide control

information

Syntax: The data interchange control number (GE02) in this trailer must beidentical to the same data element in the associated Functional GroupHeader (GS06).

Comment: The use of identical data intert ,ange control numbers in the associatedfunctional group header and trailer is designed to maximize functionalgroup integrity. The control number is the same as that used in thecorresponding header.

Data Element Summary"REF. DATADES. ELEMENT NAME ATTRISUTES

Mandatory GEO1 97 Number of Transaction Sets Included M NO 1/6Total number of transaction sets included in the functional group or interchange(transmission) group terminated by the trailer containing this data element.


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

Implementation Note:Assigned by the translation software. This control number must match the control number of the precedingGS06 control number.

03.0.12 BASELUNE AS OF: JANUARY 29, 1993.• Dine


001 CONTROL SEGMENTS 843 RESPONSE TO REQUEST FOR QUOTATIONlEA - INTERCHANGE CONTROL TRAILER ANSI ASC X12 VERSION;RELEASE 003010DOD_

Segment: lEA Interchange Control Trailer

Purpose: To define the end of an interchange of one or more functional groupsand interchange-related control segments.

Data Element SummaryREF. DATADES. ELEME]t NAME ATTRhUVrES

Mandatory IEA01 116 Number of Included Functional Groups M No 1/5A count of the number of functional groups incluced in a trmnsmissio•n.


Mandatory IEA02 112 Interchange Control Number M NO 9/9This number uniquely identifies the intechange data to the sender. It is assignedby the sender. Together with the sende. ID it uniquely identifies the interchangedata to the receiver. It is suggested that the sender, receiver, and all third partiesbe able to maintain an audit trail of interchanges using this number.

!mplementation Note:Assigned by the translation software. This number must match the number that occurs in ISA13.

BASEUNE AS OF: JANUARY 29, 1993 • DI08 3.0.13


843 . RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD_

3.0.14 BASEUNE AS OF: JANUARY 29,1993


843 • RESPONSE TO REQUEST FOR QUOTATIONANiSI ASC X12 VERSION/RELEASE 003010DOD

3.3 EXAMPLE OF CONVENTION USE



843 - RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSIONIRELEASE 003010DOD_

3.0.16 BASELINE AS OF: JANUARY 29, 1993


643 * RESPONSE TO REQUEST POR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD

EXAMPLE - RESPONSE TO REOUEST FOR OUOTATION (843)

ASC X12 EDT FORMAT DEJ[]:j

ST*843*RFQ3010 N/L THIS IS AN 843 RESPONSE TO REQUEST FORQUOTATION WITH A CONTROL NUMBER OFRFQ3010.

BQR*00*N0001993Q3010*92103 1*098*9211 10*BI N/L AN ORIGINAL BID IN RESPONSE TO RFQN0001993Q3010 DATED OCTOBER 31,1992.THE EFFECTIVE DATE OF THE BID ISNOVEMBER 10. 1992 AND IT IS A BIDWITHOUT EXCEPTION.

REF*PR*PQ3010 N/IL THE PRICE QUOTE NUMBER IS PQ3010.

1TD*08*3*2-*10**30 NIL THE BID OFFERS A 2 PERCENT DISCOUNT IFPAYMENT IS MADE WITHIN 10 DAYS OF THEINVOICE DATE. THE TOTAL INVOICEAMOUNT IS DUE WITHIN 30 DAYS.

PWK*FD*EL**DL NIL REPRESENTS THE CERTIFICATION THAT THEBIDDER IS A REGULAR DEALER IN THECOMMODITIES BEING QUOTED. SATISFIESTHE FAR REQUIREMENT BY VIRTUE OFTRANSMITTING THE PWK SEGMENT USINGTHESE CODES.

Nl*SEO*33*lB712 N/L THE SELLING PARTY'S CAGE CODE IS 1B712.

PER*SU*ROY ROGERS*EM*TLEM4231 N/L THE SELLER'S POINT OF CONTACT IS ROYROGERS AND HIS ELECTRONIC ADDRESS ISTLEM4231.

POI*0001*4*ST*2500 N/L THE PRICE BID FOR ITEM 0001 IS $2500 PERSET.

POI*0002*I0*EA*500 N/L THE PRICE BID FOR ITEM 0002 IS S500 EACH.

C'rr2"3000 NIL THERE ARE 2 PO1 SEGMENTS IN THISTRANSACTION. THE SUM OF THE VALUE OFP0102 IS 3000.

AMTf*1' T15000 NIL THE TOTAL AMOUNT OF THE BID IS S15,000.

SE*12*RFQ3010 NIL THE TRANSACTION SET HAS 12 SEGMENTSAND THE CONTROL NUMBER IS RFQ3010.

NOTE: ALL NUMBERS ARE NOTIONAL AND USED FOR ILLUSTRATION PURPOSES ONLY.



843 - RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSIONIRELEJ'iE 003010DOD



843 . RESPONSE TO REQUEST FOR QUOTATIONO ANSI ASC X12 VERSIONJRELEASE 003010DOD_

843 Response to Request for QuotationThis standard provides the format and establishes the data contents of aresponse to request for quotation transaction set.The response to request forquotation transaction set provides potential buyers with price, deliveryschedule, and other terms from potential sellers of goods and services, inreaponse to 3 request for such information.

Table 1PAGE# POS. # SEG. ID NAME REQ. DES. MAX USE LOOP REPEAT

5 010 ST Transaction Set Header M 16 020 BQR Beginning Segment for Response to Request M 1

For Quotation7 030 NTE Note/Special Instruction F 1008 040 CUR Currency 0 111 050 REF Reference Numbers 0 12N/U 060 PER Administrative Communications Contact 0 3N/U 070 TAX Sales Tax Reference 0 312 080 FOB F.O.B. Related Instructions 0 1N/U 090 CTP Pricing Information 0 25. N/U 100 SSS Special Services 0 25N/U 110 CSH Header Sale Condition 0 1N/U 120 ITA Allowance, Charge or Service 0 1014 130 lTD Terms of Sale/Deferred Terms of Sale 0 5N/U 140 DIS Discount Detail 0 2016 150 DTM Date/Time Reference 0 1017 160 LDT Lead Time 0 12N/U 180 LIN Item Identification 0 5N/U 190 PID Product/Item Description 0 200N/U 200 MEA Measurements 0 4018 210 PWK Paperwork 0 2520 220 PKG Marking, Packaging, Loading 0 25N/U 230 TD1 Carrier Details (Quantity and Weight) 0 2N/U 240 TM5 Carrier Details (Routing Sequence/Transit 0 12

Time)N/U 250 TD3 Carrier Details (Equipment) 0 12N/U 260 TD4 Carrier Details (Special Handling/Hazardous 0 5

Materials)N/U 270 MAN Marks and Numbers 0 10

1 DCos . JANUARY 29 1993


843. RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD_

N/U 280 CTB Restrictions/ Conditions 0 5

'LO.P 110- N9 1000~N/U 290 N9 Reference Number 0 1N/U 300 MSG Message Text 0 1000

LOOPId-N 200

22 310 NI Name 0 124 320 N2 Additional Name Information 0 225 330 N3 Address Information 0 226 340 N4 Geographic Location 0 1N/U 350 REF Reference Numbers 0 1227 360 PER Administrative Communications Contact 0 3N/U 370 FOB F.O.B. Related Instructions 0 1N/U 380 TD1 Carrier Details (Quantity and Weight) 0 2N/U 390 TD5 Carrier Details (Routing Sequence/Transit 0 12


Materials)N/U 420 PKG Marking, Packaging, Loading 0 25

Table 2PAGE* POS6. SEG. ID NAME REQ. DES. MAX USE LOOP REPEAT

LOPI-POIt 1000(0028 010 PO1 Purchase Order Baseline Item Data 0 1N/U 020 CUR Currency 0 131 030 P03 Additional Item Detail 0 25N/U 040 CTP Pricing Information 0 25N/U 049 MEA Measurements 0 40

32 050 PID Product/Item Description 0 133 060 MEA Measurements 0 10N/U 070 PWK Paperwork 0 2534 080 PKG Marking, Packaging, Loading 0 2536 090 P04 Item Physical Details 0 138 100 REF Reference Numbers 0 12N/U 110 PER Administrative Communications Contact 0 3N/U 120 SSS Special Services 0 25N/U 130 ITA Allowance, Charge or Service 0 10N/U 140 IT8 Conditions of Sale 0 1N/U 150 ITD Terms of Sale/Deferred Terms of Sale 0 2N/U 160 DIS Discount Detail 0 20N/U 170 TAX Sales Tax Reference 0 3

OC05 . JANUARY 29 1993 2


843 -RESPONSE TO REQUEST FOR QUOTATION ANSI ASC X12 VERSIONIRELEASE 003010DOD_

39 180 FOB F.O.B. Related Instructions 0 1N/U 190 SDQ Destination Quantity 0 5041 200 DTM Date/Time Reference 0 1042 210 LDT Lead Time 0 1243 220 SCH Line Item Schedule 0 104N/U 230 FST Forecast Schedule 0 5N/U 240 TD1 Carrier Details (Quantity and Weight) 0 1N/U 250 TD5 Carrier Details (Routing Sequence/Transit 0 12


Materials)N/U 280 MAN Marks and Numbers 0 10N/U 290 CTB Restrictions/ Conditions 0 5

L OOP 1- CST 100N/U 300 CST Cost Analysis 0 1N/U 310 PID Product/Item Description 0 1N/U 320 CUR Currency 0 1N/U 330 DTM Date/Time Reference 0 2

. PIiO . N.... .1000N/U 340 SLN Subline Item Detail 0 1WU 350 PID Product/Item Description 0 1000

LOOP IDNCST 100N/U 360 CST Cost Analysis 0 1N/U 370 PID Product/Item Description 0 1N/U 380 CUR Currency 0 1N/U 390 DTM Date/Time Reference 0 2

LOI 1D - No 1000N/U 400 N9 Reference Number 0 1N/U 410 MSG Message Text 0 1000

LO O P 10-I. ~...i.•.~,:iiili;i•.ii:.ii i :!!.i. i"..200N/U 420 N1 Name 0 1N/U 430 N2 Additional Name Information 0 2N/U 440 N3 Address Information 0 2N/U 450 N4 Geographic Location 0 1N/U 460 REF Reference Numbers 0 12N/U 470 PER Administrative Communications Contact 0 3N/U 480 FOB F.O.B. Related Instructions 0 1N/U 490 TD1 Carrier Details (Quantity and Weight) 0 2N/U 500 TD5 Carrier Details (Routing Sequence/Transit 0 12

Time)N/U 510 TD3 Carrier Details (Equipment) 0 12

3 DCos. JANUARY 29 1993


843 • RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD

N/U 520 TD4 Carrier Details (Special Handling/Hazardous 0 5Materials)

N/U 530 PKG Marking, Packaging, Loading 0 25

Table 3PAGE# PO.8 BEG. I1 NAME REQ. DES. MAX USE LOOP REPEAT

44 010 CTT Transaction Totals M 145 015 AMT Monetary Amount 0 146 020 SE Transaction Set Trailer M 1

DC05 • JANUARY 29 1993 4


843 • RESPONSE TO REQUEST FOR QUOTATION* ST. TRANSACTION SET HEADER ANSI ASC X12 VERSION/RELEASE 003010DOD0

Segment: ST Transaction Set Header

Level: Header

Loop: _

Mandatory Usage: Mandatory

Max Use: 1Purpose: To indicate the stait of a transaction set and to assign a control number

Comment: The transaction set identifier (ST01) is intended for use by the translationroutines of the interchange partners to select the appropriate transactionset definition (e.g., 810 selects the invoice transaction set).

Data Element SummaryREF. DATAO•. ILEDI NAME A'fRISUUES

Mandatory ST01 143 Transaction Set Identifier Code M ID 3/3Code uniquely identifying a Transaction Set.

843 X12.8 Response to Request for Quotation

Mandatory ST02 329 Transaction Set Control Number M AN 419Identifying control number assigned by the originator for a transaction set.

5 DCOS . JANUARY 29 1993


843 . RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD BOR - BEGINNING SEGMENT FOR RESPONSE TO REQUEST FOR QUOTATION

Segment: BQR Beginning Segment for Response to Request For Quotation

Level: Header

Loop:Mandatory Usage: Mandatory

Max Use: 1

Purpose: To indicate the beginning of a response to request for quote transactionset and to transmit identifying numbers and dates

Syntax: If BQR05 is present, then BQR04 is required.

Data Element SummaryREF. DATADIS. ELEMENT NAME AT"IIUTES

Mandatory OQR01 353 Transaction Set Purpose Code M ID 2J2Code identifying purpose of transaction set.

Implementation Note:Use code 00 for all original quotations; code 01 when cancelling a quotation; code 02 when adding data to apreviously transmitted quote; code 03 when deleting data from a previously transmitted quote; code 04 whenchanging data in a previously transmitted quote; and code 07 when sending a duplicate quote

00 Original01 Cancellation

02 Add03 Delete04 Change07 Duplicate

Mandatory BQR02 586 Request for Quote Reference Number M AN 1/45Number assigned by the purchaser to identify his request for quote.

Mandatory BQR03 652 Request Quotation Control Date M DT 6/6Date to be used for reference purposes in an RFQ and a response to RFQ.

Conditional BQR04 374 Date/Time Qualifier C ID 3/3Code specifying type of date or time, or both date and time.

098 Bid (Effective)

Optional BQR05 373 Date 0 DT 6/6Date (YYMMDD).

Optional BQR06 379 Bid Type Response Code 0 ID 2/2Code indicating the type of response to the request for bid or quote.

Implementation Notes:1. If code AB or code UQ is used, explain in NTE segment following this segment.

2. An alternate bid (code AB) shall only be used to provide variations in volume or packaging. It is no to beused for a quote on an equal or substitute item unless the item description explicitly allows equivalentproducts.

AB Alternate BidBI Bid Without Exception

UQ Unable to Quote

DC05 • JANUARY 29 1993 6


843 - RESPONSE TO REQUEST FOR QUOTATION* NTE NOTE/SPECIAL INSTRUCTION ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: NTE Note/Special InstructionLevel: Header

Loop: -

Floating Usage: Floating

Max Use: 100

Purpose: To transmit information in a free-form format, if necessary, for commentor special instruction

Comment: The NTE segment permits free-form information/data which, under ANSIX12 standard implementations, is not machine processable. The use ofthe "NTE" segment should therefore be avoided, if at all possible, in anautomated environment.

Data Element SummaryREF. DATA

ME*. ELEMENT NAME ATUI@VrI ES

Optional NTE01 363 Note Reference Code 0 ID 3/3Code identifying the functional area or purpose for which the note applies.

GEN Entire Transaction Set

Mandatory NTE02 3 Free Form Message M AN 1/60Free-form text.

Implementation Note:If code AB or code UQ is used, in BQR06, NTE02 is used to explain.

7 co05 JANUARY 29 1993


843 . RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD CUR CURRENCY

Segment: CUR currencyLevel: Header

Loop:Optional Usage: Optional

Max Use: 1Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a

transaction

Syntax: 1. If CUR08 is present, then CUR07 is required.

2. If CUR09 is present, then CUR07 is required.

3. If CUR1 1 is present, then CUR10 is required.




7. If CUF,17 is present, then CUR16 is required.




Comments: 1. Monetary values are assumed to be expressed in the currency of thecountry of the transaction originator unless the optional CUR segment isused to specify a different currency. The CUR segment also permits thetransaction originator to indicate a specific exchange rate, foreignexchange location and date/time as the basis for a currency conversion.Example 1. Assuming the currency of the transaction originator is U.S.dollars, the following CUR segment, when used in the heading area of atransaction, would indicate that all monetary values appearing in thetransaction are expressed in Canadian Dollars (CAD). (In this examplethe exchange rate is at the discretion of the receiver).

CUR*BY*CAD* N/L

Example 2. Assuming the currency of the transaction originator is U.S.dollars, the following CUR segment, when used in the detail area of atransaction, describes a currency conversion for that particular item fromU.S. dollars to Canadian dollars. It also indicates that a specificexchange rate, at a specified foreign exchange location on a givendate/time be used as the basis for the currency conversion. Notes belowthe diagram describe the meaning of the element values.

DCOS - JANUARY29 1993 8


843 . RESPONSE TO REQUEST FOR QUOTATIONCUR -CURRENCY ANSI ASC X12 VERSION/R ELEASE 00301 ODOD_

2. CUR*BY*USD* 1.20*SE*CAD*NY*007*840821 * 1400 N/L1 2 3 4

1. Identifies the buyer's (BY) currency as U.S. dollars (USD).2. The multiplier (1.20) is the exchange rate factor for the conversion.3. Identifies the seller's (SE) currency as Canadian dollars (CAD).4. Indacaes the basis for the excharnje rate as the New York Foreign

Exchange (NY) and the effective date/time (007) as August 21, 1984(840821) at 2:00 P.M. (1400).The value for this item is to be converted to Canadian dollars (CAD' atthe exchange rate of 1.20, based on the New York Foreign Exchange(NY) at 2:00 P.M. (1400) on August 21, 1984. The actual unit priceconversion for the item would be:The unit price value 7.50 (U.S. dollars) multiplied by the exchange rate(1.20) equals 9.00 Canadian dollars (7.50 X 1.20 = 9.00) CUR07 through

CUR21 provide for five (5) dates/times relating to the currencyconversion, i.e., effective date, expiration date, etc.

Data Element Summary

REF. DATADES. ELBISENr NAME -ATMRIUTFS

Mandatory CUR01 98 Entity Identifier Code M ID 2/2Code identifying an organizational entity or a physical location.

Implementation Note:Use code BY for the government and code SE for the contractor.

BY Buying Party (Purchaser)

SE Selling Party

Mandatory CUR02 100 Currency Code M ID 3/3Code (Standard IS() for country in whose currency the charges are specified.

Optional CUR03 280 Exchange Rate 0 R 4/6Value to be used as a multiplier conversion factor to convert monetary value fromone currency to another.

Optional CUR04 98 Entity Identifier Code 0 ID 2/2Code identifying an organizational entity or a physical location,

Implementation Note:Use code BYfor the government and code SEfor the contractor.

BY Buying Party (Purchaser)

SE Selling Party

Optional CURO5 100 Currency Code 0 ID 3/3Code (Standard ISO) for country in whose currency the charges are specified.

Optional CUR06 669 Currency Market/Exchange Code 0 ID 3/3Code identifying the market upon which the currency exchange rate is based.

Implementation Note:Use any code.

Conditional CUR07 374 Date/Time Qualifier C ID 3/3Code specifying type of date or time, or both date and time.

9 DC05 • JANUAhY 29 1993

DEPARTMENT OF DEFENSEDRAFT IMPLEMENTATION CONVFNTION

843 RESPONSE TO REQUEST FOR GUOTATIONANSI ',SC X12 VERSION/RELEASE 0O3010DOD_ CUR CURRENCY

Implementation Note:Use code 007 for the date. tine the cited rate will be effective (start) and code 036 for the date/time the citedrate will cease to be effective (stop).

007 Effective

036 Expiration

Optional CUR08 373 Date 0 DT 6/6Date (YYMMDD).

Optional CUR09 337 Time 0 TM 4/4Time expressed in 24-hour clock time (HHMM, time range: 0000 though 2359).

Not Used CURIO 374 Date/Time Qualifier C ID 3/3

Not Used CURl1 373 Date 0 DT 616

Not Used CUR12 337 Time 0 TM 414

Not Used CUR13 374 Date/Time Qualifier C ID 3/3

Not Used CUR14 373 Date 0 DT 6/6

Not Used CUR15 337 Time 0 TM 4/4


Not Used CUR17 373 Date 0 DT 6/6

Not Used CUR18 337 Time 0 TM 414


Not Used CUR20 3/3 Date 0 DT 6/6

Not Used CUR21 337 Time 0 TM 4/4

DC05o JANUARY 29 1993 10


843 RESPONSE TO REQUEST FOR QUOTATIONREF REFERENCE NUMBERS ANSI ASC X12 VERSIONIRELEASE 003010DOD

Segment: REF Reference Numbers

Level: Header

Loop:Required Usage: Optional

Max Use: 12

Purpose: To specify identifying numbers.

Syntax: Either REF02 or REF03 is required.

Implementation Note:One iteration of this segment is required to provide the Price Quote Number, code PR.

Data Element Summary"REF. DATA

DES, ELEMENT NAME ATTRtiwSafs

Mandatory REF01 128 Reference Number Qualifier M ID 2/2Code qualifying the Reference Number.

Implementation Notes:1. When REFOJ is code CR or CT there must be an iteration of the DTM segment, code 036 to pro',,ide theexpiration date of the schedule or contract cited. Failure to provide this date, will require the buying activityto send afollow up message. Use code CR for Federal Supply Schedule.

2. When REF01 is code CR, REF02 will carry the number of the Federal Supply Schedule in which thequoted item can be found.

3. When REFO0 is code CT, it will represent a contract other than a supply schedule, known to the quoter,from which the quoted item can be ordered. Give the contract number in REF02 and explain the nature (if the

contrac: in REF03, if necessary.

4. REFOI must contain one iteration using code PR so that any response can reference the quoting party's

quotation number.

5. Code 65 may optionally be used for the transactions Unique Tracking Number (UTN).

65 Total Order Cycle Number

CR Customer Reference NumberCT Contract Number

PR Price Quote Number

Conditional REF02 127 Reference Number C AN 1/30

Reference number or identification number as defined for a particularTransaction Set, or as specified by the Reference Number Qualifier.

Conditional REF03 352 Description C AN 1/80A free-form description to clarify the related data elements and their content.

S1 DCos. JANUARY 29 1993


843 • RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD_ FOB. F.O.B. RELATED INSTRUCTIONS

Segment: FOB F.O.B. Related InstrrvtionsLevel: Header

Loop: -

Optional Usage: Optional

Max Use: 1Purpose: To specify transportation instructions relating to shipment

Syntax: 1. If FOB03 is present, then FOB02 is required.

2. If FOB04 is present, then F0805 is required.3. If FOB07 is present, then FOB06 is required.4. If FOB08 is present, then FOB09 is required.

Comments: 1. FOB01 indicates which party will pay the carrier.2. FOB02 is the code specifying *ransportation responsibility location.3. FOB06 is the code specifying title passage location.4. FOB08 is the code specifying the point at which the risk of losstransfers. This may be different than the location specified inFOB02/FOBO3 and FOB06/FOB07.

Implementation Note:Use only when quoting other than FOB destination.

Data Element SummaryREF. DATADES. ELENMEW NAME ATThUJES

Mandatory FOB01 146 Shipment Method of Payment M ID 2/2Code identifying payment terms for transportation charges.

DF Defined by Buyer and Seller

Conditional FOB02 309 Location Qualifier C ID 1/2Code identifying type of location.

Implementation Notes:1. Use code ZZ when the FOB point is other than origin or destination (e.g.. intermediate point).

2. FOB destination is assumed unless specified otherwise.

OR Origin (Shipping Point)

ZZ Mutually Defined

Optional F0803 352 Description 0 AN 1/80A free-form description to clarify the related data elements and their content.

Implementation Note:When FOB02 is code ZZ, use FOB03 to explain the nature of the other location.

Not Used FOB04 334 Transportation Terms Qualifier Code 0 ID 2/2

Not Used FOB05 335 Transportation Terms Code C ID 3/3

Not Used FOB06 309 Location Qualifier C 10 1/2

NotUsed F0807 352 Description 0 AN 1/80

DCO5. JANUARY 29 1993 12


843 . RESPONSE TO REQUEST FOR QUOTATION. FOB • F.O.B. RELATED INSTRUCTIONS ANSI ASC X12 VERSIONWRELEASE 003010DOD

Not Used FOB08 54 Risk of Loss Qualifier 0 ID 2/2

Not Used FOB09 352 Description C AN 1/80

13 DCo5 . JANUARY 29 1993


843. RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003011ODOD ITD -TERMS OF SALE/DEFERRED TERMS OF SALE

Segment: ITD Terms of Sale/Deferred Terms of SaleLevel: HeaderLoop: _


Max Use: 5

Purpose: To specify terms of sale.

Syntax: 1. If ITDO3 is present, then at least one of ITDO4, ITDO5, ITD13 isrequired.2. If ITDO8 is present, then at least one of ITDO4, ITDO5 or ITD13 is

required.

3. If ITDO9 is present, then ITD1 0 or ITD1I1 is required.

Comment: If the code in ITD01 is 04, then ITDO9 is required and either ITD1 1 orITD12 is required. If the code in ITD01 equals 05, then ITDO6 or ITDO7 isrequired.

Implementation Note:If no discount is applicable to the quotation, or if the terms are Net, 30 Days, do not transmit thissegment.


REP. DATAM(6. MAW NAME ATrR*IUTES

Optional ITD01 336 Terms Type Code 0 ID 2/2Code identifying type of payment terms.

Implementation Note:Use code 08 only.

08 Basic Discount Offered

Optional ITDO2 333 Terms Basis Date Code 0 ID 1/2Code identifying the beginning of the terms period.

Implementation Note:Any applicable code can be used.

Optional ITDO3 338 Terms Discount Percent 0 R 1/6Terms discount percentage, expressed as a percent, available to the purchaser ifan invoice is paid on or before the Terms Discount Due Date.

Conditional ITDO4 370 Terms Discount Due Date C DT 616Date payment is due if discount is to be earned.

Conditional ITDO5 351 Terms Discount Days Due C NO 1/3Number of days in the terms discount period by which payment is due if termsdiscount is earned.

Not Used ITDO6 446 Terms Net Due Date 0 DT 6/6

Optional ITDO7 386 Terms Net Days 0 NO 1/3Number of days until total invoice amount is due (discount not applicable).

Optional ITDO0 362 Terms Discount Amount 0 N2 1/10

DC05 . JANUARY 29 1993 14


843 - RESPONSE TO REQUEST FOR QUOTATION

ITDO TERMS OF SALE/DEFERRED TERMS OF SALE ANSI ASC X12 VERSION/RELEASE 003010DOD

Total amount of terms discount.

Implementation Note:Used so that rounding-off methodology will not be a factor.

Not Used ITDO9 388 Terms Deferred Due Date 0 DT 6/6

Not Used ITD1O 389 Deferred Am.unt Due C N2 1/10

Not Used ITD1 1 342 Percent of Invoice Payable C R 1/5

Not Used ITD12 352 Description 0 AN 1180

Conditional ITD13 765 Day of Month C NO 1/2The numeric value of the day of the month between 1 and the maximum day ofthe month being referenced.

Optional ITD14 107 Payment Method Code 0 ID 1/1Code identifying type of payment procedures.

Implementation Note:This data element will normally not be used in DoD applications.

15 DCo. JANUARY 29 1993


843 • RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD DTMU DATE/TIME REFERENCE

Segment: DTM Date/Time Reference

Level: Header

Loop: _


Max Use: 10

Purpose: To specify pertinent dates and times

Syntax: At least one of DTM02 or DTM03 must be present.

Implementation Note:Quoted delivery date will be provided in this segment as an actual date or in the LDT segment as aset number of calendar days after receipt of order. If the latter is used, omit this segment.

Data Element SummaryREF. DATADES& ELEMET NAME ATMII•TES

Mandatory DTM01 374 Date/Time Qualifier M ID 3/3Code specifying type of date or time, or both date and time.

Implementation Notes:1. Use code 036 to indicate the expiration date of a Federal Supply Schedule or contract.

2. Use code 001 when the quoter wants to extend the quote expiration date beyond a 30-day time from theeffective date of the quote, as specified in BQR05.

3. Use code 075, the delivery date being quoted, when the quoted delivery date will be less than the requireddelivery date specified in the RFQ, applies to the whole order and the delivery date is not defined in the LDTsegment.

001 Cancel After036 Expiration075 Promised for Delivery (Prior to and Including)

Conditional DTM02 373 Date C DT 616Date (YYMMDD).

Not Used DTM03 337 Time C TM 4/4

Not Used DTM04 623 Time Code 0 ID 212

DC05. JANUARY 29 1993 16


843 RESPONSE TO REQUEST FOR QUOTATION* LDT LEAD TIME ANSI ASC X12 VERSIONIRELEASE 003010DOD_

Segment: LDT Lead Time

Level: Header


Max Use: 12

Purpose: To specify lead time for availability of products and services.

Comment: LDT04 is the effective date of lead time information.

Implementation Notes:1. This segment should be used when the quoted delivery dates will be less than the requireddelivery date specified in the RFQ. In this case, use code "AF" for Quoted Delivery Date.

2. Quoted delivery date will be provided in this segment as a set number of days after receipt oforder or in the DTM segment as an actual date. If the latter is used, omit this segment.

Data Element SummaryR"'. DATADES. ELDIS NAME ATTNUTES

Mandatory LDT01 345 Lead Time Code M ID 2/2Code indicating the time range.

AF From date of PO receipt to delivery.

Mandatory LDT02 380 Quantity M R 1/10

Numeric value of quantity.

Mandatory LDT03 344 Unit of Time Period Code M ID 2/2Code indicating the time period.

DA Calendar Days

Not Used LDT04 373 Date 0 DT 6/6

17 DCO5 JANUARY 29 1993


843. RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOO_ PWK PAPERWORK

Segment: PWK PaperworkLevel: Header


Max Use: 25

Purpose: To specify the type and transmission of paperwork relating to a product,order or report.

Syntax: If either PWK05 or PWK06 is present, then the other is required.Comments: 1. PWK05 and PWK06 may be used to identify the addressee by a code

number.

2. PWK07 may be used to indicate special information to be shown onthe specified report.

3. PWK08 may be used to indicate action pertaining to a report.

Implementation Notes:1. Use this segment to indicate which CERTS and REPS, if any, and other paperwork will betransmitted electronically with this response to an RFQ (e.g., if PWK segment in 840 transactionset imposes such a requirement).

2. When the total amount of the quote exceeds $10,000, this segment is REQUIRED.

:E DATA Data Element Summary

Dies, ELEMENT NAME A'J•IOMTE5

Mandatory PWK01 755 Report Type Code M ID 2/2Code indicating the title and/or contents of a document or report.

Implementation Notes:1. Use FD when report is provided electronically with the response to the RFQ.

2. When the quote (AMT02) exceeds $10,000.00, there must be at least one iteration of the PWK segmentusing code FD.

FD Federal Specification Compliance

Mandatory PWK02 756 Report Transmission Code M ID 2/2Code defining timing and transmission method by which reports are to be sent.

EL Electronically Only

Not U,.d PWK03 757 Report Copies Needed 0 NO 1/2

Optional PWK04 98 Entity Identifier Code 0 ID 2/2Code identifying an organizational entity or a physical location.

Implementation Notes:1. REQUIRED when AMT02 exceeds $10,000.

2. Codes are used to certify if quoter is a manufacturer, distributor, or a regular dealer in accordance withthe terms of the Walsh-Healy Act.

DL DealerDS DistributorMF Manufacturer of Goods

DC05. JANUARY 29 1993 18


843 • RESPONSE TO REQUEST FOR QUOTATION. PWK - PAPERWORK ANSI ASC X12 VERSION/RELEASE 00301 0DOD_

Not Used PWK05 66 Identification Code Qualifier C ID 1/2

Not Used PWK06 67 Identification Code C ID 2/17

Optional PWK07 352 Description 0 AN 1/80A free-form description to clarify the related data elements and their content.

Implementation Note:Use to make additional certifications and/or representations that may have been required by the terms of theRFQ to which this transmission is responding.

Not Used PWK08 704 Paperwork/Report Action Code 0 ID 1/2

19 DCo5 JANUARY 29 1993


843 -RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD PKG. MARKING, PACKAGING, LOADING

Segment: PKG Marking, Packaging, LoadingLevel: Header

Loop: _


Max Use: 25

Purpose: To describe marking, packaging, loading and unloading requirements.

Syntax: 1. If PKG04 is present, then PKG03 is required.

2. At least one of PKG04 or PKG05 must be present.

Comments: 1. Use MEA (Measurements) segment to define dimensions, tolerancesweights, counts, physical restrictions, etc.

2. When PKGO1 is "F, PKG04 is not used.

3. PKGO1 relates only to PKG04 and PKG05.

4. Use PKG03 to indicate the organization that publishes the code listbeing referred to.

5. PKG04 should be used for industry-specific packaging descriptioncodes.

6. Special marking or tagging data can be given in PKG05 (Description).

Implementation Notes:1. A table might be required to convert DoD to ASC X12 packaging codes.

2. Segment is not used when the packaging is as requested, if special packaging requirements wereindicated in the RFQ.

Data Element SummaryREF DATADES. ELEMENT NAME ATMIiUTfES

Mandatory PKG01 349 Item Description Type M ID 1/1Code indicating the format of a description.

F Free-formS Structured (From Industry Code List)

Optional PKG02 753 Packaging Characteristic Code 0 ID 1/5Code specifying the marking, packaging, loading and related characteristicsbeing described.

Implementation Notes:1. Use any code.

2. Use code .5 for Unitizing; code 36for PacklPreservation; and code 37for Packing.

Conditional PKG03 559 Association Qualifier Code C ID 2/2

Code identifying the association assigning the code values.

DD Department of Defense

Conditional PKG04 754 Packaging Description Code C ID 1/7A code from an industry code list which provides specific data about the marking,packaging or loading and unloading of a product.

DC05 . JANUARY 29 1993 20


843 - RESPONSE TO REQUEST FOR QUOTATIONPKG - MARKING, PACKAGING, LOADING ANSI ASC X12 VERSION/RELEASE 003010DODConditional PKG05 352 Description C AN 1/80

A free-form description to clarify the related data elements and their content.

Implementation Note:When PKGO4 carries a code indicating that the item is packed differently than required by the RFQ. explainin PKGO5.

21 DCO. JANUARY 29 1993


843 * RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD_ NI. NAME

Segment: NI Name

Level: Header

Loop: N1 Repeat: 200Optional Usage: Optional

Max Use: 1

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

Syntax: 1. At least one of N102 or N103 must be present.

2. If either N103 or N104 is present, then the other is required.

Comment: This segment, used alone, provides the most efficient method ofproviding organizational identification. To obtain this efficiency the "IDCode" (N104) must provide a key to the table maintained by thetransaction processing party.

Implementation Note:When NlOJ is code SE or ZZ, then NII O, N103, and N104 are required to be used in lieu of usingthe balance of the NI and the N2-N4 segments. When NIO1 is code AG, either the CAGE code orthe long-line address may be used.

Data Element SummaryREF- DATADES. ELVEENT NAME ATrRtIMTME$

Mandatory N101 98 Entity Identifier Code M ID 2/2Code identifying an organizational entity or a physical location.

Implementation Notes:1. Use code ZZ when certifying that you are a small business for the SIC code(s) that is (are) carried inP0108 of the 840 transaction set being responded to.

2. Use code SE in all other cases.

3. In another iteration of the NJ loop, use code AG to indicate that you are bidding on behalf of a companynamed in a previous iteration of the NJ loop.

AG AgentSE Selling PartyZZ Mutually Defined

Conditional N102 93 Name C AN 1/35Free-form name.

Conditional N103 66 Identification Code Qualifier C ID 1/2Code designating the system/method of code structure used for IdentificationCode (67).

Implementation Note:Code 33 is the CAGE Code. Use code ZZ to qualify a temporary CAGE Code assigned during theregistration process when a CAGE Code is not yet assigned.

33 Commercial and Government Entity (CAGE)

ZZ Mutually Defined

Conditional N104 67 Identification Code C ID 2/17Code identifying a party.

DC0. * JANUARY 29 1993 22


843 - RESPONSE TO REQUEST FOR QUOTATIONS N1 NAME ANSI ASC X12 VERSIOWRELEASE 003010DOD_

Implementation Note:

Carries the actual CAqF Code or the temporary CAGE Code assigned at time of registration.

0



843. RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 00301ODOD N2 ADDITIONAL NAME INFORMATION

Segment: N2 Additional Name InformationLevel: Header

Loop: N1Optional Usage: Optional

Max Use: 2

Purpose: To specify additional names or those longer than 35 characters in length


DES. ELEMENT NAME ATTRISLTES

Mandatory N201 93 Name M AN 1/35Free-form name.

Optional N202 93 Name 0 AN 1/35Free-form name.

DCO5 . JANUARY 29 1993 24


843- RESPONSE TO REQUEST FOR QUOTATIONN3 ADDRESS INFORMATION ANSI ASC X12 VERSIONIRELEASE 00301 ODOD.,

Segment: N3 Address Information

Level: Header


Max Use: 2

Purpose: To specify the location of the named party

Data Element SummaryREF. DATADES, ELMENT NUAME ATrrIBUTES

Mandatory N301 166 Address Information M AN 1/35Address information

Optional N302 166 Address Information 0 AN 1/35

Address information

25 oCos, - ANUARY 29 1993


843- RESPONbE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD N4 GEOGRAPHIC LOCATION

Segment: N4 Geographic Location

Level: Header


Max Use: 1

Purpose: To specify the geographic place of the named party

Syntax: 1. At least one of N401 or N405 must be present.

2. If N401 is present, then N402 is required.

3. If either N405 or N406 is present, then the other is required.

Comments: 1. A combination of either N401 through N404 (or N405 and N406) maybe adequate to specify a location.

2. N402 is required only if city name (N401) is in the USA or Canada.

Data Element SummaryREF. DATADES. ELWIMdT NMIE A'rnY'MS

Conditional N401 19 City Name C AN 2/19Free-form text for city name.

Conditional N402 156 State or Province Code C ID 212Code (Standard State/Province) defined by appropriate governmental agencies.

Optional N403 116 Postal Code 0 ID 419Code defining international postal zone code excluding punctuation and blanks(zip code for United States).

Implementation Note:Use only when the "party's" address has no ZIP code but may have another type of postal code (e.g., in aforeign country).

Optional N404 26 Country Code 0 ID 2/2Code identifying the country.

Implementation Note:A translation table will be required to convert those standard coaes used by ANS to those used by the DoD.

Not Used N405 309 Location Qualifier 0 ID 1/2

Not Used N406 310 Location Identifier C AN 1/25

0DC05 - JANUARY 29 1993 26


843- RESPONSE TO REQUEST FOR QUOTATIONPER ADMINISTRATIVE COMMUNICATIONS CONTACT ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: PER Administrative Communications Contact

Level: Header


Max Use: 3Purpose: To identify a person or office to whom administrative communications

should be directed

Syntax: If PER03 is present, then PER04 is required.

Data Element SummaryREF. DATADE. ELEMENT NAME ATTNM*UTES

Mandatory PER01 366 Contact Function Code M ID 2/2Code identifying the major duty or responsibility of the person or group named.

SU Supplier Contact

Optional PER02 93 Name 0 AN 1/35Free-form name.

Optional PER03 365 Communication Number Qualifier 0 ID 2/2Code identifying the type of communication number.

Implementation Note:Communication from the buying activity will be by electronic mail to the electronic mail address from whichthe quote was received. Quoters at their option may provide additional communication numbers at whichtheir contact can be reached.

EM Electronic MailFX FacsimileTE Telephone

Conditional PER04 364 Communication Number C AN 7/21Complete communications number including country or area code whenapplicable.

Implementation Note:If the communications number is greater than 21 characters, repeat the PER segment to provide theremaining characters.

27 DCo5 . JANUARY 29 1993


843 - RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD PO1 - PURCHASE ORDER BASEUNE ITEM DATA

Segment: P01 Purchase Order Baseline Item DataLevel: Detail

Loop: P01 Repeat: 100000


Max Use: 1Purpose: To specify basic and most frequently used purchase order line item data

Syntax: 1. If P01 05 is present, then PO1 04 is required.

2. If PO106 is present, then P01 07 is required.

3. If P0108 is present, then P0109 is required.

4. If PO110 is present, then PO111 is required.

5. If P0112 is present, then PO113 is required.






11. If P0124 is present, then P01 25 is required.

Comments: 1. See the Data Dictionary for a complete list of ID's.

2. PO10 1 is the line item identification

3. P0106 through P0125 provide for ten (10) different product/serviceID's per each item. For example: Case, Color, Drawing No., UPC No.,ISBN No., Model No., SKU.

Data Element SummaryREF. DATADES. ELEMENT NAME ATTWIUIIUES

Required P0101 350 Assigned Identification 0 AN 116Alphanumeric characters assigned for differentiation within a transaction set.

Implementation Note:POlO1 must contain the line item number assigned by the buying activity in the RFQ being quoted in thistransaction. When quoting on multiple line items, use as many iterations of the P01 segment as necessary.

Mandatory P0102 330 Quantity Ordered M R 1/9Quantity ordered.

Implementation Note:The quantity being quoted for the line item.

Mandatory P0103 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit of measurement.

Implementation Note:DoD uses DoD Manual 5000.12-M for unit of issue codes. These differ from the X12 DE 355 code list andmust be translatedfrom one to the other.

DC05 - JANUARY 29 1993 28


843 RESPONSE TO REQUEST FOR QUOTATIONP01 * PURCHASE ORDER BASELINE ITEM DATA ANSI ASC X12 VERSION/RELEASE 003010DOD

Conditional P0104 212 Unit Price C R 1/14Price per unit of product, service, commodity, etc.

Implementation Note:For the line item being quoted. The total amount of the line item (quantity x unit price) will be calculated bythe application program.

Not Used P0105 639 Basis of Unit Price Code 0 ID 212

Optional P0106 235 Product/Service ID Qualifier 0 ID 212Code identifying the type/source of the descriptive number used inProduct/Service ID (234).

Implementation Notes:I. Use any code.

2. P0106 through P0125 (Product or Service ID Qualifier and Product or Service ID pairs) will be used, asrequired, to carry additional information regarding the product or service being quoted on in the particulariteration of the P01 loop.

Conditional P0107 234 Product/Service ID C AN 1/30Identifying number for a product or service.


Conditional P0109 234 Product/Service ID C AN 1/30Identifying number for a product or service.. Optional P0110 235 Product/Service ID Qualifier 0 ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service iD (234).

Conditional P0111 234 Product/Service ID C AN 1130Identifying number for a product or service.

Optional P0112 235 Product/Service ID Qualifier 0 ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234).




Optional P0116 235 Product/Service ID Qualifier 0 ID 212Code identifying the type/source of the descriptive number used inProduct/Service I D (234).

Conditional P0117 234 Product/Service ID C AN 1/30Identifying number for a product or service.. Optional P0118 235 Product/Service ID Qualifier 0 ID 2/2

29 C05 o JANUARY 29 1993


843 • RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD PO1 • PURCHASE ORDER BASELINE ITEM DATA

Code identifying the type/source of the descriptive number used inProduct/Service ID (234).








DC05- JANUARY 29 1993 30


843- RESPONSE TO REQUEST FOR QUOTATIONP03- ADDmONAL ITEM DETAIL ANSI ASC X12 VERSION/RELEASE 003010DOD

Segment: P03 Additional Item DetailLevel: Detail

Loop: P01


Max Use: 25

Purpose: To specify additional item related data involving variations in normalprice/quantity structure.

Syntax: If P0304 is present, then at least one of P0303 or P0305 must bepresent.

Comments: 1. Some examples of price/quantity variations are: price in different unitsfrom the P01 segment, price changes by date, or price changes byquantity (break and level).

2. P0307 defines the unit of measure for P0306.

Data Element SummaryREF. DATADIS EUitseT NAIE ATPRMUVM"S

Mandatory P0301 371 Change Reason Code M ID 2/2Code specifying the reason for price or quantity change.

AQ Alternate Quantity and Unit of Measure

PC Pack DifferenceOT Quantity Price BreakUM Unit of Measure Difference

Optional P0302 373 Date 0 DT 6/6Date (YYMMDD).

Optional P0303 236 Price Qualifier 0 ID 3/3Code identifying pricing specification.

PB0 Unit Price Beginning Quantity

Conditional P0304 212 Unit Price C R 1/14Price per unit of product, service, commodity, etc.

Optional P0305 639 Basis of Unit Price Code 0 ID 2/2Code identifying the type of unit price for an item.

Mandatory P0306 380 Quantity M R 1/10Numeric value of quantity.

Mandatory P0307 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit of measurement.

Implementation Note:See note for P0)03.

Optional P0308 352 Description 0 AN 1180A free-form description to clarify the related data elements and their content.



843 RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD PID- PRODUCT/ITEM DESCPiPTION

Segment: PID Product/Item DescriptionLevel: Detail

Loop: PID Repeat: 1000Optional Usage: Optional

Max Use: I

Purpose: To describe a product or process in coded or free-form format

Syntax: 1. If PID04 is present, then PID03 is required.

2. At least one of PID04 or PID05 must be present.

Comments: 1. When PID01 is "F", PID04 is not used.

2. Use PID03 to indicate the organization that publishes the code listbeing referred to.

3. PID04 should be used for industry-specific product description codes.

4. Use PID06 when necessary to refer to the product surface or layerbeing described in the segment.

Data Element SummaryREF. DATAWES. E HlMET E ATTMiBUTES

Mandatory PID01 349 Item Description Type M ID 1/1Code indicating the format of a description.

F Free-form

Not Used PID02 750 Product/Process Characteristic Code 0 ID 2/3

Not Used PID03 559 Association Qualifier Code C ID 2/2

Not Used PID04 751 Product Description Code C ID 1/12

Conditional PID05 352 Description C AN 1/80A free-form description to clarify the related data elements and their content.

Implementation Notes:1. Whep, - P01 qUalitfier used code SV, PlD'V can carry an additionalfree-form dAcription of thecontracted services, if necessary. It may also be used for an explanation of a contract condition, in lieu ofusing the 1NTE segment.

2. SF 18 Block 12b

Not Used PID06 752 Surface/Layer/Position Code 0 ID 2/2

DC0S - JANUARY 29 1993 32


843 RESPONSE TO REQUEST FOR QUOTATION. MEA . MEASUREMENTS ANSI ASC X12 VERSIONIRELEASE 003010DOD_

Segment: MEA MeasurementsLevel: Detail

Loop: PID


Max Use: 10

Purpose: To specify physical measurements, including dimensions, tolerances,weights and counts.

Syntax: 1. Either MEA03 or MEA05 or MEA06 or MEA08 is required.

2. If either MEA03, MEA05 or MEA06 is used, MEA04 is required.

3. If MEA07 is used MEA03 is required.

4. Either MEA08 or MEA03 may be used, but not both.

Comment: When citing dimensional tolerances, any measurement requiring a sign(+ or -), or any measurement where a positive (+) value cannot beassumed use MEA05 as the negative (-) value and MEA06 as thepositive (+) value.

Implementation Note:This segment can be used any time a measurement needs to be described for an item being quoted.

Data Element SummaryREF. DATAD__. ELMENT NE A__IWJUTES

Optional MEA01 737 Measurement Reference ID Code 0 ID 2t2Code specifying the application of physical measurement cited.


Optional MEA02 738 Measurement Qualifier 0 ID 1/3Code identifying the type of measurement.


Conditional MEA03 739 Measurement Value C R 1/10The value of the measurement.

Conditional MEA04 355 Unit of Measurement Code C ID 212Code identifying the basic unit of measurement.


Not Used MEA05 740 Range Minimum C R 1/10

Not Used MEA06 741 Range Maximum C R 1/10

Not Used MEA07 935 Measurement Significance Code 0 ID 2/2

Not Used MEA08 936 Measurement Attribute Code C ID 2/2. Not Used MEA09 752 Surface/Layer/Position Code 0 ID 2/2

33 OCos. JANUARY 29 1993


843- RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD PKG. MARKING, PACKAGING, LOADING

Segment: PKG Marking, Packaging, Loading

Level: Detail

Loop: P01


Max Use: 25

Purpose: To describe marking, packaging, loading and unloading requirements.

Syntax: 1. If PKG04 is present, then PKG03 is required.

2. At least one of PKG04 or PKG05 must be present.

Comments: 1. Use MEA (Measurements) segment to define dimensions, tolerancesweights, counts, physical restrictions, etc.

2. When PKGO1 is "F", PKG04 is not used.

3. PKG01 relates only to PKG04 and PKGO5.

4. Use PKG03 to indicate the organization that publishes the code listbeing referred to.

5. PKG04 should be used for industry-specific packaging descriptioncodes.

6. Special marking or tagging data can be given in PKG05 (Description).

Implementation Notes:1. A table might be required to convert DoD to ASC X12 packaging codes.

2. Segment is not used when the packaging is as requested, if special packaging requirements wereindicated in the RFQ.


REF, DATADES. ELAEMET NAME ATTRIMUTES

Mandatory PKGO1 349 Item Description Type M ID 1/1Code indicating the format of a description.

F Free-formS Structured (From Industry Code List)

Optional PKG02 753 Packaging Characteristic Code 0 ID 115Code specifying the marking, packaging, loading and related characteristicsbeing described.

Implementation Notes:1. Use any code.

2. Use code 35 for Unitizing; code 36for Pack/Preservation; and code 37/or Packing.

35 Type of Package

Conditional PKGO3 559 Association Qualifier Code C ID 212

Code identifying the association assigning the code values.

OD Department of Defense

Conditional PKG04 754 Packaging Description Code C ID 1/7

DC05- JANUARY 29 1993 34


843 • RESPONSE TO REQUEST FOR QUOTATION. PKG - MARKING, PACKAGING, LOADING ANSI ASC X12 VERSION/RELEASE 003010DOD_

A code from an industry code list which provides specific data about the marking,packaging or loading and unloading of a product.

Conditional PKG05 352 Description C AN 1180A free-form description to clarify the related data elements and their content.

Implementation Note:When PKGO4 carries a code indicating that the item is packed differently than reQ: 'red by the RFQ, explainin PKGO5.

35 DC05- JANUARY 29 1993


843 RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD P04 - ITEM PHYSICAL DETAILS

Segment: P04 Item Physical DetailsLevel: Detail

Loop: P01Optional Usage: Optional

Max Use: 1

Purpose: To specify the physical qualities, packaging, weights and dimensionsrelating to the item.

Syntax: 1. If P0402 is present, then P0403 is required.

2. If P0405 is present, then at least one of P0406 or P0407 is required.


4. If P0413 is present, then at least one of P0410, P0411 or P0412 isrequired.

Comments: 1. P0403 - The "Unit of Measure Code" (Element #355) in this segmentposition is for purposes of defining the pack (P0401)/size (P0402)measure which indicates the quantity in the inner pack unit. Example: Ifthe carton contains 24 12-Ounce packages, it would be described asfollows: Element 356 = 24; Element 357 = 12; Element 355 = OZ.

2. P0410 defines the unit of measure for P0408, P0409, and P0410.

Data Element SummaryREF. DATADES. ELEMENT NAME ATTRIUTES

Optional P0401 356 Pack 0 NO 1/6Number of inner pack units per outer pack unit.

Implementation Note:SF 18 Block 12b.

Optional P0402 357 Size 0 R 1/8Size of supplier units in pack.

Conditional P0403 355 Unit of Measurement Code C ID 2/2Code identifying the basic unit of measurement.

Optional P0404 103 Packaging Code 0 ID 5/5Code identfying the type of packaging. Part 1. Packaging form. Part 2.Packaging Material.

Implementation Note:These codes are X12 codes. A translation table will be required to convert them to DoD codes, to the extentthat the DoD codes differ from the X12 codes.

Optional P0405 187 Weight Qualifier 0 ID 1/2Code defining the type of weight.

Conditional P0406 384 Gross Weight per Pack C R 1/9Numeric value of gross weight per pack.

Conditional P0407 355 Unit of Measurement Code C ID 2/2

DC05- JANUARY 29 1993 36

DEPARTMENT OF DEFENSEDRAFT IMPLEMFNTATION CONVENTION

843 - RESPONSE TO REQUEST FOR QUOTATIONP04 - ITEM PHYSICAL DETAILS ANSI ASC X12 VERSION/RELEASL J03010DOD_

Code identifying the basic unit of measurement.

Optional P0408 385 Gross Volume per Pack 0 R 1/9Numeric value of gross volume per pack.

Conditional P0409 355 Unit of Measurement Code C ID 2/2Code identifying the basic unit of measurement.

Optional P0410 82 Length 0 R 1/8Largest horizontal dimension of an object measured when the object is in theupright position.

Optional P0411 189 Width 0 R 1/8Shorter measurement of the two horizontal dimensions measured with the objectin the upright position.

Optional P0412 65 Height 0 R 1/8Vertical dimension of an object measured when the object is in the uprightposition.

Conditional P0413 355 Unit of Measurement Code C ID 2/2Code identifying the basic unit of messuremant.

37 C05 . JANUARY 29 1993


843. FRESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 00301 0DOD_ REF- REFERENCE NUMBERS

Segment: REF Reference Numbers

Level: Detail

Loop: P01Optional Usa -, Optional

Max Use: 12

Purpose: To specify identifying numbers.

Syntax: Either REF02 or REF03 is required.

Data Element SummaryREFP DATADES. ELEMENT NMI ATTRIIUTES

Mandatory REF01 128 Reference Number Qualifier M ID 212Code qualifying the Reference Number.

Implementation Notes:1. When REFO1 is code CR, REF02 will carry :he number of the Federal Supp!y Schedule in which thequoted item can be found.

2. When REFO1 is code CT, it will represent a contract other than a supply schedule, known to the quoter,from which the quoted item can be ordered. Give the contract number in REF02 and explain the nature of thecontract in REF03, if necessary.

CR Customer Reference Number

CT Contract Number

Conditional REF02 127 Reference Number C AN 1130Reference number or identification number as defined for a particularTransaction Set, or as specified by the Reference Number Qualifier.

Conditi-nal REF03 352 Description C AN 1/80A free-form description to clarify the related data elements and their content.

DCOS - JANUARY 29 1993 38


843, RESPONSE TO REQUEST FOR QUOTATIONFOB , F.O.B. RELATED INSTRUCTIONS ANSI ASC X12 VERSION/RELEASE 00301ODOD_

Segment: FOB F.O.B. Related Instructions

Level: Detail

Loop: PO1


Max Use: 1

Purpose: To specify transportation instructions relating to shipment

Syntax: 1. If FOB03 is present, then FOB02 is required.

2. If FOB04 is present, then FOB05 is required.



Comments: 1. FOB01 indicates which party will pay the carrier.

2. FOB02 is the code specifying transpoi tation responsibility location.

3. FOB06 is the code specifying title passage location.

4. FOB08 is the code specifying the point at which the risk of losstransfers. This may be different than the location specified inFOB02/FOB03 and FOB06/FOB07.

Implementation Note:Use only when quoting other than FOB destination, at the line item level.

0 Data Element Summary

AEFP DATADMe. ELEMEWT NAME ATTtRIBUTES

Mandatory FOB01 146 Shipment Method of Payment M ID 2/2Code identifying payment terms for transportation charges.

DF Defined by Buyer and Seller

Conditional FOB02 309 Location Qualifier C ID 1/2Code identifying type of location.

Implementation Notes:1. Use code ZZ when the FOB point is other than origin or destination, (e.g., an intermediate point).

2. FOB destination is assumed unless specified otherwise

OR Origin (Shipping Point)ZZ Mutually Defined

Optional FOB03 352 Description 0 AN 1/80A free-form description to clarify the related data elements and their content.

Implementation Note:When FOB02 is code ZZ, use FOB03 to describe the other location.

Not Used FOB04 334 Transportation Terms Qualifier Coda 0 ID 212

Not Used FOB05 335 Transportation Terms Code C ID 3/3

Not Used FOB06 309 Location Qualifier C ID 1/2. Not Used FOB07 352 Description 0 AN 1/80

39 Dcos, JANUARY 29 1993


843 - RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSIONIRELEASE 003010ODOD FOB - F.O.B. RELATED INSTRUCTIONS

Not Used FOB08 54 Risk of Loss Qualifier 0 ID 2/2

Not Used FOB09 352 Description C AN 1180

DC05 - JANUARY 29 1993 40


843- RESPONSE TO REQUEST FOR QUOTATIONDTM o DATE/TIME REFERENCE ANSI ASC X12 VERSION/RELEASE 003010DOD

Segment: DTM Date/Time ReferenceLevel: Detail


Max Use: 10

Purpose: To specify pertinent dates and times

Syntax: At least one of DTM02 or DTM03 must be present.

Implementation Note:Quoted delivery date will be provided in this segment as an actual date or in the LDT segment as aset number of calendar days after receipt of order. If the latter is used, omit this segment.

Data Element Summary"REF. DATA

DES. ELEABdr NAME ATTIrJUTES

Mandatory DTM01 374 Date/Time Qualifier M ID 3/3Code specifying type of date or time, or both date and time.

Implementation Notes:1. Use code 036 to indicate the expiration date of a Federal Supply Schedule or contract.

2. Code 075, the delivery dale being quoted, should be used only when the quoted delivery date will be lessthan the required delivery date specified in the RFQ, applies to the entire line and the delivery date is notdefined in segment LDT. Use the SCH segment if deliveries for a line item will differ by quantity or date.

036 Expiration

075 Promised for Delivery (Prior to and Including)

Conditional DTM02 373 Date C DT 6/6Date (YYMMDD).

Not Used DTM03 337 Time C TM 4/4

Not Used DTM04 623 Time Code 0 ID 2/2

41 DCOS. JANUARY 29 1993


843. RESPONSE TO REQUEAT FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD LWT- LEAD TIME

Segment: LDT Lead TimeLevel: Detail

Loop: PO1


Max Use: 12

Purpose: To specify lead time for availability of products and services.

Comment: LDT04 is the effective date of lead time information.

Implementation Notes:I. This segment should be used when the quoted delivery dates will be less than the requireddelivery date specified in the RFQ. In this case, use code "AF"for Quoted Delivery Date.

2. Quoted delivery date will be provided in this segment as a set number of days after receipt oforder or in the DTM segment as an actual date. If the latter is used, omit this segment.

Data Element Summary"NEF. DATADES. ELIDaIT NAME A1"MISRJTES

Mandatory LDT01 345 Lead Time Code M ID 212Code indicating the time range.

AF From date of PO receipt to delivery.

Mandatory LDT02 380 Quantity M R 1/10Numeric value of quantity.

Mandatory LDT03 344 Unit of Time Period Code M ID 2/2Code indicating the time period.

DA Calendar Days

Not Used LDT04 373 Date 0 DT 6/6

DC05 - JANUARY 29 1993 42


843 - RESPONSE TO REQUEST FOR QUOTATION* SCH o UNE ITEM SCHEDULE ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: SCH Line Item ScheduleLevel: Detail


Max Use: 104

Purpose: To specify the data for scheduling a specific line item.

Syntax: 1. If SCH03 is present, then SCH04 is required.

2. If SCH09 is used, then SCH08 is required.

Comment: SCH05 specifies the interpretation to be used for SCH06 and SCH07.

Implementation Note:Use only to describe a lesser partial delivery at the line item level.

Data Element Summary"REF. DATA-. S. ELEMiWdA NAME ATTRIBUTES

Mandatory SCH01 380 Quantity M R 1/10Numeric value of quantity.

Mandatory SCH02 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit of measurement.. Not Used SCH03 98 Entity Identifier Code 0 ID 2/2

Not Used SCH04 93 Name C AN 1/35

Mandatory SCH05 374 Date/Time Qualifier M ID 3/3Code specifying type of date or time, or both date and time.

Implementation Note:The promised delivery dale.

Mandatory SCH06 373 Date M DT 6/6Date (YYMMDD).

Not Used SCH07 337 Time 0 TM 4/4

Not Used SCHL 3 374 Date/Time Qualifier 0 ID 3/3

Not Used SCH09 373 Date C DT 6/6

Not Used SCH10 337 Time 0 TM 414

43 DCo5. JANUARY 29 1993


843. RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD C"T1- TRANSACTION TOTALS

Segment: CTT Transaction TotalsLevel: Summary


Max Use: 1Purpose: To transmit a hash total for a specific element in the transaction set

Syntax: 1. If CTT03 is present, then CTT04 is required.

2. If CTT05 is present, then CTT06 is required.

Comment: This segment is intended to provide hash totals to validate transactioncompleteness and correctness.


REP. DATADES. ELEMENT NAME ATMIBUTES

Mandatory CTT01 354 Number of Line Items M NO 1/6Total number of line items in the transaction set.

Implementation Note:Total number of P01 segments.

Optional CTTO2 347 Hash Total 0 R 1/10Sum of values of the specified data element. All values in the data element willbe summed without regard to decimal points (explicit or implicit) or signs.Truncation will occur on the leftmost digits if the sum is greater than themaximum size of the hash total of the data element.

Example:

-.0018 First occurrence of value being hashed..18 Second occurrence of value being hashed.1.8 Third occurrence of value being hashed.

18.01 Fourth occurrence of value being hashed.1855 Hash total prior to truncation.

855 Hash total after truncation to three-digit field.

Implementation Note:C7TO2 is the sum of the value of the quantities quoted (P0102) for the total number of PO I segments.

Not Used CTT03 81 Weight 0 R 1/8

Not Used CTT04 355 Unit of Measurement Code C ID 2/2

Not Used CTTO5 183 Volume 0 R 1/8

Not Used CTT06 355 Unit of Measurement Code C ID 2/2

Not Used CTT07 352 Description 0 AN 1/80

DC05 -JANUARY29 1993 44


843 RESPONSE TO REQUEST FOR QUOTATION* AMT- MONETARY AMOUNT ANSI ASC X12 VERSION/RELEASE 00301 0DOD_

Segment: AMT Monetary AmountLevel: Summary


Max Use: 1

Purpose: To indicate the total monetary amount.

Comments: 1. If AMT is used in the detail area of transaction set 850, 855, 860 or865, AMT02 will indicate total line amount as calculated by the sender. IfAMT is used in the summary area of transaction set 850, 855, 860 or865, AMT02 will indicate total transaction amount as calculated by thesender.

2. If segment AMT is used in Table 2 of the 850, 855, 860 or 865transaction sets, then AMT01 = 01. If it is used in Table 3 of thosetransaction sets, then AMT01 TT.

Data Element SummaryREF DATADES. ELEMENT NAME Al I ,B'TE5

Mandatory AMT01 522 Amount Qualifier Code M ID 1/2Code to qualify amount

Implementation Notes:1. Code TT will represent the Iota! amount quoted.

2. When code TT is used, it is that amount upon which the manufacturer/regular dealer certification is made,if over $10,000.00. See the PWK segment in Table 1 of this transaction set.

TT Total Transaction Amount

Mandatory AMT02 782 Monetary Amount M R 1115Monetary amount.

45 DCo5 JANUARY 29 1993


43 - RESPON:E TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 00301ODOD SE TRANSACTION SET TRAILER

Segment: SE Transaction Set TrailerLevel: Summary


Max Use: 1

Purpose: To indicate the end of the transaction set and provide the count of thetransmitted segments (including the beginning (ST) and ending (SE)segments).

Comment: SE is the last segment of each transaction set.


DES. ELEMWT NAME A"TRIDUTES

Mandatory SE01 96 Number of Included Segments M NO 1/6Total number of segments included in a transaction set including ST and SEsegments.

Mandatory SE02 329 Transaction Set Control Number M AN 4/9Identifying control number assigned by the originator for a transaction set.

Implementation Note:This is the same number as appears in ST02.

0

0DC05.- JANUARY 29 1993 46


843 RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE 003010DOD

3.4 DoD CONVENTION

BASELINE AS OF: JANUARY 29, 1993 3.0.19


843 . RESPONSE TO REQUEST FOR QUOTATIONANSI ASC X12 VERSION/RELEASE O03010DOD_




* 4.0 ASC X 12 FORMS

In this chapter, applicable ASC X12 forms are presented.

RASEUNE AS OF: JANUARY 29, 1993 4.0.1


...KIS I IORMTON MANUAL

ASC X1 2 Work Reqiest Form

ASC X12 New Pirod PposaJ Form

ASC X12 New Transaction Set Development Form

Form for New or Revied Apandix A Code Source Reerence

Documern Preparu•ion for Ihpretagons GuikeWns and Control Standards

San'fg Transmia Form

ASC X12 Balo( CaWrnert Response Letter Formg

ASC X12 Standards Orde Form

FALL M VIII- I


I~DEPARM•T OF

PSAT NPL111111AIM CIOWAN'W

Re. 5/1019C DM NUMBER

OATE SUBMnTED ASC X12 (Secusadt Only)

WORK REQUEST FORM

ALL REQUE.ATS MUST BE TYPED or printed legibly In black ink. Complete both sides,

1. TO USE TKIS FORM FOR SUPPORTING DATA MAINTENANCE FOR A NEW DRAFT STANDARD OR X12 WITEFPqErATKION go am

mquo9wmeon wa ONE Wom-. L4O a nments as nemesay. Ii Wnt M new wgmuM. Voin AN now 4aM ememei/odoe/cade *our-.

Then No teviWi 3 Diing wmel and lao eem QnS S/A A aMoue . The lnt a ny ageo (e.g., X12.5. X12.6).

2. TO USE THIS FORM TO :'jOUEST A CHANGE TO AN V5ST01NG STANOAR•. use a amparafa work bquW For m la aS WwVe lt

onenaw •- t. one egneeetwee am e= l strucu, at we deoamoent. A# secaim must be Ocmelvd. Atacft ret may be uaedfor sanbiuabion w4 •a•)Wd be numbered.

3. TO USE THIS FORM TO REQUEST A PROPOSED NEW X12 PROJECT. compiet Secand A Pr•vide a pupoee/•ave &a desribe any

new labse ed n Seo Povidea dew09 On. lbasi-,G.d and ia4 n to Wenew praeothinSemC/Patt TheWk equet waI be foad toaw appempnia X12 aubcoe'm,•ifte ter aaym&w a prpiaMon of a P pro poed.

Circle One; (1) Now Standam Svioor•ng Data Maintenance (uis anachrets)(2) Exist Standard Maintenance Requs (see S*.-*m 0)(3) Requei for New X12 Prole¢

n i a ed ed e e mu Mumbe aiewlyesPo0ialned. Pt1l•de AppendlWA A•0aerefer etonces Ior @N exlemaly pubblasid ende km cited. Ihwamplw tune. or lAmn wOl hudequale 9uppa ter Via chang requieesd

wul be rob~me 310w submiewte.

A. SUBMIT1TR INFORMATION

Submitter Name

C npany .. . ....... _i

Address __ _ _ __ _ _

Address/W _________________________

Phone

Indicate the X1 2 subcommittee or tak group whoses position is represented here.I declare that this represents the offiial posiio Of X12 WORK GROUP:established at the meeting dated

B. PROPOSED WORK. List the specific chrnges to the standards being requested. Give the names andassociated iutIfleras; of the standards. sogrmeris daft eleewn and codes affe•-•d.


DEPARTMET OF DOWISiUDRAFT NPLEMENTAT106 CCSOY TION

Page Two

C. REASON FOR CHANGE:Pail I: LUt the vetson/reas of the standard you wre usig or using as a reference. Name the trnsaction setthat Is being/will be used that dictat the reOquested changed. LW affected segments and data elements. orother stanarfd. Provide only reference numbers/IDs.

Reference Source Version 2/ReieamTransaction Set UsedSegment AffectdData Element Affected_Otle Standard

Part 11: Explain why you .-AM the proposed change. Provide a complete scenario tt tells what the businessfunction. operation or problem is that will be satisfied by a change to the Standard. The X12J TechnicalAssessment Subcommittee requires enough Information in this Pant II to be abe to propose an alternate solutbon Inecessary.

0. RAMIFICATIONS: if you chirced (2) on Page 1. cwrrplete thi section. To ensuire t at l ramifications of yourpropose change arm recorded and DOa your reQuet Is complete. c~role below all sections of the starcards

affeced by the proposed change.

TRANSACTION SET Nmtw A /Ses Tame. Nm/Cwmw'Sopmr Peos s200. Oft M& UrnDes Se taeS0. dSge

SEGMENT kmnwS NOm OffiumnAM o DE D m We n1SWIM

Pa" -DO $ANNW semfWft Hm~cammfem

DATA ELEMENT Nom 0"jp6" Type

CODE Add so& Doi,"~ cows pwvi cow.

OTHER (e.g.. X12.5, X12.6):

ERRORS NOTED IN ThE STANDARD (Gve p n and 1he ):

ilAEgLjE As OF: JANUARY 23, 1PM 4.o.S

DEPARTMENT OF 1DRAFT IPLEMENTATION CONVENTION

PP No. ro. /

(Secretarlat Only)

ASC X12

NEW PROJECT PROPOSAL FORM

PROCEDURE: Only X12 subcommittees may use this form to register new development activities as X12 projectproposals (PPs). Complete all pages. PPs approved by the X12 Procedures Review Board will be registered andassigned a PP number by DOIS and a Transmittal Form wIil be Issued.

Date and complete the form below. Type or print legibly ;n black ink and number all attachment pagesconsecutively. Subrnit to DISA prior to an ASC X12 meeting, or to XI2J Technical Assessment Subcommitteeduring the subcommittees agenda period at an ASC X1 2 meeting.

Date Submitted:Date Approved by Subcommittee:

Subcommittee Name:Taok Group Name/No'.:

Joint Development Subcommittee (if any):

Circle one: (a) Transaction Set (b) Guidine (c) Other

Project Working Title:

Official Delegate(s) for This Project To Be Named on Transmittal Form:

Name Name

Company Company .....

Address Address

Address/ZIP Address/ZIP

Telephone Teleph__

4.0.6 BASELhuE AS OF: JANUARY 29,1993

OEPAETWO OF DEB4SEDRAFT &ULEMENfTAWlN CONVMJ4T1O

A. PURPOSE AND SCOPE FOR THE PROPOSED WORK. Provid a wsll-d'nsd pejrpose/scop for theWPftpWe work. Se~e X12 Design Rules vid GuideIles for ruqlrmerwf

S. BACKGROU-ND: Provie details 00a wi be helpful In mevewigV Me proposel. Who ares the expected useirs?How wil tMe standarid be used? What buksinss kuiftn(a) doese k serve?. If fte proqposed4 eadard avs'l"v owfunctiomirny of an existin standard or oae in du'idoprwes provde juMlIoon 10 Me prpml Is no for a nowstAndard or giidelkie. describe Vw project in detal. Nese manchcnerus I necessaery.)

C. O -HER STMANDARDS INVOWVED It i.ppica-le eW~y my Wwe buml;nm Rbioint slandards tin aresimlar/related to fte pruposaW, and ruins sandards develper (e6g., ANSI Accredited SWwtanad Committees)whose activites nay be kwohfed or affected.

0. EXECTED CONTENT/GENERAL DESCRIPTMO: (OPTIONAL) Submitte rmy anach a prsll~nvwy draft dfte Proposed standiard or cowr svpporting m dowisaton Dlecuesrnewaspeu~ .data lermes coawrstructures, and ctungu to X12-5 or X12-6 OW wre reqire or artlclted. (Use lctmnerwi.)

DAMILDE Ail OF- JANUARY 20, 1M 4.0.7

DEPARTMENT OF DEMU4EDRAFT NPLEt WATION CONVENTION

FORM FOR NEW OR REVISED 41

APPENDIX A CODE SOURCE REFERENCE

INSTRUCTIONS: Complete this form whenever a new data element or data element code is requested to be

added which references a code list published by an external (non-XI 2) organization. Use one form for each new

reference. This form may be used to revise current references; fill out the appropriate areas below.

CIRCLE ONE, COMPLETE AS APPROPRIATE:

(1) NEW REFERENCE(2) REVISED REFERENCE, Current reference number/name

REFERENCE TITLE: If there is orgy one source for codes for the data element, the title should be the same as the

data element name. If there are multiple codes referencing external code sources for the same data element. tideshould approxjmate the code definition.

REFERENCE TITLE:

DATA ELEMENTS USED IN: Give the data element reference number and name which directs the user to thisAppendbc A code source reference. Give the code ID (W assigned) I this Is for a specific code of the data element

USED IN: DE No. , Code ID-

SOURCE: Provide the name of the publication which contains the codes referenced.

PUBUSHED IN:

AVAILABLE FROM: Give the publisher, or other contact. from whom the user can obtain the document

Name/Attn of .......

Company

Address

Address

Address/ZIP

ABSTRACT: Briefly describe the publication, Its purpose, and indicate what codes It contains.

ABSTRACT:

4.0.A BASELNE AS OF: JANUARY 29, IMS


DOCUMENT PREPARATION FOR fv / 1

INTERPRETATIONS, GUIDELINES AND CONTROL STANDARDS

Thes instructions are provided to assis developers of interpretations, guidelines arid control structure Which arenot transaction sets (for transaction sets use the New Transaction Set Developrmen Form).

GENERAL- DISA provides tie page and front matter for publications and copyedits the documnent according toDISA house "t4.

REVISIONS, If the documnent is a revision ofa previously published Interpretation. guideline or stanidard. provide asummaory of the changes to the oadginolatets contained In the documnent

I INTERPRETATIONSA formal interpretation of an X12TM Standard Is considered part of the body of standards when it Is approved forpublicaton The Interpretation draft should Vetat the Issue presented by the requesto. state the proposedinterpretation and show as attachments any Work Requests tha may be necessary to @efmc the interpretationwithin the subject standard. The draft interpretation Is processed like any other subconAmmte document.

It GUIDELINESFor publication purposes, guidelines are Veated Ilk* a Journal article. Basic requirements are given below.

ABSTRACT: This is a precise summrary of the Pupose/Scope (see below), and may be iderttcal to It N tha is brief(Iwo paragraphs); otherwise summrafte the purpose/scope. It should contain enough inlormatlan abosA the. document to enable a reader deteirmine what the guidelineo is intended to accomnplsh within an EDO erNironnmet

PURPOSE AND SCOPE: This statemnent nmus Indicate purpose of the guildeline. e.g0. the busines funictiont oroperation addressed. Scope and any specifi lrimkations of scope should be def-ined.

BODY OF TEXT: This rney be a number of subsections logically organized. Provide aectioins for forewordintroduction, definition of termu and concepfts references anti related standards, methdolgogy. specdfications,requiremens discussion and conclusions, as appropriate to the subject

ART AND GRAPHICS: Graphics or artwork necessary to Eustrate the documnent are encouraged. Providecamera-reedy copy N these are not already prepared and delivered on a WP diskette to DISK.

FOREWORD, FOOTNOTES. APPENDICES: These may be used for purpoees of clarity. Eustration, or generalinorniallon not as opert of the guideline. A tatement Indicating the material Is for informationt purposes only andnot penat oteguidelineshappearat the beginin ole foreword or appendis.

NI CONTROL STRUCTURES AND OTHER STANDARDSFor publication purposes. these documents aretreated lI*e guidelines (see Section 11 above). The requiremnents arethe samne. with the addition of the folowkng

NEW SEGMENTS AND DATA ELEMENTS: These may be defined within the tnd; however, since they representchaniges to X12.22 and X12.3, they should be specified on a Work Request Form attached to the draft;

RELATED Xa2W STANDARDS AND OTHER REFERENCES: These sha be Identified in a section wkth* the text.


DEPARTMENT OF ODEFESEDRAFT NPLEMENTATION CONVENTION

Fag0 TWO

FORMAT: 4Thi "t Staidua for TrW U4e eamabut fti f10W ard e~taihe fte das wuu'a d the_______Trangeactin So (__ for use wkW* the cafte of an 6E~ircm Data Irartungs (E01)

mi~cwnovemt The ifarseadon W~ (cMn be used to..

C. PURPOSE AND SCOPE This amamen mug indicae die kii "g of capabliie of tie asnsWOW WC~ &Mwho the eegnrewaluer ame Expiai fti biisiii hiCUoII or opedion OW b add f---ed. FcIoIv ASC X1 2

seipi Raise a&W Guidaibw Mid urn M format

FORMAT: wTft suwdard pr&Aide fte bn W ai eewwiam Owe do& cmrier d ft Te_______Set whti fte cortext ofa EWi B mrnl Oils lrerctsng (M0) erwirwmemU ThiUs ftncdom w(can be used to...

9. ThANSACIION SET TABU3(% For each %We provitde tfe WofblM kVornWeftv FORMAT:

TAILSX

POSITION SEGMNUT REQ. MAX. LOOP REPEAT NOTE!No, lip TITLr DIR USE, COUNT? !?010 ST Transaction Set Header N 1 Note 1020 B3 Beginning Segment For K 1 Comment Ietc.

Note 1: This Ba nwAt NOTES we punofgo- w (reaftered).Conmmt A. This i a awmwe COMMENTS we not pe of Me M-rids (Islad).

K APPENDIX EXMPLES &wiipWs No used tote 1"e VS "We of 10;noMed wDamean mid to 604M a touwen At WWm one wmnpis b nwidmy. No recoginuble po" rmmm may be amid In wW wompe.

FIGURE 1: (Opoadw Use a =n~ 1:1 per domownen iaebi mcx dw. N uese d. wma m be wwarWhy m~appedtoFIP1g,2 Orgneig gnsphk no be aftclid (-¶ /bal,1 tsod con be copied.

FIGURE 2 W~ EXAMPLE): The tie "w and providie a Eusinese Scuenwo w exlan to fte -soer wto is qC*gan in Vie x amP's. Add fte rate: In I* awaipie fte aslatk (*) repieseert toe dfa elemuwt 9speraror and theN(1. churaers repraer tiet ae*ner teinikwor.* Pfews EDO ~Wwniesion dew and ft moew"i in Iwo cokwmi&uuidweby-sde. ZU or = coad we diecowaged. Mica swi* wametijaeimin ain vowy wanope Is ni. FORMAT:

BUSINESS SCENARIO: In ftb Uwwscdo m tiet wider bs XY2 Ras Camenermd Mie eceiver is Oak spuVOr.Fantaotc Produca Maai*nuINI~tg In....M.

EDI TRANSMISSIOt4 QATA ffRANSACTION SET PURPOSEa DAA

ST*SXX'0005 N/L Begin Transaction Set SXX; ControlNO. 000535S010798000' N/L Original Transmission; Ref. No.79600etc.

4.0,10 BASELINE AS OF: JANUIARY 29, IMs


ftv 5/10/w

DM Number_________(Secretaflt Oniy)

Documesnt No.__ _ _ _(Dwelopeir Obtain fromi DSA)

ASC X12

NEW TRANSACTION SET DEVELOPMENT FORM

INSTRUCTIONS: Use this formi to submit a draft transaction set for review by X12J Techncal AMsusment intl It istext processed by DISA. Use a now Transaction Set Development Form whenever revisions are proposed and atext fie has not yet boen prepared by DISAK

ATTACHMENTS: Attach aJ pages; use this form as the Wist. Follow these instructions for preparing materilsi.

The subrnlttu' must obtain a document number assignment from DiSA. Post It to this form (above).

Attach a LIst o! Rovsinsh If the draft was previously reviewed by X12J or I this Is a revised/redesignedtransaction se standard requirin X12 bal5a

Use ONE Work Request Form to list aNl supporting data meintenience for the ftansaction set and attach itto this form. Propose new or revised codes for DE 143 and DE6479 atea minimum, I require.

A Transmittal Farm, mugt accompany#thi document when it Is submitted to DISA for distribuion.

Use the most recent X12TM Standarde Developmn Workbook to checkl your document for accuracy.

A. SUBMITTER INFORMATICOt

Submitter~ Name_______________ _______

company _ _ _ _ _ _ _ _ _ _ _ _ _

Address __ _ _ _ _ _ _ _ _

Addres/ZIP _______________________

Phone _________________________

Indicate the X12 subcommittee or task group whose position is represented here.I declare that this represents fth official poeftion of X 12 WORK GROUP:___________established at the meetng dated___________

S. ABSTRACT The Abstract Is registered with the American Nationgi Standards lnstgut~e. it is & precise summaryof the Purpose/Scope (see Section C below). It may be Idenca" to the Purpose/Scope I that is brie (twopa~ragralphs), OOewtse Summarize the purpose/scope. It should contain enough Informnation about the standardto enaia* a potential user deterinen whet equivalent pape transection it represents or whet the standard is. ~Intended to do. Follow fth format on page two.

BASELINE AS OF: JANUARY 29,193W 4.0.11


noy. 5/10/10

SAMPLE TRANSMrT'AL FORM

InitializedKEY DATE: Febrnmy 15, 1990

DELEGATE'S NAME John Doe

RESPONSIBLE SUBCOMMITTEE/TGO ASC X120 XX Subcomnlttee/TG4

TRANSACTION SET/GUIDEUNE TITLE X12XX ABC/XYZ TRANSACTION SET (SI

BALLOT Document No.Current Document No. ASC X`20/90.051Previous Document No. ASC X120/90-004Project Proposal No. PP-W9Associted WR/DM No. DM 012-190

PROJECT PROPOSALPP Review by X12J (DATE) 2/7/90PRB Approves PP (DATE) 2/9/90

DEVELOPMENT PHASE: Project proposal approval drough approval for X12 vote.

Documet Submitted for DISA Ted Proceessn (DATE)Subcommittee Approves Draft fo Review by Xl 2J. Tech Assessment (DATE)Xi 2J Tech Assessmert Review (DATE)PRB Approves Doaumet for X12 Vote (DATE)_ _

ORIGINAL BALLOT DATA (DISA):

Ballot Closed Date (DATE)Tally/Comments Sent to Chair/Dalegates (DATE)Tally Stats (Number and Percent)

Ballots Maled (100%). Ballots Returned (_%)

Approved (.%)-- App w/Comewt (,_%)

Disapproved (_.)Abstain•ed (.)

4.0.12 B*AEL3EE AS OF: JA4WARY 21, 13


Palle TWO

COMMENT RESOLUTION PHASE: See Sections A. 8 and C. Iftithe subcommittee at aytime decides to rebalotIts documenk. PAD1 approval is sequired and response letters are notr ncesaaiy.

A. COMMENT RESPONSE LETTERS: An Open Forum muat be scheduled at the nod X12 meeting following theb&Wo diosi date. AN thoe who comnmerted receive a conicerv response letter from mhe developingsubcommittee. DISA records thi process and handles fth aluling.

Open Forum Date (DATE)_ ___Response Leoamr Maild Ott by DISA (DATE) ______

Rab1tl" Period (30 days) Closes (DATE)

ADJUSTED BALLOT DATA (DIMA):30-Day Respons Review Ciose DaM (DATE) ______

Tally/Comments Sent to Chair/Oslegates (DATE) ______

Tally Stats (Number and PercentBallots Malled (100%)Ballots Returned (_%)

- Approved (%- App w/Cornmsnt( )- Diapproed (%-Abstained (%

B. SUBS-TANTIVE REVISION: If ballot comments resuit in subsarien revisions to the documerw.ths aMSefreiewd by X12J and processed by DISA. The revise documenet IS submitted to X12 vowes for a 30-da reviewperiod. DISA records tIs proces/twdes mainn Subcommittees shauld conduct 30-Gay reviews for responseletters/revised documents coneurreroy.

Subicomm~tee, Approva of Revisions (DATE)_ ___X12J Review of Revison (DATE)_ ____DISA Malls Revised Document (DATE)Substantive Revision 30-Day Review Cosese (DATE)

ADJUSTED BALLOT DATA (DISA):30-Day Substanitve Chang Review Closed Date (DATE)______Tally/Comments SetK to Chum /Delegate (DATE)______Tally Stats (Number and Percent)

Ballots Malled (100%)-Ballots Returned L_%)- Approved L %-App w/Comment (_%)

Disapproved L-%)Abstained L %

BASELINE AS OF: JANUARY 29,8IM 4.0.13


DRAFT IMPLEMENTATIOM COWVDN'fON

Page Throe

C. CONTINUING OBJECTIONS. If there are continuing disapprovals after the 30 Jay rvlew peulod, thedocurnent/dlsapprovais/respornsl/corltinuflg objections are ealed to X12 members who originally cast a ballot.for another 30-day review, to give them an opportunity to change their vote.

Continuing Objections Maled to Chair/Delegate by DISA (DATE) _

DISA Mall Documents (DATE)

30-Day Review Ooses (DATE)

FINAL ADJUSTED TALLY (DISA): Whenever any disapprovaJs are withdrawn. a letter to this effect must bereceived In writing by DISA.

Final Tally Results Seot to Chair/Delegate (DATE)30-Day Review Stats (Adjusted Tally)

Ballots Mailed (100%)Ballots Returned (%)

- Approved )App w/Comment L_%)Dlsapproved (%)Absauined L-%)

PRB APPROVAL PHASE: After the comment reslution periW, the subcommittee votes to submit the documentto the PRO for approval to publish.

Subcommittee Votes to Releam to PRB (DATE)PRB Approves Publication (DATE)

FOR DRAFT STANDARDS FOR TRIAL USE:VERSION/RELEASE/SUBRELEASE ID CODE ASSIGNED:

4.0.14 BASEUNE AS OF: JANUARY 29., 1m


Page Few

TRANSMITTAL FORM INSTRUCTIONS:

GENERAL- This TrnmlnMn Pami is a ~TURNAROUND DOCUMENT which ecodsmthehI~m~/calreris aaWmofaproOe docmeet It is uged to tcclunge i~rwrnetion beWee thie SocrvWWie aaW tie conviime d X1 Zlriom*mato Is coomiats" (ad on. This fOm is affachad to the docmuwen whenewe It III iesued for dWbion (k isfmadaory for submlthi documersa to O9SA. X1 2J Tectvic* Asseasmrat uW the PRO). DOoihwt cortroiwnibei wre at. rmpre on each dowiwit a~nd rownertn are reqikd whenver It Is reved.

KEY DATIE: Th~iis IIeud to duetty the latew ve~ ficil tie docuwtir (date associaWe wati the cwret traremiWfom -me.

DELEGATIL, Each mibcomrnitee deslgreas n hidKdi (delegut) from the gro*p rupo oeb for the proiea

. ~ ~IfNITATION: P0rrnry daais rcordd by DISAon the kOJiWlze foml elfte pi m'o$ proposl IsI ppemed by thePRO. The Kh~ownvnlm u--* &W dulgopes) recoli Ow the We Tmw "ve Pitm frm DIM. tierafter. theywre rospon*Je for @=0rhi ft approprift as*mommltts approval doates The cle/dedeg. will geemi pof ft vpated tamW form wheonover It is ,vw by O&I

UPDATING: At each appoprims ga. DISA wE POST hell dmt to the form. ADD goe nod spproproe bier's tothe fom. eIW SEND It to the siboaruMse clair/dolegat at each vWs clwVge The deloegte mut POST theform with fresh dat at each ftats chang far wihtoe WAsabc ~onm Is mqreaorb and SEND It with theapproprist docmert to tie Secoa*Lf.

BASELINE AS OF: JANUARY 23,1993 4.0.15

DEPARTMENT OF DEFENSEDRAFT IMPLEM101TATION CONVENTION

ASC X12 BALLOT COMMENTRESPONSE LETTER FORMAT

OfINERAlloor~uA11

AFTE ANIE SLO, TIWE 0102NLE SUSCOMMITTEE1 (Of1t f DE5IONATO TASK GROUP) MUST fsmd iwimagwv dodumov vascm Th OMwaan A PimimAs ws mm (CPU) swn o s you -am no CAs 0 Megn 0 Pam asabMi Oft

-@N Oomesw -l0 "flbt~Wf~A w~y aimmaas 0 h P a aim WP ~t'mUI " l., mga CW.

Thaws N me mo weswow kn wAo bumwl ~ 0 aae: a gaiuaw mw ~4 we he aMR 0 of awmw"nm, OW bbcie,umoes 10 imaf uuoWsw. Usee mIWuS bawl& to Usf -asm

OPTION 1: OGdENI LETTE (MAMAE LETTER) TO ALL COMMIDTO~lYou maw pipwo w Ws barn be umfa al U snUm~a. Ew~y awma I3HfaW i s be spaWaa 'rin aw. Fal a&* oanNotmwne pow mm omnm (Xit ummbar mopm nama) &Wd ft, ims mmintd beim Lk* yma mapow t fIt inwawwm I ywdwome fn not ym. may gooiftmauin utu~ wes aanllw md snp, oW losme a as. Eway ammiro ds mp pd mats be

0, - A I&U

OPTION 2: INDIVIOAL, LETIW TO EAm COMMIITORY~u Nmj popusma woWWlr soM odi mm. If yW m. f almU pbma.V ram. ee nfawt Is mlt mig iawrwo pss4bd an Is bmktftkw ft %mmo haaiso Ww a* &W gut a kmW uWaWo bal. Emy) Nhftw fts dupopsd fito be nouwdW u.

MmuTRUTIN

ST P 1 PID w" tou IM pW ofu W * s) man MC X12 Moeed. I ywu donv Imm Imsd you w eSSt aims u IsmfSain Or repeaimW tv aqis ~aed you amy noe poauo. omwwa. or SMw b~umtud1 pe sammmeww~ 'sPo bomta).

SWEP: CU sbse bedsumouu ii. tmmrmimmm r s p I ns lI upq li mIt yo m"a man frdwIMAsd ISM mato mamamam ft ommw4n miWu m~n us~ed f tbe Ws k wkm sbe tfwe by an *A*(04. SC X1 2tF/GOUO.3AJ fs uesoo bw I W(e.,,. MSC mbWOGSI-iaoSl). OIL

STEPS: Chases yoww law Iamoplon (ma Chea dowwis Oft ses)

STEP4: PvgptMs Is m ised is sW~une. balm amgat~qA*WbAsmfsakM besa. P ov a wow - (man~) into is W rp mm w bar Of ft MafMW-; lMOA phs NmM.u.b. P" toI domoms=iw amift nwib uda to NwUe km.C. PiuS ft dm WNW I* dmomwA maido fuwIbe?4. MAae s ft b 0 is ki4 AMo. w ern 8 owVt M kmkW anid mid*saae bw &Wt ass be.

r.~ m "Ian vbowpuy 0 a@ uli ft, Inv kis apampoedy - -1 fm ft afus~m.t. You way web 0 MWp ft betalk ly (Sum yaw Temoad ai om) ow is Mbemman ofto meft,

STEP 4: Porew islames S 'is Uswsu APutAw Seasuk Saeelsa *0t a - kWfsm raaag *Sudn s4ift tomeukmwa) yuhamo 0rep Whoa ft WWI heMWimafasuki& to p"*u INlp madt uNO ~ ud~ mo ont maTowauvuak on ht m ~ h t nwIg dMe maW 30de mvim pulad dosin dam psd.M

Alldonow~ XII" Laes SmailbS- Omn~ uAwespopmu Low

-bdvi*a Lowe

44.10 BASELINE AS OF: JANUARY 29,1993


Tim JoanseyASC Xl 2-ELECTRONIC DATA INTERCHANGE (EDI) (999) 99.9999

Accredod StwWws Camw Da Smitheyietu tnw Srw ':os ofeim of (999) 999.9999Amra Net•aW Surwl~ instiut

Oocanment NoASC X12C/TrG2/90-999

June 2, 1990

TO: X12 Members Who Commented on Modifications toX12.= Control Stritures

RE: Response to Comments on December BalotDM& 205289, 215299. 317239

Thank you for your comments. Thi ballot involved modiilcatio to X12.x. Of the 327 ballots mai&" 3 ballos werereturned. Of these, 81 approved, 13 approved with comment, 20 disapproved with comment and 37 abheaiAed.

In general, the vote responses were ia favw of the modifications. The majority of the comments focused on the impacof thes modiffatios on the ptestat•tiom of informa•on in the X12Z Scome Directruy. The pmposed modiriciatioand the resulting presentation i the segment directory have bes rworked a ,p to these commen. A rcvsemodilfcation to X12.wu srrvivewd by Technical Auesment at the Jume ASC X12 meeting. Modifcatiom to thedocument have bees made whik rellect responses to the commmsu bom this ballot, and a mrisd copy of X12.i inbeing dstribted to all who voted on th"s iue, for 30-day eview of revisdos.

Specific responsea to comments foalmo.

COMMENT: Automobile Corporation"Add the following note to Paragaph 3.3: NOTE- Communicadon protocol charaers should be excluded from thecharacter set.

RESPONSE-The cove lettar t out with the voung pckaedpained that the intent ws to obtain conenu an the proowedmodification to X12.x. X2.i is a ffiadtstandard to amend. We request that ballot respose be cons red on themerits of the recommended modificetio and not on the smdard as a whole. Your comment was outside the scope ofthe requested modifications.

BN

BASEUNE AS OP: ,JANUARY23, IWS 4.0.17

DEPARTMET OF DEFENSE

DRAFT rPLEMENTATION CONVENTION

rape Two

COMME.T: Aircraft Engine Corporabou"Some consideration for Ab6srac Symax Notati•on One (ASN.1) should be allowed

L ASN.A is capable of defin* all of the neceur intcr.relazios needed by XI2 trasaionL

2. ASN.1 requires s Wag- ers to defrne the same information.

3. ASN.1 is the encoding scheme used by most OSI work.,

RESPONSE-The recommCndation to consider usap of ASN.1 encodi reaches far beyond the scope of the modifications requestedin this baloL Aivities such as this am best submitted as separate work requestL

COMMENT: Some Software Inc."*Conditionality of data elemens should be left to the discretion of impiemewtarion guidelines and apeements. There ismuch discussion at times u far as whether certain data elemCnIu should be mandatory or am many application sytemare incapable of providing certain 'nadatoq'informaton and, as such, filler-type data must be iuserted.*

RESPONSE:"The inae of data elemen conditionality m a whole is a much broader subject than was intended to be addresae withisthe scope of this ballot. Tlis ballot was int•nded to provide a means for consistent documentation and applicoion ofalready Mstin condiuti strturels. If the commentor belek that the conditiona structure should be removod f"rmthe st •ndard, the task group recommends that this be submitted as a separate work request.

Etc.


DEPARTMENT OF DEFENSEDRAFT NPLEMEJTA rsON CONVENT)0t4

ASC X1 2-ELECTRONIC DATA INTERCHANGE (EDI)Ag~reowd Standws Covmrrmae Joe Somebodyam s"a wr~w tft Proaok of uth Chai TO 19. X12CAmerew Neano Scowvs wat(99a9~u

Occumont NoASC X12C/TGS/9"0A

M& la DoeAuqu 10. 1990

American lanikone Central FuanMiddle America, MO 9999

RE. Resos to Sa"a Comrnnu asASC X12 Model Guideline

Dew M&. Doc

Subasamitte XI2C has empowere its Task Group 19 to provide respoises to the aswnts as this bsfaL Theambers ot TG19 wish to thAall . X12 nembers who took the time gad efart to voce ca this gWuiwee. We

epuaythank eA&h indvua who pe owie asmeats whether is approval or disapproval of the guideline. Werapm ad appreciate your careful review a("hi daoisat.

Ow r npoome is keyesd to dhe umbered itemas in the commeMs attached to your bdalm

RESPONSEL We arce writh you cmmmeu. in Section 4.2.2 we have repbwd -%e ateamn rli -0 sick 'ruleg amw ncilmd".

2. Thecosafimsbetwe moSectkon42.3 andSectmilon .2ony is because.1theý inil dwe c inei the firsmboc A 6 Thsa a hypothetical cumple, of a simliWe =ode' Headers aid trailers cas be placed as the instent at

ALL keWl, OWd do adtnecessarkl correspond to ASC X12 headers sAM traiera

3. We agre with your comment Sectiom 6.2 has been canged so that athe establishment of -0 was added to tevasI and 4.

BASELINE AS OF: J ýNUARY 29,1993 4.0.13

m ! II





* 5.0 GLOSSARY

This chapter contains ASC X 12 and DoD specific glossaries.

5.1 X12 GLOSSARY

ANSIAmerican National Standards Institute

ANSI StandardA document published by ANSI that has been approved throughthe consensus process of public announcement and review. Eachof these standards must have been developed by an ANSI commit-tee and must be revisited by that committee within 5 years forupdate. See Draft Standard for Trial Use (DSTU).

Area Transaction SetIdentifies a predefined area within a transaction set (header, detail,summary) containing segments and their various attributes.

ASC X12Accredited Standards Committee, X12 comprises industry mem-bers who create EDI standards for submission to ANSI for sub-sequent approval and dissemination; or for submission to theUN/ECE for approval and submission of UN/EDIFACT stan-dards.

Authentication

A mechanism which allows the receiver of an electronic transmis-sion to verify the sender and the integrity of the content of thetransmission through the use of an electronic "key" or algorithmwhich is shared by the trading partners. This is sometimes referredto as an electronic signature.

Compliance CheckingA checking process that is used to ensure that a transmissioncomplies with ANSI X12 syntax rules.

Conditional (C)A data element requirement designator which indicates that thepresence of a specified data element is dependent on the value orpresence of other data elements in the segment. The conditionmust be stated and must be computer processable.

Control Segment

A Control Segment has the same structure as a Data Segment butis used for transferring control information for grouping datasegments. Control Segments are Loop Control Segments (LS/LE),Transaction Set Control Segments (ST/SE), and Functional GroupControl Segments (GS/GE), defined in X12.6. and InterchangeControl Segments (ISA/IEA/TAI) defined in X12.5.

BASELINE AS OF: JANUARY 29,1993 S.0.1


Data ElementThe basic units of information in the ED! standards containine aIset of values that represent a singular fact. They may be singl:-character codes, literal descriptions, or numeric values.

Data Element Length

This is the range, minimum to maximum, of the number of char-acter positions available to represent the value of a data element.A data element may be of variable length with range from mini-mum to maximum, or it may be of fixed length in which theminimum is equal to the maximum.

Data Element Reference Number

Reference number assigned to each data element as a uniqueidentifier.

Data Element Requirement Designatork code defining the need for a data efm-ent value to appear in thesegment if the segment is transmitted. The X12 codes are man-datory (M), optional (0), or conditional (C). DoD may "require"a segment which is optional by X12 standards.

Data Element SeparatorA unique character preceding each data element that is used todelimit data elements within a segment. Dod uses "*' as thedelimiter.

Data Element Type

A data element may be one of six types: numeric, decimal.identifier, string, date, or time.

Delimiters

The delimiters consist of tw, levels of separators and a terminator.The delimiters are an integral part of the transferred data stream.Delimiters are specified in the interchange header and may not beused in a data element value elsewhere in the interchange. Fromhighest to lowest level, the separators and terminator are segmentterminator and data element separator.

DISAData Interchange Standards Association. A nonprotit organizationfunded by ASC X12 members which serves as the Secretariat forX 12.

DSTUDraft Standard for Trial Use. Represents a document approved forpublication by the full X12 committee following membership con-sensus and subsequent resolution of negative votes. (Final Reportof X12 Publications Task Group). The Draft EDI Standard forTrial Use document represents an ASC Xl 2 approved standard foruse prior to approval by ANSI. See ANSI Standard.




EDIElectronic Data Interchange. The computer application to corn-puter application exchange of business information in a standardformat.

Electronic Envelope

Electronic information which binds together a set of transmitteddocuments being sent from one sender to one receiver.

Element DelimiterA single-character which follows the segment identifier andseparates each data element in a segment except the last.

Functional Group

A group of one or more transaction sets bounded by a functionalgroup header segment and a functional group trailer segment.

Functional Group Segments

GS/GE segments identify a specific functional group of documentssuch as purchase orders.

Industry ConventionsDefines how the ASC X12 standards are used by the specificindustry

Industry GuidelinesDefines the EDI environment for using conventions within anindustry. It provides assistance on how to implement X12 stand-ards.

Interchange Control SegmentsISA/IEA segments identify a unique interchange being sent fromone sender to one receiver (see electronic envelope).

Interchange Control StructureThe interchange header and trailer segments envelop one or morefunctional groups or interchange-related control segments and per-form the following functions: (1) defines the data elementseparators and the data segment terminators. (2) identifies thesender and receiver, (3) provides control information for the inter-change, and (4) allows for authorization and security information.(X12.5)

LoopA group of semantically related segments: these segments may beeither bounded or unbounded (X12.6). The NI loop is an exampleof a loop, which includes segments NI to PER for name andaddress information.

Mandatory (M)A data element/segment requirement designator which indicatesthe presence of a specified data element is required.



Mapping

The process of identifying the standard data element's relawionshipto application data elements.

Max UseSpecifies the maximum number of times a segment can be used atthe location in a transaction set

MessageEntire data stream including the outer envelope

Optional (0)A data element/segment requirement designator which indicatesthe presence of a specified data element/segment is at the optionof the sending party which can be based on the mutual agreementof the interchange parties.

QualifierA data element which identifies or defines a related element, setof elements, or a segment. The qualifier contair- a code takenfrom a list of approved codes.

Repeating SegmentA segment that may be used more than orce at a given locationin a transaction set. See Max Use.

SecuritySystem screening which denies access to unauthorized users andprotects data from unauthorized uses

SegmentSegments consist of logically related data elements in a definedsequence. A data segment consists of a segment identifier, one ormore data elements each preceded by an element separator, andends with a segment terminator.

Segment DirectoryProvides the purpose and format of the segments used in theconstruction of transaction sets. The directory lists each segmentby name, purpose, identifier, the contained data elements in thespecified order, and the requirement designator for each dataelement.

Segment IdentifierA unique identifier for a segment composed of a combination oftwo or three upper-case letters and digits. The segment identifieroccupies the first-character positions of the segment. The segmentidentifier is not a data element. The segment identifier inEDIFACT is a component data element - part of a compositedata element consisting of a segment identifier and an explicitlooping designator.



Segment TerminatorA unique character appearing at the end of a segment to indicatethe termination of the segment, e.g., N/L.

SyntaxThe grammar or rules which define the structure of the EDIstandards (i.e., the use of loops, qualifiers, etc.). Syntax rules arepublished in ANSI X12.6.

Transaction SetThe transaction set unambiguously defines, in the standard syntax,information of business or strategic significance and consists of atransaction set header segment. one or more data segments in aspecified order, and a transaction set trailer segment.

Transaction Set IDAn identifier that uniquely identifies the transaction set. Thisidentifier is the first data element of the transaction set headersegment.

TranslationThe act of accepting documents in other than standard format andtranslating them to the standard.

Version/Release

Identifies the publication of the standard being used for the genera-tion or the interpretation of data in the X12 standard format. Maybe found in the Functional Group Header Segment (GS) and in theInterchange Control Header Segment (ISA). See Control Segment.

VICS CommitteeVoluntary Interindustry Communications Standards for ElectroaicData Interchange

X12The ANSI committee responsible for the development and main-tenance of standards for electronic data interchange (EDI).

X12.5Interchange Control Structure. This standard provides the inter-change envelope of a header and trailer for the electronic inter-change through a data transmission, and it provides a structure toacknowledge the receipt and processing of this envelope.

X12.6Application Control Structure. This standard describes the controlsegments used to envelop loops of data segments, to enveloptransaction sets, and to envelop groups of related transaction sets.



5.2 DoD GLOSSARY

AIS

Automated Information Systems

ASD(P&L)Assistant Secretary of Defense (Production and Logistics)

DESData Encryption Standard

DISADefense Information Systems Agency

DLADefense Logistics Agency

ISAInterchange Control Header Identifier

NISTNational Institute of Standards and Technology

NTENote Identifier

PLUSProtection of Logistics Unclassified/Sensitive Systems

UN/EDIFACTEDIFACT; Electronic Data Interchange for Administration, Com-merce, and Transport


REPORT DOCUMENTATION PAGE Form 4pprovedO D .01 0704-0188

Pubic reoIrting tibrden for this collection of information is estimated to average 1 hour per response, including the time tar revievring ti,.tructions searhing exsting mta isourtesgathering. and maintaining the data needed, end reviewing the collection of information. Send comments regarding this burden estimate or any other spent of this tolection ofinformation, including suggestionsfor reducing this burden, to Washington Headquarters Services, Oirectorate for Information Operations arnd Reports. 121$ Jefferson Davts Highway, Suite1204. Arlfington, VA 2220241302. and tothe Office of Information and Regulatory Affairs. Office of Management and Budget. Washington, DC 20503

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

Jan 93 Draft

4. TITLE AND SUBTITLE 5. FUNDING NUMBERS

DoD Electronic Data Interchange (EDI) Convention: C MDA903.90,C-00O6ASC X12 Transaction Set 843 Response to Request for Quotation (Version 003010) PE 0902198D

6. AUTHOR(S)

Stephen LusterRichard Modrowski

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

Logistics Management Institute REPORT NUMBER

6400 Goldsboro Road LMI-DL203LN 18Bethesda, MD 20817-5886

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORING'MONITORING

DoD Executive Agent for EC/EDI/PLUS AGENCY REPORT NUMBER

Defense Logistics AgencyDLA-ZIE, Cameron StationAlexandria, 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 (EDI) systems design document that describes the standards or "convention" the Department ofDefense (DoD) will use to accept a price quotation using the ASC X12 Transaction Set 843 Response to Request for Quotation (003010).

14. SUBJECTTERMS 15. NUMBER OF PAGES

Electronic Data Interchange; EDI; DoD EDI Convention: Electronic Commerce: ANSI X 12; XI 2; electronic 104standards; electronic business standards; computer.to-computer exchange of data; electronic documents; 16. PRICE CODEelectronic records; paperless environment; conventions

17. SECURITY CLASSIFICATION 18. SECURITY CLASSIFICATION 19. SECURITY CLASSIFICATION 20. LIMITATION OF ABSTRACTOF REPORT OF THIS PAGE OF ABSTRACTUnclassified Unclassified Unclassified

NSN 7540-01-280-5500 Standard Form 298. (Rev 2-89)0reasctbed by ANSI Std 219 19

299-0t