electronic data interchange (edi) convention · 2011. 5. 14. · ad-a263 476 draft department ~ of...

AD-A263 476

DraftDepartment

~ of

L k-SDefense

DoDElectronic DataInterchange (EDI)ConventionASC X 12 Transaction Set 865Purchase Order ChangeAcknowledgment(Version 003010)

DL203LN23 DTI

~ ~' ~- -~APR 26 1993

January 1993

BAN A93-08748BASELINE AS OF: JANUARY 29, 1993 \-Z•,

DEPARTMENT OF DEFENSE PURCHASE ORDER CHANGE ACKNOWLEDGMENT

DRAFT IMPLEMENTATION CONVENTION 865.003010DoD_

Draft

Ah.I DepartmentS~of

Defense

DoDElectronic DataInterchange (EDI)ConventionASC X12 Transaction Set 865Purchase Order ChangeAcknowledgment(Version 003010)

This document was prepaied by the Logistics Management nrLsttute for the Defense Logitics Agency under

Task DL203. The task was perfomwd under Contract MDA903-90-C-O006 with the Department of Defense.Permission to quote or repioduoe any part of this documeni except for Government purposes nust beobtained from the Depamnent of Defense Executive Agent for Electronic Commerce/Electronic DataInterchange/Pfotection of Logistics Unclassified/Sensitive Systems.

Executive Agent for EC/EDI/PLUS

Defense Logistics AgencyCameron StationAlexandria, VA 22304-6100

BASELINE AS OF: JANUARY 29, 1993

Form Approved

REPORT DOCUMENTATION PAGE OPMNo. 0704-O188

Publk reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, s•arching existing data sourcesgathering, and maintaining the data needed, and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection ofinformation, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 121S Jefferson Davis Highway, Suite1204. Arlington. VA 222024302, end to the 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-0006ASC X12 Transaction Set 865 Purchase Order Change Acknowledgment (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-DL203LN23Bethesda, MD 20817-5886

9. SPONSORING/MONITORING AGENCY NPMEý.) AMC) ADDRESS(ES) 10. SPONSORING/MONITORING

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

Defense Logistics AgencyDLA-ZIE, Cameron StationAlexandria, VA 22304

11. SUPPLEMENTARY NOTES

1 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 Purchase Order Change Acknowledgment using the ASC X12 Transaction Set 865 Purchase Order ChangeAcknowledgmentf003010).

14. SUBJECTTERMS 15. NUMBER OF PAGES

Electronic Data Interchange; EDI; DoD EDI Convention: Electronic Commerce; ANSI X 12; X 12: electronic 122standards; electronic business standards; computer-to-computer exchange of data, e'ectronic 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 ABSTRACT LUnclassified Unclassified Unclassified

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

DEPARTMENT OF DEFENSEDRAFT IMPLEMENTATION CONVENTION

TABLE OF CONTENTS

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

1.1 PURPOSE Or- 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.1lConventions, Standards, and Guidelines . . 1.0.21 .4.2 Documentation 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 X12

TRANSACTION SETS 3.01

DTI QV~r~ ~3.1 INTRODUCTION.................. 3.0.1

3.2 CONTROL SEGMENTS............. 3.0.13.2.1lDescription of Use................. 3.0.23.2.2Control Segment Specifications......... 3.0.5

3.3 EXAMPLE OF CONVENTION USE . ... 3.0.15

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

,OTS Rklt C34.0 ASC X 12 FORMS...................... 4.01

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

5.1 X12 GLOSSARY.................. 5.0.1

Dsr- codes 5.2 DoD GLOSSARY.................. 5.0.6&L~bI. ý/ or

DASEUNE AS OF: JANUARY 29, 1993


Iv BASELUNE AS OF: JANUARY 29,1993

DEPARTMENT OF DEFENSE

DRAFT IMPLEMENTATION CONVENTION

1.0 INTRODUCTION

This chapter explains the 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 Chiefs 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 authority. See Chapter 2.0 Maintenance, Section 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 theED! Implementation 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 X12 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 EDT. They provideadditional information to assist in conducting EDT. 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 EDT 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 EDT 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 BASEUNE 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 conventions can 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 and 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/I" 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.



DEPARTM4NT OF DEFENSEDRAFT UPLEMENTATION CONVEION

824. APPUCATION ADVICEANSI ASC X12 VERSIONIRELEASE 003010000

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 format.It 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 1PACIE pK&S 11".M "ME ", "of. WAX ULOWPNWI4T

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

LOOP, ID - fI 24 L40 NI Name 0 15 040 N2 Additional Name Information 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 2PAGEla Pf SWIo "M IAO. t. 1At11UK LOWOP0U110AT

LOOPID-O1 16000010 010 OTI Original Transaction Identification M 112 020 REF Reference Numbers 0 1213 030 0TM Date/Tru Reference 0 2N/U 040 PER Administrative Communications Contact 0 3N/U 050 AINT Monetary Amount 0 10N/U 060 QTY Quantity 0 10

LOOP ID - TED lam0014 070 TED Technical Error Description 0 1is 080 NTE Note/Special Instruction 0 10016 090 SE Transaction Set Trailer M 1

DA01 - JANUARY 29 IM3

Figure 1.4-1 Example of a Transaction Set Table


OEPARTM•N OF BWENSEDRAFT U1PLEMENTATION CONVENTION


524. APPUCATION ADVICEOGN . BEGINNING SEGMENT ANSI ASC X12 VERSIONiRELEASE 003010DOD

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 Numbqr.

2. BGN03 is the Transaction Set Date.

3. BGN04 is the Transaction Set Time.

4. BGN05 is the transaction set time qualifier.

Data Element Summary

BA~loh

Mandatory BGN01 353 Transaction Set Purpoee Code M ID 2/2Code 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 BGN03 373 Date M 0T 6/6Date (YYMMDD).

Conditional *GN04 337 Time C TM 414Time expressed in 24-hour clock time (HHMM, time range: 0000 though 2359).

Implemnentation Note:Use HHMM.

Not Used BGNOS 623 Time Code 0 ID 2/2

3 DAO1. JANUARY n IM

Figure 1.4-2 Example of a Transacion Set Segment

BASEUNE AS OP: JANUARY 29, IM 1AS


" RequwfedRequired 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. bui the industry recommendstheir use to facilitate EDI. Most companies in the industryare expected to use this data ele!ment.

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

ConditionalConditional d.ta eler mnts depend on the presence of other dataelements in the transaction !et.



DRAFT iMPLEMENTATION CONVENTION

2.0 MAINTENANCE

This chapter describes the procedures for maintaining the DoDconventions. It also presents a seciuun 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 esta'-lished a 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 processes, the EA has established focal pointswithin the ASD Offices, the Military Services, and the DefenseAgencies from which EDI information is obtained and dissemi-nated.

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

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

EDI Standards CoordinatorA77N: DLA-ZCCameron StationAlexandria, VA 22304-6100

See Chapter 4 for reproducible ASC X12 Work Request forms.

2.2 VERSION/RELEASE TIMINGIdentification of the official "version" 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 byASC X12 as follows:

BASELUNE AS OF: JANUARY 29,1993 2.0.1


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 1 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 11th and 12thcharacters may be used by the Military Departments or DefenseAgencies.

Dot, 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.

2.0.2 BASEUNE AS OF: JANUARY 29, 1993


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD

3.0 DoD CONVENTIONS FOR USINGASC X12 TRANSACTION SETSThis chapter defines the DoD transaction set conventions. Itincludes the instructions for 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 Dictionary 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 control segment (also called an envelope) of a headerand trailer for 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 X12 published technical documentation. Con-tact 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



865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD_

designed to identify uniquely the start and end of the interchangefunctional 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 control 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.



865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD

Communications Transport ProtocolISA / Interchange Control Header

GS/,Functional Group Header

ST (/ Transaction Set Header

Detail Segments(e.g., Purchase Order)

SE Transaction Set Trailer 0/0ST Transaction Set Header C. o

Detail Segments S z(e.g., Purchase Order) c c

aJ t

SE Transaction Set Trailer _

GE Functional Group Trailer• 2ESGS ,Functional Group Header _l

ST / Transaction Set Header

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

SE Transaction Set Trailer i

GE Functional Group Trailer

IEA Interchange Control Trailer

Communications Transport Protocol

Figure 3.2-1. Hierarchical Structure

BASELINE AS OF: JANUARY 29,1993 3.0.3


865 - PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD_



865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSIONIRELEASE 003010DOD

3.2.2 Control Segment Specifications

BASEUNE AS OF: JANUARY 29, 1993 3.0.5


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 00301ODOD



001 - CONTROL SEGMENTS 865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTISA 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 SummaryREF. DATADES. ELEMENT NAME ATTRIOSUTES

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/2Code to identify the type of information in the Security Information.

01 Password

Mandatory ISA04 104 Security Information M AN 10/10This 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 2/2Qualifier to designate the system/method of code structure used to designate thesender or receiver ID element being qualified.

ZZ Mutually Defined

Code 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 ID 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 • D114 3.0.7


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENT 001 • CONTROL SEGMENTSANSI ASC X12 VERSION/RELEASE OO3010DOD ISA • INTERCHANGE CONTROL HEADER

Code Value Implementation Note:An agreed upon designation of DoD Activity Address Code (DoDAAC) 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 ISA11 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 X12, 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 Xl 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 i- 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 ISA15 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 BASEUNE AS OF: JANUARY 29, 1993 . D114


001 - CONTROL SEGMENTS 865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTISA • INTERCHANGE CONTROL HEADER ANSI ASC X12 VERSION/RELEASE 003010DOD

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 "<".

BASEUNE AS OF: JANUARY 29,1993 . D114 3.0.9


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENT 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. ELEMNT NAME ATRImUTES

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.

CA Purchase Order Change Acknowledgement (865)

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 (DoDAAC). 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 GS00 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 Control Number M NO 1/9Assigned number originated and maintained by the sender.

3.0.10 BASEUNE AS OF: JANUARY 29, 1993 • D114


001 -CONTROL SEGMENTS 865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTGS -FUNCTIONAL GROUP HEADER ANSI ASC X12 VERSION/RELEASE 00301 0DOD


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 X1 2Code 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 Dictionaryfor source code list.



865 PURCHASE ORDER CHANGE ACKNOWLEDGMENT 001 -CONTROL SEGMENTSANSI ASC X12 VERSION/RELEASE 00301 0DOD_ GE- FUNCTIONAL GROUP TRAILER

Segment: GE Functional 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 interchange 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 SummaryREF. DATADES. IELEMENT NAM ATrRIBUTES

Mandatory GEO0 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.

3.0.12 BASEUNE AS OF: JANUARY 29,1993 • D114


001 - CONTROL SEGMENTS 865 PURCHASE ORDER CHANGE ACKNOWLEDGMEM'7IEA - INTERCHANGE CONTROL TRAILER ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: lEA Interchange Control TrailerPurpose: To define the end of an interchange of one or more functional groups

and interchange-related control segments.

Data Element SummaryRlF. DATADES. ELMENrT NAME ATTRI3BrES

Mandatory IEA01 116 Number of Included Functional Groups M NO 1/5A count of the number of functional groups included in a transmission.


Mandatory IEA02 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.

Implementation Note:Assigned by the translation software. This number must match the number thai occurs in ISA 13.



865 . PURCHASE ORDER CHANGE ACKNOWLEDGMENT

ANSI ASC X12 VERSION/RELEASE 003010DOD_




3.3 EXAMPLE OF CONVENTION USE

BASELINE AS OF: JANUARY 29, 1993 3.0.15




3.0.16 BASELINE AS OF: JANUARY 29, 1993


"S66 PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD_

EXAMPLE - PURCHASE ORDER CHANGE ACKNOWLEDGMENT (865)

ASC X12 EDT FORMAT DEIITION

ST*865*COA0001 N/L THIS IS AN 865 CHANGE ORDERACKNOWLEDGMENT WITH A CONTROLNUMBER OF COA0001.

BCA*0*AC*N0001993P3010**PO0001* THIS IS AN ORIGINAL ACKNOWLEDGMENT930120****930204*930206 N/L OF CHANGE P00001 TO PURCHASE ORDER

N0001992P3010 DATED JANUARY 20,1993.THE ACKNOWLEDGMENT IS WITH CHANGETHE ACKNOWLEDGMENT DATE ISFEBRUARY 4,1993 AND THE EFFECTIVEDATE OF THE CHANGE IS FEBRUARY 6,1993.

REF*65*PC0001 N/L THE UNIQUE TRACKING NUMBER FROMTHE 860 CHANGE ORDER.

REFRQ*N000192252055 N/L THE REQUISITION NUMBER FROM THE 860CHANGE ORDER.

POC*0001*CA N/L IDENTIFIES THE CHANGE TO THE 860INFORMATION IS APPLICABLE TO LINEr1EM 0001.

DTM*017*930622 N/L THE SELLER IS CHANGING THE REQUIREDDELIVERY DATE IN THE CHANGE ORDERFROM JUNE 15,1993 TO AN ESTIMATEDDELIVERY DATE OF JUNE 22.1993.

cTTI N/L THERE IS ONE POC SEGMENT IN THISTRANSACTION SET.

SE*8*COA0001 N/L THE TRANSACTION SET HAS 8 SEGMENTSAND THE CONTROL NUMBER IS COA0001.

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



865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE O03OlODOD_



865 . PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD_

3.4 DoD CONVENTION



865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSIONIRELEASE 003010DOD_




865 Purchase Order Change AcknowledgmentThis standard provides for the format and establishes the data contents of apurchase order change acknowledgment transaction set. This transaction setcan be used: (1) by the seller to acknowledge or convey acceptance ofchanges to a previously suLnTitted purchase order or (2) by a seller to notifythe buyer of changes initiated by the seller to a previously submittedpurchase order.

Implementation Notes1. The 865 transaction set can be used for one of two purposes.

2. One purpose for the 865 is for a contractor to acknowledge a buyer initiated 860 Purchase OrderChange Request. The acknowledgment can be one of 5 types: a. An acknowledgment with detail and change.This means the contractor will include contractor initiated change items in the 865 for the original 860. b.An acknowledgment with detail and no change. This means the contractor will repeat back to the buyer thedetail sent with the original 860. c. An acknowledgment with exception detail only. This means thecontractor will only include contractor exception items in the 865 for the original 860. d. Anacknowledgment with no detail or change. This means the contractor will send back a simple, summary leveltype of acknowledgment to the buyer. No line item detail is used or required. e. The 860 is rejected by thecontractor.

3. The second purpose for the 865 is for a contractor to initiate a change order for an 850 Purchase Order.In this case, the 865 reflects the items needed to properly identify the related 850 Purchase Order and theitems the contractor is requesting be changed.

4. When this transaction set is used to provide a simple acknowledgment, (BCA02 is code AK). only themandatory and required segments need be transmnitted. Segments CUR, PER, and PWK may be transmittedat the option of the originator.

5. When this transaction set is used for all other type acknowledgments (BCA02 is code AC, AD, or AE) orfor a contractor initiated change (BCA13 is code CP) in addition to the mandatory and required segments,transtmnit other appropriate segments as indicated.

6. When this transaction set is used to provide a rejection to an 860 Purchase Order Change Request,(BCA02 is code RJ), only the mandatory and required segments need be transmitted. Any other segmentwhich might provide information relative to the reason for the rejection, may be transmitted at the option ofthe originator.

Table 1PAGES POS.8 SEG. ID NAME REQ.DDES. MAX USE LOOP REPEAT

5 010 ST Transaction Set Header M 16 020 BCA Beginning Segment for Purchase Order M 1

Change Acknowledgment9 030 NTE Note/Special Instruction F 10010 040 CUR Currency 0 113 050 REF Reference Numbers 0 12

N/U 060 PER Administrative Communications Contact 0 3

N/U 070 TAX Sales Tax Reference 0 315 080 FOB F.O.B. Related Instructions 0 117 090 CTP Pricing Information 0 25N/U 100 SSS Special Services 0 25

DC12 . JANUARY 29 1993


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD_

N/U 110 CSH Header Sale Condition 0 1N/U 120 ITA Allowance, Charge or Service 0 1019 130 ITD Terms of Sale/Deferred Terms of Sale 0 5N/U 140 DIS Discount Detail 0 2021 150 DTM Date/Time Reference 0 1023 160 LDT Lead Time 0 12N/U 180 LIN Item Identification 0 5N/U 190 PID Product/Item Description 0 20024 200 MEA Measurements 0 4026 210 PWK Paperwork 0 2528 220 PKG Marking, Packaging, Loading 0 25N/U 230 TD1 Carrier Details (Quantity and Weight) 0 2N/U 240 TD5 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)30 270 MAN Marks and Numbers 0 10

31 280 N9 Reference Number 0 132 290 MSG Message Text 0 1000

33 300 NI Name 0 1

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


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

Table 2PAGE# POS. 0 SEG. AD NAME RE&. DES. MAX USE LOOP REPEAT

L0P0V O - . 1000040 010 POC Line Item Change 0 1N/U 020 CUR Currency 0 1N/U 030 P03 Additional Item Detail 0 25

DC12. JANUARY 29 1993 2


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 00301ODOD

44 040 CTP Pricing Information 0 2546 049 MEA Measurements 0 40

48 050 PID Product/Item Description 0 149 060 MEA Measurements 0 1050 070 PWK Paperwork 0 2552 080 PKG Marking, Packaging, Loading 0 2554 090 P04 Item Physical Details 0 156 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 1T8 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 357 180 FOB F.O.B. Related Instructions 0 1N/U 190 SDQ Destination Quantity 0 50059 200 DTM Date/Time Reference 0 1060 210 LDT Lead Time 0 1261 220 SCH Line Item Schedule 0 200N/U 230 TD1 Carrier Details (Quantity and Weight) 0 1N/U 240 TD5 Carrier Details (Routing Sequence/Transit 0 12


Materials)

N/U 270 ACK Line Item Acknowledgment 0 1 IN/U 280 DTM Date/Time Reference 0 162 290 MAN Marks and Numbers 0 1063 300 AMT Monetary Amount 0 1

N/U 310 SLN Subline Item Detail 0 1N/U 320 PID Product/Item Description 0 1000N/U 330 P03 Additional Item Detail 0 25N/U 340 ACK Line Item Acknowledgment 0 104

64 350 N9 Reference Number 0 165 360 MSG Message Text 0 1000

66 370 Ni Name0167 380 N2 Additional Name Information 0 2

3 DC12 . JANUARY 291993


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 00301ODOD_

68 390 N3 Address Information 0 269 400 N4 Geographic Location 0 1N/U 410 REF Reference Numbers 0 12N/U 420 PER Administrative Communications Contact 0 3N/U 430 FOB F.O.B. Related Instructions 0 1N/U 440 TD1 Carrier Details (Quantity and Weight) 0 2N/U 450 TD5 Carrier Details (Routing Sequence/Transit 0 12


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

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

70 010 CTT Transaction Totals M 171 020 AMT Monetary Amount 0 172 030 SE Transaction Set Trailer M 1

DC12 . JANUARY 29 1993 4


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTST • TRANSACTION SET HEADER ANSI ASC X12 VERSION/RELEASE 00301ODOD

Segment: ST Transaction Set Header

Level: Header

Loop:Mandatory Usage: Mandatory

Max Use: 1

Purpose: To indicate the start 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. DATADES& ELEMENT NAME AIrRIUTES

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

865 X1 2.16 Purchase Order Change Acknowledgment

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

5 DC12 - JANUARY 29 1993


865 . PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD_ BCA - BEGINNING SEGMEdT FOR PURC4ASE ORDER CHANGE ACKNOWLEDGMENT

Segment: BCA Beginning Segment for Purchase Order ChangeAcknowledgment

Level: Header


Max Use: 1

Purpose: To indicate the beginning of the purchase order changeacknowledgment transaction set and transmit identifying numbers anddates.

Comments: 1. BCA09 is the seller's order number.

2. BCA1 2 is order change acknowledgment date.

Data Element SummaryREER DATADES& ELNEMNT NAME ATTRMIUTES

Mandatory BCA01 353 Transaction Set Purpose Code M ID 2/2Code identifying purpose of transaction set.

Implementation Notes:1. Use code 00 for an original change order acknowledgment, code 01 to cancel a change orderacknowledgment, 07 to send a duplicate change order acknowledgment, code 22 to send an information onlychange order acknowledgment to other interested parties.

2. When changes are initiated by the contractor, code 04 is used for changes to an 850 Purchase Order or860 Buyer Purchase Order Change Request. Code 05 is used when a contractor replaces a previously sent865 transaction set. Code 18 is used when the contractor reissues a Purchase Order Change Request.

00 Original01 Cancellation

04 Change

05 Replace

07 Duplicate

18 Reissue22 Information Copy

Optional BCA02 587 Acknowledgment Type 0 ID 212Code specifying the type of acknowledgment.

Implementation Notes:1. For acknowledgments to an 860 Buyer Purchase Order Change Request, codes AC, AD, AE, and AK areused.

2. Use code RJ if the 860 is rejected.

3. When changes are contractor initiated, BCA02 is omitted.

AC Acknowledge - With Detail and ChangeAD Acknowledge - With Detail, No ChangeAE Acknowledge - With Exception Detail OnlyAK Acknowledge - No Detail or ChangeRJ Rejected - No Detail

DC12 -JANUARY 29 1993 6


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTBCA • BEGINNING SEGMENT FOR PURCHASE ORDER CHANGE ACKNOWLEDGMENT ANSI ASC X12 VERSION/RELEASE 00301 ODOD_

Mandatory BCA03 324 Purchase Order Number M AN 1/22Identifying number for Purchase Order assigned by the orderer/purchaser.

Implementation Notes:1. Enter the purchase order number from the related 860 Buyer Purchase Order Change Request. Relates tothe 860 BCH03 Purchase Order Number. For contractor initiated changes, enter the purchase order numberfrom the related 850 Purchase Order. Relates to the 850 BEG03 Purchase Order Number.

2. If the related 860 is used for changes to orders against existing contracts, the 860 BCH03 may contain azero. When this occurs, send the original call or delivery order number in BCA04 if applicable (relates to the860 BCH04), and the original contract number of the contract being modified in BCA08 (relates to the 860BCH08).

3. For contractor initiated changes, if the relate4 850 is used for orders against existing contracts, the 850BEGO3 may contain a zero. When this occur;, send the original call or delivery number in BCA04 ifapplicable (relates to the 850 BEG04), and the original contract number of the contract being modified in

BCA08 (relates to the 850 BEG06).

Optional BCA04 328 Release Number 0 AN 1/30Number identifying a release against a Purchase Order previously placed by theparties involved in the transaction.

Implementation Notes:1. Enter the call or delivery order number from the related 860 Buyer Purchase Order Change Request.Relates to the 860 BCH04.

2. For contractor initiated changes, enter the call or delivery order number from the related 850 PurchaseOrder. Relates to the 850 BEGO4.

Optional BCA05 327 Change Order Sequence Number 0 AN 1/8Number assigned by the orderer identifying a specific change or revision to apreviously transmitted transaction set.

Implementation Notes:I. Enter the modification number from the related 860 Buyer Purchase Order Change Request. Relates to the

860 BCH05.

2. For cot, -actor initiated changes, this data element may contain a contractor reference number.

Mandatory BCA06 323 Purchase Order Date M DT 6/6Date assigned by the purchaser to Purchase Order.

Implementation Note:Date of the criginal purchase or delivery order. Relates to the 850 Purchase Order BEG05 Purchase Order

Date.

Not Used BCA07 326 Request Reference Number 0 AN 1145

Optional BCA08 367 Contract Number 0 AN 1/30Contract number.

Implementation Notes:1. Enter the original contract or order number if applicable from the related 860 Buyer Purchase Order2 hange Request. Relates to the 860 BCH08.

2. %or contractor initiated changes, enter the contract number if applicable from the related 850 PurchaseOrder. Relates to the 850 BEG06.

Not Used BCA09 127 Reference Number 0 AN 1/30

Optional BCA10 588 Acknowledgment Date 0 DT 6/6Date assigned by the sender to the acknowledgment.

7 DC12 - JANUARY 29 1993


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSIONRELEASE 003010DOD_ BCA • BEGINNING SEGMENT FOR PURCHASE ORDER CHANGE ACKNOWLEDGMENT

Optional BCA1 1 279 Purchase Order Change Request Date 0 DT 6/6

Date of the purchase order change request.

Implementation Notes:1. Enter the change order effective date from the related 860 Buyer Purchase Order Change Request.Relates to the 860 BCH] 1.

2. When changes are contractor initiated, this data element reflects the contractor's change request date.

Not Used BCA1 2 373 Date 0 DT 6/6

Optional BCA13 92 Purchase Order Type Code 0 ID 2/2Code specifying the type of Purchase Order.

Implementation Notes:1. For contractor initiated changes to an 850 Purchase Order, use code CP.

2. When the 865 Purchase Order Change Acknowledgment is used to acknowledge a buyer initiated change,BCA13 is omitnred.

CP Change to Purchase Order

DC12 JANUARY 29 1993 8


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTNTE NOTE/SPECIAL INSTRUCTION ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: NTE Note/Special Instruction

Level: 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. DATADES. ELEMIT NAME ATTUIBUTES

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

Implementation Notes:1. This segment can be used for detail (code AC, AD, or AE) acknowledgment or contractor initiated changeorder.

2. Use any code to indicate the type of note or instruction that applies to the original purchase order,purchase order change, or acknowledgment. Use code GEN for general notes that apply to the entiretransaction set.

GEN Entire Transaction SetORI Order Instructions

OTH Other Instructions

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

9 DC12 • JANUARY 29 1993


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD CUR.CURRENCY

Segment: CUR CurrencyLevel: Header

Loop:Optional Usage: Optional

Max Use: 1

Purpose: To specify the currency (dollars, pounds, francs, etc.) used in atransaction

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

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

3. If CURl 1 is present, then CUR1 0 is required.



6. If CUR15 is present, then CUR13 is required.7. If CUR17 is present, then CUR16 is required.

8. If CUR18 is present, then CUR16 is required.9. If CUR20 is present, then CUR19 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.

DC12 . JANUARY 29 1993 10


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTCUR -CURRENCY ANSI ASC X12 VERSION/RELEASE 003010DOD_

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. Indicates the basis for the exchange rate as the New York ForeignExchange (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 throughCUR21 provide for five (5) dates/times relating to the currencyconversion, i.e., effective date, expiration date, etc.

Implementation Notes:1. Use of this segment is not required for simple (code AK) acknowledgments.

2. Use this segment when appropriate for other types of acknowledgments such as Detail andChange (code AC), Detail and No Change (code AD), and Exception Only (code AE). For changesand exceptions, only send change or exception items. For Detail and No Change acknowledgments,repeat back the information from the 860 Buyer Purchase Order Change Request.

3. This segment can also be used for a contractor to confirm or define what currency they will beusing.

Data Element SummaryREF. DATADES. ELEMENT NAME ATIDUTES

Mandatory CUR0t 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 ISO) 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 SE for the contractor.

BY Buying Party (Purchaser)SE Selling Party

Optional CUR05 100 Currency Code 0 ID 313

1 DC12 - JANUARY 29 1993


866 . PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD CUR -CURRENCY

Code (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.

Implementation Note:Use code 007 for the date and time the cited rate will be effective (start), and code 036for the date and timethe cited rate will expire (stop).

007 Effective

036 Expiration

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

Optional CURO9 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 6/6

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 CUR1S 337 Time 0 TM 4/4



Not Used CUR18 337 Time 0 TM 4/4



Net Used CUR21 337 Time 0 TM 4/4

DC12. JANUARY29 1993 12


865 * PURCHASE ORDER CHANGE ACKNOWLEDGMENTREF- REFERENCE NUMBERS ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: REF Reference NumbersLevel: Header

Loop:Required Usage: Optional

Max Use: 12

Purpose: To specify identifying numbers.

Syntax: Either REF02 or REF03 is required.

Implementation Notes:1. At least 2 iterationsofREF01/02 are required in order to carry the Unique Tracking Number(UTN) (Code 65) and the relevant Purchase Request number (Code IL) or requisiton number (codeRQ)from the 860 Change Order. The latter is required because vendors must provide it on theirshipment.

2. This segment can be used for detail (code AC, AD, and AE) or simple (code AK)acknowledgments.

3. For change (code AC) and exception (code AE) acknowledgments, only send change orexception items. For Detail and No Change acknowledgments (code AD), repeat back theinformation from the 860 Buyer Purchase Order Change Request.

4. This segment can also be used for contractor initiated change orders to an 850 Purchase Orderas needed to further clarify or describe the change order.

Data Element SummaryREP. DATADES. ELEMNT NAME AiUrOUTES

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

Implementation Notes:1. Use applicable codes to relate to information in an 860 Buyer Purchase Order Change Request or 850Purchase Order Header level REF Segment as required. Also refer to the notes for the 860 or 850 Headerlevel REFOI for additional information on how the codes are used.

2. Other codes can also be used to identify additional reference numbers specific for the acknowledgment orcontractor initiated change order.

65 Total Order Cycle NumberAT Appropriation NumberAX Government Accounting Class Reference Number (ACRN)CJ Clause NumberDF Defense Federal Acquisition Regulations (DFAR)FA Federal Acquisition Regulations (FAR)IL Internal Order NumberIT Internal Customer Number

RQ Purchase Requisition No.

TC Vendor TermsZZ Mutually Defined

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

13 DC12 JANUARY 29 1993


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 00301ODOD_ REF • REFERENCE NUMBERS

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

Implementation Notes:I. When REFOI is code AT, REF03 contains the long-line accounting code.

2. When REFOI is code DX, IT, CJ, ZZ, or TC, REF03 contains the explanation, source, etc.

3. For acknowledgments to an 860 Buyer Purchase Order Change Request, the 860 BCH12 may containcode OT to indicate the change order is for other types of modifications. When this occurs, REF03 maycontain the type of modification information.

DC12. JANUARY 29 1993 14


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTFOB - F.O.B. RELATED INSTRUCTIONS ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: FOB F.O.B. Related Instructions

Level: Header


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.

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 transportation 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:This segment is only used when a contractor initiates a change to an 850 Purchase Order and thechanges apply to the FOB information. This FOB Segment is used when the FOB informationapplies to the entire order.

Data Element SummaryREF. DATADES. ELBNT NAME A1"ISOrTES

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 Note:Code ZZ is used when the FOB point is listed as Other than the destination or origin.

DE Destination (Shipping)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:FOB03 carries the location of a site when FOB02 is code ZZfor other.

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

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

Conditional FOB06 309 Location Qualifier C ID 1/2

15 DC12 . JANUARY 29 1993


865 - PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 0O301ODOD FOB • F.O.B. RELATED INSTRUCTIONS

Code identifying type of location.

Implementation Notes:I. Inspection or acceptance site. They are assumed to be the same unless specified otherwise.

2. Use code ZZ when the inspection and acceptance points will not be the same.

DE Destination (Shipping)

OR Origin (Shipping Point)

ZZ Mutually Defined


Implementation Note:If FOB06 is code ZZ, identify the locations of the inspection and acceptance points.

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

Not Used FOB09 352 Description C AN 1/80

DC12 JANUARY 29 1993 16


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTCTP PRICING INFORMATION ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: CTP Pricing InformationLevel: Header


Max Use: 25

Purpose: To specify pricing information

Syntax: 1. If CTP02 is present, then CTP03 is required.

2. If CTP04 is present, then CTP05 is required.


Comments: 1. Example of use of CTP03 and CTP04.

PRICE QUANTITY RANGE1.00 0 to 9990.75 1000 to 49990.50 5000 to 99990.25 10000 and above

CTP03 CTP041.00 00.75 10000.50 50000.25 10000

2. Example of use of CTP03, CTP04 and CTP07.

CTP03 CTP04 CTP071.00 0 0.900.75 1000 0.900.50 5000 0.900.25 10000 0.90

3. CTP07 is a multiplier factor to arrive at a final discounted price. Amultiplier of 90 would be the factor if a 10% discount is given.

Implementation Notes:1. This segment is not required for simple (code AK) acknowledgments.

2. For changes (code AC) and exceptions (code AE) acknowledgments, only send change orexception items. For Detail and No Change acknowledgments (code AD), repeat back theinformation from the 860 Buyer Purchase Order Change Request Header level CTP Segment.

3. This segment is not used for contractor initiated changes to an 850 Purchase Order.

Data Element Summary"REF. DATA

DES. ELEMENT NAME A'TRIStUTES

Not Used CTP01 687 Class of Trade Code 0 ID 2/2

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

17 DC12 . JANUARY 29 1993


865 - PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD CTP - PRICING INFORMATION

Implementation Notes:1. Use any code as appropriate for the acknowledgment.

2. Use code CON to indicate contract price changed from; use code ALT to indicate contract price changeto; use code CHG to indicate a total contract price increase; code DAP to indicate a total contract pricedecrease.

3. Use code SPC to indicate a net amount due for the settlement of a contract terminated for the convenienceof the government.

ALT Alternate Price

CHG Changed Price

CON Contract Price

DAP Dealer Adjusted Price

SPC Special Price

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

Implementation Note:This data element is being used to carry aggregate contract prices, as qualified by the codes in CTP02,instead of unit prices.

Optional CTP04 380 Quantity 0 R 1/10Numeric value of quantity.

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

Optional CTP06 648 Price Multiplier Qualifier 0 ID 3/3Code indicating the type of price multiplier.

Conditional CTP07 649 Multiplier C R 1/10Value, identified by price multiplier qualifier, to be used to multiply price to obtaina new value.

DC12. JANUARY 29 1993 18


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTITD. TERMS OF SALE/DEFERRED TERMS OF SALE ANSI ASC X12 VERSION/RELEASE 00301 ODOD_

Segment: ITD Terms of Sale/Deferred Terms of SaleLevel: Header

Loop:

Optional Usage: Optional

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 isrequired.

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

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



3. For contractor initiated changes to an 850 Purchase Order, use this segment if the original 850included the Header level ITD and the changes apply to the ITD Segment. This segment is onlyused in the 850for discounts.

Data Element SummaryREF. DATADES. ELIEBMT NAME ATTRIDUTES

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

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

Implementation Note:Use the same code as the one specified in the related 850 Purchase Order Header level ITD02.

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 6/6Date 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 it termsdiscount is earned.

Optional ITDO6 446 Terms Net Due Date 0 DT 6/6Date when total invoice amount becomes due.

19 DC12 . JANUARY 29 1993


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 00301 ODOD_ ITO - TERMS OF SALE/DEFERRED TERMS OF SALE

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

Optional ITDO8 362 Terms Discount Amount 0 N2 1/10Total amount of terms discour,.

Implementation Note:This data element is used to eliminate the impact of any rounding off methodolog).

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

Not Used ITDIO 389 Deferred Amount Due C N2 1/10

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

Not Used ITD12 352 Description 0 AN 1/80

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 Notes:1. This data element is not normally used in DoD applications.

2. Use any code.

DC12. JANUARY 29 1993 20


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTDTM . DATE/TIME REFERENCE ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: DTM Date/Time ReferenceLevel: Header

Loop: _


Max Use: 10

Purpose: To specify pertinent dates and times

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

Implementation Notes:1. This segment can be used for detail (code AC, AD, and AE) acknowledgments.


3. This segment can also be used for contractor initiated change orders to an 850 Purchase Orderas needed.

4. When this DTM Segment is used, the date information relates to the entire order. For line itemswith specific date details, the Detail level DTM, LDT, or SCH Segments are used.

5. Delivery date will be provided in this segment as an actual date or in the LDT segment as a setnumber of calendar days after receipt of order. If the latter is used, omit the segment.

6. For acknowledgments to an 860 Purrhase Order Change or rontractor initiated changes to an850 Pu,chase Order, contractor may elect to include expected, scheduled, or estimated deliverydates.

Data Element SummaryHER DATADES. ELDMENT NAME ATTRIBUTES

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 002 for the required delivery dcte(unless delivery date is defined in segment LDT); code 053 forthe date of the request for quotati .,,, code 098for the date of the quote, and 036for the expiration date of aFederal Supply Schedule.

2. Acknowledgment dates should reflect dates transmitted with an 860 Buyer Purchase Order ChangeRequest.

3. Other codes such as 004 for Purchase Order and 008 for Purchase Order Received can be used by thecontractor to relate to dates in an 850 Purchase Order.

002 Delivery Requested004 Purchase Order

008 Purchase Order Received036 Expiration

053 Buyers Local

098 Bid (Effective)

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

Not Used DTM03 337 Time C TM 4/4

21 DC12- JANUARY 29 1993


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSIONRELEASE 003010DOD_ DTM - DATE(TIME REFERENCE

Not Used DTM04 623 Time Code 0 ID 2/2

DC12 JANUARY 29 1993 22


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTLDT LEAD TIME ANSI ASC X12 VERSION/RELEASE 00301ODOD

Segment: LDT Lead TimeLevel: 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. Delivery date will be provided in this segment as a set number of calendar days after receipt oforder or in the DTM segment as an actual date. If the latter is used, omit this segment.

2. For acknowledgments to an 860 Purchase Order Change or contractor initiated changes to an850 Purchase Order, contractor may elect to include expected, scheduled, or estimated deliverydates.

Data Element SummaryREP. DATADES. ELEMENT NAME ATTRIBUTES

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/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

23 DC12 . JANUARY 29 1993


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD MEA -MEASUREMENTS

Segment: MEA MeasurementsLevel: Header


Max Use: 40

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.



3. This segment is used when a contractor initiates a change to an 850 Purchase Order and thechanges apply to the MEA information. This MEA Segment is used when the MEA informationapplies to the entire order.

4. Max use is 10.

Data Element SummaryREF. DATADES. ELEMENT NAME ATRIBiTES

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

Implementation Notes:I. Use any code that may be applicablefor describing measurements.

2. Code CT is used when the related 850 also uses the code CT for variations in quantity.

CT Counts

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

Implementation Notes:1. Use any code that may be applicable. Use code PO for variations in quantity.

2. Code PO is used when the related 850 also uses the code PO for variations in quantity.

PO Percent of Order

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

DC12 . JANUARY 29 1993 24


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTMEA - MEASUREMENTS ANSI ASC X12 VERSION/RELEASE 003010DOD

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

Implementation Notes:1. Use any code that may be applicable.

2. Code P1 is used when the related 850 also uses the code P1 for variation in quantity.

Conditional MEA05 740 Range Minimum C R 1/10The value specifying the minimum of the measurement range.

Implementation Note:Used to indicate the variation in quantity under.

Conditional MEA06 741 Range Maximum C R 1/10The value specifying the maximum of the measurement range.

Implementation Note:Used to indicate the variation in quantity over.

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

25 DC12. JANUARY 29 1993


865 - PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD PWK . PAPERWORK

Segment: PWK PaperworkLevel: Header

Loop: _


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 codenumber.

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. This segment can be used for detail (code AC, AD, and AE) or simple (code AK)acknowledgments.

2. For change (code AC) and exception (code AE) acknowledgments, only send change orexception items. For Detail and No Change acknowledgments (code AD), repeat back theinformation from the 860 Buyer Purchase Order Change Request. For simple (code AK)acknowledgments, the contractor can use this segment to indicate how the paperwork will be sent.

3. This PWK Segment in the 860 or 850 Purchase Order is used to indicate which paperwork mustbe provided with the delivery or as specified in the order. With the acknowledgment, the contractorcan use this segment to indicate how the paperwork will be sent to the buyer. For a contractorinitiated change to an 850, the PWK Segment is included when the changes apply to the PWKSegment.

Data Element SummaryREF. DATADES. ELEMDENT NAME ATTRILUTES

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

Implementation Note:Codes used should correspond to the codes used in the related 860 Buyer Purchase Order Change Request or850 Purchase Order. Also refer to applicable notes for the Header level PWKOl for the 860 or 850foradditional information on the codes used.

CP Certificate of Compliance (Material Certification)MR Material Inspection and Receiving ReportMS Material Safety Data SheetPD Proof of DeliveryRA Revision AnnouncementSN Shipping Notice

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

DC12 . JANUARY 29 1993 26


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTPWK • PAPERWORK ANSI ASC X12 VERSION/RELEASE 003010DOD_

Implementation Notes:

1. Any code can be used, but code EL is preferred.

2. Contractor can use the PWK02 to indicate the method they will use to send the requested paperwork.

BM By Mail

EL Electronically Only

WS With Shipment (With Package)

Optional PWK03 757 Report Copies Needed 0 NO 1/2The number of copies of a report that shouid be sent to the addressee.

Not Used PWK04 98 Entity Identifier Code 0 ID 2/2

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.

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

27 DC12. JANUARY 29 1993


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD_ PKG MARKING, PACKAGING, LOADING

Segment: PKG Marking, Packaging, LoadingLevel: Header


Max Use: 25

Purpose: To describe marking, packaging, loadinn 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 PKG01 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).



3. This segment can also be used for a contractor initiated change to an 850 Purchase Order andthe changes apply to the PKG information. This PKG Segment is used when the PKG informationapplies to the entire order.


DES. ELEMENT NAME ATTRMIUTES

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 1/5Code specifying the marking, packaging, loading and related characteristicsbeing described.

Implementation Note:Use code 35 for Unitizing; code 36for PacklPreservation; 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/7

DC12. JANUARY 291993 28


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTPKG. 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 1/80A free-form description to clarify the related data elements and their content.

Implementation Note:Used when any code or string of codes is longer than can be carried in PKGO4.

29 DC12- JANUARY 29 1993


865- PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE O03010DOD MAN -MARKS AND NUMBERS

Segment: MAN Marks and NumbersLevel: Header


Max Use: 10

Purpose: To indicate identifying marks and numbers for shipping containers



3. This segment can also be used for a contractor initiated change to an 850 Purchase Order andthe changes apply to the MAN information. This MAN Segment is used when the MAN informationapplies to the entire order and any time marks and numbers cannot be described as an address inthe following NI loop.

Data Element SummaryREK. DATADES. ELEMENT NAME ATTRIBUTES

Mandatory MAN01 88 Marks and Numbers Qualifier M ID 1/2Code specifying the application or source of Marks and Numbers (87).

Mandatory MAN02 87 Marks and Numbers M AN 1/45Marks and numbers used to identify a shipment or parts of a shipment.

Implementation Note:Used to carry additional Mark For data that cannot be carried in the NJ - N4 Segments.

DC12 * JANUARY 29 1993 30


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTN9. REFERENCE NUMBER ANSI ASC X12 VERSIONIRELEASE 003010DOD_

Segment: N9 Reference NumberLevel: Header

Loop: N9 Repeat: 1000Optional Usage: Optional

Max Use: 1

Purpose: To transmit identifying numbers and descriptive information as specifiedby the reference number qualifier

Syntax: At least one of N902 or N903 must be present.



3. This segment can also be used for contractor initiated change orders to an 850 Purchase Orderfor any information needed to help clarify the change or to indicate the changed items.

Data Element SummaryREF. DATADES. ELEMENT NAME ATT'RIDUTES

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

Implementation Note:Use any code.

Conditional N902 127 Reference Number C AN 1/30Reference number or identification number as defined for a particularTransaction Set, or as specified by the Reference Number Qualifier.

Conditional N903 369 Free-form Description C AN 1/45Free-form descriptive text.

Not Used N904 373 Date 0 DT 6/6

Not Used N905 337 Time 0 TM 4/4

31 DC1.2 JANUARY 29 1993


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD MSG- MES3AGE TEXT

Segment: MSG Message TextLevel: Header

Loop: N9Optional Usage: Optional

Max Use: 1000

Purpose: To provide a free form format that would allow the transmission of textinformation.

Comment: MSG02 is not related to the specific characteristics of a printer, butidentifies top of page, advance a line, etc.

Implementation Note:This segment can be used for code AC, AD, or AE acknowledgments or contractor initiatedchanges to an 850 Purchase Order.

Data Element SummaryREF. DATADES. ELEMENT NAME ATTRMIUTES

Mandatory MSGO1 933 Free-Form Message Text M AN 1/264Free-form message text.

Not Used MSG02 934 Printer Carriage Control Code 0 ID 2/2

DC12 JANUARY 29 1993 32


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTNi - NAME ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: N1 NameLevel: Header

Loop: Ni 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.


2. For change (code AC) and exception (code AE) acknowledgments, only send change orexception items. For Detail and No Change acknowledgments (code AD), repeat back theinformation from the 860 Buyer Purchase Order Change Request. Information should correspondwith the related 860 Buyer Purchase Order Change Request.

3. For a contractor initiated change to an 850 Purchase Order, the NJ Segment is included whenthe changes apply to the NI Segment.

Data Element SummaryREF. DATADES. ELEMENT NAME ATTRMUTES

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

Implementation Notes:1. Use code BY for Issued By, Block 6, SF 30; use code O for Administered by, Block 7; use codes SE, SU,VN, or ZZfor contractor, Block 8; use code PR for paying office; use code BTfor mail invoice to; use codeST for ship to; use code SW if there is a separate location for packaging; use code UC to represent a MarkFor, if an address (otherwise, use the MAN segment). Use code MP when facility (Block 8) is different fromthe address given for the contractor. Do not send afacility code if it is the same code as that sent for thecontractor. In a second iteration of the Ni loop, use code PL if the party to receive the order is other than thelisted contractor (e.g., an agent).

2. Use code SE when selling party is a large business, code ZZ when a small business; code SU when smalldisadvantaged; code VN when woman-owned; and code DA when services are ordered, to indicate the sitewhere they are performed at.

BT Party to be Billed For Other Than Freight(Bill To)

BY Buying Party (Purchaser)

DA Delivery AddressMP Manufacturing Plant

01 Outside Inspection Agency

PL Party to Receive Purchase Order

PR PayerSE Selling Party

33 DC12 'JANUARY 29 1993


865• PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 00301 ODOD N1 - NAME

SU Supplier/Manufacturer

SW Sealing Company

UC Ultimate Consignee

VN Vendor

ZZ 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 Notes:1. When N101 is code BT, BY, 01, or PR, use code 10. When N101 is code MP, SE, SU, VN, PL, or ZZ, usecode 33 if a valid CAGE codes has been assigned, or code ZZ if a temporary CAGE code has been assigned.When NI01 is code DA, ST or UC, code 10, code 33, or code ZZ can be used. Code 10 would be used if theMark For is a DoD address with a DoDAAC. If the Mark For is a contractor, codes 33 or ZZ are used whena CAGE or temporary CAGE cod. has been assigned. In all other cases, the long-line address must be given(e.g., using NI02, etc.). When code BY is used, it will be understood that code 10 is this application refers tothe DFASRS Appendix G (formerly Appendix N) code. When N101 is code SW, use code 33, ZZ, or the longline address.

2. Use code ZZfor a temporary CAGE code when the permanent one is not yet assigned.

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

10 Department of Defense Activity Address Code (DODAAC)

33 Commercial and Government Entity (CAGE)

ZZ Mutually Defined

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

DC12 JANUARY 29 1993 34

DEPARTMENT OF DEFENSEDRIAFT IMPLEMENTATION CONVENTION

865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTN2 ADDITIONAL NAME INFORMATION ANSI ASC X12 VERSION/RELEASE 0030101DOD_

Segment: N2 Additional Hame Information

Level: Header

Loop: N1Optional Usage. Optional

Max Use: 2

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

Data Element SummaryREF. DATADES. ELEMENT NAME ATTRIBUTES

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

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

35 DC12 JANUARY 29 1993


865- PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD N3 . ADDRESS INFORMATION

Segment: N3 Address informationLevel: Header

Loop: NIOptional Usage: Optional

Max Use: 2

Purpose: To specify the location of the named party

Data Element Summary"REF DATADES. ELEMENT NAME ATTRIBUTES

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

Optional N302 166 Address Information 0 AN 1/35Address information

DC12 . JANUARY 291993 36


865 - PURCHASE ORDER CHANGE ACKNOWLEDGMENTN4- GEOGRAPHIC LOCATION ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: N4 Geographic LocationLevel: Header


Max Use: 1

Purpose: To spec.fy the geographic place of the named party


2. If N401 is present, then N402 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. ELEMENT NAME ATMRIBUTES

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

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

Optional N403 116 Postal Code 0 ID 4/9Code 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 212Code identifying the country.

Optional N405 309 Location Qualifier 0 ID 1/2Code identifying type of location.

Conditional N406 310 Location Identifier C AN 1/25Code which identifies a specific location.

37 DC12. JANUARY 29 1993


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD REF • REFERENCE NUMBERS

Segment: REF Reference NumbersLevel: Header

Loop: N1


Max Use: 12




2. For change (code AC) and exception (code AE) acknowledgments, only send change orexception items. For Detail and No Change acknowledgments (code AD), repeat back theinformation from the 860 Buyer Purchase Order Change Request. Use this segment if the original860 included the Header level NI loop REF Segment.

3. For contractor initiated changes to an 850 Purchase Order, use this segment if the original 850included the Header level NJ loop REF Segment and the changes apply to the REF Segment.Contractor can also use this segment to include any additional reference numbers needed to helpclarify the change.

Data Element SummaryREF. DATADES. ELEMENT NAME ArTRIBUTES


Implementation Note:The 860 Buyer Purchase Order Change Request and 850 Purchase Order use code IT for the buyer's officesymbol, ard code DSfor the criticality designator.

DS Defense Priorities Allocation System (DPAS) Priority Rating

IT Internal Customer Number



DC12 . JANUARY 29 1413 38


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTPER - ADMINISTRATIVE COMMUNICATIONS CONTACT ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: PER Administrative Communications Contact

Level: Header

Loop: N1


Max Use: 3

Purpose: To identify a person or office to whom administrative communicationsshould be directed

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

Implementation Notes:1. Contractor can elect to use this segment to indicate their contact person.

2. For contractor initiated changes to an 850 Purchase Order, use this segment if the original 850included the Header level N1 loop PER Segment and the changes apply to the PER Segment.Contractor can also use this segment to include any additional contact information.

Data Element SummaryREF. DATADES. ELEMENT NAME ATmrUTfS

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

Implementation Notes:1. Codes used should correspond to the codes used in the related 860 Buyer Purchase Order ChangeRequest or 850 Purchase Order. Refer to the notesfor the 860 or 850 PERO] in the NI loop for moreinformation on the codes used.

2. Contractor can use code SUfor their contact person.

SLU 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:Use any code although code EM is preferred.

EM Electronic MailFX FacsimileTE Telephone

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

39 DC12. JANUARY 29 1993


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD POC . LINE ITEM CHANGE

Segment: POC Line Item ChangeLevel: Detail

Loop: POC Repeat: 10000Optional Usage: Optional

Max Use: 1

Purpose: To specify changes to a line item

Syntax: 1. If POC03 is present, then POC04, and POC05 must be present.

2. If POC07 is present, then POC06 is required.


4. If POCl 0 is present, then POC11 is required.









Comment: POC01 is the purchase order line item identification.

Implementation Notes:1. Use the POC Segment and related segments in the POC loop to acknowledge specific line itemswhen the BCA02 Acknowledgment Type code is AC, AE or AD.


3. For contractor initiated changes to an 850 Purchase Order, use this segment and loop forchanges at the line item level.


Optional POC01 350 Assigned Identification 0 AN 1/6Alphanumeric characters assigned for differentiation within a transaction set.

Implementation Note:The line item number (or counter) assigned by the related 860 Buyer Purchase Order Change Request or 850Purchase Order.

Mandatory POC02 670 Change or Response Type Code M ID 2/2Code specifying the type of change to the line item.

DC12 . JANUARY 29 1993 40


865 - PURCHASE ORDER CHANGE ACKNOWLEDGMENTPOC LINE ITEM CHANGE ANSI ASC X12 VERSION/RELEASE 003010DOD_

Implementation Note:Any applicable code may be used. Some of the more common ones are Al for add additional items; CA forchanges to line items; CB for change of dates; DIfor deleting items; PC for price change; QD for quantitydecrease; Qlfor quantity increase; RE for replacement item; or RS for reschedule.

Al Add Additional Item(s)

CA Changes To Line Items

CB Change of Date Terms

DI Delete Item(s)

PC Price Change

OD Quantity Decrease

QI Quantity Increase

RE Replacement Item

RS Reschedule

Optional POC03 330 Quantity Ordered 0 R 1/9Quantity ordered.

Conditional POC04 671 Quantity Left to Receive C R 1/9Quantity left to receive as qualified by the unit of measure.

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

Implementation Note:DoD uses DoD 5000.12M for unit of measure codes.

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

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

Implementation Note:Any applicable code may be used. Some of the more common codes are CT for an order placed against apriced contract, ES when the price is estimated, and QT when the price is based on a quote.

CT Contract

ES Estimated

OT Quoted

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

Implementation Notes:I. Use any code. Selected codes should be the same as those used in the 860 Buyer Purchase Order ChangeRequest or the 850 Purchase Order. The 850 may use information from the original RFQ or provided in thequote. For contractor initiated changes to an 850, relates to the information in the P0106 - refer to the notefor the 850 P0106 for additional information on the codes used.

2. Code IN is the line item number from an RFQ. If code VN is used, this is the seller's quote line itemnumber.

3. When code PD or SV is used, insert the noun or verb description in a Product/Service Id data elementsuch as POC09.

FS National Stock Number

FT Federal Stock Classification

41 DC12 . JANUARY 29 1993


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DO POC - LINE ITEM CHANGE

IN Buyer's Item Number

MG Manufacturer's Part NumberPD Part Number Description

PG Packaging Specification Number

SI Standard Industrial Classification Code

SV Service Rendered

SW Stock Number

VN Vendor's (Seller's) Item Number

VP Vendor's (Seller's) Part Number

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


Implementation Note:Use POCIO through POC27 in pairs (for example,. POCIO and POClI) as required, to carry additionalinformation regarding the product or service.

Conditional POC1 1 234 Product/Service ID C AN !130Identifying number for a product or service,










DC12. JANUARY 29 1993 42


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTPOC - LINE ITEM CHANGE ANSI ASC X12 VERSION/RELEASE 003010DOD_








43 DC12 . JANUARY 29 1993


865 - PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD CTP- PRICING INFORMATION

Segment: CTP Pricing InformationLevel: Detail

Loop: POCOptional Usage: Optional

Max Use: 25

Purpose: To specify pricing information

Syntax: 1. If CTP02 is present, then CTP03 is required.



Comments: 1. Example of use of CTP03 and CTP04.

PRICE QUANTITY RANGE1.00 0 to 9990.75 1000 to 49990.50 5000 to 99990.25 10000 and above

CTP03 CTP041.00 00.75 10000.50 50000.25 10000

2. Example of use of CTP03, CTP04 and CTP07.

CTP03 CTP04 CTP071.00 0 0.900.75 1000 0.900.50 5000 0.900.25 10000 0.90

3. CTP07 is a multiplier factor to arrive at a final discounted price. Amultiplier of 90 would be the factor if a 10% discount is given.

Implementation Notes:1. This segment is not required for simple (code AK) acknowledgments.

2. For changes (code AC) and exceptions (code AE) acknowledgments, only send change orexception items. For Detail and No Change acknowledgments (code AD), repeat back theinformation from the 860 Buyer Purchase Order Change Request Header level CTP Segment.

3. This segment is not used for contractor initiated changes to an 850 Purchase Order.

Data Element SummaryREF. DATADES. ELEMEIT NAME ATTRISUTES

Not Used CTP01 687 Class of Trade Code 0 ID 2/2

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

DC12 . JANUARY 29 1993 44


865 - PURCHASE ORDER CHANGE ACKNOWLEDGMENTCTP . PRICING INFORMATION ANSI ASC X12 VERSION/RELEASE 003010DOD_

Implementation Notes:1. Use any code as appropriate for the acknowledgment.

2. Use code UCP to indicate the original unit price and use code EUP to indicate the revised unit price.

EUP Expected Unit PriceUCP Unit cost price

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

Optional CTP04 380 Quantity 0 R 1/10Numeric value of quantity.

Conditional CTP05 355 Unit of Measurement Code C ID 212

Code identifying the basic unit of measurement.

Optional CTP06 648 Price Multiplier Qualifier 0 ID 3/3Code indicating the type of price multiplier.

Conditional CTP07 649 Multiplier C R 1/10Value, identified by price multiplier qualifier, to be used to multiply price to obtaina new value.

45 DC12 . JANUARY 29 1993


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 0030101DOD MEA- MEASUREMENTS

Segment: MEA MeasurementsLevel: Detail


Max Use: 40Purpose: 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.



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

Implementation Notes:1. This segment is used any time a measurement needs to be described for an item in theacknowledgment or contractor initiated change to an 850 Purchase Order.

2. It is also used to describe any variation in quantity applicable at the line item level.

3. Max use is 10.

Data Element SummaryREF. DATADES. ELEMEN NAME ATrMMUTES

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

Implementation Notes:1. Use any code that may be applicable for describing measurements. Also refer to the codes used in therelated 860 Buyer Purchase Order Change Request or 850 Purchase Order Detail level MEA01.

2. Code CT is used when the related 860 or 850 also uses the CT for variation in quantity.

CT Counts


Implementation Notes:1. Use any code that may be applicable. Also refer to the codes used in the related 860 Buyer PurchaseOrder Change Request or 850 Purchase Order Detail level MEA02.

2. Code PO is used when the related 860 or 850 also uses the code PO for variations in quantity.

PO Percent of Order

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

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

DC12 . JANUARY 29 1993 46


865 - PURCHASE ORDER CHANGE ACKNOWLEDGMENTMEA • MEASUREMENTS ANSI ASC X12 VERSION/RELEASE 003010DOD

Implementation Notes:1. Use any code that may be applicable. Also refer to the codes used in the related 860 Buyer PurchaseOrder Change Request or 850 Purchase Order Detail level MEA04.

2. Code P1 is used when the related 860 or 850 also uses the code P1 for variation in quantity.

P1 Percent

Conditional MEA05 740 Range Minimum C R 1/10The value specifying the minimum of the measurement range.

Implementation Note:Used to indicate the variation in quantity under.

Conditional MEA06 741 Range Maximum C R 1/10The value specifying the maximum of the measurement range.

Implementation Note:Used to indicate the variation in quantity over.

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


Not Used MEA09 752 Surface/Layer/Position Code 0 ID 212

47 DC12 . JANUARY 29 1993


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD PID- PRODUCT/ITEM DESCRIPTION

Segment: PID Product/Item DescriptionLevel: Detail

Loop: PID Repeat: 1000


Max Use: 1Purpose: 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 list

being 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. DATADES. ELEMEWT NAME ATIMOIUTES

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. When POC08 uses codes SV or PD, PID05 can carry an additional description of the services rr item ifnecessary.

2. PID05 can also be used to explain a contract condition if appropriate for a contractor initia:,ed changeorder to a related 850 Purchase Order.

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

DC12 JANUARY 29 1993 48


865- PURCHASE ORDER CHANGE ACKNOWLEDGMENTMEA. MEASUREMENTS ANSI ASC X12 VERSION/RELEASE 093010DOD_

Segment: MEA MeasurementsLevel: Detail

Loop: PIDOptional Usage: Optional

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.



Comment: When citing dmensional 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 in the preceding PIDSegment.

Data Element Summary"NEF. DATA

DES. ELEMENT NAME ATTRIBUTES

Optional MEA01 737 Measuremen t Reference ID Code 0 ID 212Co.,j specifying the application of physical measurement cited.

Implementation Note:Use any code. Translation may be required.



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

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 MEAO" 935 Measurement Significance Code 0 ID 2/2


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

49 DC12 JANUARY 29 1993


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD PWK • PAPERWORK

Segment: PWK PaperworkLevel: Detail


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 codenumber.

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. This Detail level PWK Segment in the 860 Buyer Purchase Order Change Request or 850Purchase Order is used to indicate what paperwork must be provided with the delivery or asspecified in the order.

2. For acknowledgments, the contractor can use this segment to indicate how the paperwork willbe sent to the buyer.

3. For contractor initiated change orders to an 850, the contractor can use this segment to indicateany changes to the PWK information.


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

Implementation Note:Codes used should correspond to the codes used in the related 860 Buyer Purchase Order Change Request or850 Purchase Order Detail level PWK.

CP Certificate of Compliance (Material Certification)

MR Material Inspection and Receiving Report

MS Material Safety Data Sheet

PD Proof of Delivery

SN Shipping Notice

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

Implementation Notes:1. Any code can be used, but code FL is prtferred.

2. For acknowledgments, contractor can use the PWK02 to indicate the method they will use to send therequested paperwork.

BM By Mail

EL Electronically Only

WS With Shipment (With Package)

DC12 . JANUARY 29 1993 50


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTPWK . PAPERWORK ANSI ASC X12 VERSION/RELEASE 003010DOD_

Optional PWK03 757 Report Copies Needed 0 NO 1/2The number of copies of a report that should be sent to the addressee.

Not Used PWK04 98 Entity Identifier Code 0 ID 2/2

Not Used PWKO5 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.

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

51 DC12. JANUARY 29 1993


865 . PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD PKG- MARKING, PACKAGING, LOADING

Segment: PKG Marking, Packaging, LoadingLevel: Detail


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, tolerances

weights, counts, physical restrictions, etc.

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

3. PKGO1 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).

Data Element Summary"REF. DATADES. ELEMENT NAME ATTRIOUTES

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

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. Translation may be required.

2. Use code 35for Unitizing; code 36 for PackiPreservation; code 37for Packing.

Conditional PKG03 559 Association Qualifier Code C ID 2/2Code identifying the association assigning the code values.


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.


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

DC12 . JANUARY 29 1993 52


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTPKG - MARKING, PACKAGING, LOADING ANSI ASC X12 VERSION/RELEASE 003010DOD

Implementation Note:Use if any code, or string of codes, is longer than can be carried in PKGO4.

53 DC12 JANUARY 29 1993


865 PURCHASE OPDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD P04 ITEM PHYSICAL DETAILS

Segment: P04 Item Physical DetailsLevel: Detail


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.

3. If P0408 is present, then P0409 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 P041 0.

Data Element SummaryREF. DATADES. ELIEN3T NAME ATTRIBUTES

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

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 identifying the type of packaging. Part 1. Packaging form. Part 2.Packaging Material.

Implementation Note:These are the ANSI ASC X12 codes. A translation table will be required to connect them to DoD codes wherethe DoD codes are different than the ANSI ASC 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.

DC12 . JANUARY 29 1993 54


865 • PURCHASE ORDER CHANGE ACKNOWLEDGMENTP04 - ITEM PHYSICAL DETAILS ANSI ASC X12 VERSION/RELEASE 003010DOD



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



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.



55 DC12 JANUARY 29 1993


865 . PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD REF- REFERENCE NUMBERS

Segment: REF Reference Numbers

Level: Detail


Max Use: 12





Implementation Note:Use any applicable code for the line item level, e.g., qualifier codes RQ or IL when the requisition orpurchase request are different at the line item level. Use code AX for the ACRN; use code DX for the RFQnumber; use code IX for the RFQ line item number; and use code PR for the price quote number.



DC12. JANUARY 29 1993 56


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTFOB . F.O.B. RELATED INSTRUCTIONS ANSI ASC X12 VERSION/RELEASE 003010DOD

Segment: FOB F.O.B. Related InstructionsLevel: Detail

Loop: POC


Max Use: 1

Purpose: To specify transportation instructions relating to shipment

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




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

2. FOB02 is the code specifying transportation 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 Notes:1. Use this segment if the if the original 860 Buyer Purchase Order Change Request included theDetail level FOB Segment and the 865 BCA02 Acknowledgment Type code is AC, AE, or AD.

2. For change (code AC) and exception (code AE) acknowledgments, only send change orexception items. For Detail and No Change acknowledgments (code AD), repeat back theinformation from the 860.

3. This segment is used when a contractor initiates a change to an 850 Purchase Order and thechanges apply to the Detail level FOB information. This FOB Segment is used when the FOBinformation applies to the specific line item. The FOB Segment in the NI loop is used when morethan one FOB condition applies to a specific address for a specific line item.

Data Element SummaryREF. DATADES. ELEMENT NAME ATTrIUTES

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

DF Defined by Buyer and Seller


Implementation Note:Code ZZ is used when the FOB point is listed as Other than the destination or origin.

DE Destination (Shipping)OR Origin (Shipping Point)ZZ Mutually Defined


57 DC12 , JANUARY 29 1993


865 - PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE O03010DOD_ FOB -F.O.B. RELATED INSTRUCTIONS

Implementation Note:FOB03 carries the location of a site when FOB02 is code ZZfor other.

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

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


Implementation Notes:1. Inspection or acceptance site. They are assumed to be the same unless specified otherwise.

2. Use code ZZ when the inspection and acceptance points will not be the same.

DE Destination (Shipping)

OR Origin (Shipping Point)ZZ Mutually Defined


Implementation Note:If FOB06 is code ZZ, identify the locations of the inspection and acceptance points.

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

Not Used FOB09 352 Description C AN 1/80

DC12. JANUARY 29 1993 58


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTDTM o DATE/TIME REFERENCE ANSI ASC X12 VERSION/RELEASE 003010DOD

Segment: DTM Date/Time ReferenceLevel: Detail

Loop: POC


Max Use: 10

Purpose: To specify pertinent dates and times

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

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


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 002 for the required delivery date when it applies to the entire line item. Dates should reflect thedate information for the related 860 Buyer Purchase Order Change Request or 850 Purchase Order.

2. The SCH segment is used when deliveries will differ by quantity or date.

3. For acknowledgments, contractor may elect to include dates to reflect planned or estimated delivery dates.

4. For contractor initiated changes to an 850, contractor may elect to include expected, scheduled, orestimated delivery dates.

002 Delivery Requested

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

59 DC12 JANUARY 29 1993


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD LDT- LEAD TIME

Segment: LDT Lead TimeLevel: Detail

Loop: POC


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. Delivery date w;ll be provided in this segment as a set number of calendar days after receipt oforder or in the DTM segment as an actual date. If the latter is used, omit this segment.

2. For acknowledgments to an 860 Purchase Order Change or contractor initiated changes to an850 Purchase Order, contractor may elect to include expected, scheduled, or estimated deliverydates.

Data Element Summary"REF. DATADES. ELEMENT NAME ATTR IUTES

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/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

DC12 JANUARY 29 1993 60


865 PURCHASE ORDER CHANGE ACKNOWLEDGMENTSCH , UNE ITEM SCHEDULE ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: SCH Line Item Schedule

Level: Detail


Max Use: 200

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: SCHOS specifies the interpretation to be used for SCH06 and SCH07.

Implementation Note:This segment is used to describe a partia! delivery at the line item level.

Data Element Summary

ElP. DATAonE. ELB9EMT NAME ATTRIBUTES

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

Mandatory SCH02 355 Unit of Measurement Code M ID 2/2

Code identifying the basic unit of measurement.

Not Used SCH03 98 Entity Identifier Code 0 ID 212

Not Used SCH04 93 Name C AN 1/35

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

Implementation Notes:1. Code 002 is used for the required delivery date in the related 860 Buyer Purchase Order Change Requestor 850 Purchase Order.

2. For acknowledgments, contractor may elect to include dates to reflect planned or estimated delivery dates.

3. For contractor initiated changes to an 850, contractor may elect to include expected, scheduled, orestimated delivery dates,

002 Delivery Requested

Mandatory SCH06 373 Date M DT 6/6

Date (YYMMDD).

Not Used SCH07 337 Time 0 TM 414

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

Not Used SCH09 373 Date C DT 6/6

Not Used SCH10 337 Time 0 TM 4/4

61 DC12 .JANUARY 29 1993


865. PURCHASE ORDER CHANGE ACKNOWLEDGMENTANSI ASC X12 VERSION/RELEASE 003010DOD MAN . MARKS AND NUMBERS

Segment: MAN Marks and Numbers

Level: Detail


Max Use: 10

Purpose: To indicate identifying marks and numbers for shipping containers

Data Element Summary"'EF. DATA

DES. EL.EM(T NAME AIWrtJTES

Mandatory MAN01 88 Marks and Numbers Qualifier M ID 1/2Code specifying the application or source of Marks and Numbers (87).

Implementation Note:Code L is used to indicate that the change order has mark for instructions in addition to ship to information

at the line item level.

Mandatory MAN02 87 Marks and Numbers M AN 1/45

Marks and numbers used to identify a shipment or parts of a shipment.

Implementation Note:Use to enter Mark For information that cannot be carried in the NI-N4 segments.

DC12 . JANUARY 29 1993 62


865 . P.O. CHANGE ACKNOWLEDGEMENT/REQUES" - SELLER INITIATEDAMT. MONETARY AMOUNT ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: AMT Monetary Amount

Level: Detail


Max Use: 1

Purpose: To indicate the total monetary amount.

Comments: 1. If AMT is used in the detail area of transactikn 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 thosetransact!--' Gets, then AMT01 = TT.


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

Implementation Note:Use code I for the line item total.

I Line Item Total

Mandatory AMT02 782 Monetary Amount M R 1115

Monetary amount.

Implementation Note:The total amount of the line item.

63 DC12 JANUARY 29 1993


865 * P.O. CHANGE ACKNOWLEDGEMENT/REQUEST -SELLER INITIATEDANSI ASC X12 VERSION/RELEASE 003010DOD N9- REFERENCE NUMBER

Segment: N9 Reference Number

Level: Detail


Max Use: 1

Purpose: To transmit identifying numbers and descriptive information as specifiedby the reference number qualifier

Syntax: At least one of N902 or N903 must be present.


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

Implementation Notes:1. Use any code that helps clarify the line item.

2. Codes used should reflect information sent in the related 860 Buyer Purchase Order Change Request or850 Purchase Order.

Conditional N902 127 Reference Number C AN 1/30Reference number or identification number as defined for a particularTransaction Set, or as specified by the Reference Number Qualifier.

Conditional N903 369 Free-form Description C AN 1/45Free-form descriptive text.

Not Used N904 373 Date 0 DT 6/6

Not Used N905 337 Time 0 TM 4/4

DC12 JANUARY 29 1993 64


865s P.O. CHANGE ACKNOWLEDGEMENTIREQUEST - SELLER INITIATEDMSG. MESSAGE TEXT ANSI ASC X12 VERSION/RELEASE 00301 0DOD_

Segment: MSG Message TextLevel: Detail


Max Use: 1000

Purpose: To provide a free form format that would allow the transmission of textinformation.

Comment: MSG02 is not related to the specific characteristics of a printer, butidentifies top of page, advance a line, etc.

Data Element SummaryREF. DATADES ELEMENT NAME ATTRIEs

Mandatory MSGO1 933 Free-Form Message Text M AN 1/264Free-form message text.

Not Used MSG02 934 Printer Carriage Control Code 0 ID 2/2

65 DC12 - JANUARY 29 1993


865 . P.O. CHANGE ACKNOWLEDGEMENT/REQUEST -SELLER INITIATEDANSI ASC X12 VERSION/RELEASE 003010DOD Ni NAME

Segment: N1 NameLevel: Detail


Max Use: 1

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



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

Data Element SummaryREF. DATADES. ELEMBIT NAME ATTRIBUTES

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

Implementation Notes:1. Codes used should reflect codes used in the related 860 Buyer Purchase Order Change Request or 850Purchase Order.

2. Typical codes used are ST for ship to information and code UCfor Mark For information when the MarkFor information is an address.

ST Ship ToUC Ultimate Consignee

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

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

Implementation Notes:1. When NIO1 is code ST or UC, code 10 is used when it is a DoD address. Code 33 is ZZ is used forcontractor addresses.

2. Code 33 is used when a CAGE code has been assigned to a contractor. Code ZZ is used when a temporalyCAGE code has been assigned to a contractor.

3. A long line address (N.'02) may be used when no code number applies.

10 Department of Defense Activity Address Code (DODAAC)33 Commercial and Government Entity (CAGE)

ZZ Mutually Defined

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

0C12. JANUARY 29 1993 66


865 • P.O. CHANGE ACKNOWLEDGEMENT/REQUEST - SELLER INITIATEDN2 ADDITIONAL NAME INFORMATION ANSI ASC X12 VERSION/RELEASE 003010DOD

Segment: N2 Additional Name Information

Level: Detail

Loop: N1


Max Use: 2

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

Data Element SummaryREF. DATA0ES. ELEMENT NAME ATTHMUTES

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

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

67 DC12. JANUARY 29 1993


865 • P.O. CHANGE ACKNOWLEDGEMENT/REQUEST - SELLER INITIATEDANSI ASC X12 VERSION/RELEASE 00301 ODOD N3 ADDRESS INFORMATION

Segment: N3 Address InformationLevel: Detail


Max Use: 2

Purpose: To specify the location of the named party

Data Element SummaryREF. DATADES. ELEMENT NAME ATn IDUTES

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

Optional N302 166 Address Information 0 AN 1/35Address information

DC12. JANUARY 29 1993 68


865 - P.O. CHANGE ACKNOWLEDGEMENT/REQUEST -SELLER INITIATEDN4 GEOGRAPHIC LOCATION ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: N4 Geographic LocationLevel: Detail

Loop: NIOptional Usage: Optional

Max Use: 1Purpose: To specify the geographic place of the named party


2. If N401 is present, then N402 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.


DES. ELEMENT NAME ATTRIUrTES

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

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

Optional N403 116 Postal Code 0 ID 4/9Code 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 a

foreign country).

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

Implementation Note:Generally not required. Only include the N404 if the related 860 Buyer Purchase Order Change Request or850 Purchase Order included an N404.

Not Used N405 309 Location Qualifier 0 ID 1/2

Not Used N406 310 Location Identifier C AN 1/25

69 DC12 . JANUARY 29 1993


865 . P.O. CHANGE ACKNOWLEDGEMENT/REQUEST -SELLER INITIATEDANSI ASC X12 VERSION/RELEASE 003010DOD CTI'- TRANSACTION TOTALS

Segment: CTT Transaction TotalsLevel: Summary


Max Use: 1

Purpose: 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.

Data Element SummaryREA. DATADES6 ELEMENT NAME ATTRIBUTES

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

Implementation Note:Accumulation of number of POC Segments when appropriate for detailed acknowledgments and contractorinitiated change orders to an 850 Purchase Order.

Optional CTT02 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:CTT02 is the sum of the value of quantities ordered (POCO3) for each POC Segment when appropriate.

Not Used CTT03 81 Weight 0 R 1/8

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

Not Used CTT05 183 Volume 0 R 1/8Not Used CTT06 355 Unit of Measurement Code C ID 2/2Not Used CTT07 352 Description 0 AN 1/80

DC12 JANUARY 29 1993 70


865- P.O. CHANGE ACKNOWLEDGEMENTJREQUEST- SELLER INITIATEDAMT MONETARY AMOUNT ANSI ASC X12 VERSION/RELEASE 003010DOD

Segment: AMT Monetary Amount

Level: 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. ItAMT 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 ATMIStrTn "

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

Mandatory AMT02 782 Monetary Amount M R 1/15Monetary amount.

Implementation Notes:1. The total amount of the order when appropriate for detailed acknowledgments or contractor initiatedchanges to an 850 Purchase Order.

2. Not used for single line awards.

71 DC12 • JANUARY 29 1993


865- P.O. CHANGE ACKNOWLEDGEMENT/REQUEST -SELLER INITIATEDANSI ASC X12 VERSION/RELEASE 003010DOD SE - TRANSACTION SET TRAILER

Segment: SE Transaction Set Trailer

Level: Summary

Loop: _

Mandatory Usage: Mandatory

Max Use:

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.


Mandatory SEO1 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 ST02.

DC 12 . JANUARY 29 1993 72



4.0 ASC X 12 FORMS

In this chapter, applicable ASC X12 forms are presented.



K1~A 9PNIIATIN U&NUAL

ASC X12 Wow Requet Fa0n

ASC X1 2 Now P•j PMMo F~m

ASC X12 Now Trmacftn Set Deo~bpiset Forn

Foan for Now cw Revisd Appendix A Code Sw€o Reference

Dosmmor Prevpwaon fr n"mUo Gu~nm en Conf Sunuwu

Sawnis TrwwW Fornm

ASC X12 BaNX Comnih Rsponw Loner Fomn

ASC X12 SUmde Order Form

PALL, 1141 VIIl- I


GIPAMAIWf OF 01,

~~v. u~so~~go DM NUMBER _______

DATE SUBMrTTED ASC X1 2(eceftOn)

WORK REQUEST FORM

AUL REQUESTS MUST BE TYPED or puinted legibly In black ink. ComPlete both sides

1. TO USE T145 FORMI FOR SUPPONT?4 DATA MANITENANE FOR A NEW DRAFT STANDARD OR X12 INTERPRETATION. ft 20mqswement on ON feem. UMse-d, aimmn nasmammay. Us firt IN no aegmieni. menSO now @1sift oimn'e/esdee/oae nmbuThen NO ewabon 0 eOsuo" OepIenm No d=aimeeerns/of ee/0 OAA0 SOIM& Then IM W 01W (er.g.. X12.5. X12.6).

L. TO USE THIS FORM~ TO AEOUES A CHANG TO AN VQSTiNG STANDARD, urNG nPwas alk A9w Fqei om 10 NO aN dugea forens venmacfn usK one megmt wes on@ = urnas. worna dims selement. AN wedans mugM be ameed. Aftwnenbt may be usedfar sonlinusabn wid elOul be nuwflbetd.

&. TO USE THIS FORM TO REOUEST A PROPOSED NIEW X12 PROJECT. 00-mp-es SedonA&Poieappe/ap n eleMntw feaftarekos noo ui Seaon & Pmovide a eWiON of moebuwaine need w4d pmedirnan for me new projeet in Se~a n C/Pat I TheWeb ~queu wiS be oewuded U en eepopdXIS eubeommdibee tar Melym an p MReeun sop A! Froes mpropei

Circle One. (1) Now Stendad Su&apoitng Data Maintenance (use attachments)(2) Ex~sqn Standard Muintenance Rwquest (see Section 0)(3) Request for New X12 Project

Pdronyip /abbrevAuftnsa oIngb added te me 4 Idem heduryqepeodl unte mug be &leet e-plelned. Peovldg Appendh AsodeIeo IefAeenme for af eaemaly pubir~ed eode Ofbedd. A mipinn Rle tarfw v~ N ial bmeeqae" euppoet for me abenge requeeleg

"A6be iemed 1 elm u O*Nm.

A. SUSUMITFE INFORMATION

Submitte. Name _____________ _______

Address __ _ _ __ _ _

Addrss/MP _______________________

Phon_ ___ __

Indicate the X12 subcomlff*W or task 9osp whose position Is represented hersI declare tha #thi represenis the offaid position of X12 WORK GROUP: __________

establihe at the meetin dated _______

9. PRO5POSED WOWL Ut the specific dunge to the standards being requested. GGv the name a Iassociated identilisu of the standard sgnswft data elmeTs and codes affeote.

4.0.4 BASELINE AS OF: JANUARY 2,5IM

DEPARUOCT OF OWISERDRAFT NPLEMW4ATION CONTEosi

Pawe Two

C. REASON FOR CHANGE:paul 1: List the veusion/releaa d the standard you are usin or Usirg as a reference. Name the wansection satthat Is being/wiN be used that dicttes fth requeated changed. List affectd segmen and dat elemeufs or'herw sandards. Provide arty reference mnmbers/10s.

Reference Source Version 2/Re1lease__Transaction Set Used______ _________

Segmeet Affected _______ _______

Data Elementl Affected ___________

Other Stndard_____ ______

Ponl II: Explain why you need fth proposed change. Provide a complete scetiarlo 00thals wiw whah businessfunction, operation or problem is ftht we be satisie by a change to the standard. The X 2.1 T ecnl,Assessment Subcommnittes requires enough Intomation in fthi Pant 11 to be afle to propose en elhnteo solution IF

0. ItIIATOS you chrAm' (2) an Pape 1, complete thi section. TO ensure toa 40 uw clfIoe a o yawrproposed chiange awe recorded and do~ your request is conopwt. circle below d secion of the stanardsWaffcted by fth proposed chengs

ThANSACTION SET Nw Pwpss./tmps Towi Nmw/CmnuwuW

Do Paset is Ie u

SEGMENT krwanlWs DOuIrmNA"~i Cm Omm 911isef in Sso@u

ft~v Of S Nmm So Fwi Nm k

DATA ELEMENT No"s O uNO" V

CODE Addeaft Omm cuo ftocoo

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

ERRORS NOTED IN THE STANDARD (Gve pope no. end ow her ordlestonl:

SAOILDI AG OF: JANUARYU. im0 4.0.5

DEPARMMBT OF DUUIUEDRIAIFT NPLEMU0NTATION CONVENTION

PP No.______ __

(Secretariat Only)ASC X1 2

NEW PROJECT PROPOSAL FORMPROCEDURE: Ongy X12 subcommittees "may use this form to register new development activties as X12 projectproposais (PPs). Complete allpage.. PPs approved by the X12 Procedures Review Board will be registered andassigned a PP number by DISA. and a Transmittal Form will be Issued.

Date and complete the form below. Type or print legibly in black Ink and number all attachment pagesconsecutively. Submit to DISA prior to an ASC X1 2 meeting, or to X1 2J Technica Assessment Subcommitteeduring the subcommittees agenda, period at an ASC X1 2 meeting.

Date Submitted:Date, Approved by Subcommittee:

Subcommittee Name:Task Group HNam/No.:

Joint Development Subconmmittee (if any):

Circle one: (a) Trmnsaction Set (b) Gtidelln (c) Other

Prooec Working Title:

Official Delegate(s) for This Project To Be Nameed on Transmital Form:

Nameo Name_ _ _ _

company C~ompany__ _______

Address Addres_ _ __ _ _

Address/ZIP ______________Address/ZIP ______________

Telleph~one __________ ____Telephone_ _____________

4.0.6 BSELINE At OF: JANUARY 29, 1NM

OIPANTUIMIT OF DEFENSEDRAFT SWLEENTATION CONVENTION

A. PURPOSE AND SCOPE FOR THE PROPOSED WORK~ Provte a vWeldefnb purpoue/aope far thePfprmad-s work SeeX12 Design Adae and Guidein~es for rmqurownsff

3. BACKGROUND: PraMo dusk oMe Ib hslki hnrswewingdw 9;e -1w Who arethe expectd uer?HIw vAw the standard be used? WhtW buekiess Wxcd~fls) does It sewo?. If ft p oposed-standard overlaps thehotiIonalkYd an soodstig standard or ane In developmwi. provide oiUcaftnL If go p 9 pa not forea newSlanldad or gtgdelbt, describe the proaew In dom. (Uee amachmelw I nmeessry.)

C. OTHER STANDARD WiMVEWD If Sp0Icsae Mantify WWy Whe buelmss bRnngla. n tan dord wtaesknAr/rsltedto te propoest. ardiwiftsadrdws deIhlae (e.g., ANSI Accredited Stondards Committees)whio" wcMues may be invawaov or h~lacesd.

D. EXECTED CONTEN/GENEAL DESCRP 10N: (OFTMOAL) Stbnftte nay attach areliMiwy draft ofmhe proposed m standard or adhe uqxftVi docuiteinalon. O~cus now segmesa d@ elmews caM estruasuvres and chenge to X12.5 or X12.6 Ow awe required or eridconted. (Us afIvn- -s

SMILDE A@ OF: JANUARY 2s, 15U 4.0.7

DEPARTMENT OF DEFESEDRAFT PLEMIENTATION CONVENTION

FORM FOR NEW OR REVISED

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 eernal (non-X1 2) organization. Use one form for each new

reference. T"his 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 only one source for codes for the data element the title should be the same as thedata element name. If there are multiple codes referencing external code sources for the same data elemerL toshould approximate the code definition.

REFERENCE TITLE:

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

USED IN: DE No. , Code 1D

SOURCE: Provide the name of the publication which contain the code, rlefre d.

PUBLISHED IN:

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

Name/Atln of

Company

Address

Address

Address/ZIP

ABSTRACT: Briefly describe the publication, its purpose. and indicate what codes it contains,

ABSTRACT:

.BASELINE AS OF: JANUARY 3, 193W


DOCUMENT PREPARATION FOR t.419

INTERPRETATIONS, GUIDELINES AND CONTROL STANDARDS

These Instructions are provided to assist developers of interpretations, guidelines anid comarc structure which arerot transaction sets (Wo transaction sets use the New Transaction Set Developmert Form).

GENERAL- DISA provides tite page and front matter for publications and copyedlts the documert acorin toDISA house "t4.

REVISIONS: If the documnent Is a revision of a previously published Interpretation, guideline or stanidard, provide asummoaryofthe chages to thecorig'n that are containedin the document.

I INTERPRETATIONSA formal Interpretation of an X12TMd Standar is consierd pant of the body of standards when It is approved forpublIcation The kInerpretation draft should state the issu presented by the requedtor. state the FaproaeInterporetation, anid show as attachments any Work Requests that may be necessary to ~lc the Interpretationwithin the &ubec stanodard. The draft interpretation is processed lie any other subcommittee document.

II OL4DEUNESFor Publication purposes, guidelines awe treated Wie a journal article. Basic requirements arm given below.

ABSTRACT: ThisIs ia precis summary of the Purpose/Scope (see below), and may be Identical to kt 10 ttIs brisf(two paragraphs); otherwise sumrinwiethe purpose/scope. It shouid corntainsvoughotrmafti abeutSthedocume -nt to enable a r eader determine what the guideline is Inended to accomplish within an EDI environment.

PURPOSE AND SCOPE:- This stsmernt must Indicate purpose of the gukdeine e~g.. the businsess function oroeation addressed. Scope anid any spc Wi irAtdons of scope should be defined.

BODY OF TEXT This may be a onuber of subsections logically organized. Provide sections for fotreordintrodluction. definition of tarmw an concepts. tolerences and related standards methodology. speclflcations,requirmnts. discussion, and conclusions. as appropriate to the subjecL

ART AND GRAPHICS: Graphics or artwork necessary to Eustrate the document are encouraged. Providecamera-resdy copy 9 these are not already prepared and delivered on a WP diskete to OISA.

FOREWORD, FOOTNOTES1, APPENDICES: These may be used for purposese of clarity, Bustrotimn or generalkofntinlx not as 'pert of the gudltinalk A statement indicaltin the materia Is for Information purpowe arty andnot pant of the guidelin shlfd appea at the beghnning of aforeword or appendis

III CONTROL STRUCTURES AND OTHER STANDARDSFor publication purposes thee documnents are treated like guidelines (see Section If above). The requiremenits arethe same, with the addition of the folowing

NEW SEGMENTS AND DATA ELEMENTSI: These may beode&ie ihnte1dhwvesnete ersnchange to X12.22 and X12.3. they ahosd be speciWe on a Work Request Form attached to the drit.

RELATED X12TM STANDARDS AND OTHER REFERENCES: These shlld be Idetf'e -IMn a section within the to&t

BASELINE AS OF- JANUARY 20, IONs 4.0.9

DEPARMM WI OF DEFENSEDRAFT WIPLEMENTATION CONVENIfON

Pges TWO

FORMAT: wTt Draft Smaaidard fo TiW Use coiwlis Ul ftheW NXMd esta~ilim fte data corterta of the________Trmneala Set (j for use wlf~h the contsa of an BEcbarfc OMa inwercun (EOI)

winwiwoner The varwacton w (csi be used to .. )

C. PURPOSE AND0 SCOPE This esmuiwt mUst kuidcste Onhef i raW of cepablites of fte tramacin uL samwho the -ed - -s/reeulae am. Eiapl the bW~usinma i on or ape ation m 911Is addrasoed Follow ASC X12ONOl~ RUes wad Guidelns ami we "hi fomWa

FORMAT: Mthl ndwd providwtes Ice woma ad gesbblihes the data cuoftef of fte TuameactonSet widih the cora~ of an IEaionlc Date lnurechong "50) w~uknowt This vnnesacton so (can be used to...

D. TRANSACTON SET TAW J(5) For ea&* taie provide fte olowin' ft~i~offe FORMAT:

TANUE X

POSITION SEGMENT REQ. HAX * LOOP REPEAT NOTEHOA.-an rr-rILr 0K. USt. -COUNT *"- ,010 ST Transaction Set Header x4 I Note I2020 33 1eginning Segment For x I Cemment Iaet.

NOWe 1: 11s bda nole. NOME ere pert of fth go F- (uumewsere.Cioanewr A: This isda commsetw COMMENT am not pus of ft - -am Gsevre).

L APPEN0M XAMPLE Evw~egnowe um towente meaitofthe mpgooe twmmmsco and to;;Rlhi 4useN ideMa mnei udoy NO rCOgrible 'pCrop ainnny be used ianymiple

FIGURE : (OpUod) Use a piny popW dosumwt usin mock We. V useid. rea be accumtey mappedto Figre. Oalkosslgophissmumbe I 1 WIed so/a11 fothey be copiedd

FIGUOR 2 (W EXAMPLE): TfteO "a gw. d provide a BSeramies Seseawb to w*Wl to fth seder wtat id goingon in fte 1-p1e0 Add fth nowt In ft emaiipe the aswidk (0) reprees-s thedw data elesme separaor and fthN/L. detuamesp rerseaw 9fs sogmeaw toan*o.e Proesa 501 WewrAnidWo dima and ba meaag In two cokwiwualdetby-elde Z or =code me dideounged. *wne Virk useinee hIn an w~idaay - pi~ Is d . FORMAT:

USINESS SCENARIO- hIn* seemscnm s~m unerdXYZ PAW Ce~ate md V roe"v sidtekirspplie.Feaftai Pradok" ManLmawblg ftc... .c.

EDI TRANSRaSSON DATA (TRANSACTION SET PURPOSIEI DATA

ST'SXX'000S N/L begin Transaction Set 4XX; ControlNo. 000533'01*79600* N/L original Transmission; Ref. No.79600aet.



DM. Number_________

Document No.__ _ _ _(Developer Obtains from [ISA)

ASC X1 2

NEW TRANSACTION SET DEVELOPMENT FORM

INSTRUCTIONS: Use Othi form to submit a draft transaction sot for review by X12J Technical MAsessment until it istext processed by DISA. Use a new Transaction Set Development Form whenever revisions are proposed and ateot go Nas not yet been prepared by DISA.

ATTACHMENTS: Attach al pages; use Othi form as the first. Follow thes Instructions for prpepring materials.

The submitter must obtain a documenoit number assignment from DISA. Post itto this form (above).

Attach a List of Revision If the draft was previously reviewed by X12J or I this Is a re'.lsed/rodesignedtransaction sM standard requiring X12 ballt.

Use ONE Work Request Form to list ANl supporting data maintenance for the transaction sot and attach itto this form Propose new or revse codes for DE 143 and DE 479 at a minimum. If reuied.

A Transmittal Form must accompany this document when it IsI submitted to DISA for dlstrbtion.

Use the mostrecen XI3Tm Standards Development Workbook to checki your document for accuracy.

A. SUBMMTER INFORMATION

Submitter~ Name ____________________company ___

Address _ _ _ _ _ _ _ _ _

Address/ZIP_______________________

Indicate the X 12 subcommittee or task group woeposition Is represented here.I declare that this represents the official positio0n of X12 WORK GROUP: _________

established at fth meetin dated___________

I. ABSTRACT The Abstract is registered with the American National Standards Institute. it Is a precise summeryof the Purpose/Scope (see Section C below). It may be Identical to the Purpose/Scope IF that Is brief (twoparagraphs), otherwise surmmarize the purpose/scope. it -hemi contain enough wnormation about the standardto enable a potentili user determine what equivalent paper transaction it represents or what the standad isIntended to do. Follow dho format on page two.

BASLINE AS OF: JANUARY 29,5IM 4.0.11

DEPARTMENT OF DEFENSEDRAFT IPLEMENTATION CONVENTKM

ftl 5/10/90

SAMPLE TRANSMITTAL FORM

InftllizedKEY DATE: February 15, 100

DELEGATFS NAME John Do@

RESPONSIBLE SUBCOMMITTEE/TG* ASC X120 XX Subconvnhttes/TG4

TRANSACTION SET/GUIDEUNE TITLE X12.X ABC/XYZ TRANSACTION SET (G=X)

BALLOT Document No.

Current Document No. ASC X120/90051Previou Document No. ASC X120/90.004Protect Proposal No. PP40GAssociated WR/DM No. DM 012-190

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

DEVELOPMENT PHASE: ProMj proposal approval WOh approval for X12 vote.

Doment SubAmited for DISA Text Proga*. (DATE)Subcxomnft'ee Approven Drmf for Review by X12J. Tech Assesm'wt (DATE)X12J Tech Assessment Review (DATE)

PRB Approves Document for X12 Vote (DATE)

ORIGINAL BALLOT DATA (DISA):

Ballot Oosed Date (DATE)Tally/Comments Sent to Chai/Delegt (DATE)Tally Stats (Number and Permnt)

Ballots Malld (10•)Ballots ReUtned (_%)ApprovedApp w/Cammerd (_ )Disapproved (__%)Abstained

4.3.12 SBASELM AS OF: JMEUARY n, 1393

DEPARTMEN't OF DEFENSEDRAFT IMPLEMENTAMIN CON VENTION

Page Two

COMMENT RESOLUTION PHASE: See Sectionis A. 8 WnO C. If the subcommittee at aftY time decides to reballothe documerl. PRS approval is requird and response letter are not necessaary.

A. COMMENT RESPONSE LETTERS: An Open For~m must be schedied at the roet X1 2 meeting foloong theballot dosing date. AA those who coinmerwed recive a conwner response letter from the dlevelopingsubcommittee. DISA records thi process and hanldles the midin.

Open Forumi Date (DATE) ______

Responise Lettem Mailed Out by DISA (DATE)_ ___Rebmuta Period (30 days) Closes (DATE)______

ADJUSTED BALLOT DATA (DISA):304Oay Respons Review 00ose Date (DATE)______Tally/Commerfa Seuw to Chair/Delegaes, (DATE)_ ___Taly Stats (Number and PercW0t

SdlowtalMued (100%)Ballts Returned %Approved ( )A~ppw/Commew (W %

- Disapproved )Abstained (%

a. SUBSTANTIVE REVISEOW libf it cormmeis r~esut in sieutuien revisions to the documet thes arereviewd by X12j aOW prgocessed by 045'. The revised doctinert Is submitted to X12 voters for a 30-day reviewperlodl. DISA recrds ethi process/hondles maling. Subcormlztees should conlduct 30.daY reviews for responsletters/revised documrts conawisutdy.

Subcommittee Approval of Revisions (DATE)______X12J Review of Revisiorts (DATE) ____

DISA Malls Revised Documert (DATE) ______

Substantive Revision 30.ay Review Closes (DATE) ______

ADJUSTED BALLOT DATA (DISA):30-Day Substantive Clwng Review Closed Date (DATE) ______

Tally/Comnrerfts SM to Chair/Delegates (DATE)_ ___Tally Stats (Nwrber and Percert)

Balts Malled (100%)Ballots ReturniedC..)

- Approved )App w/Commert L~Disapproved L_%)AbstakWd %

BASELINE AS OF: JANUARY 25, IMS 4.0.13

DEPARTMENT OF DEFENSEDRAFT IMPLEMENTATIION CONVENTION

Page Three

C. CONTINUING OBJECTIONS. If there are continuing disapprovals after the 30-day review period, thedocument/dlspprovals/resporIsO/COitflnukfl objections are malled to X1 2 members who originally cast a ballot,for another 30-day review, to give them an oppotnilty to change their vote.

Continuing Objecton Malled to Chair/Delegate by DISA (DATE) _____

DISA Malls Documerts (DATE)______30-Day Review Closes (DATE)______

FINAL ADJUSTED TALLY (DISA): Whenever any disapproval: are withdrawn, a letter to this effect must bereceived in wrktng by DISA.

Fina Tally Results Sort to Chair/Delegae (DATE)_____30-Day Review Stats (Adjusted Tally)

-Ballots Mailed (100%)-Ballots Retuned (_%)

Approved L-%)App wfCommert (_%)Disapproved (L-%)Abstalined (%

PRO APPROVAL PHASE: After the comment resoltilon period, the subcommnittee votes to submit the documeritto the PRB for approval to puLish.

Subcommittee Votes to Release to PRO (DATE)_____PRO Approves Publication (DATE)______

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

4.0.14 BASELME AS OF: JANUARY 2, Iee


page Four

TRANSM17TAL FORM INSTRUCTION:

GENERAL. This Tuwwnlne Poem is a TURNAOUND DOCUMENT wtlhrecoffts the hwy/cwwet stowu ofprolw documeiw. It is used to =w"twng bmilow b theen ' SweiStW ad 00the rI ooiwfle X12.I'Vo'mstio is cmdar"ve (add on). This form is suhded to the documer whenever It is issued for dlWrbAmo (k isnundawoy for himoldng documewo to 0D&,k X12J Tectwke Anowsamet ard the PRI). Doctanrmtcomurmbtm ram Mi rmird on each document, and now ruptu ame rqued wenever It is roved.

KlEY DATE: This is used to Wenty the Woea verinlof dth dociunert (date amocisre wMO the ewre' taraneithefoem udf

DELEGAM,. Each w-a~cwunat deeomm an kKdA*W (deleat) *=dom UWgow igiporielbfor thepimo eThe Sevarllat mig be I thmedls delepe dwige

INITIATION: Prlwmy dm is ecrde by DISAonfthe 111se 'fom eller Vie pre mpgo isapproiued byViePfI. The subomnbr chi* &W dmogWs) receve Mie I " ed Ttranew Fnw from VISA. U'ersar, theaore repordihlefermoording U't pp mprg vuhconuiiWe epproeldates. The ch*/deleatewE recesa copd fte update vaiuinf form wteneve It is towse by Mk8

UPDATING: At sech aapprpwe step, DISA wE POST fresh dif to fte fom. ADD fte now a ppeoprm blanks toVie fom i.nd SEND ft to tie ebaftomftee ctwi/delegat at aech sms chIange The delegae mM POST Mieformwith frsh di a och ~stmb~wipw forwihthesucorvimlsleis rupitle and SEND B wih theapproprkfe documen to fte 3@eorwarW

DASEUNIE AS OF: JANUARY 2,93, N401

DEPARTMENT OF WOMSSDRAFT NPLEMMEATION CONVENTION

&WIS A§C X12 BALLOT COMMENTRESPONSE LETTER FORMAT

AFTE MN XIS BALLOT Wh 111111ULENJ SJSOOUrMITE 40011T OI' NAYW TASK GROUP MUTNW W Mei kr~ 0 ald1 n - use. MWe O"Wuevn 4 proesns wuier (COP" u) goe "Mt yan ow mew"d v osinwi Vae ftNnbeh oft

owpoo wet ounnows, Us 11tG drosmeamh Wseen MG .n Th OPM $00e Ofs d commW melwb ~~us s be doh~vim "s~ubNowffsu C.

Thug M SM fllllsfs MW %M100 WO ii ~ 0es a gwaih best MW~ Wil be sWd 0 d u60uanNM OW a 011MAN0101nop'if a ge omnumeor. I" rjw51S woue vIMt-

OPTIINI 1: =O~ftC LWWE (MASE LIFTR TO All 0011111180011Yew way pupewam wr -ma toamn a d asmenom. Emwy uwmiom toos~iv uns be mp A -in pt~w Sow. Fo ubm~.immINK mm MOM ft omaur P112 memberWO& e nompfil) aid f usO aweduor ba mm Lkf pestompwe S os mU. U psidnes fft epea I y m"p ~p. to ameme ~iy aft S mU ruspe I d rn 10 me poo. BMW AT& iiSo ime0Ppu aWe be

OPTM:IONS MOMUAL 1117W TO ICH OO0111NTO

3WWII Plon Soflv 9103 ds y5ew s WulS)o AIG X12 bmed ee01m aa. s -eNt mn bsbauss or nepdlest ft @omole oid" Yeu wa Mt puine w inueovoe. or W& SehodI pw so mobi toopssee w~

I*#e. ABC XIV1119006131f Ur mW layea W Wip.. AMC X12TGSObl1Uslitw.

fTW4l: Pupin ft workl "wsuos nmn beows froe a Windbsevss ourt bMWa. Pubmvi a oasms mans (man*) int mow fsu movst us boxa sof bootgdhut ibf 0srs imam.b. Pew Use domoea onw" nluae -i d-- MeWepsSW bon.r. P"w Use New smr Osisam eeuwitso mN~t.ms AOw ftm~ Wwra t &MAorfo a' goef lowi WWIr aun ibimesm Im wd Mmle Sm.0. livalft OtMba Iuip ooow 0 oO s ftbowisl a" iaany mIsi t Os saves".t. You .W~ Wafts me" ft E wetm (ftm pest TuMaNdIsoPm) fo obalmboo"of dso Rear

W1W 4: PwaseuW Us bum a to Seaiut. Armblos huinmut leds. wa a amsur I~ i doofumilmn d ft fwevesmbWso) yo hows paUWed When fMOW beh m been isbsAd. ft p mess. W aw 41111 S WNt WI 4 00014 sd01101TmwsnsnM Pews ~bd heng to -ai udo W4. Wt avow, W"o & pogi

Amuw~u. 12 1.0100how 1110111-w~ Mow -ep Lown

amIm IiiLaw

4.0.1 BASELANE AS OF: JANUARY 23, IM0


'run JoeacyASC X1 2-ELECTRONIC DATA INTERCHANGE (EDI] (99) 9-999

Accmdrted St'dar Carwrv~ Dan Smitheyooeretng uniw* tft gre~jeou of ow 99)9949AmwvC, Nacio-W Standwts Isitute 99)"-99

Oocumernt NoASC X12C/rG2D/W0999

June 25, 1990

TO: X12 Members Who Commented an Modificmatons toX12im Control Structures

RE- Response to Comments on December BallotDM& 205289, 215239,317289

Thank you (or your comments. This ballot involved modifications to X12.xm. Of the 327 ballots mailed, L.53 ballots werreturned Of these, at approwed, 15 approved with commeat4 20 disapproved with comment and 37 abstained.

In general. the vowtresponses wer ia (ave o( the modification.. The majority of the comments focused on the impactof these modifications on the presentation of information, in the X122 Sepum Direactor. The proposed modificationsand the msidtiag presentation a the scament direuctry have beesrewcoradi response to these comments. A revisedmodificationa to X12.in was reviewe by Technical Assessment at the Jime ASC =1 neeim& Modifications to thedocument have bees made which reflect responses to the comments firom tho balot and a revised coW of XJ2.x abeing distributed to all who voted on this Wose, (or 30.day review of revisons.

Speacic responses to comments follow.

COMMENT: Automobile Corportion*Add the follow-in not to ?araaph 3.3- NOTE- Communication protocol characters should be enelded from thecharacter sw

RESPONME.The cove lewe amn out with the suing package explained that the intent was to obain cosseume on the proposedmodifications to X12xu X12.in isa AMfficul standard to amendt We request that ballot responses be considered on themerit of the recommended modifications and not on the standaird as a ,whok Yow comment was outside the scope ofthe requested modifiscatios..

BASEUNE AS OF: JANUARY 29,lIM 4.0.17

DIUPAR=UIT OF DEENSE

DRAFT ,PLB"ENTAT1ON WOV ON

Page Two

COMMENT.: Aircraft Enoie Crporatim"Some consideration for Abstract Syntax Notatn One (ASN.1) should be allowed.

I. ASN.1 is capable of dehaiug all of the necessay inter.relatioas needed by X12 transaaions.

2. ASN. requires less characters to define the same informatio.

3. ASN.A is the encoding scheme used by most 05I work.

RESPONSE.The recomme.dation to consider usae o ASN.1 encoding reaches far beyond the scope o the modification requestedin this ballot. Activities such as this ae best submitted as separate work requests.

COMMENT: Some Software lac.Cooditiona of data elements should be left to the discretion of implementation guidelines and areewents. Then ismuch discussion at times as far as whether ce'tam data elements should be mandatory or not; many application systsane incapabk of providing cetain 'mandatoty information a, as such, Sler-type data mug be iserte

RESPONSE-The issue of data element conditionaliy as a whole is a much broader subject than was intended to be addressed withinthe scope of this ballot. This ballot was intended to provide a means for consistent documentation and application ofalready existn conditional strucrm~a, If the commentor believes that the conditional structure should be removed fromthe standard, the task goup reommeds that this be submitted as a separate work requa.

EIAc.

4AI BASELINIE AS OF: JANUARY 29, IMH


ASC X1 2-ELECTRONIC DATA INTERCHANGE (EDI]ADcr** Stavd" C.wnvcm Jac Someboidycopwvw LOa do tft o=*x of ve Chair TG19. XI2CAmrvwrc Nacui Suridwt WISWAS (999) 999999

Document NoASC X12CfrG8/9O~96

ML Jame Doe W 1%90

Anan Baankoue Cgs"r piazMiddle Amena. mo 99m9

R& Reaposi to Ballot Com-eat osASC X12 Model Guidelime

Dear ML Doe.

Sabeomaiftte X12C has empmesu its Task Group 191to provd rusponses to the =am=em an thig bmfm& lbsmsembers of TG19 wok to tbsAk A5 =L mmbers who took the time ad effort to voc ms thia guideS.. We

u eddyhak eadhlvda wko provde commata, whethe is approval or duappruva of the gufide.. Weow~an appreciate yaw arem reiw of this doine.L

Ow respomse a keyed to the sumbeed tems a the cmacase attacied to yaw ballot.

RESPONSEL We apes vhh yaw mmcm. la Section 42.2.2 we hew feplad, -we vu~ rum -1 with rnal_ -e mUdlmd.

2. The e0002603 betweem 0 Section 4.23 ad Sectal 6.2 o*l exs becauso cm te maple we chos in m feirma@man flit is a hYPmoshesa Mmape of a maplifed model. Headers ad trilm an be plead on the coste atALL levels, md do not waecasi coarespoad to ASC X12 headers wid waaers.

3. We Wus wvith your cmaca. Sectios 6.2 has bee &&and so tho %'he establielethat of.. w added to iteasI sad 4.

BASELINE A OF: JANUARY 23, 1in4.=1


5.0 GLOSSARY

This chapter contains ASC X12 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 X12

Accredited 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 UNJEDIFACT stan-dards.

AuthenticationA 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 SegmentA 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 (LSILE),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.



Data ElementThe basic units of information in the EDI standards containing aset of values that represent a singular fact. They may be single-character codes, literal descriptions, or numeric values.

Data Element LengthThis 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 NumberReference number assigned to each data element as a uniqueidentifier.

Data Element Requirement DesignatorA code defining the need for a data element 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 TypeA data element may be one of six types: numeric, decimal,identifier, string, date, or time.

DelimitersThe delimiters consist of two 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 nonprofit organizationfunded by ASC X12 members which serves as the Secretariat forX12.

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 X12 approved standard foruse prior to approval by ANSI. See ANSI Standard.



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

Electronic EnvelopeElectronic 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 GroupA 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 Guidelines

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

Interchange Control Segments

ISA/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.

BASELINE AS OF: JANUARY 29,1993 5.0.3


MappingThe process of identifying the standard data element's relationshipto 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 contains a code takenfrom a list of approved codes.

Repeating SegmentA segment that may be used more than once 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.

Translation

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

Version/ReleaseIdentifies 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 ElectronicData Interchange

X12

The 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.

BASEUNE AS OF: JANUARY 29,1993 S.O.S



5.2 DoD GLOSSARY

AISAutomated Information Systems

ASD(P&L)

Assistant Secretary of Defense (Production and Logistics)

DESData Encryption Standard

DISADefense Information Systems Agency

DLA

Defense Logistics Agency

ISAInterchange Control Header Identifier

NISTNational Institute of Standards and Technology

NTENote Identifier

PLUS

Protection of Logistics Unclassified/Sensitive Systems

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


electronic data interchange (edi) convention · 2011. 5. 14. · ad-a263 476 draft department ~ of...

Documents