111111

A11104 7^2S4 4

NIST

PUBLICATIONS

NIST Special Publication 881-2

i H

iiji inn ii Hiiiii&iiliiatfilllilllllll 1:: 1

nist

QC

100

U57

NO. 881 -2

1995

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 838

Trading Partner Profile

(Confirmation of Vendor Registration)

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology
The 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 Public Inquiries Desk, 301-975-3058.

Office of the Director

• Advanced Technology Program

• Quality Programs

• International and Academic Affairs

Technology Services

• Manufacturing Extension Partnership

• Standards Services

• Technology Commercialization

• Measurement Services

• Technology Evaluation and Assessment

• Information Services

Materials Science and Engineering

Laboratory

• Intelligent Processing of Materials

• Ceramics

• Materials Reliability 1

• Polymers

• Metallurgy

• Reactor Radiation

Chemical Science and Technology

Laboratory

• Biotechnology

• Chemical Kinetics and Thermodynamics

• Analytical Chemical Research

• Process Measurements 2

• Surface and Microanalysis Science

• Thermophysics2

Physics Laboratory

• Electron and Optical Physics

• Atomic Physics

• Molecular Physics

• Radiometric Physics

• Quantum Metrology

• Ionizing Radiation

• Time and Frequency 1

• Quantum Physics 1

Manufacturing Engineering Laboratory

• Precision Engineering

• Automated Production Technology

• Intelligent Systems

• Manufacturing Systems Integration .

• Fabrication Technology

Electronics and Electrical Engineering

Laboratory

• Microelectronics

• Law Enforcement Standards

• Electricity

• Semiconductor Electronics

• Electromagnetic Fields'

• Electromagnetic Technology1

• Optoelectronics 1

Building and Fire Research Laboratory

• Structures

• Building Materials

• Building Environment

• Fire Safety

• Fire Science

Computer Systems Laboratory

• Office of Enterprise Integration

• Information Systems Engineering

• Systems and Software Technology

• Computer Security

• Systems and Network Architecture

• Advanced Systems

Computing and Applied Mathematics

Laboratory

• Applied and Computational Mathematics2

• Statistical Engineering2

• Scientific Computing Environments2

• Computer Services

• Computer Systems and Communications2

• Information Systems

'At Boulder, CO 80303.

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

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 838

Trading Partner Profile

(Confirmation of Vendor Registration)

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

August 1995

U.S. DEPARTMENT OF COMMERCE

Ronald H. Brown, Secretary

Technology Administration

Mary L. Good, Under Secretary for Technology

National Institute of Standards and Technology

Arati Prabhakar, Director
Reports on Computer Systems Technology

The National Institute of Standards and Technology (NIST)'s Computer Systems Laboratory (CSL)

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

related telecommunications systems to advance the effective utilization of information technology

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

commerce, CSL 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-2

Natl. Inst. Stand. Technol. Spec. Publ. 881-2, 20 pages (August 1995)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1995

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. Use this transaction set to acknowledge the successful processing of a previously received request for

registration as a Federal Government trading partner.

2. Use this transaction set to inform a registering party that a request to register was partially processed. When

used in this manner, use the transaction set to provide the reason(s) why the request could not be fully processed.

3. Successful confirmation will be determined in part, only upon the validation of the registering party's DUNS

and TIN numbers, as provided in the 838 contractor registration transaction set.

4. Validation of registration will take some time, therefore, registering parties should not anticipate an immediate

confirmation of successful or partial registration. Registrants are advised to wait until they have received an

official response from the registration process.

5. Do not use this transaction set to notify a registering party of an unsuccessful registration. Use the 824

transaction set to notify a registrant of an application problem that precludes a successful registration.

Heading:

N/U

Pos. No. 010

020

021

025

Seg.

ID

ST

BTP

REQ

PER

Name

Transaction Set Header

Beginning Segment For Trading Partner Profile

Request Information

Administrative Communications Contact

Req.

Pes. M

M

O

O

Mai.Use

1

1

1

Loop

Repeat

Notes and

Comments

029 LX Assigned Number

N/U

N/U

030

040

050

PLA

LCD

LIN

Place/Location Description

Item Identification
838 - Confirmation of Vendor Registration RELEASE - FED1

060 Nl Name O 1

N/U 070 N2 Additional Name Information o 2

N/U 080 N3 Address Information O 2

N/U 090 N4 Geographic Location O 1

100 N9 Reference Number O >1

N/U 110 PER Administrative Communications Contact O >1

N/U 120 CUR Currency O >1

N/U 130 TAX Tax Reference O >1

N/U 140 FOB F.O.B. Related Instructions O >1

N/U 150 ITD Terms of Sale/Deferred Terms of Sale O >1

N/U 160 TD5 Carrier Details (Routing Sequence/Transit Time) O >1

N/U 170 FBB Foreign and Industry Business O >1 nl

N/U 171 DTM Date/Time Reference O 2

N/U 172 LCD Place/Location Description

iwmmwmm.

O >1

/>;;;:•:;;:•:;;:-::::-:-;::-::: 180 TPD Trading Partner Detail o ii

N/U 190 N9 Reference Number o >1

XT/T T rlD ituuuwu item j_/CJ>mipiiun

N/U 210 DTM UMJCf I 1II1C IVClCTCTlwC kj

N/U 215 LS T Ann \Ae*'»nt>r KJ 11

>t

N/U 220 TUD

: ::v:v:: :v: ::

:

: ::

:

:

: :: :v::

:

:

:

:

:

: :;

:

:

:

:

:

: ::

:

: ::

:

:

:

:

: ::

: ::

:

;

: ::

:

:

: ::

:

:

:

: :: ::

: ::-::: ::'^ :»ww Trade Union Data

;-^:-^:; ^:'>>:': : :': :

: :: ::

: :: :: :v:-::•:: ::': : ;:

:

: :• o 1

: :;

: x:

:

:

:

: ;:

;

N/U 230 DTM Date/Time Reference o >1

N/U 240 Nl Name o 1

N/U 250 N2 Additional Name Information o 2

N/U 260 N3 Address Information o 2

N/U 270 N4 Geographic Location o 1

N/U 280 PER Administrative Communications Contact o >1

N/U 285 LE Loop Trailer o 1

:^::v:¥¥¥:¥:¥:¥:¥:¥;¥;¥:¥:¥:¥:¥:¥:¥^^

:¥::x¥:*:vXv:¥:v:¥:¥:¥:¥:¥:: :

:

:

:

.•!!•«•!!-!•!•!•!:!•!:!•!•!•!:!!'! mmm

¥!¥*ks : : ;:• :«<vX->:v»K«i*:v»:i«i« N/U 290 SPR Supplier Rating o l

N/U 300 N9 Reference Number o >i

N/U 310 DTM Date/Time Reference o >i

iliiiiliiili.

N/U 320 PAM Period Amount o 1

: ::

: :

:

: :¥: ;

:

;

N/U 330 DTM Date/Time Reference o >1

N/U 340 TAX Tax Reference o >1

N/U 350 CUR Currency o >1

Federal X12-3040 2 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED1

N/U 360 TXN

N/U 370 N9

N/U 380 DTM

N/U 390 ENE

N/U 400 Nl

N/U 410 N2

N/U 420 N3

N/U 430 N4

XT n T N/U 440 IrD

N/U 450 PID

N/U 460 N9

N/U 470 PER

N/U 480 TXN

N/U 490 N9

N/U 500 DTM

N/U 510 ERI

N/U 520 AMT

530 SE

Transaction Capabilities

Reference Number

Date/Time Reference

O

O

o

1

>1

>1

|||i|$§/

Name

Additional Name Information

Address Information

Geographic Location

Trading Partner Detail

Product/Item Description

Reference Number

Administrative Communications Contact

O

O

O

O

O

O

o

o

1

2

2

1

>1

>1

>1

>1

Transaction Capabilities

Reference Number

Date/Time Reference

mm

o

o

o

1

>1

>1

Entity Relationship

Monetary Amount

Transaction Set Trailer

O

O

M

>1

>1

1

Transaction Set Notes

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

100.

Federal X12-3040 3 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED1

Segment: Transaction Set Header

Position: 010

Loop:

Level: Heading

Usage: Mandatory

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

Notes:

Syntax Notes:

Semantic Notes: 1 The transaction set identifier (STO 1) used by the translation routines of the

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

set). Comments:

Data Element Summary

M

Ref.

Pes.

ST01

Data

Element

143

Name

Transaction Set Identifier Code

Code uniquely identifying a Transaction Set.

Attributes

M ID 3/3

838 X12. 17 Trading Partner Profile

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

Federal X12-3040 4 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED1

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

BTP

020

Beginning Segment For Trading Partner Profile

Heading

Mandatory

1To indicate the type and purpose of the profile data

When cancelling a previously transmitted confirmation of registration use of the

transaction set, use BTP07/08/09 to carry the number, date and time of the transmission being cancelled.

Syntax Notes:

Semantic Notes:

this transaction.

1 If BTP08 is present, then BTP07 is required.

2 If BTP09 is present, then BTP08 is required.

1 BTPO1 indicates the purpose of this EDI transmission.

2 BTP02 is the identifying number of this transaction.

3 BTPO3 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

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

Comments:

M

Ref.

Pes.

BTP01

Data

Element

353

M BTP02 127

M

M

BTP03

BTP04

373

Attributes

M ID 2/2

337 Time

Data Element Summary

Name

Transaction Set Purpose Code

Code identifying purpose of transaction set.

00 Original

Use to indicate the original confirmation ofa request

for registration. Use if the transmission contains either an acknowledgment ofa successful registration or a

partial acceptance ofa requestfor registration.

Cancellation

Use to indicate a cancellation ofa previously

transmitted response to a requestfor registration.

Duplicate

Use to indicate a duplicate response to a requestfor

registration. Use only when informed that the original

response to a requestfor registration was not received.

Reference Number M AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number 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.

Date M DT 6/6

Date (YYMMDD).

Use to indicate the date the transaction set was created.

M TM 4/8

01

07

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

Federal XI2-3040 5 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED1

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 time the transaction set was created. Use local time. Use

only the HHMMformat (e.g., 1030, 0925, etc.). M BTP05

M BTP06

M BTP07

M BTP08

M BTP09

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.

1 1 Response

Use to indicate that this transmission is a response to a

previously submitted initial request to register, or a

change to, or annual renewal ofa previously successful

registration.

Ill Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

Use in other than cancellations, to indicate the reference number contained in

BTP02 ofthe requestfor registration transaction set. Use in cancellations to indicate the number ofthe cancelled transmission.

373 Date X DT 6/6

Date (YYMMDD).

Use in other than cancellations, to indicate the date contained in BTP03 ofthe

requestfor registration transaction set. Use in cancellations to indicate the

date ofthe cancelled transmission.

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 in other than cancellations, to indicate the time in BTP04 ofthe requestfor

registration transaction set. Use in cancellations to indicate the time ofthe

cancelled transmission.

Federal X12-3040 6 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED1

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

PERAdministrative Communications Contact

025

Heading

Optional

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

directed

Notes: Use this segment to provide the toll free commercial telephone number for registering

parties to call to obtain information regarding doing business using Electronic Data Interchange (EDI) or to inquire about their registration.

Syntax Notes: 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.

Semantic Notes:

Comments:

Data Element Summary

M

Ref.

Pes.

PER01

Data

Element

366

PER02

PER03

93

365

PER04

PER05

PER06

364

365

364

Name Attributes

O AN 1/35

ID 2/2

Contact Function Code M ID 2/2

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

EA EDI Coordinator

Use to indicate the Electronic Commerce Information

Center contact. Name

Free-form name.

Communication Number Qualifier

Code identifying the type of communication number.

TE Telephone

Use to indicate the tollfree commercial telephone

number. Ensure the 800 area code is included.

Communication Number X AN

Complete communications number including country or area code when

applicable.

Communication Number Qualifier X ID

Code identifying the type of communication number.

Refer to 003040 Data Element Dictionary for acceptable code values.

Communication Number X AN

Complete communications number including country or area code when

applicable.

1/80

2/2

1/80

Federal XI2-3040 7 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED1

Segment: Ljj\. Assigned Number

Position: 029

Loop: LX

Level: Heading

Usage: Optional

Max Use: 1 Purpose: To reference a line number in a transaction set. Notes: Use to indicate the number of the iteration of the LX loop. For example, in the first

iteration of the LX loop, insert the number 1 in LX01, in the second iteration of the LX loop (if there is a second

iteration in the transmission), insert the number 2, and so on. This number may be system generated.

Syntax Notes:

Semantic Notes:

Comments:

Data Element Summary

Ref. Data

Pes. Element Name Attributes

M LX01 554 Assigned Number M NO 1/6

Number assigned for differentiation within a transaction set.

Federal X12-3040 8 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED 1

specified

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

PLAPlace or Location

030

PLA

Heading

Optional

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

Use is required in original response to a registration request. Do not use in cancellation.

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.

Data Element Summary

M

Ref.

Pes.

PLA01

Data

Element

306

M PLA02 98

M PLA03

PLA04

Name Attributes

Action Code M ID 1/2

Code indicating type of action.

Use to identify the action being taken in the response as either a successful

registration or an inability to register the requesting party. Identify by a code

value in PLA02 the same code as used by the requesting party in the original

requestfor registration transaction set. Also include the effective date ofthe

decision to register or reject the request.

IN Interim

Use to indicate that the registration application has

been partially accepted, but that there is some nonessential data under review.

KA Registration Confirmed

The application requesting registration was favorably

acted upon and registration is confirmed

Use to indicate that a requesting party has been

successfully registered.

Entity Identifier Code M ID 2/2

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

KK Registering Party

The party requesting registration into a system

Use to identify the party submitting the request to

register transaction set.

373 Date M DT 6/6

Date (YYMMDD).

Use to indicate the effective date ofthe action described by the code value in

PLA01.

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)

Federal X12-3040 9 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED1

X PLA05 1203 Maintenance Reason Code O ID 2/3

Code identifying the reason for the maintenance change.

Refer to 003040 Data Element Dictionary for acceptable code values.

Federal X12-3040 10 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED1

Segment: Nl Name

Position: 060

Loop: Nl

Level: Heading

Usage: Optional

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

Notes: There must be at least one iteration of the Nl loop in each transaction set to carry the

address of the requesting party.

Syntax Notes: 1 At least one of N102 or N103 is required.

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

Semantic Notes:

Comments: 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 N105 and N106 further define the type of entity in N10 1

Data Element Summary

M

Ref.

Pes.

N101

X N102

N103

N104

X N105

X N106

Data

Element Name Attributes

98

93

66

67

706

98

Entity Identifier Code M ID 2/2

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

KK Registering Party

The party requesting registration into a system

Use to identify the party submitting the requestfor

registration.

X AN 1/35

X ID 1/2

Name

Free-form name.

Identification Code Qualifier

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

Code (67).

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

Use, ifapplicable, to identify the party requesting

registration.

Identification Code X AN 2/17

Code identifying a party or other code.

Entity Relationship Code O ID 2/2

Code describing entity relationship.

Refer to 003040 Data Element Dictionary for acceptable code values.

Entity Identifier Code O ID 2/2

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

Refer to 003040 Data Element Dictionary for acceptable code values.

Federal X12-3040 11 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE- FED1

Segment: N9 Reference Number

Position: 100

Loop: Nl

Level: Heading

Usage: Optional

Max Use: >1

Purpose: To transmit identifying numbers and descriptive information as specified by the

reference number qualifier

Notes: Use this segment to provide a unique number assigned by the Federal Government to a

successfully registered trading partner. Do not use if the registration is not successful.

Syntax Notes: 1 At least one of N902 or N903 is required.

2 If N906 is present, then N905 is required.

Semantic Notes: 1 N906 reflects the time zone which the time reflects. Comments:

Ref.

Pes.

M N901

X

X

X

N902

N903

N904

N905

N906

Data

Element

128

127

369

373

337

623

Attributes

M ID 2/2

Data Element Summary

Name

Reference Number Qualifier

Code qualifying the Reference Number.

EL Electronic device pin number

Use to provide a unique Trading Partner Identification

Number (TPJNJ to a successfully registering party.

Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

Free-form Description X AN

Free-form descriptive text.

Date O DT

Date (YYMMDD).

1/45

6/6

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.

Refer to 003040 Data Element Dictionary for acceptable code values.

Federal X12-3040 12 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED1

Segment: TPD Trading Partner Detail

Position: 180

Loop: TPD

Level: Heading

Usage: Optional

Max Use: 1 Purpose: To describe attribute of a trading partner

Notes: Use only in unsuccessful registrations, to indicate the reason(s) why the request to register could not be completely processed.

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

Semantic Notes:

Comments:

Data Element Summary

Ref. Data

Pes, Element Name Attributes

M TPD01 349 Item Description Type M ID 1/1

Code indicating the format of a description.

F Free-form

X TPD02 23 Commodity Code Qualifier X ID 1/1

Code identifying the commodity coding system used for Commodity Code.

Refer to 003040 Data Element Dictionary for acceptable code values.

X TPD03 22 Commodity Code X AN 1/16

Code describing a commodity or group of commodities.

TPD04 352 Description O AN 1/80

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

Use to advise the registrant ofa partial registration by indicating the nature of

the data under review, or the problem precludingfull registration. Use also to inform partially accepted registrants that they can inquire about the status of

their registration by calling the EDI help desk. The telephone number is to be

provided in the l/PER/025 segment.

Federal X12-3040 13 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE- FED1

Segment: SE Transaction Set Trailer

Position: 530

Loop:

Level: Heading

Usage: Mandatory

Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the transmitted

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

Notes:

Syntax Notes:

Semantic Notes:

Comments: 1 SE is the last segment of each transaction set.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

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

M 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 of

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

Federal X12-3040 14 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED1

838 TRANSACTION SET USAGE

TRADING PARTNER PROFILE

Usage of the segments and data elements arrayed in alphabetical order by information content.

INFORMATION

PONTFNT

TS

POS

• NO.

SEGMENT/

DATA

ELEMENT

R

I

c

A

N

c

D

U

P

T COMMENTS

ACTION

CODE/ENTITY/EFFECTIVE

DATE

1/030 PLA01/02/03 R R Identify the action being taken for either a

successful registration or an inability to

register. Include the effective date of the decision to register or reject.

ASSIGNED NUMBER 1/029 LX01 R R R Loop iterations.

DATE -PREVIOUS

'1 i|i * XTC A /TiYZ-WT TRANSAC I ION

1/020 BTP08 R R R Use to indicate the date contained in BlrUJ. Use in cancellations to indicate the date of canceled transmission..

DA 1 h (JKbAlfcD BlrUJ K K K The date the transaction set was created.

DESCRIPTION OF REASON

FOR INCOMPLETE

REGISTRATION

1/180 TPD01 R

* o o Required if PLA01 is IN

NUMBER OF INCLUDED

SEGMENTS

1/530 SE01 R R R Total it of segments included in the transmission including the ST and SE

segments.

PHONF-INFORMATTON

CONTACT FOR EC

1/025 Tnfnrmatinn C*c\r\tnc°t T'aII fr**** mimher

REFERENCE NUMBER 1/020 BTP02 R R R A unique #, assigned by the originator of

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

REFERENCE

NUMBER-PREVIOUS

TRANSACTION

1/020 BTP07 R R R Use to indicate the reference # contained

in BTP02. Use in cancellation to indicate the number of the canceled transmission.

REFERENCE NUMBER-TPIN 1/100 N901/02 O O O Cite code.

REGISTERING PARTY 1/060 N101/03/04 R R R Cite code (DUNS).

TIME 1/020 BTP04 R R R The Time the transaction set was created. Use local time, HHMM format.

TIME- PREVIOUS

TRANSACTION

1/020 BTP09 R R R Use to indicate the time in BTP04. Use

in cancellations to indicate the time of the canceled transmission.

TRANSACTION SET CONTROL

NUMBER

1/010 ST02 R R R A unique tt assigned by the originator of

the transaction set.

Federal XI2-3040 15 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE - FED1

TRANSACTION SET CONTROL

NUMBER

1/530 SE02 R R R Transmit the same unique control number

assigned by the originator of the

transaction set, in ST02.

TRANSACTION SET

IDENTIFIER CODE

1/010 ST01 R R R

TRANSACTION SET PURPOSE

CODE

1/020 BTP01 R

0

0

R

0

1

R

0

7

Original, Cancellation, Duplicate.

TRANSACTION SET PURPOSE

CODE

1/020 BTP06 R R R Response (1 1).

TRANSACTION TYPE CODE 1/020 BTP05 R R R Cite code TP.

Federal XI2-3040 16 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE -FED1

838 TRANSACTION SET USAGE

TRADING PARTNER PROFILE

Usage of the segments and data elements arrayed in transaction set order.

TS

POS.

SEGMENT/

DATA INFORMATION

o

R

I

Vr G

C

A

N

c

D

U

P COMMENTS

1/010 ST01 TRANSACTION SET

IDENTIFIER CODE

R R R

1/010 ST02 TRANSACTION SET

CONTROL NUMBER

R R R A unique # assigned by the originator of

the transaction set.

1/020 BTP01 TRANSACTION SET

PURPOSE CODE

R

0

0

R

0

1

R

0

7

Original, Cancellation, Duplicate.

1/020 BTP02 REFERENCE NUMBER R R R A unique M, assigned by the originator of

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

1/020 BTP03 DATE CREATED R R R The date the transaction set was created.

1/020 BTP04 TIME R R R The Time the transaction set was created. Use local time, HHMM format.

1/020 BTP05 TRANSACTION TYPE CODE R R R Cite code TP.

1/020 BTP06 TRANSACTION SET

PURPOSE CODE

R R R Response (11).

1/020 BTP07 REFERENCE

NUMBER-PREVIOUS

TRANSACTION

R R R Use to indicate the reference ft contained in BTP02. Use in cancellation to indicate the number of the canceled transmission..

1/020 BTP08 DATE -PREVIOUS

TRANSACTION

R R R Use to indicate the date contained in BTP03. Use in cancellations to indicate the date of canceled transmission..

1/020 BTP09 TIME- PREVIOUS

TRANSACTION

R R R Use to indicate the time in BTP04. Use in cancellations to indicate the time of the canceled transmission.

1/025 PER01/03/04 PHONE-INFORMATION

CONTACT FOR EC

O O O Information Contact Toll free number.

1/029 LX01 ASSIGNED NUMBER R R R Loop iterations.

1/030 PLA01/02/03 ACTION CODE/

ENTITY/EFFECTIVE DATE

R R Identify the action being taken for either a

successful registration or an inability to

register. Include the effective date of the decision to register or reject.

Federal XI2-3040 17 August 31, 1994
838 - Confirmation of Vendor Registration RELEASE -FED1

1/060 N101/03/04 REGISTERING PARTY R R R Cite code (DUNS).

1/100 N901/02 REFERENCE NUMBER-TPIN O O O Cite code.

1/180 TPD01 DESCRIPTION OF REASON

FOR INCOMPLETE

REGISTRATION

R

* O O •Required if PLA01 is IN

1/530 SE01 NUMBER OF INCLUDED

SEGMENTS

R R R Total # of segments included in the transmission including the ST and SE

segments.

1/530 SE02 TRANSACTION SET

CONTROL NUMBER

R R R Transmit the same unique control number

assigned by the originator of the

transaction set, in ST02.

Federal X12-3040 18 August 31, 1994
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 NISTlRs—from the National Technical Information

Service, Springfield, VA 22 1 61.

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 1 1717 (38 FR 12315, dated May 11, 1973) and Part 6 of

Title 15 CFR (Code of Federal Regulations).

NIST Interagency Reports (NISTTR)—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.
s ^

E

eU

S

o

c

O

E-1 T3c

S3

X)

is

u Q

Q

<3 CO z o

CO

t: « £? -ac .a 3 ~

2 £ o -f