FAQ for legacy data transfer in SAP_FIN 720
How does the conversion of Asset Accounting to the "standard journal entry" impact the legacy data transfers?
Answer: The process of the conversion of Asset Accounting to the typical journal entry, sub ledger-specific Asset Accounting tables have been eliminated. Going forward all the contents are set up from standard document which is present at runtime. Subsequently it’s impossible to handle the asset sub-ledger and the general individually, while the legacy data transfer is ongoing.
You need to ensure that now you post the takeover values against a transfer G/L account as a transfer document, while the takeover values for each fixed asset were earlier written directly to the sub ledger-specific tables without merging any with the general ledger.
Therefore, there are also changes to process listed below:
Until now, the master data could be maintained master data and takeover values in one transaction (AS91). The G/L account balances in the transfer G/L account are written manually in a summarized format in a separate step altogether.
Now, In the new solution, the master data will still be formed in AS91 and/or altered in AS92. Now the takeover values are posted in a separate manner in the new posting transaction ABLDT. Upon doing this, a posting will be made to the transfer clearing account right away. This means that now it is no longer required to process the manual step for the summary write-off.
Why is the "Takeover values" button not required available in transaction AS91?
Answer: Earlier, the asset values were written straight to a sub ledger-specific totals and balance table (ANLC). This table is outdated and is not revised because of the conversion to the standard journal entry. Instead of this, the values in the former table ANLC are set up during runtime by means of accumulation from standard journal entry persistence. Now it has been designed in such a manner, that all the reconciliation problems between totals and line items in Asset Accounting are completely negated out.
In the present time, rather than writing the takeover values straight to the sub ledger-specific table ANLC (as was previously the case) all the values are, with immediately posted as isolated transfer documents. You will be required to save as well as create the fixed asset in dialog mode (transaction AS91) first. This is applicable to the program design for legacy asset master record maintenance and for all the resulting technical restrictions. Incase the legacy asset has been saved and created, then you should be able to use the "Takeover values" button on the primary screen in transaction AS92 to circumnavigate directly to transaction ABLDT for entering the takeover values. What is significat is that the asset has to first exist first (which is right before you can make a posting to this asset). From transaction AS93, you need to utilize the 'Takeover values' button for navigating to the asset document display (AB03) where the posted transfer documents are all visible and are displayed.
Can I still continue to use both the legacy data transfer BAPI and transaction AS100. if the adjustments also been made to both of them?
Answer: BAPI_FIXEDASSET_OVRTAKE_CREATE and transaction AS100 (which calls the BAPI internally) have been fully attuned to the new logic. Quite contrary to the new dialog mode, the BAPI also provides support to the transfer as well as creation of the legacy asset values in a single stage. In case you wish to transfer mid-year transactions, then it is advised that you see the explanations in SAP 2182475. You must also implement SAP 2231678 in case you want to transfer other transactions (except from acquisitions).
Please : The BAPI supports only the new assets for legacy assets and the optional transfer of values. Both the correction of values transferred previously and the transfer of values to an existing legacy asset are not supported by BAPI.
Why are the similar currency amounts in transaction ABLDT not converted automatically from the base depreciation areas while BAPI_FIXEDASSET_OVRTAKE_CREATE readily translates the values even if they have already been entered?
Answer: Parallel currencies are always to have the historical values. Generally, the conversion of the entire history on a key date with one exchanges the rate will, at best, returns a useful approximated value. What you should keep in mind is that these values should be specified from the feeder system. Otherwise, you would be required to determine these values externally. You need to keep in mind that this system conversion is very dubious.
In order to keep the conversion simple, this questionable mechanism is not required to be implemented in transaction ABLDT. You need to follow the approach listed below: During entry, users determine and acquire detailed values in a beneficial manner.
Earlier, the BAPI, was based on the same ANLC logic as transaction AS91. The conversion was implemented here. The logic has been present for reasons of "feature parity", because BAPIs have to ensure a specific type of stability and compatibility.
The settings in transaction OAYD actually regulate and govern of the values have been converted or transferred 1:1 from the interface values transferred. In case the option to transfer to a foreign currency is active then there are no currency translations performed.
How is the exchange rate determined, if an automatic translation takes place?
- For all the collective year the exchange rate is determined by the start values, on the basis of the activation date of the asset
- For mid-year transactions the exchange rate is determined, on the basis of the date of the legacy data transfer that the transfer of open items for an AuC with line item management (transaction type 900/910) is assessed in this context in the form of a transaction, so when the translation occurs with the exchange rate specifically for the date of the legacy data transfer.
How should I be able to make retroactive changes to the takeover values of a fixed asset?
Answer: Initially, it was possible to change the sub ledger-specific information directly in the table ANLC and therefore operate, as and when required, the takeover values already entered. However, one major drawback was that this particular option was also frequently tainted outside the legacy data transfer, which thus resulted in compromising of the errors and required a lot of effort as these manipulations could be replicated only to a certain extent.
The one and only way to change takeover values is by virtue of reversing the posted transfer document and then reposting these, as this will ensure a higher level of transparency, and to make certain that all the transfer documents are posted in the new solution.
For reversing the transfer document, you need to make sure that the fixed asset must not have any subsequent transactions as the legacy data transfer paves way for the value foundation for this fixed asset. In case the follow-on transactions have already been posted to the fixed asset, the you would need to you first reverse all transactions, it is preferred to reverse in the same sequence, then the transfer transaction has to be first reversed and then finally post the new takeover values. You can also create the follow-on transactions, individually.
Will the new transaction ABLDT support batch input?
Answer: The Transaction ABLDT utilizes an input-enabled ALV grid control. However as per the SAP 311440, it does not have any provision for batch input and neither does it support the same.
As an option, you can use BAPI_FIXEDASSET_OVRTAKE_CREATE.
Would it be possible to perform an LSMW recording in transaction ABLDT?
Answer: It is not possible to create an LSMW recording for transaction ABLDT, the LSMW recording is generally based on the batch input recorder and therefore has the same set of limitations as listed in the SAP 311440.
As an alternate option, you can use BAPI_FIXEDASSET_OVRTAKE_CREATE.
What is the alternative option is available in relation to uploading mass data?
Answer: Initially the batch input was used regularly for transferring the legacy assets in huge quantities. Now this option is no longer available. Additionally, direct input is no longer available.
For transferring mass data, you need to either use either transaction AS100 or the BAPI BAPI_FIXEDASSET_OVRTAKE_CREATE for the legacy data transfer (or the method CreateInclValues for the business object BUS1022). Transaction AS100 can process a maximum of 5,000 assets in one file upload. However, if required you wish you can even divide the file.
When you use LSMW in combination with BAPI_FIXEDASSET_OVRTAKE_CREATE, it may be possible to process. For instance, an Excel file which has more than 5,000 assets in which one fixed asset is always ded by a (very wide) line in the Excel file. For doing this, you need to preserve the field mapping accordingly and then define internally which depreciation areas or depreciation-area-specific information can be stored in which columns (fixed assignment; for example: column BK - BZ contains, by convention, the ANLB information for area 20). This process is quite handy incase the feeder supports an Excel system, from which the data is to be transferred.
In case you need support while you are when setting up LSMW mapping, then you need to reach out to your SAP consultant. Setting up field mapping is considered to be a customer specific consulting service and is not treated as part of standard SAP support.
What all am I supposed to keep in mind while transferring old subnumbers?
Answer: For transferring the sub numbers, you need to implement SAP s 2245187 and 2243637. Else, depending on the data constellation, you will find that in the documents which have been transferred are showing as posted however the corresponding asset sub numbers are absent.
For a mass upload via LSMW with sub numbers, it is significant to know that:
- It is imperative to that if the main asset number already exists, then only the sub number can only be formed.
- Each number must also lock the main asset number once it is formed or created.
You should follow the following steps to split the upload:
- You will first be required to upload of all main asset numbers, which is without completely without sub numbers. You can utilize the standard LSMW parallelization mechanisms for all this.
- Uploading of sub numbers following successful completion of step 1, you need to divide the sub numbers into numerous files so that the corresponding main asset numbers can never arise in two files at the same time. Then these parallel files need to be started without parallel processing. These files can also be uploaded at the same time, which looks like a case of manual parallelization.
- This process is quite effective as it avoids the problem of lock as long as the files are separate with respect to the concerned main asset numbers.
What all do I need to keep in mind while transferring assets under construction with line item management?
Answer: In assets under construction (AuCs), you will not be able to transfer cumulative APC or the accumulated depreciations. This resulted in a scenario, which is due to a program error, which was possible in few cases, in which you would not be able to settle the values to the AuC with line item management. This particular problem was rectified and was resolved for the mid-year legacy data transfers with SAP 2252940 and was applicable for the end-of-year transfers with SAP 2294012. The transfer has to take place by means of the transfer of transactions, so:
With regards to the manual case, and not via transaction ABLDT but via AB01 or, as of SAP 2294012, via the new transaction ABLDT_OI.
For the transfer using BAPI_FIXEDASSET_OVRTAKE_CREATE, you should not enter the values into the table CUMULATEDVALUES; instead enter them into the table TRANSACTIONS.
For transfer, there are special transaction types (900/910). It is advisable not to use the transaction types 970/980. In the case of a special scenario of proportional depreciations for the AuC, these have to be entered as these are proportional depreciations for previous years using the transaction.
How can you transfer the assets under construction for investment measures?
Answer: Currently, the transfers for AuCs for investment measures are not maintained. A transfer can only be used for an independent AuC as described in SAP 29475. The values transferred to the independent AuC have to be transferred posted separately with the AuC settlement to the recipients of the final settlement, during the final settlement.
The other options listed in SAP 29475 (summary investment measure) are presently not yet fully available.
Why am I seeing the duplicate values in the grid after the legacy data transfer?
Answer: The year start values of the legacy data transfer are added as transactions of the current year, and all of these is because the error is corrected with SAP 2212511.
What all has to be kept in mind for transferring depreciations/revaluations/devaluations which have already been posted in the feeder system, incase these have been manually entered and have not been calculated by the system?
- The transferred values need to entered using transaction AB01 and the corresponding transaction type, for the legacy data transfer, including the transferred values which use transaction AB01 and the corresponding transaction type.
- The legacy data transfer date has to be entered as the posting date. You need to utilize the asset value date for controlling the point from when the transaction has to be taken into account, in the automatic calculation of depreciations/replacement values, therefore in accordance with the period control. You need to first implement SAP 2297667.
- You need to ensure that all the appropriate values have been entered for areas with parallel currencies, as these are determined by the system during the entry of the transaction by virtue of the currency conversion which is done on the basis of the posting date.
- If, in the configuration, in "Date Specifications -> Specify Last Period Posted in Prv.System (Transf.During FY)", you have specified a period before the posting period from the transfer date, the system will then alter the posting date which you entered to the last day of the period.
In the peculiar cases, why are the legacy assets not formed regardless of the issue of an error message?
Answer: If you have not implemented all of the program corrections which have been stated here, and also pass input data with errors, then as general rule, this symptom occurs if you have not followed ad and or implemented all of the program corrections referenced here and also pass input data with errors.
This problem can be listed in the following ways:
- The number of "successfully" processed IDocs (status 53) is not matching the number of assets, when the LSMW is used.
- You can navigate from a transfer document to the corresponding legacy asset and even receive error AA-001, which will let you know that the asset does not exist.
- With SAP 2302201, the constancy checks of the input data were improved to avoid such faults.
Irrespective of all this, You need to use your own report to call BAPI_FIXEDASSET_OVRTAKE_CREATE, you need to that incase BAPI has run the assets are originally only flagged only for update. The actual update - in the database – will happen only with the subsequent COMMIT (via BAPI_TRANSACTION_COMMIT), which must be clearly generated by your program.