SAP ABAP Data Element CATXVARI (Use external transaction data)
Hierarchy
SAP_BASIS (Software Component) SAP Basis Component
   BC-TWB-TST-CAT (Application Component) CATT Computer Aided Test Tool
     SCAT (Package) Computer Aided Test Tools
Basic Data
Data Element CATXVARI
Short Description Use external transaction data  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type CHAR1    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Ext. data 
Medium 15 Ext. TCD data 
Long 29 External transaction data 
Heading
Documentation

Definition

External transaction data:

The transaction field values are read from external text files, not from the CATT buffer.
The field contents are constant values in TCD records, not CATT parameters.
This procedure is a precursor of 'External variants' in which the CATT parameter values for a procedure are saved as data records.
It is still supported for compatibility, but should only be used by experienced users.

Functionality:

The transaction field values are read from external text files whose names are specifed by the procedure or test module. This name assignment means that only one transaction in a CATT module can have external TCD data.
The transaction is run up to 999 times under external control.

The screen sequence in the external data must be identical with the CATT example screen sequence.
The values for BDC_OKCODE and BDC_CURSOR always come from the CATT data.
The values for other screen input fields are generally read from the external files. An appropriate control can cause the CATT field contents to be used for specified screens.

The SPA/GPA parameter CTP provides the path; if this is empty, the standard system path is used.

Text file structure:

Control record WS_UPLOAD from file ABLAUFNR.000
is written back, possibly with changes

Transaction records WS_UPLOAD from file ABLAUFNR.nnn
are not written back

Control record:
Sequence of one line for the general control
and additional lines for the transaction control


First line for the general control:

character from Offset 0 Length 3

000... general control (1st line in set)

character from Offset 3 Length 1

000X... Productive execution of all variants,
is changed to 000R... after execution
000R... no further execution, already executed
productively, log Rcode=10
000T... Test mode, transaction records can be executed
repeatedly, control record not changed


Text from Offset 4 Length 30

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


result field for productive runs from Offset 34 Length 80

000RText...run data (with SPACE separators):
System ID (3-character)
Procedure number (8-character)
Date (YYYYMMDD) (8-character)
Time (HHMMSS) (6-character)
Release (3-character)
Client (3-character)
Language (1-character)
User name (12-character)


Following transaction control lines :

TCD dataset ID from Offset 0 Length 3

nnn Transaction control; the TCD dataset nnn
has a transaction record under
ABLAUFNR.nnn (screens and fields).
TCD dataset ID in range 001 .. 999


character from Offset 3 Length 1

nnnX... Execute TCD dataset nnn, is changed after
productive execution to:
nnnS... Transaction TCD dataset ran successfully
nnnE... Transaction TCD dataset ran with errors
nnnA... Transaction TCD dataset termination
WS_UPLOAD error log Rcode=01..08
screen error in log Rcode=11..99
curr. screen number from Rcode - 10

Text from Offset 4 Length 30

nnnXText... TCD dataset text is passed to the log in &LTX

result field for productive runs from Offset 34 Length 80

nnnSText...Message: Last transaction message

Transaction records:
Sequence of screen lines and field lines

Screen lines from Offset 0 Length 12 or 13
ProgramScrno Program = Module pool (8-character)
scrno = Screen number (4-character)
X = CATT flag (1-character),
i.e. take original CATT field contents


Field lines begin with space, then from offset 1
LnLiNameCont Ln = Field name length (2-character)
Li = Field contents length (2-character)
Name = Field name (Length in Ln)
Cont = Feld contents (Length in Li)

Field lines always refer to the previous
screen line

History
Last changed by/on SAP  20110908 
SAP Release Created in