ABAA - AFAR : Unplanned Depreciation - Recalculation of Depreciation

ABAA - Unplanned Depreciation

 

There is an unexpected permanent reduction in the worth of the asset that you have to post as unplanned depreciation.

 

As a rule, the system automatically determines the planned depreciation for the current fiscal year by means of the depreciation keys entered in the master record. If you need to specifically set the amount of depreciation, the system offers a manual unplanned depreciation forecasting option. This means you can manually increase the planned values managed for the asset.The G/L accounts in Financial Accounting are not initially affected by this posting transaction. Asset line items are created, but no FI posting documents. The general ledger accounts are updated and the corresponding FI documents are created by the periodic depreciation posting run. The system then determines the depreciation to be posted up to a specific period, and creates the accompanying posting documents.

 

Transaction type - 640 : Unplanned depreciation on prior year acquistions

 

During posting system automatically calcualtes the depreciation in different amounts for different depreciation areas.

 

After posting you can see the same in AW01N in Planned values section under 'change' column against Unplanned depreciation

 

AFAR - Recalculation of Depreciation

 

This might be necessary if:

 

· You have changed depreciation keys.

· You have made mass changes that you programmed yourself, and these changes affected data relevant to depreciation.

· You want to calculate subsequent revaluation (after the legacy data transfer is closed) using current index figures. In order to correctly calculate replacement values, however, you can only use index series that calculate historically.

 

This program enables you to recalculate planned annual depreciation using the depreciation terms that are valid at the time that you start the report. You can also run the report in test mode. However, you can only recalculate planned depreciation for fiscal years that are still open. After the system recalculates the planned annual depreciation, it creates a statistical log with the total number of assets processed and the number of assets with errors. You can check the assets with errors using the asset value display transaction.
 

SAP: Transfer of Legacy Asset Data Methods

How is depreciation entered during old assets data takeover?

 

Answer:

 

Asset Accounting always manages the values related to the fiscal year.

Depreciation values for previous fiscal years are always entered as cumulative values.

 

Estimated annual depreciation values for the current fiscal year with an old assets data takeover during the fiscal year cannot be entered because they are calculated automatically by the system. Differences from the estimated annual depreciations can therefore only be adjusted as manual value corrections, that is, by entering an asset transaction.

However, if you use a a depreciation key which does not automatically calculate the depreciation, for example depreciation key MANU, the manual depreciation must be entered during the transfer with a 6xx transaction type.

 

If depreciations have already been posted for the takeover year in the legacy system, these values must also be entered into the SAP System sothat they can be used by the posting program.

 

Source: OSS 50607

 

What are the legacy data transfer methods available in Asset Accounting and how are they different?

 

Answer:

 

The following is an overview of the legacy data transfer methods with additional information on the transferring legacy assets R/3 library.

 

1. Manual transfer with Transaction AS91 - This works with Transaction AS01 and is suitable for transferring smaller datasets.

 

2. RAALTD01 transfer via batch input - This is suitable for the mass processing of larger datasets. The batch input session fills the fields of Transaction AS91 up to and including Release 4.0B or of Transaction AT91 for subsequent R/3 releases. Therefore, only the data fields of these transactions can be filled.

 

3. RAALTD11 Transfer via direct input - This is suitable for transferring very large datasets. It transfers the same fields as RAALTD01 does, however it only carries out limited field checks. So that you do not receive any incorrect datasets as a result, first test at random the assets to be transferred in AS91 or as of Release 4.5B with Transaction AT91.

 

Furthermore, bear in mind that value fields are not converted. If, for example you specify a value field for an amount of money in euro in the BALTD-structure, you must consider the format. If, for example the value field has the format ###,## and you only enter 10 as a value, this value is interpreted as 0,10. Therefore you must specify 10,00 as value in BALTD.

 

To achieve the high performance of RAALTD11, the writing of change documents was also dropped. When you go into the change document display of an asset that was created with this report, the system generates the message "Asset created with Transaction AS02" or " ... AS92" by mistake.

 

Both RAALTD01 and RAALTD11 have not been enhanced since Release 4.5B.As of Release 4.6B, the legacy data transfer therefore is recommended via BAPI BAPI_FIXEDASSET_OVRTAKE_CREATE since this offers all of the transfer options of the new Transaction AS91 (as of Release 4.5B).

 

The following methods use this BAPI.

 

1. Transaction AS100 data transfer with Microsoft Excel - This is suitable for the transfer of smaller datasets (limited by the line count of your Excel version). This transaction is suitable in particular if you have mapped your Asset Accounting prior to R/3 using Microsoft Excel. However, you can create only main asset numbers. More restrictions are described in Note 303710.

 

2. Transfers via Workbench LSMW or SXDA - BAPI_FIXEDASSET_OVRTAKE_CREATE is used by Business Object Method BUS1022->Create Incl Values, message type FIXEDASSET_CREATEINCLVALUES and IDoc type FIXEDASSET_CREATEINCLVALUES01.You can also call it for the legacy data transfer even from your own program. You can find more information in the documentation of the function module in Transaction BAPI.

IFRS: The Right Next Step for US Business

Overview

International Financial Reporting Standards (IFRS) is the framework used by most publicly traded companies in the world today to report their financial results. With support from important constituencies, the Securities and Exchange Commission (SEC) and the Financial Accounting Standards Board (FASB) have taken first steps toward a transition to IFRS from the accounting and reporting framework currently in place in the US. Is the US really going to set aside US generally accepted accounting principles (US GAAP)? The answer is almost certainly yes. As this white paper shows, within a few years the SEC is likely to designate a date for mandatory adoption of IFRS by all US public companies.

 

Read Full Story --> Click HERE

 

source: sdn. sap. com

Author: pwc

Data Processing Using ABAP code in LSMW

Data Processing Using ABAP code in LSMW

Before heading towards where and how we can process data using ABAP code I will explain in brief about data migration steps and where LSMW fits in it. Sounds boring, isn't it!!!

 But will be helpful to those who are new to data migration and LSMW.

Let's start!!!!!

Data Migration

It's a process to transfer data from Legacy System to SAP.

Data Migration Steps

 - Analyze the data to be Migrated
 - Create field mapping for legacy to SAP fields
 - Extract the Legacy data
 - Transform the Legacy data to SAP format
 - Load Transformed data to SAP
 - Validate the Data Loaded. 

Read Full Story here 

Author:Vijay Sharma
source:sdn. sap. com

SAP : Business Transaction Events (BTE)

Business transaction events:BTE is Customer Enhancements. It defines the standard interface, how the  communication is done to/from external system to SAP.
 
There are two types of interface available

1. Publish & Subscribe interfaces (also called "informing interfaces")
2. Process interfaces (also referred to as "process" in the following)

Publish & Subscribe interfaces:     These will inform you about particular events (such as a document   being entered) in the SAP standard application and make the data    generated as a result available to the external software.

 

Examples of such events in the R/3 System are:

 

-   Master record was created, changed, or blocked

-   Document was entered, parked, changed, or reversed

-   Items were cleared or reset

 

Process interfaces: Process interfaces are used to submit business processes to a different control which cannot be realized with the standard system,  that is process interfaces replace standard processes. It is possible   to connect different external developments to the standard R/3   System. The additional developments are generally carried out using the ABAP/4 Development Workbench.

 

Click here for full story