Fixed Assets : Intercompany Asset Transfer

SAP Intercompany and Intracompany Asset Transfers in SAP Fixed Assets Module

Introduction

Asset transfers play a critical role in managing fixed assets efficiently within an organization. In SAP, asset transfers can occur within the same company code (intracompany) or between different company codes (intercompany). This article focuses on the intercompany asset transfer process in the SAP Fixed Assets module, detailing its methods, advantages, and challenges.

Understanding Intercompany Asset Transfers

An intercompany asset transfer occurs when an asset is moved from the books of one company code to another. This process involves:

• Retirement of the asset in the sender company code

• Acquisition of the asset in the receiver company code

Reasons for Intercompany Transfers

Intercompany transfers may be necessary due to:

• Organizational restructuring requiring asset reassignment to another company code.

• Physical relocation of the asset necessitating reassignment to a different company.

Since an asset's organizational assignment cannot be changed directly, the transfer process must be executed by retiring the asset in the sending company and acquiring it in the receiving company. SAP provides predefined transaction types to facilitate this process, but custom transaction types can also be created based on business needs.

Methods of Intercompany Asset Transfers

There are two primary methods for transferring assets between company codes in SAP:

1. Automatic Intercompany Transfer (Transaction Code: ABT1N)

SAP provides the ABT1N transaction to automate intercompany asset transfers. This method allows for:

• One-step execution: The retirement in the sender company code and the acquisition in the receiver company code occur simultaneously.

• Automatic asset master creation: The receiving company can create an asset master record during the posting process if it does not exist.

• Automatic population of trading partner: Ensures correct intercompany transaction postings.

• Currency conversion: Asset values are automatically calculated and converted based on exchange rates maintained in the system.

• Partial or full asset transfer: Users can specify the portion of the asset being transferred.

2. Manual Intercompany Asset Transfer

A manual intercompany transfer requires two separate steps:

Step 1: Retirement of Asset in the Sender Company Code

• Transaction Code: ABAON

• The asset is retired in the sending company code.

• The trading partner field must be populated with the receiving company code.

Step 2: Acquisition of Asset in the Receiving Company Code

• Transaction Code: ABZP

• The asset is acquired in the receiving company code using the affiliated company acquisition transaction type.

• The trading partner field must be populated with the sending company code.

In the manual method, users must manually select the appropriate gross or net transfer transaction type while posting transactions.

Gross vs. Net Transfer of Asset Values

Depending on the nature of the transfer, asset acquisition can be posted using:

• Gross Transfer: Retains historical APC (Acquisition and Production Cost) and accumulated depreciation.

• Net Transfer: Transfers only the net book value (NBV) without accumulated depreciation.

In the automatic transfer method (ABT1N), the transfer variant controls whether the transfer occurs gross or net. In the manual transfer method, transaction types determine the transfer mode.

Pros and Cons of Each Method

Automatic Transfer (ABT1N)

Pros:

• Single transaction execution.

• Auto-population of trading partner field.

• Auto-generation of intercompany documents.

• On-the-fly asset master record creation.

• Automated currency conversion.

• Control over gross/net transfer via transfer variant.

Cons:

• Requires configuration of cross-system depreciation areas if different valuation purposes exist.

• Additional configuration required for varying depreciation area structures.

Manual Transfer (ABAON & ABZP)

Pros:

• Uses standard SAP transactions.

• Suitable for different depreciation area structures without extra configuration.

• Partial retirements can be handled easily.

Cons:

• Requires execution of two separate transactions.

• Trading partner must be entered manually.

• Manual selection of gross/net transfer transaction types.

• Currency conversion must be handled manually.

Reversal of Intercompany Asset Transfers

Automatic Transfer Reversal:

• Transaction Code: AB08

• Reverses both retirement in the sender company and acquisition in the receiver company.

• If a new asset was created for the transfer, it can be blocked using AS05 to prevent further postings.

Manual Transfer Reversal:

• Retirement and acquisition reversals must be performed separately in their respective company codes.

Conclusion

Intercompany asset transfers in SAP can be handled efficiently using either automatic (ABT1N) or manual (ABAON & ABZP) methods. While the automatic transfer is faster and reduces manual errors, the manual approach provides flexibility when dealing with complex depreciation structures. Choosing the appropriate method depends on business requirements and the configuration of depreciation areas across company codes.

In a future discussion, we will explore cross-system depreciation areas and their role in intercompany asset transfers.