Description of Transfer Format
BALTD (Master Data and Values)
The master data to be transferred has to be in a sequential input file and be structured according to Dictionary structure BALTD:
EOR| Key |
Master data | Area-01
| ... | Area-08
|EOR
(EOR = end of record)
You can see the exact structure of the transfer record by choosing Goto → Analyze Files and Data Structures → Structure → Display in the Data Transfer Workbench. You can create a record layout for this structure with the programming languages COBOL, C, ASSEMBLER and PL1 in the Data Transfer Workbench.
Make sure that the 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 master data you should always enter record type A In the TCODE field, you have to specify the transaction for which batch input should be created:
- AS91 (create legacy asset)
- AS92 (change legacy asset)
- AS94 (create sub-number for legacy asset)
- AS81 (create legacy group asset)
- AS82 (change legacy group asset)
- AS84 (create sub-number for legacy group asset)
· Master data
The fields of the asset master record which are independent of the depreciation areas are in the general asset master data. In particular you should specify the main number and the sub-number of the new asset master record here, if you provided for external number assignment in the number range or in the asset class.
Enter the number of transactions that should be transferred with the asset in the field BWCNT (refer to Description of the Transfer Format BALTB (Transactions)).
Transfer investment keys into the fields INVSL01, INVSL02,... and so on.
The cost center of an asset cannot be transferred with time dependence. It is only possible to transfer the cost center that is currently valid. You can enter a cost center history after the transfer, using the legacy data transaction (AS92).
· Area-01 to area-08
The fields of the block for area-nn can be recognized by the suffix nn in the field name. They contain the entries to be transferred for the depreciation area into the field AFABEnn, that is
– Depreciation terms and
– Transferred values
The sequence of the fields is identical in every area-nn.
Depreciation Terms
AFABG01 ordinary depreciation start date
ZINBG01 start date for interest calculation
SAFBG01 special depreciation start date
AFASL01 depreciation key
NDJAR01 useful life (years)
NDPER01 useful life (periods)
WBIND01 index series
ALIND01 index series (age-dependent)
APROP01 variable depreciation portion
UMJAR01 changeover year
NDURJ01 original useful life (years)
NDURP01 original useful life (periods)
SCHRW01 scrap value
NDABJ01 expired useful life (years)
NDABP01 expired useful life (periods)
ANDSJ01 expired useful life of special depreciation (years)
ANDSJ01 expired useful life of special depreciation (periods)
ANLGR01 group asset (main number)
ANLGR201 group asset (sub-number)
INBDA01 date ready for start-up
VYEAR01 acquisition year
VMNTH01 acquisition month
RSTCK01 remaining units depreciated
Values
KANSW01 cumulative acquisition value
KAUFW01 cumulative revaluation of replacement value
KINVZ01 cumulative investment support
KNAFA01 cumulative ordinary depreciation
KSAFA01 cumulative special depreciation
KAAFA01 cumulative unplanned depreciation
KMAFA01 cumulative transfer of reserves
KAUFN01 cumulative revaluation of ordinary depreciation
KZINW01 cumulative interest
AUFWB01 posted revaluation of replacement value
NAFAG01 posted ordinary depreciation
SAFAG01 posted special depreciation
AAFAG01 posted unplanned depreciation
MAFAG01 posted transferred reserves
ZINSG01 posted interest
AUFNG01 posted revaluation of cumulative ordinary depreciation