X12 Implementation. Guidelines. For. Transfer Version (996o)

Size: px

Start display at page:

Download "X12 Implementation. Guidelines. For. Transfer Version 3030. (996o)"

Eunice Johns
8 years ago
Views:

1 X12 Implementation Guidelines For Outbound ss File Transfer Version 3030 (996o) 996_3030 (003030) 1 April 29, 2003

2 996 File Transfer Functional Group ID=FT Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the File Transfer Transaction Set (996) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit file information in formats agreed to by the sending and receiving parties. This transaction set is not intended to replace or bypass the use of existing X12 transaction sets to accommodate internal applications. The transaction set is solely intended for the exchange of formatted electronic accounting machine (EAM), 80 column card images. Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 ST Transaction Set Header M 1 M 020 BGF Beginning Segment for File Transfer M 1 Information M 030 K3 File Information M >1 M 040 SE Transaction Set Trailer M 1 996_3030 (003030) 2 April 29, 2003

This transaction set is not intended to replace or bypass the use of existing X12 transaction sets to accommodate internal applications.

3 Segment: ST Transaction Set Header Position: 010 Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Semantic Notes: 1 The transaction set identifier (ST01) is 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: M ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 996 X12.32 File Transfer M ST 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 996_3030 (003030) 3 April 29, 2003

Comments: M ST01 143 Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 996 X12.

4 Segment: BGF Beginning Segment for File Transfer Information Position: 020 Max Use: 1 Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set Semantic Notes: Comments: 1 Due to the installation of the ST segment in all transaction sets, data element 143 in all of the "B" segments is redundant. DE 143 will be retained as an optional data element for a period of adjustment. It is suggested that DE 143 not be transmitted so it may be dropped from segment definitions in the future. The reference number qualifier code for file identifier is "FI". X BGF Transaction Set Identifier Code O ID 3/3 Code uniquely identifying a Transaction Set Refer to Data Element Dictionary for acceptable code values. M BGF Reference Number Qualifier M ID 2/2 Code qualifying the Reference Number. FI File Identifier M BGF 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. 996_3030 (003030) 4 April 29, 2003

DE 143 will be retained as an optional data element for a period of adjustment. It is suggested that DE 143 not be transmitted so it may be dropped from segment definitions in the future.

5 Segment: K3 File Information Position: 030 Max Use: >1 Purpose: To transmit a fixed format record Semantic Notes: Comments: M K Fixed Format Information M AN 1/80 Data in fixed format agreed upon by sender and receiver X K Record Format Code O ID 1/2 Code specifying the format of information Refer to Data Element Dictionary for acceptable code values. 996_3030 (003030) 5 April 29, 2003

upon by sender and receiver X K302 1333 Record Format Code O ID 1/2 Code specifying the format of

6 Segment: SE Transaction Set Trailer Position: 040 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). Semantic Notes: Comments: 1 SE is the last segment of each transaction set. M SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments M SE 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 996_3030 (003030) 6 April 29, 2003

M SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments M SE02 329 Transaction Set

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 003020 996 File Transfer