MDSb03 PUBLICATIONS

NIST Special Publication 881-48

nist

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003070 Transaction Set 838

Trading Partner Profile

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology
rhe National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in the development of technology . . . needed to improve product quality, to modernize manufacturing processes,

to ensure product reliability . . . and to facilitate rapid commercialization ... of products based on new scientific

discoveries."

NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's

competitiveness; advance science and engineering; and improve public health, safety, and the environment. One

of the agency's basic functions is to develop, maintain, and retain custody of the national standards of

measurement, and provide the means and methods for comparing standards used in science, engineering,

manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal

Government.

As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and

applied research in the physical sciences and engineering, and develops measurement techniques, test methods, standards, and related services. The Institute does generic and precompetitive work on new and

advanced technologies. NIST's research facilities are located at Gaithersburg, MD 20899, and at Boulder, CO 80303.

Major technical operating units and their principal activities are listed below. For more information contact the

Publications and Program Inquiries Desk, 301-975-3058.

Office of the Director

• National Quality Program

• International and Academic Affairs

Technology Services

• Standards Services

• Technology Partnerships

• Measurement Services

• Technology Innovation

• Information Services

Advanced Technology Program

• Economic Assessment

• Information Technology and Applications

• Chemical and Biomedical Technology

• Materials and Manufacturing Technology

• Electronics and Photonics Technology

Manufacturing Extension Partnership

Program

• Regional Programs

• National Programs

• Program Development

Electronics and Electrical Engineering

Laboratory

• Microelectronics

• Law Enforcement Standards

• Electricity

• Semiconductor Electronics

• Electromagnetic Fields'

• Electromagnetic Technology 1

• Optoelectronics 1

Chemical Science and Technology

Laboratory

• Biotechnology

• Physical and Chemical Properties

2

• Analytical Chemistry

• Process Measurements

• Surface and Microanalysis Science

Physics Laboratory

• Electron and Optical Physics

• Atomic Physics

• Optical Technology

• Ionizing Radiation

• Time and Frequency'

• Quantum Physics'

Materials Science and Engineering

Laboratory

• Intelligent Processing of Materials

• Ceramics

• Materials Reliability'

• Polymers

• Metallurgy

• NIST Center for Neutron Research

Manufacturing Engineering

Laboratory

• Precision Engineering

• Automated Production Technology

• Intelligent Systems

• Fabrication Technology

• Manufacturing Systems Integration

Building and Fire Research

Laboratory

• Structures

• Building Materials

• Building Environment

• Fire Safety Engineering

• Fire Science

Information Technology Laboratory

• Mathematical and Computational Sciences 2

• Advanced Network Technologies

• Computer Security

• Information Access and User Interfaces

• High Performance Systems and Services

• Distributed Computing and Information Services

• Software Diagnostics and Conformance Testing

'At Boulder, CO 80303.

2 Some elements at Boulder, CO.
NIST Special Publication 881-48

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003070 Transaction Set 838

Trading Partner Profile

Implementation Convention

Electronic Commerce Acquisition Program Management Office

Standard Management Committee - Secretariat

National Institute of Standards and Technology

Gaithersburg, MD 20899-0001

Editor: Dr. Jean-Philippe Favreau

January 1998

U.S. DEPARTMENT OF COMMERCE

William M. Daley, Secretary

Technology Administration

Gary R. Bachula, Acting Under Secretary for Technology

*

National Institute of Standards and Technology

Raymond G. Kammer, Director
Reports on Information Technology

The National Institute of Standards and Technology (NIST)'s Information Technology Laboratory (ITL)

develops standards and guidelines, provides technical assistance, and conducts research for computers

and resources. As part of the overall federal effort to establish a single face to industry for conducting

electronic commerce, ITL has been designated as the organization responsible for coordinating the

development of Federal Implementation Conventions (ICs) for Electronic Data Interchange (EDI). ICs are

defined by functional-area experts who create and select options from standard EDI Transaction Sets to

yield the implementations to be used for practical EDI. These ICs are made available to federal agencies

and industry by electronic means and this Special Publication Series.

National Institute of Standards and Technology Special Publication 881-48

Natl. Inst. Stand. Technol. Spec. Publ. 881-48, 49 pages (Jan. 1998)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1998

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
838 Trading Partner Profile

Functional Group ID=TD

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the Trading Partner Profile

Transaction Set (838) for use within the context of an Electronic Data Interchange (EDI) environment. This

transaction set can be used to request, change, verify or transmit business profile information to or from a trading

partner. This information can be used by the receiver to facilitate the processing of the sender's business

transactions. The transaction set may be used to convey government survey information, business classification,

general survey information, summary supplier ratings, changes in the EDI environment information, tax information, entity relationships, and general business profile information to update automated information data

bases between trading partners.

Notes:

1. Each business entity desiring to do business with the Federal Government must register as a Federal

Government Trading Partner. A Subordinate business element who intends to do business directly with the

Federal Government should register in its own right and should not use the registration ofits parent company.

2. Use this transaction set eitherfor an initial requestfor registration, or to cancel or change previously

transmitted data. Use also to transmit a duplicate requestfor registration when the original was not received by

the Federal Government. Use also to submit an annual, or such other update (e.g., when mandated changes to certifications or representations compel an update), as may be required by the Federal Government, of

Registration information to the Federal Government including any annual requirementfor submitting

certifications and representations.

3. In all cases, except cancellation, transmit the complete transaction set containing all information in the most

currentform. For example, when submitting a change, information that is not changed is transmitted along with

the changed information. Deleted information is omitted in the new submission.

4. Use this transaction set to register as either an EDI capable or a non-EDI capable trading partner. When

registering as an EDI capable trading partner, use the I/ENE/390 loop to completely describe the registrants EDI

capabilities. When registering as a non-EDI capable trading partner, do not use the l/ENE/390 loop.

5. All Federal Agencies may use this transaction set to register in the Central Contractors Request (CCR)

database.

6. DUNS + 4 Business Rulesfor Commercial Trading Partners:

Background

Thefollowing are a set ofrules designed to ensure data integrity while supporting DUNS + 4 identification of

companies in the Central Registration.

Definitions.

Parent: A business entity with controlling ownership (more than 50%) in another corporation.

Subsidiary: A corporation with more than 50% ofits voting stock owned by another business entity,

DUNS + 4 Implementation Rules

A parent corporation must register with a DUNS number.

A subsidiary must be pre-identified in the parent corporation 's registration.

003070F838_0 1 1 September 1997
838 - Trading Partner Registration

Subsidiaries may be identified with a DUNSat a DUNS + 4 number.

A parent corporation may identify only thefirst level ofsubsidiaries with DUNS + 4 numbers.

When a parent corporation 's registration goes inactive, the subsidiary's registration, ifDUNS + 4, goes inactive.

A subsidiary with a DUNS number has a registration independent ofthe parent corporation 's.

Upon a parent corporation 's registration becoming inactive, notifications will be sent to all DUNS + 4 identified

subsidiaries.

A subsidiary will not be permitted to change its corporate name and DUNS + 4 number.

The author and reason for de-activation ofa subsidiary's registration will be contained in a message to the

subsidiary corporation.

Corporate parents may select a corporate-wide or subsidiary-unique TPIN

7. Ifa registrant has multiple remit to addresses, a separate registration is required utilizing the DUNS + 4

Business Rulesfor Commercial Trading Partners.

8. l/BTP/020, ifBTP06 = 01, 04 or 30, then one iteration ofN901 with an " EL " is required to transmit the

TPIN.

Pos. Cam beg. Keq. Loop Notes and

No. ID Name Pes. Max.Use Repeat Comments

Must Use 010 ST Transaction Set Header M 1

Must Use 020 BTP Beginning Segment For Trading Partner Profile M 1

Not Used 021 REQ Request Information O 1

Not Used 025 PER Administrative Communications Contact O 1

Not Used 027 SPI Specification Identifier O >1 LOOP ID - LX >1

029 LX Assigned Number 1

030 PLA Place or Location O 1

Not Used 040 LCD Place/Location Description 0 >1

Not Used 050 LIN Item Identification 0 >1 LOOP ID-N1 >1

060 Nl Name I

070 N2 Additional Name Information 0 2

080 N3 Address Information 0 2

090 N4 Geographic Location 0 1

100 N9 Reference Identification 0 >1

110 PER Administrative Communications Contact 0 >1

Not Used 120 CUR Currency 0 >1

Not Used 130 TAX Tax Reference 0 >1

Not Used 140 FOB F.O.B. Related Instructions 0 >1

Not Used 150 ITD Terms of Sale/Deferred Terms of Sale 0 >1

Not Used 160 TD5 Carrier Details (Routing Sequence/Transit 0 >1 Time)

165 SPI Specification Identifier 0 >1

Not Used 170 FBB Foreign and Industry Business 0 >1 nl

Must Use 171 DTM Date/Time Reference 0 2

Not Used 172 MEA Measurements 0 >]

003070F838 0 2 1 1 September 1997
838 - Trading Partner Registration

LOOP ID - LCD

HHRhSHSnhB

>1

173 LCD Place/Location Description 0 1

Not I kerl 174 N2 auui AHHitional ii ui loi Namp l xai i Inuiivjiii formatanti nnwi o 1

Not Used 175 N4 Geographic Location 0 1

Not Used 177 DMG Demographic Information 0 >1

Not Used 178 MEA Measurements 0 >1

LOOP ID - TPD >1

180 TPD Trading Partner Detail 0 1

Nnt I keH 190 N9 Rpfprpnrp Identification o >1

Not Used 200 PID Product/Item Description o >1

210 DTM Date/Time Reference 0 >1

Not Used 215 LS Loop Header 0 1 LOOP ID - TUD >1

Not Used 220 TUD Trade Union Data 0 1

Not Used 230 DTM Date/Time Reference 0 >1

Not Used 240 Nl Name 0 1

Not Used 250 N2 Additional Name Information o 2

Not Used 260 N3 Address Information 0 2

Not Used 270 N4 Geographic Location 0 1

Not Used 280 PER Administrative Communications Contact 0 >1

Not Used 285 LE Loop Trailer 0 1 LOOP ID - SPR >1

Not Used 290 SPR Supplier Rating 0 1

Not Used 300 N9 Reference Identification 0 >1

Not Used 310 DTM Date/Time Reference 0 >1

LOOP ID - PAM >1 PAM PpnnH Amount o 1

330 DTM Date/Time Reference 0 >1

Not Used 340 TAX Tax Reference 0 >1

Not Used 350 CUR Currency 0 >1

I OOP ID - TXN >1

Not Used 360 TXN Transaction Capabilities 0 1

Not Used 370 N9 Reference Identification 0 >1

Not Used 380 DTM Date/Time Reference 0 >1

LOOP ID - LM >1

Not Used 381 LM Code Source Information "6

Not Used 382 LQ Industry Code M >1

LOOP ID - ENE

390 ENE Electronic Systems Environment O 1 LOOP ID-N1

. . ., .... >1

400 Nl Name O

Not Used 410 N2 Additional Name Information O 2

Not Used 420 N3 Address Information O 2

Not Used 430 N4 Geographic Location O 1

Not Used 440 TPD Trading Partner Detail O >1

Not Used 450 PID Product/Item Description O >1

003070F838 0 3 1 1 September 1997
838 - Trading Partner Registration

460 N9 Reference Identification O >1

Not Used 470 PER Administrative Communications Contact O >1

LOOP ID - TXN >i

480 TXN Transaction Capabilities O

'

1

Not Used 490 N9 Reference Identification O >1

Not used UIM Date/Time Reference KJ

Not Used 510 ERI Entity Relationship O >i

Not Used 520 AMT Monetary Amount O >i

Must Use 530 SE Transaction Set Trailer M i

Transaction Set Notes

1. With each occurence of the PLA loop, the sum of FBB03 for separately identified countries cannot exceed

100.

003070F838 0 4 11 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

ST Transaction Set Header

010

Mandatory

1To indicate the start of a transaction set and to assign a control number

1 The transaction set identifier (ST01) used by the translation routines of the

interchange partners to select the appropriate transaction set definition (e.g., 810

selects the Invoice Transaction Set).

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use ST01 143 Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

838 Trading Partner Profile

Must Use ST02 329 Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Use to transmit a unique number assigned by the originator ofthe

transaction set, This number may be system generated.

003070F838 0 5 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

BTP

020

Beginning Segment For Trading Partner Profile

Mandatory

1To indicate the type and purpose of the profile data

1 If BTP08 is present, then BTP07 is required.

2 If BTP09 is present, then BTP08 is required.

1 BTP01 indicates the purpose of this EDI transmission.

2 BTP02 is the identifying number of this transaction.

3 BTP03 and BTP04 are the transaction set date and time.

4 BTP06 indicates the status of the data content within the transaction.

5 BTP07 indicates reference number or previous reference number associated with this transaction.

6 BTP08 and BTP09 are date and time associated with BTP07.

Comments:

Ref. Data

Pes. Element

Must Use BTP01 353

Data Element Summary

Name

Transaction Set Purpose Code

Code identifying purpose of transaction set

Attributes

M ID 2/2

00 Original

Use to indicate the initial submission ofa request to

register and the original submission ofa change or annual update.

01

07

Cancellation

1. Use to indicate a cancellation ofa previously

submitted request to register.

2. Use BTP07, BTP08 andBTP09 to identify the

transmission being cancelled, andprovide one

iteration ofthe LXLoop with an Nl segment citing the

trading partner's D-U-N-S or D-U-N-S+4.

3. Cancellation will be considered effective upon

receipt oftransaction set. Duplicate

Use to indicate a duplicate submission. Use only when

informed that the original request to register was not

received

Must Use BTP02 127 Reference Identification M AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Use to indicate a unique number, assigned by the originator ofthe

transaction set, that can be used as a reference in a subsequent transaction

set. This number may be system generated.

Must Use BTP03 373 Date M DT 6/6

Date (YYMMDD)

Use to indicate the Universal Time Coordinate (UTC) date the transaction set was created. In the context ofregistration, this date will represent the date

003070F838 0 11 September 1997
838 - Trading Partner Registration

Must Use BTP04

Must Use BTP05

BTP06

the request was 'signed',

337 Time M TM4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Use to indicate the Universal Time Coordinate (UTC) time the transaction

set was created. Use only the HHMMformat. (e.g., 1030, 0925, etc.). 640 Transaction Type Code M ID 2/2

Code specifying the type of transaction

TP Trading Partner Information

353 Transaction Set Purpose Code O ID 2/2

Code identifying purpose of transaction set Use is required when BTP01 is either code 00 or code 07. Do not use when

BTP01 is code 01. 04 Change

/. Use to indicate a change to the data previously

transmitted that contains either additions, deletions,

changes or a combination ofadditions, deletions and

changes. When used, transmit the complete

transaction set containing all information in the most

currentform. Information that is not changed is transmitted along with the changed information.

Deleted information is omitted in the new transaction

set being transmitted. The entire data set representing

the tradingpartner is replaced with the information

contained in the change transmission.

30

2. Must use 1/DTM/l 71 to indicate date ofchange.

Renewal

1. Use to indicate the transmission is an annual

renewal of a previously approved registration. Annual

renewal transmissions may contain changes and

deletions. Wlien used, transmit the complete

transaction set containing all information in the most

currentform. Information that is not changed is transmitted along with the changed information.

DeleteaHnformation is omitted in the new transaction

set being transmitted. The entire data set representing the trading partner is replaced with the

information contained in the renewal transmission.

35

2. Must use 1/DTM/l 71 to indicate date ofrenewal.

Request Authority

/. Use to indicate the initial submission ofa request to

register.

2. Must use 1/DTM/l 71 to indicate date ofrequest to

register.

BTP07 127 Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Use, as needed, in cancellations, changes and annual renewals, to indicate a

reference number ofa previous transmission related to this transmission.

For example, ifthis transmission is changing data previously transmitted in an original requestfor registration as a trading partner, put the unique

reference number ofthis transmission in BTP02 and the reference number

003070F838 0 1 1 September 1997
838 - Trading Partner Registration

X DT 6/6

ofthe original registration transmission in BTP07.

BTP08 373 Date

Date (YYMMDD)

Use, as needed, in cancellations, changes and annual renewals, to indicate

the Universal Time Coordinate (UTC) date ofthe transmission referenced in

BTP07.

BTP09 337 Time O TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Use as needed in cancellations, changes and annual renewals, to indicate the

Universal Time Coordinate (UTC) time ofthe transmission referenced in

BTP07.

BTP10 591 Payment Method Code O ID 3/3

Code identifying the method for the movement of payment instructions

Ifthe registering party's financial institution cannot pass remittance

information when received with electronic funds transfer payment, the

registering party can receive remittance information directly or have it sent

to afinancial service provider by a Payment Order/Remittance Advice (820

transaction set). The 820 transaction set must be listed in the TXN segment

ifremittance information is to be sent to the registering party. Ifthe

remittance information is to be sent by the 820 to the registering party's

financial institution, then an iteration ofthe 1/N1/400 loop must be used

citing thefinancial institution and a l/TXN/480 segment showing an 820

capabilityfor the financial institution.

CHK Check

1. Cite code CHK only when the registrant cannot

accept electronic funds transfer (EFT) and has been

approvedfor a Debt Collection Improvement Act

(DCIA) waiver.

2. When CHK is specified, the trading partner must

also specify the Remit To information in 1/N1/060,

N101, codeRI, andN102, name.

DXC

DZC

SXC

SZC

3. Use 1/PER/110 to identify the official to identify the

point-of-contactfor obtaining DCIA waiver

information. Cite code ZZ in PER01.

ACH Demand Corporate Trade Exchange (CTX) Credit

Use 1/PER/ll 0 to identify the ACH coordinator. Cite

Code 3A in PER01.

ACH Demand Cash Concentration/Disbursement Plus

(CCD+) Credit

Use l/PER/110 to identify the ACH coordinator. Cite

Code 3A in PER01.

ACH Savings Corporate Trade Exchange (CTX) Credit

Use l/PER/110 to identify the ACH coordinator. Cite

Code 3A in PER01.

ACH Savings Cash Concentration/Disbursement Plus

(CCD+) Credit

Use l/PER/110 to identify the ACH coordinator. Cite

Code 3A in PER01.

003070F838 0 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

LX

029

LX

Assigned Number

Optional

Optional

1To reference a line number in a transaction set

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use LX01 554 Assigned Number M NO 1/6

Number assigned for differentiation within a transaction set

Insert the number 1 in LX01 to satisfy XI2 syntax requirements.

003070F838 0 9 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

PLA Place or Location

030

LX Optional

Optional

1To indicate action to be taken for the location specified and to qualify the location

specified

1 PLA03 is the effective date for the action identified in PLA01.

2 When used, PLA04 is the effective time for the action identified in PLA01

.

1. Failure by an EDI capable registering party to use this segment in an initial

registration and annual update will be causefor either rejection ofthe application or removalfrom the Central Contractor Registration (CCR) database.

2. Use as applicable in all transmissions except cancellations. No exceptions can be

made.

Must Use

Ref.

Pes.

PLA01

Must Use PLA02

Must Use PLA03

Not Used PLA04

Not Used PLA05

Data

Element

306

98

373

337

1203

Data Element Summary

Name Attributes

Action Code M ID 1/2

Code indicating type of action

WQ Accept

Use, as applicable in all transmissions except

cancellations, to indicate that the registering party

represents that information provided as part ofthis

transaction set is current, accurate, and complete as of

the submission date.

Entity Identifier Code M ID 2/3

Code identifying an organizational entity, a physical location, property or an

individual

KK Registering Party

The party requesting registration into a system

Date M DT 6/6

Date (YYMMDD)

Use as applicable in all transmissions except cancellations to indicate the

effective UTC date ofthe action identified in PLA01.

Time O TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Maintenance Reason Code O ID 2/3

Code identifying the reason for the maintenance change

003070F838 0 10 11 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

N101

Nl Name

060

Nl Optional

Optional

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

1 At least one of N102 or N103 is required.

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

1 This segment, used alone, provides the most efficient method of providing

organizational identification. To obtain this efficiency the "ID Code" (N104) must

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

2 N1 05 and N1 06 further define the type of entity in N1 0 1

.

/. For commercial trading partners, at least two iterations ofthe Nl loop are required

to carry the identity and address ofthe registering party (N101 = 'KK'),

and the identity and address ofthe party to receive payment ('remit to ' address)

(N101 = 'RI'). A DUNS or DUNS + 4 (refer to transaction set note 6) number must be

provided.

2. Thefull name and address ofthe registering party, including the registering party's

DUNS number, is required in the initial requestfor registration. Once successfully

registered, the registering party will be referred to by its DUNS number.

3. All EDI related information for cited parties shall be provided in the l/ENE/390

loop.

4. Ifthis transaction set is used to register a government entity, the registrant must

provide at least two iterations ofthe Nl loop; one with N101 = "KK" to identify the

registrant, and one with N101 = "QW" to identify the activity or agency ofthe

registrant.

Data Element Summary

Data

Element Name Attributes

98 Entity Identifier Code M ID 2/3

Code identifying an organizational entity, a physical location, properly or an

individual

04 Asset Account Holder

Use to identify the name ofthe account holder ifother

than the registering party.

61 Performed At

The facility where work was performed

Use, as applicable in all transmissions except

cancellations, to identify all business locations where

work under contracts and orders might be performed.

Use only when the address is other than the one given

for the registering party. Use as many iterations ofthis

Nl loop with this code as necessary to list all locations.

B3 Previous Name of Firm

A name by which a business entity was previously

known

Use, as applicable in all transmissions except

cancellations, to identify a previous name ofthe

registering company. Use as many iterations ofthis Nl

loop with this code as necessary to convey all previous names.

003070F838 0 1 I 1 1 September 1997
838 - Trading Partner Registration

B4 Parent Company

The organizational entity which, by virtue of

organization, ownership, and/or management, exercises

control over a subordinate but separate business entity

Use, as applicable in transmissions other than

cancellations, to identify the parent company ofthe

registering party. Use as many iterations ofthis Nl

loop with this code as necessary to convey all parent

companies.

B5 Affiliated Company

An organizational entity that shares a business

affiliation with another business entity

Small Business registering parties use, as applicable

in transmissions other than cancellations, as many

iterations ofthis Nl loop as necessary to cite all

affiliated businesses.

C5 Party Submitting Quote

A business entity submitting a quote; this entity may be

the party who ultimately performs if an order is received, or the entity may be submitting the quote on

behalf of another entity who will perform if an order is received

Use, as applicable in all transmissions except

cancellations, to indicate the name and address ofa

party authorized to submit quotes on behalfofthe

registering party, ifother than the registering party

itself

DH Doing Business As

Use, as applicable in all transmissions other than

cancellations, to identify the name ofthe registering

business if different than the name ofthe registering

party.

DV Division

Use only to identify a division ofthe registering party.

When used, cite either one or both ofthe division

name (using N102) or the division number (using

Nl 03/04). When the division number is cited, use code

56 in N103.

FE Mail Address

Use, as applicable in all transmissions other than

cancellations, to identify the mailing address ofthe

registering party only ifdifferentfrom the address

providedfor the registering party (Code KK).

KK Registering Party

The party requesting registration into a system

1. Use in all transmissions to identify the legal name

ofthe party submitting the request to register.

2. When 1/N1/060, N101 = KK, N301 cannot contain

P.O. Box or "in care ofaddressing.

MJ Financial Institution

Use, as applicable in all transmissions except

cancellations, to identify the name and address ofthe

registering party's financial institution forpayment.

PK Party to Receive Copy

003070F838_0 12 1 1 September 1997
838 - Trading Partner Registration

PL

PV

QW

RI

XX

N102 93 Name

Free-form name

Use, as applicable in all transmissions except cancellations, to identify the

legal name ofthe party cited in N10L When N102 is used, additional name

information can be transmitted in the N2 segment.

N103 66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67)

Use ofDUNS or DUNS+4 (refer to transaction set note 6) is always required

when N101 is code 04, 61, B4, B5, C5, KK, PK, or PL. Failure to provide a DUNS or DUNS+4 number will preclude the transmission ofan EDI

transaction to the cited party). This code is preferred over other codes and

requested to be provided, if available, when N101 is code B3, C4, DH, DV,

FE, MJ, PV, QW, RI, orX2.

1 D-U-N-S Number, Dun & Bradstreet

Use ofthe DUNS or DUNS+4 (refer to transaction set note 6) number is preferred over any other code to identify an entity.

2 Standard Carrier Alpha Code (SCAC)

4 International Air Transport Association (IATA)

9 D-U-N-S+4, D-U-N-S Number with Four Character

Suffix

003070F838_0 13 1 1 September 1997
838 - Trading Partner Registration

N104 67

10

19

21

33

38

Use ofthe DUNS or DUNS+4 (refer to transaction set note 6) number is preferred over any other code to identify an entity.

Department of Defense Activity Address Code

(DODAAC)

FIPS-55 (Named Populated Places)

Health Industry Number (HIN)

Use, as applicable, to identify the industry specific

number.

Commercial and Government Entity (CAGE)

Country Code

Use to indicate a country when the registering party

desires to do business with all buying organizations

located in the cited country. Use when N101 cites code

XX.

Division

Use only when N101 cites code DVto cite a division

number.

State Jurisdiction

Use to identify the two-letter state code ofthe business

locations in which the buying government

organizations are located with whom the registering

party desires to do business. Use code 38 with the

appropriate country code in N104 if an entire country

is desired. Use when N101 cites code XX

Mutually Defined

Use to indicate UCC EDI Communications ID (Comm

ID).

Identification Code X AN 2/20

Code identifying a party or other code

1. When N103 is code 38, use a three-character alphabetic country code as

specified in ISO 3166.

56

SJ

zz

Not Used N105

Not Used N106

2. When N103 is code SJ, use the two-character alphabetic state codes as

specified in the National Zip Code and Post Office Directory.

706 Entity Relationship Code O ID 2/2

Code describing entity relationship

98 Entity Identifier Code O ID 2/3

Code identifying an organizational entity, a physical location, property or an

individual

003070F838 0 14 11 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N2 Additional Name Information

070

Nl Optional

Optional

2

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

Use, as needed, in initial requestfor registration to indicate additional name

information over and above the name information to provided in N102. Do not use in

subsequent transmissions when theparty cited in N101 can be identified by a qualifier

code previously registered in Nl03/04; for example, when the registered party can be

identified by a DUNS number.

Data Element Summary

Must Use

Ref.

Pes.

N201

N202

Data

Element

93

93

Name

Name

Free-form name

Name

Free-form name

Attributes

M AN 1/60

O AN 1/60

003070F838 0 15 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N3 Address Information

080

Nl Optional

Optional

2

To specify the location of the named party

Use is required, as applicable in all transmissions except cancellations, to indicate, as a minimum, thefull address ofthe registering party. Also use to provide when relevant,

thefull address ofother parties cited in N101. Do not use in subsequent transmissions

when the cited party can be identified by a previously transmitted qualifier code and

code value in N103/04.

Attributes

M AN 1/55

Data Element Summary

Ref. Data

Pes. Element Name

Must Use N301 166 Address Information

Address information

1. Use to indicate the number, name, street and if applicable, suite number of

the cited party. For example, 10 Main Street, Suite 100, or 20 Washington

Ave.

N302

2. When 1/N1/060, N101 = KK, N301 cannot contain P.O. Box or "in care ofaddressing.

166 Address Information O AN 1/55

Address information

003070F838 0 16 11 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N4 Geographic Location

090

Nl Optional

Optional

1To specify the geographic place of the named party

1 If N406 is present, then N405 is required.

1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

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

Use is required, as applicable in all transmissions except cancellations, to transmit the

city, state, postal code, country (for non-U.S. registrants) and county, ifapplicable. Do

not use in subsequent transmissions when the citedparty can be identified by a

previously transmitted qualifier code and code value in N103/04.

Data Element Summary

Ref.

Pes.

N401

N402

Data

Element

19

156

Attributes

O AN 2/30

Name

City Name

Free-form text for city name

State or Province Code O ID 2/2

Code (Standard State/Province) as defined by appropriate government agency

1. Use the state code abbreviationsfound in the National Zip Code and Post

Office Directoryfor addresses in the United States.

2. Ifthe location is not in the United States, (including its territories and

possessions), or Canada, leave this data element blank.

N403 116

N404

N405

N406

26

309

310

Postal Code O ID 3/15

Code defining international postal zone code excluding punctuation and blanks

(zip code for United States)

Use either the ZIP codefound in the National ZIP Code and Post Office

Directory, Publication 65, or the postal code, ifknown, ofthe party cited in

N101.

Country Code O ID 2/3

Code identifying the country

Use a three-character alphabetic country code as specified in ISO 3166.

Location Qualifier X ID 1/2

Code identifying type of location

Use, as applicable, to identify a county code.

CY County/Parish

Use onlyfor the registering party (Le., when N101 is

Location Identifier O AN 1/30

Code which identifies a specific location

003070F838 0 17 1 1 September 1997
838 - Trading Partner Registration

Enter the county or parish name.

003070F838J) 18 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N9 Reference Identification

100

Nl Optional

Optional

>1

To transmit identifying information as specified by the Reference Identification Qualifier

12

3

4

12

At least one of N902 or N903 is required.

If N906 is present, then N905 is required.

If either C04003 or C04004 is present, then the other is required.

If either C04005 or C04006 is present, then the other is required.

N906 reflects the time zone which the time reflects. N907 contains data relating to the value cited in N902.

1. Use is required in all transmissions except cancellations to provide the taxpayer

identification number ofthe registering party when that party is a United States

business. Submission ofthe Taxpayer Identification Number (N901=TJ) is not

requiredfor registrants who areforeign suppliers (LCD02=20)

,

Federal/State/County/City Facilities - Le. government registrants (LCD02=2A), Other

Not-for-profitfacilities (LCD02=2U), other specialfacilities (LCD02-3I) or who are

municipalities (LCD02=C6).

2. Use, as applicable, to identify other reference numbers associated with the party

cited in N101. For example, ifNIOl is code KK (registering party) then an N9 segment

will carry the TIN ofthe registering party.

3. The registering party must indicate either a checking (code 11) or savings (code SG)

account as the remittance accountfor electronic funds transfer payments. One

iteration ofthe N9 segment is used to identify the ABA/Routing Transit Number; a second iteration is used to identify the account number. Only one account may be

used.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use N901 128 Reference Identification Qualifier M ID 2/3

Code qualifying the Reference Identification

Exceptfor code 01, thefollowing codes are used when N101 is code KK.

Code 01 is used when N101 is code MJ.

01 American Bankers Assoc. (ABA) Transit/Routing

Number (Including Check Digit, 9 Digits)

Use, as applicable in all transmissions except

cancellations, to identify the 9-digit routing transit

number ofthe registering party's financial institution.

1 1 Account Number

Number identifies a telecommunications industry

account

Use, as applicable in all transmissions except

cancellations, to identify thefinancial service provider

(e.g., bank) checking account number ofthe

registering party to which electronic payments will be

made.

EL Electronic device pin number

Successful registrants will be assigned a Trading

003070F838 0 19 1 1 September 1997
838 - Trading Partner Registration

Partner Identification Number (TPIN) by the Federal

Government in a confirmation ofregistration, using

the Trading Partner Profile (transaction set 838C).

Registered parties will use their TPIN number in all 838 transmissions subsequent to the initial registration

to identify themselves as successful registrants.

LB Lockbox

Q4 Prior Identifier Number

Use, as applicable in all transmissions except

cancellations, to indicate a prior identification number

thai may have been assigned by a Government

Department or Agency as a part ofa previous

electronic vendor registration process. When used, cite

the Agency issuing theprior identification number in

N903.

QR Quality Report Number

Use, as applicable in all transmissions except

cancellations, to identify the level ofquality assurance

establishedfor the registering party's manufacturing

facility. For example, when N901 is code QR, N902

could carry numbers such as either MIL-I-45208,

MIL-Q-9 859 or ISO 9000.

Savings

Use, as applicable in all transmissions except

cancellations, to identify thefinancial service provider

(i.e., bank) savings account number ofthe registering

party.

Social Security Number

Format as nine contiguous digits. No dashes.

Federal Taxpayer's Identification Number

1. Use ofthis code is required ofall tax paying

business entity registrants doing business in the

United States in initial registrations. The TIN shall be

incorporated into the iteration ofthe NI loop that cites

the party responsiblefor payment ofthe registering

party's taxes. Use also, ifapplicable, to cite the TIN of

other parties cited in N101. Use, as applicable in all transmissions except cancellations, to provide the TIN.

For example, ifN101 is code KK and that party pays

taxes in their own name, then the TIN will be carried

in the N9 segment ofthat Nl loop. Iftaxes are paid by

a common parent company, then indicate the parent

company's taxpayer identification number in the N9

segment contained in the iteration ofthe Nl loop

containing the name and address oftheparent

company. As used in Federal Government

implementation conventions, the term TIN means the

number required by the IRS to be used by a business

entity in reporting income tax and other returns. When LCD02 is code "20", "2A", "2U", "31" or "C6", this code is not used.

2. Format as nine contiguous digits. No dashes.

W7 Commercial and Government Entity (CAGE) Code

Code that identifies a commercial contractor authorized

to do business with the U.S. Government

SG

SY

TJ

003070F838 0 20 1 1 September 1997
838 - Trading Partner Registration

N902

N903

127

369

Use, if known, in all transmissions except

cancellations, to cite the CAGE Code ofthe party cited

in N10L

Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Free-form Description X AN 1/45

Free-form descriptive text When N901 is code Q4, use to identify the Agency issuing a prior

identification number.

Not Used N904

Not Used N905

Not Used N906

Not Used N907

Not Used C04001

Not Used C04002

Not Used C04003

Not Used C04004

Not Used C04005

Not Used C04006

373 Date O DT 6/6

Date (YYMMDD)

337 Time X TM4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

623 Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

C040 Reference Identifier O

To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier

128 Reference Identification Qualifier M ID 2/3

Code qualifying the Reference Identification

127 Reference Identification M AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

128 Reference Identification Qualifier X ID 2/3

Code qualifying the Reference Identification

127 Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

128 Reference Identification Qualifier X ID 2/3

Code qualifying the Reference Identification

127 Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

003070F838 0 21 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use PER01

PER Administrative Communications Contact

110

Nl Optional

Optional

>1

To identify a person or office to whom administrative communications should be directed

1 If either PER03 or PER04 is present, then the other is required.

2 If either PER05 or PER06 is present, then the other is required.

3 If either PER07 or PER08 is present, then the other is required.

1. Use to identify administrative contacts associated with the party cited in N101. For

example, ifNIOl identifies the registering party, then the PER segment will be used to pass the names and communication numbers ofpeople associated with the registering

party; ifN101 cites the parent company, then the PER segment would be used to pass, as applicable to the registration, the same information forpeople associated with the

parent company.

2. There must be at least 3 iterations ofthe PER segment to provide names and

communication numbersfor a registering party's information point ofcontact (use

codeIC), the official acknowledging the registration (use code CE) and a party who

can be contacted regarding billing problems (use codeAF). An additional iteration of

the PER segment is required ifthe registrant is EDI capable to identify the registrant's

EDI Coordinator (use code EA).

3. When an EFTmethod ofpayment is selected in BTP10, an ACH coordinator (use

code 3A) is also required. Other iterations may be required when naming a party or

parties authorized to sign quotations and contracts.

Data Element Summary

Data

Element Name Attributes

366 Contact Function Code M ID 2/2

Code identifying the major duty or responsibility of the person or group named

3A

AF

AS

CE

Automated Clearinghouse (ACH) Contact

Use to identify the communication number ofthe

ACH Coordinator at thefinancial institution. Use only

when BTP10 segment specifies EFT (ACH-...)

payment method.

Authorized Financial Contact

Use, as applicable, in all transmissions except

cancellations, to identify a communication number

that can be contacted regarding billing problems. Use, as applicable, in changes and annual updates. Do not

use in cancellations.

Authorized Signature

Use, as applicable, in all transmissions except

cancellations, to identify the name ofa party

authorized to sign on behalfofthe registering party.

Use as often as necessary to cite all authorizedparties.

Use, as applicable, in changes and annual updates. Do

not use in cancellations.

Certifier

Use, as applicable, in all transmissions except

cancellations, to identify the name and

003070F838 0 22 11 September 1997
838 - Trading Partner Registration

communications number ofthe official acknowledging

that the information provided as part ofthis

transaction set is current, accurate and complete as of

the submission date.

EA EDI Coordinator

1. Only used by registering parties to provide the name

and a communication number ofan EDI contact

2. Required ifthe registrant is EDI capable.

IC

OW

zz

Information Contact

Use, as applicable, in all transmissions except

cancellations, to indicate the name and

communication number ofa point ofcontact Use, as

applicable, in changes and annual renewals. Use in

cancellations to indicate the name ofthe party

requesting the cancellation.

Owner

Must use when LCD02 is code 2J. Not applicable

otherwise.

Mutually Defined

1. Use, as applicable, in all transmissions exceptfor

cancellation, to identify the name ofthe official to obtain waiver application information concerning a Debt Collection Improvement Act (DCIA) waiver.

Must Use PER02

Must Use PER03

PER04

93

365

364

O AN 1/60

X ID 2/2

2. Use only when DTP10 = " CHK ". Name

Free-form name

Communication Number Qualifier

Code identifying the type of communication number

/. Use to identify one ofthe communication numbersfrom the code list provided below. Ifmore than one communication number is to be provided, use the PER05/06pair to pass the second number. Use another iteration of

the PER segment with the same qualifier code in PEROI if more than two

communication numbers are to be passed.

2. When PER03 = " TE " or

" (XXX) xxx-xxxx.

FX ", PER 04 should beformatted as :

EM Electronic Mail

FX Facsimile

IT International Telephone

When used, the number must start with the country

code.

TE Telephone

Use to identify the commercial telephone number.

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

PER05 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

When PER05 - " TE " or " FX ", PER 06 should beformatted as : (XXX)

003070F838 0 23 1 1 September 1997
838 - Trading Partner Registration

PER06

Not Used PER07

Not Used PER08

Not Used PER09

XXX-XXXX.

EM Electronic Mail

EX Telephone Extension

FX Facsimile

IT International Telephone

When used, the number must start with the country

code.

TE Telephone

Use to identify the commercial telephone number.

364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

1. WhenPER03 = " TE " or " FX ", PER 06 should beformatted as : (XXX) XXX-XXXX.

365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

443 Contact Inquiry Reference O AN 1/20

Additional reference number or description to clarify a contact number

003070F838 0 24 11 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use SPI01

Not Used SPI02

Not Used SPI03

Not Used SPI04

Not Used SPI05

Not Used SPI06

Not Used SPI07

Not Used SPI08

SPI09

SPI Specification Identifier

165

Nl Optional

Optional

>1

To provide a description of the included specification or technical data items

1 If either SPI02 or SPI03 is present, then the other is required.

Use, when appropriate, to identify the security level ofthe registering party's facility

and/or thefacility where work will be performed and the highest security clearance

held by employees ofthe registering party. When used, cite the information or any

part, as shown in thefollowing example: Facility - Secret; Employees - Top Secret If afacility or employees do not have a security clearance, this information need not be

provided.

Data

Element

786

128

127

790

791

792

353

755

786

ID 2/3

X AN 1/30

Data Element Summary

Name Attributes

Security Level Code M ID 2/2

Code indicating the level of confidentiality assigned by the sender to the

information following

Use to specify government security capabilities, if any, ofthefacility or

location described in 1/N1/060.

90 Government Non-Classified

92 Government Confidential

93 Government Secret

94 Government Top Secret

Reference Identification Qualifier

Code qualifying the Reference Identification

Reference Identification

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Entity Title O AN 1/132

Title of the data entity

Entity Purpose O AN 1/80

The reason for the existence of the data item specified by the electronic data

item independent of its presence in an EDI transaction

Entity Status Code O ID 1/1

Code indicating the current status of the data item specified by the electronic

data item

Transaction Set Purpose Code O ID 2/2

Code identifying purpose of transaction set Report Type Code O ID 2/2

Code indicating the title or contents of a document, report or supporting item

Security Level Code O ID 2/2

Code indicating the level of confidentiality assigned by the sender to the

information following

Use, when appropriate, to identify the highest security clearance held by

employees ofthe registering party. Ifemployees do not have a security

clearance, this information need not be provided.

90 Government Non-Classified

92 Government Confidential

003070F838 0 25 1 1 September 1997
838 - Trading Partner Registration

93 Government Secret

94 Government Top Secret

Not Used SPI10 559 Agency Qualifier Code O ID 2/2

Code identifying the agency assigning the code values

Not Used SPI11 822 Source Subqualifier O AN 1/15

A reference that indicates the table or text maintained by the Source Qualifier

Not Used SPI12 554 Assigned Number O NO 1/6

Number assigned for differentiation within a transaction set Not Used SPI13 1322 Certification Type Code O ID 1/1

Code indicating the type of certification

Not Used SPI14 1401 Proposal Data Detail Identifier Code O ID 1/3

Code identifying the basis of a cited value in a proposal

003070F838 0 26 11 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

DTM01

Must Use DTM02

Must Use DTM03

Not Used DTM04

Must Use DTM05

Not Used

Not Used

DTM06

DTM07

DTM Date/Time Reference

171

Nl Optional

Optional (Must Use)

2

To specify pertinent dates and times

1 At least one of DTM02 DTM03 or DTM06 is required.

2 If DTM04 is present, then DTM03 is required.

3 If either DTM06 or DTM07 is present, then the other is required.

One iteration ofthe DTMsegment is required to cite the effective date ofall data

contained in this Trading Partner Profile transaction set (838).

Data

Element

374

373

337

623

624

1250

1251

Data Element Summary

Name Attributes

Date/Time Qualifier M ID 3/3

Code specifying type of date or time, or both date and time

007 Effective

Use to indicate the effective date ofthe data provided

in this transmission.

Date X DT 6/6

Date (YYMMDD)

Use to indicate the Universal Time Coordinate (UTC) date the transaction set was created. In the context oftrading partner registration, this date will

represent the effective date ofall EFT data contained in this transmission.

Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

Century O NO 2/2

The first two characters in the designation of the year (CCYY)

Cite the century ofthe date carried in DTM02.

Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format

Date Time Period X AN 1/35

Expression of a date, a time, or range of dates, times or dates and times

003070F838 0 27 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

LCD Place/Location Description

173

LCD Optional

Optional

1To further define and describe a place or location

1 If either LCD05 or LCD06 is present, then the other is required.

1. Use as many iterations as necessary to identify all attributes applicable to the

registering party. For example, to identify the type oforganization, ifit is in a labor

surplus area, the type ofbusiness, business classification, whether or not it is an 8(a)

certifiedfirm, and the business size. Use, as applicable, in changes and renewals. Do

not use in cancellations.

2. When LCD02 is either code 20, 2L or XS, there must be at least one iteration ofthe

LCD segment using LCD05/06 to indicate, as applicable, the state orforeign country in

which the registering party is incorporated.

3. When LCD02 is code XS, an additional iteration ofLCD must be included with

LCD02=2L.

Ref.

Pes.

Must Use LCD01

LCD02

4. When codes 2Y, 2L , 2J, 2K, or 2U are used, there must be a second iteration ofthe

LCD segment to indicate the type ofbusiness.

Data

Element

350

98

Data Element Summary

Name Attributes

Assigned Identification M AN 1/20

Alphanumeric characters assigned for differentiation within a transaction set A number assigned by the originator ofthe transaction set. Cite the number

1 in thefirst iteration ofthe LCD segment; 2 in the second iteration and so

on, as applicable.

Entity Identifier Code O ID 2/3

Code identifying an organizational entity, a physical location, property or an

individual

Use, as applicable, to identify other attributes ofthe registering party's

business such as the type of organization (e.g., Individual, Partnership, etc.), size ofbusiness (e.g., Small or other than small), type ofownership (e.g.,

Disadvantaged or Woman-owned), and type ofbusiness (e.g., Manufacturer,

dealer, etc.) Do not use in cancellations. Contractor must select one ofthe

applicable Corporate Tax Status Codes to identify 1099 reporting

requirements, (e.g., 2Y, 2L, 2J, 2K, 2U)

1A

20

23

27

2A

Subgroup

Use to indicate a minority institution.

Foreign Supplier

Used to indicate that the registrant is aforeign owned

and located entity.

Minority-Owned Business, Large

Used in the Federal 838 IC to report a generic

minority-owned business.

Small Disadvantaged Business

Use to indicate a small disadvantaged business concern as defined in FAR, part 19.001.

Federal, State, County or City Facility

003070F838 0 28 1 1 September 1997
838 - Trading Partner Registration

Use to indicate an agency or instrumentality ofa

Federal, state, or local government as defined in FAR,

part 52.204-3.

2J Individual

Use to indicate the corporate status ofa Sole

Proprietorship as defined in the FAR, part 52.204-3.

2K Partnership

Use to indicate the corporate status ofa Partnership as

defined in the FAR, part 52.204-3.

2L Corporation

Use to indicate the corporate status ofOther

Corporate Entities as defined in the FAR, part 52.204-

3.

2U Other Not-for-profit Facility

Use to indicate the corporate status ofa Hospital or extended carefacility that is exemptfrom taxation as

defined in the FAR, part 52.204-3.

2Y General Medical and Surgical Facility

Use to indicate the corporate status ofa Corporation

providing medical and health care services, or engaged in the billing and collecting ofpaymentsfor

such services as defined in the FAR, part 52.204-3.

31 Other Specialty Facility

Use to indicate a Tribal Government type of

organization.

77 Service Location

Use to indicate the type ofbusiness as a service

establishment.

95 Research Institute

Use to indicate the type ofbusiness as conducting

research and development

A2 Woman-Owned Business

A business (not defined as large or small) that is owned

by a woman

Use to indicate type ofownership.

A3 Labor Surplus Area Firm

A business that has an identified surplus of labor in the

geographic area where it is located

Use to indicate that the registering party will perform

work in a labor surplus area concern as defined in

FAR 19.001.

A6 Section 8(a) Program Participant Firm

A firm participating in a program (under Section 8 (a)

of the Small Business Act (15 U.S.C. 637 (a)), in which

the Small Business Administration enters into contracts on behalf of, and then subcontracts with, the

participating firm, certifying the firm's competence and

responsibility

Use to indicate an SBA certified 8(a) business

concern.

A7 Sheltered Workshop

A business entity which provides work for a special

category of worker

003070F838_0 29 1 1 September 1997
838 - Trading Partner Registration

Use to identify a qualified nonprofit agency under the

Javits-Wagner-O'Day Act as described in FAR, part

8. 701 and DFARS, part 219. 703.

A8 Nonprofit Institution

A business that by operation of policy or law does not

choose (or is not allowed) to make a profit from the

efforts of its enterprise

Use to indicate a nonprofit organization as defined in

FAR, part 27.301. Do not use if code M8 applies.

B2 Other Unlisted Type of Organizational Entity

An organization, e.g., a business, the description of

which cannot be accomplished using the existing code

list and for which the trading partners have not mutually

agreed to a definition for it Use to indicate an emerging small business concern as

defined in FAR, part 19.1002.

C6 Municipality

Use to indicate a business concern owned and

operated by an agency or instrumentality ofa state or

local government.

FK Construction Firm

Use to indicate the type ofbusiness as a construction concern.

Not Used LCD03

Not Used LCD04

LCD05

306

373

66

HB Historically Black College or University

An educational institution of higher learning with a

historical black student population.

Use to indicate a HBCU or minority institution as

defined in DEFARS, part 252.219-7003 or civilian

agency.

LJ Limited Liability Company

M8 Educational Institution

Use to indicate a university or other institution of

higher education as defined in FAR, part 27.301.

MF Manufacturer of Goods

Use to indicate the type ofbusiness as either a

manufacturer or producer.

OW Owner of Properly or Unit

Use to identify American Indian ownership.

XS S Corporation

An "S" corporation is a corporation type designation

given by the Internal Revenue Service to a corporation

meeting certain tests of ownership and profit

distribution

Action Code O ID 1/2

Code indicating type of action

Date O DT 6/6

Date (YYMMDD)

Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67)

Use, as applicable, in initial registrations, changes and renewals, to identify

the state or country in which incorporated. Do not use in cancellations.

003070F838 0 30 1 1 September 1997
838 - Trading Partner Registration

LCD06 67

38 Country Code

Use, when applicable, to identify the three-letter

alphabetic foreign country code (as specified in ISO

3166) ofthe country in which the registering party is incorporated.

SJ State Jurisdiction

Use, when applicable, to identify the two-letter state code ofthe state in which the registering party is incorporated.

Identification Code X AN 2/20

Code identifying a party or other code

003070F838 0 31 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

TPD Trading Partner Detail

180

TPD Optional

Optional

1To describe attribute of a trading partner

1 If either TPD02 or TPD03 is present, then the other is required.

/. At least one iteration ofthe TPD segment is required to provide either a SIC code

or a SIC 2+2 codefor acquisition related registrants. A second iteration to provide

either a Federal Supply Classification Code or Product Service Code is encouraged.

Use, as necessary, in all transmissions except cancellations.

2. Submission ofa SIC code or SIC 2+2 code is requiredfor acquisition related

registrants. The Federal Government plans eventually to make distribution ofthat

information which wouldfacilitate the sorting offirms by commodities. In turn, that

information could be used by prime contractors lookingfor subcontractors. Ifneither a SIC code nor SIC 2+2 code is applicable, cite 9999 in TPD03 when TPD02 is either 2

or code V.

Must Use

Ref.

Pes.

TPD01

TPD02

Data

Element

349

23

Data Element Summary

Name Attributes

Item Description Type M ID 1/1

Code indicating the format of a description

S Structured (From Industry Code List)

Use to indicate a Standard Industrial Classification

(SIC) code, Duns Standard Industrial Classification

(SIC) 2+2 code, Federal Supply Classification (FSC)

code, or a Product Service code, in codifiedformat, is provided in TPD02/03.

Commodity Code Qualifier X ID 1/1

Code identifying the commodity coding system used for Commodity Code

2

K

V

Z

Dun's SIC 2+2, Dun & Bradstreet

Federal Supply Classification

Standard Industrial Classification (SIC) Code

Mutually defined

Use to indicate a product service code. Product

service codes that may be cited in TPD03 when TPD02

is code Z are available on World Wide Web (WWW) at

http://webl. whs. osd. mil/diorhome. htm.

Not Used

TPD03

TPD04

22

352

Commodity Code

Code describing a commodity or group of commodities

Use to cite a SIC, SIC 2+2, FSC or PSC code.

Description

X AN 1/30

O AN 1/80

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

003070F838 0 32 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use DTM01

Must Use DTM02

Must Use DTM03

Not Used DTM04

Must Use

Not Used

Not Used

DTM05

DTM06

DTM07

DTM Date/Time Reference

210

TPD Optional

Optional

>1

To specify pertinent dates and times

1 At least one of DTM02 DTM03 or DTM06 is required.

2 If DTM04 is present, then DTM03 is required.

3 If either DTM06 or DTM07 is present, then the other is required.

Use to indicate the effective date ofa changefor an item cited in the TPD loop.

Data

Element

374

373

337

623

624

1250

1251

Data Element Summary

Attributes

M ID 3/3

Name

Date/Time Qualifier

Code specifying type of date or time, or both date and time

152 Effective Date of Change

Date on which the change went into effect

Use when BTP06 is either code 04, change, or code

30, renewal.

Date X DT 6/6

Date (YYMMDD)

Use to indicate the Universal Time Coordinate (UTC) date the transaction set was created In the context ofregistration, this date will represent the date

the request was 'signed'.

Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

Century O NO 2/2

The first two characters in the designation of the year (CCYY)

Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format

Date Time Period X AN 1/35

Expression of a date, a time, or range of dates, times or dates and times

003070F838 0 33 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

PAM01

PAM02

PAM03

Must Use C00101

Not Used C00102

Not Used C00103

Not Used C00104

PAM Period Amount

320

PAM Optional

Optional

1To indicate a quantity, and/or amount for an identified period

1 If any of PAM01 PAM02 or PAM03 is present, then all are required.

2 At least one of PAM02 PAM05 or PAM14 is required.

3 If either PAM04 or PAM05 is present, then the other is required.

4 If either PAM06 or PAM07 is present, then the other is required.

5 If PAM07 is present, then at least one of PAM08 or PAM09 is required.

6 If PAM07 is present, then PAM06 is required.

7 If PAM08 is present, then PAM07 is required.

8 If PAM09 is present, then PAM07 is required.

9 If PAM10 is present, then at least one of PAM1 1 or PAM12 is required.

10 If PAM1 1 is present, then PAM1 0 is required.

11 If either PAM13 or PAM14 is present, then the other is required.

1 PAM10, PAM1 1, or PAM12 are used when two dates are required.

2 PAM15 indicates whether the monetary amount identified in PAM05 is a net or gross value. A "Y" indicates amount is a gross value; an "N" indicates amount is a net value.

1. There must be at least one iteration ofthe PAMsegment as applicable in all transmissions except cancellations for all non-government acquisition related

registrants. Use one iteration to transmitfor the registering party, the previous year's

average number ofemployees, including current affiliates but notformer affiliates;

and, the average annual receiptsfor the past three years.

2. If 1/N101/060 cites either code B4 or B5, transmit the same information for the

parent and affiliates, as applicable.

Data Element Summary

Data

Element

673

Attributes

X ID 2/2

380

C001

355

1018

649

355

Name

Quantity Qualifier

Code specifying the type of quantity

ET Employee Total

Use to indicate the previous year's average number of

employees.

Quantity X R 1/15

Numeric value of quantity

Composite Unit of Measure X

To identify a composite unit of measure (See Figures Appendix for examples

of use)

Unit or Basis for Measurement Code M ID 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

EA Each

Exponent

Power to which a unit is raised

O R 1/15

Multiplier O R 1/10

Value to be used as a multiplier to obtain a new value

Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

003070F838 0 34 11 September 1997
838 - Trading Partner Registration

Not Used C00105

Not Used C00106

Not Used C00107

Not Used COO 108

Not Used C00109

Not Used C00110

Not Used C00111

Not Used C00112

Not Used C00113

Not Used C00114

Not Used C00115

PAM04

PAM05

Not Used PAM06

Not Used PAM07

Not Used PAM08

Not Used PAM09

Not Used PAM10

Not Used PAM11

Not Used PAM12

1018 Exponent O R 1/15

Power to which a unit is raised

649 Multiplier O R 1/10

Value to be used as a multiplier to obtain a new value

355 Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

1018 Exponent O R 1/15

Power to which a unit is raised

649 Multiplier O R 1/10

Value to be used as a multiplier to obtain a new value

355 Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

1018 Exponent O R 1/15

Power to which a unit is raised

649 Multiplier O R 1/10

Value to be used as a multiplier to obtain a new value

355 Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

1018 Exponent O R 1/15

Power to which a unit is raised

649 Multiplier O R 1/10

Value to be used as a multiplier to obtain a new value

522 Amount Qualifier Code X ID 1/2

Code to qualify amount

KE Annual Revenue

The sum of all incomes generated by a business over a period of one year

Use to indicate the average receiptsfor the past three

years.

782 Monetary Amount X R 1/15

Monetary amount

Values should be rounded to the nearest dollar with no decimal For

example, ifthe actual monetary value is 10500.50, PAM05 would be '10501

344 Unit of Time Period or Interval X ID 2/2

Code indicating the time period or interval

374 Date/Time Qualifier X ID 3/3

Code specifying type of date or time, or both date and time

373 Date X DT 6/6

Date (YYMMDD)

337 Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

374 Date/Time Qualifier X ID 3/3

Code specifying type of date or time, or both date and time

373 Date X DT 6/6

Date (YYMMDD)

337 Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

003070F838 0 35 1 1 September 1997
838 - Trading Partner Registration

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Not Used PAM13 1004 Percent Qualifier X ID 1/2

Code to qualify percent

Not Used PAM14 954 Percent X R 1/10

Percentage expressed as a decimal

Not Used PAM15 1073 Yes/No Condition or Response Code O ID 1/1

Code indicating a Yes or No condition or response

003070F838 0 36 11 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use DTM01

Must Use DTM02

Must Use DTM03

Not Used DTM04

Must Use

Not Used

Not Used

DTM05

DTM06

DTM07

DTM Date/Time Reference

330

PAM Optional

Optional

>1

To specify pertinent dates and times

1 At least one of DTM02 DTM03 or DTM06 is required.

2 If DTM04 is present, then DTM03 is required.

3 If either DTM06 or DTM07 is present, then the other is required.

/. Two iterations ofthe DTMsegment are required, one to transmit the closing date of

the registering party's accounting system and a second to indicate the date the

registering party's business was started or acquired.

2. This segment is not applicable to government registrants.

Data

Element

374

373

337

623

624

1250

1251

Data Element Summary

Name Attributes

Date/Time Qualifier M ID 3/3

Code specifying type of date or time, or both date and time

196 Start Use to indicate the date the registering party's

business was started or acquired.

197 End

Use to indicate the date on which the registering

party's accounting period closes.

Date X DT 6/6

Date (YYMMDD)

Use to indicate the Universal Time Coordinate (UTC) date the transaction set was created. In the context ofregistration, this date will represent the date

that the business was started or acquired, or the date the registering party's

accounting period closes.

Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

Century O NO 2/2

The first two characters in the designation of the year (CCYY)

Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format

Date Time Period X AN 1/35

Expression of a date, a time, or range of dates, times or dates and times

003070F838 0 37 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

ENE Electronic Systems Environment

Optional

390

ENE

Optional

1To specify electronic systems environment

1 If either ENE04 or ENE05 is present, then the other is required.

1 ENE05 specifies a contracted provider identification number.

/. Use is required, if registering party is EDI capable, to provide information about the

electronic system environment as it pertains to the EDI capability ofthe registering

party and related parties. Use, as applicable, in all transmissions except cancellations.

2. At least one iteration is requiredfor an EDI capable registration to provide the EDI

addressee(s) ofthe registering party, Le. citing code KK in 1/N1/060, element N101.

3. Ifapplicable, use additional ENE loops to provide EDI information for additional

parties associated with the registrant or multiple VANs or VASs used by the registrant.

4. Do not use ifregistering as a non-EDI capable tradingpartner.

5. With the exception ofthe 824, 864 and 997 transaction sets, a registrant can only

register the use ofa specific implementation convention (identified in TXN04)for use

with 1 point oftranslation (ENE03). For example, use ofthe same implementation

convention cannot be registered in two or more different occurrences ofthe ENE loop.

Ref.

Pes.

Must Use ENE01

Data Element Summary

Data

Element Name

709 Communications Environment Code

To indicate EDI systems media capability

Attributes

M ID 2/2

PP Point to Point

Use to indicate the electronic communications number

cited in ENE03 is a direct number to the party

identified in thefollowing Nl segment, not a number

at a VAN or VAS. When used, identify the applicable

Translation Software in the 1/N9/460 segment.

Must Use ENE02 365

Must Use ENE03 364

SC Service Contracted Provider

1. Use to indicate the code cited in ENE03 is that ofa

certified VAN or VAS. When used, identify the

applicable Translation Software in the 1/N9/460

segment

2. Use ofthis data element by Government registrants

is required to provide the translation point information

required in ENE03.

Communication Number Qualifier M ID 2/2

Code identifying the type of communication number

ED Electronic Data Interchange Access Number

Communication Number M AN 1/80

Complete communications number including country or area code when

applicable

1. For commercial registrants, when ENE01 cites code SC, provide the three

003070F838 0 38 1 1 September 1997
838 - Trading Partner Registration

character VAN code ofthe certified VANproviding connectivity to the

governmentfor theparty identified in thefollowing Nl segment. The three

character VAN codes can be retrievedfrom the WORLD WIDE WEB at

http://edLoti.disa.mil/certify/van-ecpn.htm.

2. For government registrants, identify the site by specifying the data entry

placed in the GS02 in interchanges being sent by the site. For those

government registrants who are connected to the Government's Electronic

Commerce Infrastructure (ECI) via either a gateway or the ECPN, identify

the site by specifying the 'Site GS Code' entryfor the registrantfrom the

table maintained on the World Wide Web at http://edLotLdisa.mil/certify/sites.pdf.

ENE04 66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67)

12 Telephone Number (Phone)

ENE05 67 Identification Code X AN 2/20

Code identifying a party or other code

For commercial registrants, specify the telephone number ofyour VAN

service provider.

003070F838 0 39 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

400

Nl Optional

Optional

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

1 At least one of N1 02 or N1 03 is required.

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

1 This segment, used alone, provides the most efficient method of providing

organizational identification. To obtain this efficiency the "ID Code" (N104) must

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

N105 and N106 further define the type of entity inNlOl.

Use this segment to identify the parties to whom the EDI information within this

2

1.iteration ofthe ENE loop applies.

2. Ifother EDI capable parties associated with the registrant use a different method of

connectivity with the government (dial-up number or VAN), use other iterations ofthe

ENE loop to provide those parties' EDI information.

3. Ifthe Trading Partner requires that the 820 Remittance Advice be sent directly to the party to receive paymentfrom the Governmentpayment office, specify code IP in

N10L

4. Ifcode IP is specified in N101, specify the name ofthe VAN or other party to receive an 820 Remittance Advice.

Must Use

Ref.

Pes.

N101

Data

Element

98

Data Element Summary

Name Attributes

Entity Identifier Code M ID 2/3

Code identifying an organizational entity, a physical location, property or an

individual

IP Provider

/. Use to indicate the party to receive an 820

remittance advice transaction.

GP

NN

2. Provide EDI related information about this party in

the l/ENE/390 loop.

Gateway Provider

Identifies a gateway access provider

1. Departments and Agencies use this code to specify

the name ofthe gateway or Electronic Commerce

Processing Node (ECPN) used to route their EDI

transmissions.

2. Provide EDI related information about this party in

the l/ENE/390 loop.

Network Name

Identifies the name of the telecommunications network,

e.g., Envoy

1. Commercial Trading Partners use this code to specify the name ofthe Value Added Network (VAN)

used to route their EDItransmissions.

003070F838 0

2. Provide EDI related information about this party in

40 11 September 1997
838 - Trading Partner Registration

Must Use N102

Must Use N103

Must Use N104

PK

PL

the l/ENE/390 loop.

Party to Receive Copy

Use to indicate the party to receive solicitations if

other than the registering party.

Party to Receive Purchase Order

Use to indicate the party to receive purchase orders if

other than the registering party.

93 Name X AN 1/60

Free-form name

1. Provide the legal name ofthe party qualified by the code in N101.

2. When code is NN, use to indicate thefull name ofthe VAN used by

registeringparty.

66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67)

1 D-U-N-S Number, Dun & Bradstreet

2 Standard Carrier Alpha Code (SCAC)

4 International Air Transport Association (IATA)

9 D-U-N-S+4, D-U-N-S Number with Four Character

Suffix

10 Department of Defense Activity Address Code

(DODAAC)

33 Commercial and Government Entity (CAGE)

ZZ Mutually Defined

Use to indicate UCC EDI Communication ID (Comm

ID).

67 Identification Code X AN 2/20

Code identifying a party or other code

1. Cite the identification code ofthe EDI translation pointfor the party

named in N102.

Not Used N105

Not Used N106

706

98

2. This value will appear in the ISAOS ofinterchanges containing groups of

transaction sets addressed to the namedparty and in the ISA06 of

interchanges containing groups oftransaction sets from the named party.

3. This identification code cannot exceed 15 characters and must be left- justified.

Entity Relationship Code O ID 2/2

Code describing entity relationship

Entity Identifier Code O ID 2/3

Code identifying an organizational entity, a physical location, property or an

individual

003070F838 0 41 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N9 Reference Identification

460

Nl Optional

Optional

>1

To transmit identifying information as specified by the Reference Identification Qualifier

1 At least one of N902 or N903 is required.

2 If N906 is present, then N905 is required.

3 If either C04003 or C04004 is present, then the other is required.

4 If either C04005 or C04006 is present, then the other is required.

1 N906 reflects the time zone which the time reflects. 2 N907 contains data relating to the value cited in N902.

One iteration ofthis N9 segment is required to provide the software product used by

the translation point cited in thepreceding Nl segment

Ref.

Pes.

Must Use N901

Must Use N902

Data Element Summary

Data

Element Name

128 Reference Identification Qualifier

Code qualifying the Reference Identification

V0 Version

Attributes

M ID 2/3

127 Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Cite the software product used by the translation point cited in thepreceding

Nl segment. Indicate the softwareproduct identification number and

version number. The product ID number can be obtainedfrom the

Compliance Certification Facility on the World Web

http://eduotLdisa.mil/soft.html. Ifadditional characters are required,

continue the citation in N903.

N903

N904

Not Used N905

Not Used N906

Not Used N907

Not Used C04001

003070F838 0

O DT 6/6

ion software identified

X TM 4/8

369 Free-form Description X AN 1/45

Free-form descriptive text 373 Date

Date (YYMMDD)

Indicate the release date ofthe version ofthe tran

in N902.

337 Time

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

623 Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

C040 Reference Identifier O

To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier

128 Reference Identification Qualifier M ID 2/3

42 11 September 1997
838 - Trading Partner Registration

Not Used C04002 127

Not Used C04003 128

Not Used C04004 127

Not Used C04005 128

Not Used C04006 127

Code qualifying the Reference Identification

Reference Identification M AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Reference Identification Qualifier X ID 2/3

Code qualifying the Reference Identification

Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Reference Identification Qualifier X ID 2/3

Code qualifying the Reference Identification

Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

003070F838 0 43 1 1 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

TXN Transaction Capabilities

480

TXN Optional

Optional

1To indicate EDI transaction capabilities

1 If used, TXN08 and TXN09 indicate the effective date and time.

/. Use, as applicable in all transmissions except cancellations, to provide capabilities

for sending and receiving EDI transaction sets based on Federal or Department of

Defense implementation conventions.

2. Use as many iterations as necessary to describe thefull EDI capability ofthe parties

cited in 1/N1/400 through the environment cited in l/ENE/390.

3. With the exception ofthe 824, 864 and 997 transaction sets, a registrant can only

register the use ofa specific implementation convention (identified in TXN04)for use

with 1 point oftranslation (ENE03). For example, use ofthe same implementation

convention cannot be registered in two or more different occurrences ofthe ENE loop.

Must Use

Ref.

Pes.

TXN01

Must Use TXN02

Must Use TXN03

Data

Element

306

455

143

Data Element Summary

Name Attributes

Action Code M ID 1/2

Code indicating type of action

5 Send

Use to indicate that the cited transaction set can be

sent by the registering party.

6 Receive

Use to indicate that the cited transaction set can be

received by the registering party.

K In Production Send and Receive

Use to indicate that the cited transaction set can be

both sent and received by the registeringparty.

Responsible Agency Code M ID 1/2

Code used in conjunction with Data Element 480 to identify the issuer of the

standard

Use to indicate the standard in which the cited transaction set can be

sent/received.

T Transportation Data Coordinating Committee (TDCC)

Used by the Federal Government to indicate that the

EDIImplementation Conventions identified in TXN04

will be specified using the IC naming conventions

detailed in Part 10 ofthe Federal Implementation

Guidelines.

Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

This data element is only populated to satisfy the requirements ofthe ANSI

ASCX12 standard concerning this mandatory data element. However, the

data contained in TXN03 will not be used or processed by the Central

Contractor Registration system.

838 Trading Partner Profile

The Federal Government is populating this data

003070F838 0 44 11 September 1997
838 - Trading Partner Registration

Must Use TXN04

element with code 838 to be compliant with the ANSI

ASCX12 standards, butfor the purpose oftrading

partner registration, the data entered in TXN03 is irrelevant and not used in anyprocessing.

480 Version / Release / Industry Identifier Code M AN 1/12

Code indicating the version, release, subrelease, and industry identifier of the

EDI standard being used, including the GS and GE segments; if code in DE455

in GS segment is X, then in DE 480 positions 1-3 are the version number;

positions 4-6 are the release and subrelease, level of the version; and positions

7-12 are the industry or trade association identifiers (optionally assigned by

user); if code in DE455 in GS segment is T, then other formats are allowed

Each Federal and Department ofDefense (DoD) Implementation

Convention (IC) used by the Federal government has a unique identifier

specified asfollows:

L For Federal and DoD ICs based on an ANSI ASC XI2 transaction set:

Positions 1 through 6: ANSI ASC X12 Version and Release

number (e.g. 003010) upon which the

IC is based.

Position 7: Organizational Scope

F = Federal

D-DOD

G

' = Government (transitional)

Positions 8 through 10: Transaction Set Identifier Code

(e.g. 850).

Position 11: Variant: A character used to differentiate between different

functional implementations ofthe

same transaction set.

Ifthe convention is not a variant, an

underscore (_) will appear in this

position.

Position 12: A sequential number starting with 0

and incremented by 1 each time the

implementation convention is revised.

An example ofthe Version/Release/Industry Identifier Codefor revision 1 of

the Federal specific ICfor the X12 Version 003050 Commercial Invoice

(810C) transaction set is 003050F810C1.

2. For Federal and DoD ICs based on a UN/EDIFACT message:

Positions 1 through 3: UN/EDIFACT Version number

(e.g. 921, 97A) upon which the

IC is based.

Position 4: Organizational Scope

F - Federal

D-DOD

G = Government (transitional)

Positions 5 through 10: Message Identifier Code

003070F838 0 45 1 1 September 1997
838 - Trading Partner Registration

(e.g. ORDERS).

Position 11:

Position 12:

Variant: A character used to differentiate between different

functional implementations ofthe

same message.

Ifthe convention is not a variant, an

underscore (_) will appear in this

position.

A sequential number starting with 0

and incremented by 1 each time the

implementation convention is revised.

Must Use TXN05

TXN06

TXN07

Not Used TXN08

Not Used TXN09

An example ofthe Version/Release/Industty Identifier Codefor revision 1 of

the Federal specific ICfor the UN/EDIFACT Version 97A Purchase Order

(ORDERS) message is 97AFORDERSJ.

306 Action Code M ID 1/2

Code indicating type of action

1 Add

124 Application Receiver's Code O AN 2/15

Code identifying party receiving transmission. Codes agreed to by trading

partners

1. Ifthe registrant will receive the implementation convention (IC) identified

in TXN04 (TXN01 = "6 " or "K"), provide the registrant's receiving

application identification code.

2 In orderfor the registrant to receive the IC identified in TXN04, this value

must be populated in GS03 ofthe GS segment ofany interchange addressed

to the registrant

3. Ifthe registrant will not receive the IC identified in TXN04, do not

populate this data element

142 Application Sender's Code O AN 2/15

Code identifying party sending transmission; codes agreed to by trading

partners

1. Ifthe registrant will transmit the implementation convention (IC)

identified in TXN04 (TXN01 = "5" or "K"), provide the registrant's

transmitting application identification code.

2. In orderfor the registrant to transmit the IC identified in TXN04, this

value must be populated in GS02 ofthe GS segment ofany interchange

transmitted by the registrant

3. Ifthe registrant will not transmit the IC identified in TXN04, do not

populate this data element

373 Date O DT 6/6

Date (YYMMDD)

337 Time O TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

003070F838 0 46 11 September 1997
838 - Trading Partner Registration

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

530

Mandatory

1To indicate the end of the transaction set and provide the count of the transmitted

segments (including the beginning (ST) and ending (SE) segments)

1 SE is the last segment of each transaction set.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use SE01 96 Number of Included Segments M NO 1/10

Total number of segments included in a transaction set including ST and SE

segments

Use to indicate the total number ofsegments included in the transmission

including the ST and SE segments.

Must Use SE02 329 Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Use to transmit the same unique control number assigned by the originator

ofthe transaction set, as the control number cited in ST02.

003070F838 0 47 1 1 September 1997



Technical Publications

Periodical

Journal of Research of the National Institute of Standards and Technology—Reports NIST research

and development in those disciplines of the physical and engineering sciences in which the Institute is

active. These include physics, chemistry, engineering, mathematics, and computer sciences. Papers cover a broad range of subjects, with major emphasis on measurement methodology and the basic technology

underlying standardization. Also included from time to time are survey articles on topics closely related to the Institute's technical and scientific programs. Issued six times a year.

Nonperiodicals

Monographs—Major contributions to the technical literature on various subjects related to the

Institute's scientific and technical activities. Handbooks—Recommended codes of engineering and industrial practice (including safety codes) developed in cooperation with interested industries, professional organizations, and regulatory bodies.

Special Publications—Include proceedings of conferences sponsored by NIST, NIST annual reports, and

other special publications appropriate to this grouping such as wall charts, pocket cards, and bibliographies.

National Standard Reference Data Series—Provides quantitative data on the physical and chemical

properties of materials, compiled from the world's literature and critically evaluated. Developed under a worldwide program coordinated by NIST under the authority of the National Standard Data Act (Public

Law 90-396). NOTE: The Journal of Physical and Chemical Reference Data (JPCRD) is published

bimonthly for NIST by the American Chemical Society (ACS) and the American Institute of Physics (AIP).

Subscriptions, reprints, and supplements are available from ACS, 1155 Sixteenth St., NW, Washington, DC

20056.

Building Science Series;—Disseminates technical information developed at the Institute on building

materials, components, systems, and whole structures. The series presents research results, test methods, and

performance criteria related to the structural and environmental functions and the durability and safety

characteristics of building elements and systems.

Technical Notes—Studies or reports which are complete in themselves but restrictive in their treatment of

a subject. Analogous to monographs but not so comprehensive in scope or definitive in treatment of the

subject area. Often serve as a vehicle for final reports of work performed at NIST under the sponsorship of

other government agencies.

Voluntary Product Standards—Developed under procedures published by the Department of Commerce

in Part 10, Title 15, of the Code of Federal Regulations. The standards establish nationally recognized

requirements for products, and provide all concerned interests with a basis for common understanding of

the characteristics of the products. NIST administers this program in support of the efforts of private-sector

standardizing organizations.

Order the following NIST publications—FIPS and NISTIRs—from the National Technical Information

Service, Springfield, VA 22161.

Federal Information Processing Standards Publications (FIPS PUB)—Publications in this series

collectively constitute the Federal Information Processing Standards Register. The Register serves as the

official source of information in the Federal Government regarding standards issued by NIST pursuant to

the Federal Property and Administrative Services Act of 1949 as amended, Public Law 89-306 (79 Stat. 1127), and as implemented by Executive Order 11717 (38 FR 12315, dated May 11, 1973) and Part 6 of

Title 15 CFR (Code of Federal Regulations).

NIST Interagency Reports (NISTIR)—A special series of interim or final reports on work performed by

NIST for outside sponsors (both government and nongovernment). In general, initial distribution is handled

by the sponsor; public distribution is by the National Technical Information Service, Springfield, VA 22161,

in paper copy or microfiche form.
O "3 WS

o

<?oooo

Quo" 4> _ j=

. o F jz TM. 3 -S -3 5z5o

oo

1)

pa