Performing Eliminations of Transferred Assets (SAP Library

Performing Eliminations of Transferred Assets

You can post the automatic elimination and adjustment entries in the consolidation menu under Consolidation ® Elim. of IC profit ® Transferred assets.

The following parameters are optional:

Consolidation is carried out for a subgroup in a particular version at a key date which is determined by year and period. Here, the system applies the consolidation frequency which you entered in Subgroup Master Record Maintenance. In the case of annual consolidation, all asset transfers which took place during the current fiscal year are included. The system also posts any adjustment entries related to previous asset transfers which are still relevant to consolidation. These may consist of adjustments to depreciation or adjustments resulting from the resale of an asset to an external company.

You can select certain document types to determine, say, how deferred taxes are to be treated.

To generate posting proposals, you can run the program in list mode without postings being made.

The list type determines the degree of detail on the audit trail:

List type '1' generates a summarization per company pair and asset. The system displays adjustments to depreciation and the elimination of IC profit for each company.
List type '2' shows how the depreciation and net book values of each individual asset have changed.
List type '3' provides the posting proposal or posting document.

You may restrict elimination to companies and asset numbers.

You can enter threshold values for APC, depreciation and IC profit/loss. If one or more of these parameters are set, then the system takes into consideration only those transfers that exceed at least one threshold value. This means that you can restrict elimination to asset transfers that substantially affect the consolidated balance sheet.

The program for eliminating IC profit/loss in transferred assets does not recognize any table changes which may have occurred since a previous run. It therefore treats all reported data equally as if it were new. As a result, errors are inevitable when the program is run repeatedly with the same parameters and if the postings are actually carried out. You must then reverse the incorrect postings.

When document types with posting level 2 are used, errors also arise if the program is started for different, but overlapping subgroups, even if the parameters are otherwise the same.