Appendix B. ASC X12 Nomenclature

id="wpcBookLinkControl_external_code_sources_1" label="Add or Delete Codes" book="cc" page="apa" forumKey="external_code_sources_1" version="15" runat="server"

B.1 ASC X12 Nomenclature

B.1.1 Interchange and Application Control Structures

Appendix B is provided as a reference to the X12 syntax, usage, and related information. It is not a full statement of Interchange and Control Structure rules. The full X12 Interchange and Control Structures and other rules (X12.5, X12.6, X12.59, X12 dictionaries, other X12 standards and official documents) apply unless specifically modified in the detailed instructions of this implementation guide (see Section B.1.1.4 - Decimal for an example of such a modification).

B.1.1.1 Interchange Control Structure

Similar transaction sets, called "functional groups," can be sent together within a transmission. Each functional group is prefaced by a group start segment; and a functional group is terminated by a group end segment. One or more functional groups are prefaced by an interchange header and followed by an interchange trailer. Figure B.1 - Transmission Control Schematic, illustrates this interchange control.

Figure B.1 - Transmission Control Schematic

Transmission Control Schematic


B.1.1.2 Delimiters

Once specified in the interchange header, the delimiters are not to be used in a data element value elsewhere in the interchange. For consistency, this implementation guide uses the delimiters shown in Table B.1 - Delimiters, in all examples of EDI transmissions.

 Table B.1 - Delimiters

CHARACTER

NAME

DELIMITER

*

Asterisk

Data Element Separator

^

Caret

Repetition Separator

:

Colon

Component Element Separator

~

Tilde

Segment Terminator


The delimiters above are for illustration purposes only and are not specific recommendations or requirements. Users of this implementation guide should be aware that an application system may use some valid delimiter characters within the application data. Occurrences of delimiter characters in transmitted data within a data element will result in errors in translation. The existence of asterisks (*) within transmitted application data is a known issue.

B.1.1.3 Data Element Lengths

Data element minimum and maximum lengths are set by the ASC X12 standard. This implementation guide may further restrict minimum and maximum lengths within the bounds set by the standard. Such restrictions may occur implicitly by virtue of the allowed qualifier for the data element, or they may be stated explicitly in a note attached to the element or in the general limitations below.

B.1.1.3.1 Maximum Length of Data Element 127 Reference Identification

The current ASC X12 standard allows a maximum length greater than 50 characters for data element 127. For implementations governed by this implementation guide, unless another value is specified in an attached note, the maximum length of each occurrence of this data element is constrained to 50 characters.

B.1.1.3.2 Maximum Length of Data Element 782 Monetary Amount

For implementations governed by this implementation guide, unless another value is specified for an instance of Data Element 782 within Section 2 (Transaction Set), each occurrence of Data Element 782 (Monetary Amount) will be limited to a maximum length of 10 characters including reported or implied places for cents (implied value of 00 after the decimal point). Note that the decimal point and leading sign, if sent, are not part of the character count.

EXAMPLE

  • The following transmitted value represents the largest positive dollar amount that can be sent: 99999999.99

  • The following transmitted value is the longest string of characters that can be sent representing whole dollars. 99999999

  • The following transmitted value is the longest string of characters that can be sent representing negative dollars and cents. -99999999.99

  • The following transmitted value is the longest string of characters that can be sent representing negative whole dollars. -99999999

B.1.1.4 Decimal

While the ASC X12 standard supports usage of exponential notation, this guide prohibits that usage.