SAP - AA : Legacy Asset Data Transfer Configuration Steps

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.

SAP FI-AA: Year End Closing Procedure

==> Settle the Assets under Construction (SAP FI-AA transaction AIAB, AIBU) - Settle the Auc settlement before you do dep.run in each period. So, that the new assets created also consider for depreciation based on the requirement.

==> Execute the depreciation run (report RAPOST2000 or transaction AFAB) (SAP FI-AA) - Execute the dep.run in each period without errors. System will not allow to post the depreciation documents with errors. This has to be finished successfully for all the periods.


==> Run the fiscal year change in Asset Accounting (transaction AJRW) (SAP FI-AA) - Execute the FY change only after depreciation posting without errors. System not allows you to change FY with errors.This process creates the balance carry forwards for Asset Accounting. We recommend that you execute this run on the first day of the new fiscal year. Note: by this time, you should have completed year-end closing for Asset Accounting of the previous year.


==> Carry out period asset postings (report RAPERB2000 or transaction ASKB) (SAP FI-AA)- This is usually done in the client where the derived depreciation area' used. Derived depreciation area amounts posted periodically to the G/L. For posting the documents in this transaction, you need to give the document type and that should be external number range. Same like as depreciation run, this also should end with out errors.


==> Run Account Reconciliation (transaction ABST2) (SAP FI-AA) - Once the above steps are through in green, you can run this report to know about the differences between the FI-GL balances and FI-AA balances.This program selects the asset summary records (ANLC), summarizes the values on G/L account and business area levels, and writes the summarized values to table EWUFIAASUM.

==> Execute the year end closing program (transaction AJAB) - After all successful steps you can close the FI-AA year.

Batch specific units of measure- step by step configuration for Steel industry

Introduction:

In some industry sectors (for example, the pharmaceutical, chemical, steel, or paper industry sectors), the composition or attributes of products vary to some degree. Therefore, you cannot use a fixed conversion factor to convert quantities of these products into various units of measure. Instead, each batch has to be given an individual conversion factor.

This component allows you to handle materials like these throughout the entire logistics chain.

Batch specific unit of measure:

Alternative units of a material for which the conversion ratio to the base unit of measure can be defined on a batch-specific basis.

 

Click here for full story

 

Author: Raja

Source: sdn.sap.com

How to approach multiple currencies for Net order value in PO Release strategy?

Introduction :

In PO release strategy Net order value is the main criteria to decide the release level .If company exists in multiple countries ,we have to use local currency for day to day transaction .If we use multiple currencies based on the country ,it is important to configure release strategy in such a way that it meets all the countries requirement without compromise .we could use only one currency in one characteristic (CEKKO-GNETW) and approval  limit values  vary as per the country requirement .In this regard how to approach this scenario .

 

Click here for full story

 

source : sdn.sap.com

Integration of FI-AA with Real Estate

Asset Accounting (FI-AA) manages fixed assets on a value basis from the accounting point of view.


In Asset Accounting. You have to enter the number of the business entity as an asset group number to set up a link between the Business entity & Asset.

You categorize and structure the objects in to different asset types such as buildings, properties or assets under construction by using asset classes.

Using the asset classes, you control the calculation type for the automatic determination and posting of depreciations, interest and evaluations.

The calculation type for these values is in addition to the legally defined guidelines; it is a customer-specific value range for determining depreciations, calculating interest, insurance values or investment grants. This allows you to define the tax or balance sheet, depreciation and valuation method for internal cost accounting.

A property or building can be assigned more than one asset. To specify the account determination, you have to identify one of the assets as leading.

Customizing settings


FI-AA is activated in Real Estate Customizing
The asset class of the leading asset is set as Real estateA main usage type (for the purpose of account determination) is set for the leading asset ( Main Usage Types); the account determination for the debit position of lease-outs may depend on the main usage type; if no asset is assigned to the building or property, the main usage type is derived from the asset class of the leading asset according to the rule defined in Customizing



The Property, Building text and Main usage type fields are automatically updated under the General Data tab depending on the asset class.

Text field in FI Document automatically from MIRO line item

When a purchase order is created to a cost centre, G/L account and cost centre are entered manually. Often Purchase Order only uses short text field as reference, i.e., Material is not mandatory.

 

MIRO process is then done for PO after GR, and the PO text (short text) is copied into MIRO.

 

G/L account line items can be displayed in FBL3N, detailing the document numbers related to the invoice/PO once posted.

 

The field "Text" is defaulted as blank, even if created with reference to a PO, which contains text. Does anybody know of a way to automate process so that the text field is populated with the text from MIRO?

 

 

You can transfer what ever the data from the MIRO to accounting document-using BTE.

 

Go to SE37 - SAMPLE_PROCESS_00001120 (this is the standard BTE for account document posting). Copy this with ZSAMPLE_PROCESS_00001120.

 

In this you cannot modify the tables t_bkpf and t_bseg. you can use t_bkpfsub and t_bsegsub.

 

For this a little bit config is required.

 

1) Go to t-code FIBF-> settings->Products->... of a customer.

Click new entries -> product name- ZPRODUCT, text - any text, RFC dest - ZSAMPLE_PROCESS_00001120, A - enable check box -> save.

2) Go back -> settings -> P/S Modules -> ... of a customer.

Click new entries -> event - 00001120, Product - ZPRODUCT, Ctr - Country key, Appl - FI-FI, Function module - ZSAMPLE_PROCESS_00001120 -> save.

3) Go back -> settings -> Process Modules -> ... of a customer.

Click new entries ->Process - 00001120, Ctr - Country key, Appl - FI-FI, Function module - ZSAMPLE_PROCESS_00001120, Product - ZPRODUCT -> save.

 

Now go to SE37->ZSAMPLE_PROCESS_00001120 logic.

 

loop at t_bkpf.

loop at t_bkpfsub.

move 'your value' to t_bkpfsub-value.

modify t_bkpfsub index sy-tabix.

endloop.

endloop.

 

loop at t_bseg.

loop at t_bsegsub.

move 'your value' to t_bsegsub-value.

modify t_bsegsub index sy-tabix.

endloop.

endloop.

 

''Your value' is imported value.

 

No need to worry about modified values. After execution of BTE it will go to standard program and copy the values of t_bkpfsub] and t_bsegsub to SAP tables. So please be perfect with code. SAP wouldn't allow change the values in t_bkpf and t_bseg values. you can add your own fields in bkpf_subst and bseg_subst.

 

But make sure that; please write the code in FM with conditions like company code doc type etc. because this BTE is very important. It will execute before acc doc is posted. If you do not specify any conditions it will execute for all co codes in acc doc. it will affect business. You can debug this BTE. Put a break point in FM and see the values while post the MIRO.

 

Once import the values free memory id and clear the variables whatever you used in BTE.