We successfully automated the migration of 15,000+ legacy assets into S/4HANA 1909 using a custom ABAP program that leverages BAPI_FIXEDASSET_CREATE. Our challenge was maintaining complete audit compliance while eliminating manual entry errors that plagued our previous system.
The custom ABAP program reads asset data from staging tables, validates required fields, creates assets via BAPI calls, and logs every transaction with timestamps and user context for audit trail purposes. We implemented batch processing with commit logic every 500 records to prevent memory issues.
Key validation checks include asset class consistency, cost center assignments, and depreciation key mappings. The program generates detailed logs showing successful creations, validation failures, and BAPI return messages. We achieved 98.7% first-pass success rate with complete traceability for compliance reviews.
This approach reduced our migration timeline from 6 weeks to 4 days while ensuring full audit documentation.
What was your data cleansing strategy before the migration? We have similar volume but our legacy data quality is questionable. Did you run validation reports first, or did the ABAP program handle all validations inline?
We built custom logging tables (Z-tables) that capture: source record ID, target asset number, creation timestamp, user ID, BAPI return codes, and before/after snapshots of key fields. Each log entry gets a unique sequence number. We also log validation failures with specific error descriptions. This gives us complete audit trail independent of SAP’s change documents, which was crucial for our compliance team’s reporting requirements.
We committed every 500 records as mentioned - calling BAPI_TRANSACTION_COMMIT after each batch. For time-dependent data, we created separate internal tables for depreciation areas and passed them to the BAPI’s IT_DEPRECIATION parameter. Each asset could have up to 15 depreciation areas configured. The key was maintaining referential integrity between the asset header and time-dependent segments in our staging tables before the BAPI call.