Description of Transfer Format BALTB (Transactions) (SAP Library - FI Financial Accounting: Data Transfer Workbench)

Background documentation Description of Transfer Format BALTB (Transactions)

The transactions to be transferred have to be structured according to Dictionary structure BALTB:

EOR| Key | Transaction data | Amount 01 | ... | Amount 08 |EOR

(EOR = end of record)

All transaction records for a fixed asset have to be structured in the same way as the transfer record for the master data of the asset (Dictionary structure BALTD). The transaction records are separate data records. In the input file, make sure they are separated from the previous record by an end of record indicator.

The structure BALTD for the transfer of master data and values (refer to Description of the Transfer Format BALTD (Master Data and Values) contains the number of transaction records that belong to a master data transfer record. This information is contained in field BWCNT:

EOR Master data record EOR Transaction record1 EOR Transaction record2 EOR ... EOR

You can also use the Data Transfer Workbench to create a record structure in various programming languages for table BALTB.

Note

Make sure that the R/3 release with which you create the data structure is the same as the release to which the data is transferred.

The individual record parts have the following meanings:

Key
The key consists of these fields:

MANDT (client)
BUKRS (company code)
ANLKL (asset class)
OLDN1 (legacy asset main number)
OLDN2 (legacy asset sub-number)
TCODE (accessed transaction)
RCTYP (record type)

For transactions always enter record type B.

Transaction data
The general transaction data consists only of two fields:

BWASL (transaction type)
BZDAT (asset value date)

Amount 01 to amount 08
Amounts belonging to the depreciation areas AFABEnn are transferred to the fields ANBTRnn. You can set up certain depreciation areas in Customizing for Asset Accounting so that they adopt their posting values from a reference depreciation area. You no not have to enter values for such depreciation areas, unless they differ from the amounts in the reference depreciation area.

Example

Depreciation area 01 is managed in the block for area 01, and area 20 is managed in the block for area 03, (this means. in the BALTD structure, AFABE01 = 01 and AFABE03 = 20). If area 20 adopts its posting values from area 01, then you only need to transfer values for the ANBTR03 field if you want the values in area 20 to be different from the values in area 01.