Description
Batch input report CACS_RV14BTCI is used to process condition records:

Note

Structures
Information on the whole batch input session is defined in the session h
eader record.
Information, for example the transaction code and key, on a whole transa
ction is defined in the header record.
A batch input structure is created in the Data Dictionary for each condi
tion table that is to facilitate batch input.
Every structure is identified by record type, condition type and table n
ame.
The structures are as follows:

• BGR00 record type 0 session header record


• BKOND1 record type 1 header data (transaction code, condition type, tabl

e name)

• BKOND2 record type 2 main data (vakey)


• BKOND3 record type 3 scale data

For every field that is transferred in the batch input structure, you mu
st be able to decide whether the value of the field is initial (in otherwords, field is to be reset to the initial value), or whether batchinput is not necessary for this field. For this, you have to agree on aspecial indicator that means: 'No batch input for this field'. Thedefault for indicator for this is '/'.
If you do not want to use '/', you can define another indicator in the s
ession header record in field BGR00-NODATA.
Before the batch input structure is filled, every field in the structure
must have this special indicator as its first character (except for thesession header record BGR00).
The fields in the structures refer to the data elements of the fields in
the original table. This is not the case, however, for numerical andpacked fields. These need their own data elements (category CHAR) forbatch input, as a special indicator cannot be used in a packed field.This allows amounts with a decimal place to be transferred at theinterface.




• File name (app. server): Path and name of file on the application server


• Local file: Path and name of file on the presentation server

This entry is either the file name (app. server) or local file.

• Only check X- file: System does not create BDC session, only the incomin

g file is checked.

Special fields in the session header record:
The session name must be given in the session header record (BGR00-GROUP
). If you send a second session header record, the current session willbe closed and another will be opened.
Special indicator NODATA can be sent in the session header record (see a
bove).
A lock date can also be given (BGR00-START). Any date set must have theformat 'YYYYMMDD'.

Supported transactions:
The following central transaction is supported in the current version:


• XK15 Create condition (for applications V or M)