The control records that provide tracking and status controls for your data are the following:
■ .FAP ■ .DTP ■ .DST
Each of these control records begins with a .xxx record identifier and the record version. By using a version field, in-network translation can support different layouts of control records to accommodate all of your data translation requirements.
.FAP control record
In-network translation creates an .FAP control record for each .FIL record to track each package during translation processing.
A detailed description of the contents of the .FAP control record follows.
.FAP control record layout:
Version 0 layout:
Name Type Size Description
Record_id Char 4 The record identifier.
Record_version Char 1 The version of the .FAP record.
Name Type Size Description
Application Char 17 The application name and application instance.
Date Char 8 The date the package was created. Time Char 6 The time the package was created. Control_number Char 9 The control number of the package
being tracked.
Record_count Char 8 The number of records in the .TRL record of the package.
Dot_count Char 8 The number of dot (.) records in the .TRL record of the package.
Process_code Char 3 The processing code for the package. Actual_record_cnt Char 8 The actual number of records calcu-
lated by in-network translation in the package being tracked.
Actual_dot_cnt Char 8 The actual number of dot (.) records calculated by in-network translation
in the package being tracked. Process_date Char 8 The date translation processing
started.
Process_time Char 6 The time translation processing started.
Proc_Accept_count Char 8 The number of documents in the package that in-network translation
accepted.
Proc_Reject_count Char 8 The number of documents in the package that in-network translation
rejected.
.DTP control record
In-network translation creates a .DTP control record for each .DOC record in a package to specify errors that may occur during translation. The data in this record is stored in the .DST database.
A detailed description of the contents of the .DTP control record follows.
.DTP control record layout:
Version 0 layout:
Name Type Size Description
Record_id Char 4 The record identifier.
Record_version Char 1 The version of the .DTP record.
Name Type Size Description
Sender_name Char 24 The application or application user that created this document. Receiver_name Char 24 For outbound documents, the
name of your trading partner. For inbound documents, the name of the application or application user.
Layout Char 8 The structure of the data records to be translated.
Test_prod_ind Char 1 Whether the transaction is a test (T) or production (P) transaction. Document_tag Char 60 The unique document identifier
within your application.
Process_code Char 3 The numeric processing code for the package.
Process_type Char 1 Whether the document is a test (T) document or not (F).
Data_type Char 3 The type of translation extension. Translation_extension Char 300 The buffer for translation
extension.
Enter_EDIServer_id Char 3 The time when translation processing begins.
EEC_date Char 8 The date the document was received by in-network trans- lation.
EEC_time Char 6 The time the document was received by in-network trans- lation.
Leave_Transform_id Char 3 The time when translation processing ends.
LTF_date Char 8 The date translation processing of the package ends.
LTF_time Char 6 The time translation processing of the package ends.
Doc_chars Char 8 The number of characters in a .DOC set.
Set_chars Char 8 The number of characters in an EDI set.
Group_Doc_cnt Char 8 The number of documents in a group. For X12, a group is a GS GE pair. For EDIFACT, a group is the UNG/UN_ pair.
Group_chars Char 8 The number of characters in the group segments.
Envelope_Doc_cnt Char 8 The number of documents in an envelope.
Envelope_chars Char 8 The number of characters in the envelope segments.
.DST control record
In-network translation creates the .DST control record from data specified in the .FIL and .DTP records during translation processing.
A detailed description of the contents of the .DST control record follows.
.DST control record layout:
Version 0 layout:
Name Type Size Description
Record_id Char 4 The record identifier.
Record_version Char 1 The version of the .DST record.
Name Type Size Description
Sender_name Char 24 The application or application user that created this document. Receiver_name Char 24 For outbound documents, the
name of your trading partner. For inbound documents, the name of the application or application user.
Layout Char 8 The structure of the data records to be translated.
Test_prod_ind Char 1 Whether the transaction is a test (T) or production (P) transaction. Document_tag Char 60 The unique document identifier
within your application.
Process_code Char 3 The numeric process code for the package.
Process_type Char 1 Whether the transaction is a test (T) transaction or not (F). Data_type Char 3 The type of translation extension. Translation_extension Char 300 The buffer for translation
extension.
Enter_EDIServer_id Char 3 The package identifier. EEC_date Char 8 The date the document was
EEC_time Char 6 The time the document was received by in-network trans- lation.
Leave_Transform_id Char 3 The package identifier.
LTF_date Char 8 The date translation processing of the package ends.
LTF_time Char 6 The time translation processing of the package ends.
Leave_EDIServer_id Char 3 The package identifier.
LEC_date Char 8 The date that in-network trans- lation sent the translated package. LEC_time Char 6 The time that in-network trans-
lation sent the translated package. ACKed_id Char 3 The package identifier.
ACK_date Char 8 The date that in-network trans- lation sent the acknowledgment for the package.
ACK_time Char 6 The time that in-network trans- lation sent the acknowledgment for the package.
Control record for querying translation status
The .QRY control record enables you to query the translation status of your application data.
.QRY control record
The .QRY control record queries the status of a document or transaction set that is stored in the .DST records. You can submit the .QRY record by itself as a single inquiry or with several .QRY records batched together within a package enveloped in .FIL and .TRL records.
A detailed description of the contents of the .QRY control record follows.
.QRY control record layout:
Version 0 layout:
Name Type Size Description
Record_id Char 4 The record identifier.
Record_version Char 1 The version of the .QRY record.
Name Type Size Description
Application Char 17 The application name and appli- cation instance.
Sender_name Char 24 The application or nickname of the application user that created this document.
Receiver_name Char 24 For outbound documents, the nickname of your trading partner. For inbound documents, the name of the application or nickname of the application user.
Layout Char 8 The structure of the data records to be translated.
Test_prod_ind Char 1 Whether the transaction is a test (T) or production (P) transaction. Document_tag Char 60 The unique document identifier