Transaction Code
SPRO Set Company Code Status
OAYE Specify Sequence of depreciation areas
SPRO Specify Transfer Date / Last Closed Fiscal Year
OAYC Specify Last Period Posted in Prv. System (Transf. During FY)
OAYD Transfer Foreign Currency Values
OAYF Recalculate Depreciation for Previous Years
OAMK Set Reconciliation Accounts (Manually)
Set Company Code Status:
SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Set Company Code Status
You use this indicator to specify the status of the company code from the point of view of Asset Accounting:
Test status - You can change values by transferring asset data from a previous system, or by posting.
Transfer status - You can enter and change values by transferring asset data from a previous system, but posting is not possible.
Production status - The asset data transfer is complete. You can only change values by posting. Before the system goes live, it is essential that you set the system status to "production" (not test).
This rule applies even if you transfer asset data from your previous system in several phases over the course of time. If you do transfer data in this way, you have to temporarily remove the "production" setting of the the company code status.
Company code status is generally set to '2' for conversion purposes. This identifies the company code as being in test with data transfer always allowed. This should be the start-up position for the asset company codes.
In the Production system, this setting should be changed to "0 – Asset data transfer completed" once all data takeover activities are completed for each company code.
Once the SAP company code has had at least one Quarter end reported and verified after go-live, and the assets data is deemed stable, the company code status will be set to '0'.
0 Asset data transfer completed
1 Asset data transfer not yet completed
2 Test company code with data transfer always allowed
3 Company code deactivated - reporting allowed
Specify Sequence of Depreciation Areas:
SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Specify Sequence of Depreciation Areas
In this field you define the order in which you want to update depreciation areas with values during legacy data transfer. You determine this sequence by entering a relative number in this field.
During the transfer of legacy data, the first depreciation area to be transferred is generally the book depreciation area.
In this step, the sequence of the depreciation areas for the data takeover transaction is specified. If there are additional depreciation areas for local / fiscal purposes, the sequence for the depreciation areas may be impacted.
Specify Transfer Date/Last Closed Fiscal Year:
SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Parameters for Data Transfer > Date Specifications > Specify Transfer Date/Last Closed Fiscal Year Status
In this step, the asset transfer date for conversions is specified. This setting is maintained in each client to facilitate test conversion activities.
This configuration is mostly maintained directly in each client. You have to enter this date before starting the asset data transfer. In most cases, the transfer date will be the last day of a fiscal year. All transactions starting in the new fiscal year are then carried out only in SAP Asset Accounting. The values transferred are the cumulative values at the end of the fiscal year.
The transfer date can also be during the fiscal year. When the transfer date is within the fiscal year, the values transferred are the values as they stand at the end of the last closed fiscal year before the transfer date. The transactions since the start of the current fiscal year, however, also have to be transferred. This is necessary in order to create the asset history sheet.
This field is only ready for input if the company code is not yet live. The system uses this date to determine the last closed fiscal year.
Specify Last Period Posted in Prv. System (Transf. During FY):
SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Parameters for Data Transfer > Date Specifications > Specify Last Period Posted in Prv. System (Transf. During FY)
The following step is only necessary if you want to perform an old assets data takeover during the fiscal year. In this case, you must specify the period up to which depreciation was posted in the previous system. This period refers to the posted depreciation that is to be transferred during old assets data takeover.
In this field, the system enters the period, for which depreciation was last posted. If the legacy data transfer is carried out during the fiscal year, you must update this field manually.
This field is not available for input if there is no legacy data transfer during the fiscal year, or if depreciation is not posted in this depreciation area.
If the asset takeover date is during a fiscal year, e.g. 31.03.2006, then the last period in which depreciation postings were made in the legacy system must be specified. This setting is maintained in each client.
This configuration is maintained directly in each client.
Transfer Foreign Currency Areas:
SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Options > Transfer Foreign Currency Areas.
You only need to carry out this step if you manage depreciation areas in foreign currencies.
In this step, you determine that foreign currency areas can receive values during old assets data takeover. Then the depreciation areas are not supplied with values from another area by the system, although they are defined as dependent areas by the Customizing settings. This specification can only be made for areas that are managed in foreign currency.
Using this indicator, you specify that you will provide values for the foreign currency area during the legacy data transfer. The system then does not provide values itself for the area (by taking over values from another area, with no changes allowed) as it normally would.
You can only make an entry in this field for an area which is managed in foreign currency.
For any Depreciation area with foregin currency values fixed at the Group Rate as at the takeover date, the takeover values for this depreciation area is calculated manually/automation tool.
Please note that if any change to depreciation area sequence is undertaken, that the manually input flag will change position and will require updating.
Recalculate Deprecation for Previous Years:
SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Parameters for Data Transfer > Options > Recalculate Depreciation for Previous Years
Set this indicator if you want the system to newly calculate accumulated depreciation from past years during the legacy asset data transfer.
You can recalculate the accumulated depreciation from the past, based on SAP depreciation rules, when a depreciation area is newly entered the values from a depreciation area should be recalculated in the R/3 system.for example, conversion data is not available for this depreciation area for these assets
This recalculation is based on the condition that the acquisition value was acquired completely at the time of capitalization. However, for the book depreciation area, this is only possible in company codes that are still in test mode.
You can also recalculate accumulated past depreciation for individual assets using the transaction "change old assets" (Function: recalculate values) after the takeover of data from your previous system.
Set Reconciliation Accounts (Manually) :
SAP Reference IMG > Financial Accounting > Asset Accounting > Preparing for Production Startup > Set Reconciliation Accounts - TCODE: OAMK (OAK5 - for automatically set)
This step is required for conversion purposes. Carried out directly in client during cutover. By default the relevant GL accounts will have been created as reconciliation accounts. As part of the conversion, the flag is removed from the GL accounts per asset class per company code. After the balances have been loaded, the reconciliation flag is reset. OAMK allows this to be carried out manually. Once they are set as reconciliation accounts, the system will only post to them via Asset Accounting from this point onwards. This is maintainable in each client except production where this step is managed by the cutover strategy.
