External TCD data 

If a test case is flagged as External TCD data, the field contents of the first transaction are obtained from external text files, not from CATT. The transaction is generally performed repeatedly under external control, up to a maximum of 999 times. The screen sequence in the external data must be the same as the CATT example screen sequence. The values for BDC_OKCODE and BDC_CURSOR are always supplied by CATT. The values for other screen input fields are generally read from the external files. You can specify that the CATT field contents are used in individual screens.

The path is taken from the SPA/GPA parameter CTP. If this is empty, the standard path of the computer is used.

Text file structure

The control record WS_UPLOAD in the file ABLAUFNR.000 is written back, possibly modified. The transaction records WS_UPLOAD from the file ABLAUFNR.nnn are not written back

Control record

A control record is a sequence comprising a general control line followed by transaction control lines. The control record structure is as follows:

The first line contains general control information:

- 000... general control (1st line in record)

- 000X... productive execution of all TCD data desired, is changed to 000R... after execution

- 000R... no further execution desired, already productively executed, log Rcode=10

- 000T... test mode, external TCD data can be executed repeatedly, no change of the control record

- 000XText... general text, is not used internally

- 000RText... procedure data (separated by SPACE):

System ID (3-character)

Session number (8-character)

Date (YYYYMMDD) (8-character)

Time (HHMMSS) (6-character)

Release (3-character)

Client (3-character)

Language (1-character)

User name (12-character)

The following lines contain transaction control information:

- nnn transaction control; a transaction record for the data record nnn exists under ABLAUFNR.nnn (screens and fields).

Data ID in the range 001 .. 999

- nnnX... execution of the external TCD data record nnn desired; changed to one of the following after productive execution:

- nnnS... transaction variant ran successfully

- nnnE... transaction variant ran with errors

- nnnA... transaction variant cancelled

- WS_UPLOAD error in log Rcode=01..08

- screen error in log Rcode=11..99

- screen sequence number from Rcode - 10

- nnnXText... Variant text is passed to the log in &LTX

- nnnSText...Message: last transaction message

Transaction records

Transaction records consist of a sequence of screen lines and field lines. The transaction record structure is as follows:

- ProgramScrno:

Program = Module pool (8-character)

Scrno = Screen number (4-character)

X = CATF flag (1-character), i.e. take original CATF field contents

- LnLcNameContents:

Ln = Field name length (2-character)

Lc = Field contents length (2-character)

Name = Field name (length in Ln)

Contents = Field contents (length in Lc)