Use
Intercompany asset transfer is the transfer of an asset between two company codes. There two steps in an intercompany transfer:
Separate asset master records are required in both the sending company code and in the receiving company code to make the transfer possible (refer to
Intercompany Asset Transfer).
Using the cross-system asset transfer, you can transfer fixed assets across system boundaries or across client boundaries. This function adds to the functions offered by the intercompany asset transfer between company codes in one system or client.
Integration
The intercompany asset transfer is not a case of distributed master data in several systems. It is instead a case of communication between two different logical systems, each of which contains part of a business transaction: one contains the posting of the asset retirement and the other the posting of the asset acquisition. The objects involved are asset master records in both transactions, but these asset master records remain completely independent objects, both in a technical sense and from an accounting perspective.
When you post a normal retirement or acquisition in the asset subsidiary ledger, the system automatically creates the FI G/L posting document with the reconciliation posting at the same time. The system also ensures the same integration with FI for cross-system asset transfers. The FI component in that case can also be managed in a different, central system. If you do manage FI in a separate, central system, the system generates a G/L account posting in that system that corresponds to the reconciliation postings (acquisition and retirement) that were posted in the decentralized systems.

Integration During Cross-System Transfer
Functions in Sending System
Post asset retirement
Functions in Receiving System
Post asset acquisition
Data Flow
During a cross-system asset transfer, the system transfers the following data, from the system or company code, from which the asset is being retired, to the receiving system or company code:

Data Flow During Cross-System Transfer
Technical Information
The transfer transaction acts as an interface for the user to enter data and to receive messages from the system. The actual processing is completely encapsulated in function modules or BAPIs. As a result, it is also possible to carry out the asset transfer using a different user interface or from a different application. The system uses the following function modules and BAPIs (business object: Accounting Asset Transfer BUS6017):
Function modules:
ACC5_GET_ITEMS_FOR_ALE (Determining receiver systems)
ALE_ACC_ASSET_TRANS_ACQ_POST (Creation and sending of IDOCs)
IDOC_INPUT_ACC_ASSET_TRANS_ACQ (Reception of IDOC)
BAPIs:
BAPI_ACC_ASSET_TRANS_RET_CHECK (Post retirement due to transfer)
BAPI_ACC_ASSET_TRANS_ACQ_POST (Post acquisition due to transfer)
BAPI_ACC_ASSET_TRANSFER_POST (Post intercompany transfer)