This step provides you with information on transferring condition records. Here you start the program which creates the batch input session for external data transfer.

The procedure for transferring condition records is different to the general external data transfer procedure. One difference is that the legacy system sender structure is predefined by what is known as the record layout generation. The second difference is that an extra step has to be carried out when the data from the legacy system sender structure is transferred to the SAP Banking tables. This involves generating a batch input session. You then process this session to import the data to the SAP Banking tables.

When you process the batch input session, the condition records are automatically created by the SAP system. The condition records refer to:

• Fixed amounts
• Surcharges</< and discounts

The following table structures describe the record layout for transferring condition records :

• BGR00 (record type 0) session record
• BKOND1 (record type 1) header data
• BKOND2 (record type 2) main data
• BKOND3 (record type 3) scale data
  

Make sure you observe the following sequence:

• Deliver the 'session record' first and once only
• Deliver 'header data' for each condition record
• Deliver 'main data' for each condition record
• Only deliver 'scale data' for condition types with scaling and per scale entry.

You can not deliver CSV format here.

Example

• Session record (once)
• Header data (for condition type 1, no scales)
• Main data (for condition type 1, condition record 1)
• Main data (for condition type 1, condition record 2)
• Main data (for condition type 1, condition record 3)
• Header data (for condition type 2, with scales)
• Main data (for condition type 2, condition record 1)
• Scale data (for condition record 1, scale record 1)
• Scale data (for condition record 1, scale record 2)
• Scale data (for condition record 1, scale record 3)
• Main data (for condition type 2,condition record 2)
• Scale data (for condition record 2, scale record 1)
• Scale data (for condition record 2, scale record 2)
  

Recommendation

Carry out a test transfer before you transfer the data to your productive system.

Requirements

To enter data automatically you have to specify how the data from your existing DP system is going to be transferred.

To do this you first have to:

1. Compare the condition record fields with your existing DP system

   To transfer the condition records you first have to compare the fields in your existing DP system with the SAP system.

   Activities

1. Compare the fields and the field contents.
2. Specify which fields can be transferred directly.
3. Create rules determining how the data fields are filled for those fields which cannot be transferred directly
2. Create a data extract for condition records

   Based on the results of the field comparison, create a (data selection) program for extracting the necessary condition record data from the existing DP system.

   Next supply the SAP System with this data in the form of a sequential file.

   Let the SAP System generate the record layout for the data. The SAP system can create the record layout in various programming languages. You can use this record layout as a data declaration for creating the sequential file ("Generate record layout")
   IF = 'SCREEN'

Processing status: not yet maintained.

1. Table settings

   Make the table entries required for maintaining the condition records (condition tables) using the "Flexible procedures" step.
   

The primary requirement for data transfer is that you have written the sender data to a sequential file and made this file available in the SAP System.

Standard Settings

For SAP Banking, the table structures must contain the following values (the fields marked 'X' must always contain the value specified here):

• BGR00-STYPE = 0. " 'X' Record type
BGR00-GROUP = 'KONDITIONSSÄTE'." Name of generated session

• BKOND1-STYPE = 1. " 'X' Record type
BKOND1-TCODE = 'JB44'. " 'X' Trans.for condition maintenance

• BKOND2-STYPE = 2. " 'X' Record type
BKOND2-VAKEY = 'EG0001'. " Key of condition record

• BKOND3-STYPE = 3. " 'X' Record type
BKOND3-KSTBM = 20. " Scale quantity/amount

Table BKOND3 is only required for scale conditions.

For value scales, the scale currency has to be transferred to the field BKOND2-SKONWA.

The NO-data indicator is set in the field BGR00-NODATA. The NO-data indicator has to be used when the field in question is not used in the interface. For example, the NO-data indicator has to be used for %-condition rates in the field BKOND-KONWA (currency).

Activities

1. First transfer the condition records in a test run. In a test run, no session is created.
1. Enter the name and path of the sequential file in which you have set the data from your existing system for the converter program.
2. Set the check indicator (Check file only).
3. Create a batch input session (Execute).
4. Process this session to create the condition records.
5. Test the transferred data.
2. If the test run is successful, transfer the data to your productive system by creating and processing the batch input session
   

Additional Information

For further information on batch input sessions see "BC Kernal Components" in the R/3 Library.