SAP FICO New G/L Issue-56

NEW G/L
Issue No.: 56
The user has reported that the system is not splitting document type SA but is splitting other document types.

In the standard configuration, document type SA is assigned to transaction type 0000, to which no splitting rule is assigned. In these circumstances, the system is expecting that you will enter an account assignment while entering a business transaction.

See how your system is configured in the following menu path:

•  Financial Accounting (New) → General Ledger Accounting (New) → Business Transaction → Document Splitting → Classify document types for document splitting
•  Financial Accounting (New) → General Ledger Accounting (New) → Business Transaction → Document Splitting → Classify GL account for document splitting

SAP FICO PROFIT CENTER ACCOUNTING Issue--55

PROFIT CENTER ACCOUNTING (PCA)
Issue No.: 55
While posting the AP balance to PCA through transaction code 1KEK, the user found that some of the line items are posted to a dummy profit center. The user is expecting these to go to specific profit centers.

A customer and vendor balance consists of open items, i.e., those that are yet to offset. While transferring balances, the system looks for profit centers from the offsetting entry. In the case of open items, the system will not find an offsetting entry and will post line items to a dummy profit center. You can transfer the posting from a dummy profit center to another profit center through transaction code 4KE5.

SAP FICO COST CENTER ACCOUNTING (CCA) issue -54

Issue No.: 54
A client posted an entry to 0001 cost center instead of 4000. Now the client wants to correct the posting without revising the document. How can the correction be done without reversing the document?

Using T-code KB11N, you can repost the costs from one cost center to another cost center.

SAP FICO COST CENTER ACCOUNTING (CCA) issue -53

COST CENTER ACCOUNTING (CCA)
Issue No.: 53
The canteen cost center costs (for example, Rs. 10,000) were to be allocated to other receiving cost centers with "No. of Employees" as the statistical key figure. The canteen cost center also has some employees, so it is becoming both the sender and the receiver for itself. The problem is that when trying to allocate the costs through the distribution method, the system is first allocating some portion of the costs (for example, Rs. 500) back to the canteen cost center and then reallocating the costs to the other cost centers, so that in the end, the debit and the credit balances for the canteen cost center is showing Rs. 10,500 (10,000 + 500). When trying the assessment method, however, the system is sending the portion of the canteen cost center costs back (Rs. 500), it is not reallocating them to the other cost center, and the debit side is showing Rs. 10,500 while the credit side is only showing Rs. 10,000.

When defining assessment, be sure to check the check box for iterative. This will repeatedly allocate the costs to other cost centers until the balance becomes zero.

SAP FICO ASSETS MANAGEMENT Issue - 52

Issue No.: 52
While posting a transaction through transaction code ABSO- Miscellaneous Transaction, the system returns an error message. After further analysis, the user finds that his company code is activated for parallel currencies. How can the user set up depreciation areas for parallel currencies?

If your company code is set up for multiple currencies and has implemented asset management, then be sure you are complying with the following steps:
1. Verify how many currencies are active for your company code. You can verify this setting in transaction code:__(menu path: IMG → Financial Acctg → Financial Acctg Global Settings → Company Code → Multiple Currencies → Define additional local currencies).
2. Review your depreciation areas in AA. In case of multiple currency scenarios, you should have one additional depreciation area for each currency. You can check this setting in transaction code OADB (menu path: IMG → Financial Acctg → Asset Accounting → Valuation → Depreciation Areas → Define Depreciation Areas).
3. For each additional depreciation area, define the depreciation transfer rule with transaction code OABC (menu path: IMG → Financial Acctg → Asset Accounting → Valuation → Depreciation Areas → Specify Transfer of Depreciation Terms). You must set up the transfer values for additional depreciation areas from book depreciation area 01.
4. Similar to step 3, you have to set up the APC transfer rule. You can set up this transfer rule through transaction code OABD (menu path: IMG → Financial Acctg → Asset Accounting → Valuation → Depreciation Areas → Specify Transfer of APC Values).
5. Now you can set up currency for additional depreciation areas through transaction code OAYH (menu path: IMG → Financial Acctg → Asset Accounting → Valuation → Currencies → Define Depreciation Areas for Foreign Currencies).

SAP FICO ASSETS MANAGEMENT Issue - 51

Issue No.: 51

The user posts an acquisition transaction through transaction code F-90 and expects the capitalization and depreciation start date to be filled by the system. SAP help says the capitalization date and depreciation start date will be filled by the system with the first acquisition date. But this is not happening in his case. How can this be resolved?

As per SAP standard practice, on the first acquisition, the system will populate capitalization and the first depreciation date. If this is not happening, check your configuration setting in transaction code AO73 (menu path: IMG → Financial Accounting → Asset Accounting → Transactions → Acquisitions → Define Transaction Types for Acquisitions → Define Transaction Types for Acquisitions).

In the screen that appears, shown in Figure  check whether the Capitalize fixed asset box is checked. If not, check it.

TC AO73

SAP FICO ASSETS MANAGEMENT Issue - 50

Issue No.: 50
A user needs help with the following situation:
Some assets will be purchased for $50 million. Then, after using them for 12 years, they can be sold for $5 million. So, the depreciable basis needs to be $45 million instead of $50 million over 12 years, or $3.750 million per year. The method will be straight line. So at the end of the 12 years, the net book value should be $5 million.

The SAP R/3 system comes with two options to handle the scrap: (1) by defining an absolute percentage or (2) by entering an absolute value.

1. You can define an absolute percentage in the scrap key and then assign the key to the asset master. To define the scrap key, use transaction code ANHAL (menu path: IMG → Financial Accounting → Asset Accounting →Depreciation → Valuation Methods → Further Settings → Define the Cutoff Value Key).

Using transaction code ANHAL

2. Instead of a scrap key, you can enter an absolute amount in the asset master as a scrap value.
Depending upon your other configurations, either the scrap value will be reduced before calculation of depreciation or the system will limit depreciation to the scrap value.

SAP FICO ASSETS MANAGEMENT Issue - 49

Issue No.: 49
How can the user change the screen layout for equipment masters in order to add warranty information?

If you are trying to put the warranty information on the equipment master data record itself, you can configure this in the IMG within the PM module.
Follow the menu path: IMG → Plant Maintenance and Customer Service → Master Data in Plant Maintenance and Customer Service → Technical Objects → General Data → Set View Profiles for Technical Objects.
The transaction code for Set View Profiles for Technical Objects controls various field layouts of the equipment master.

SAP FICO ASSETS MANAGEMENT Issue - 47

Issue No.: 47
The user is configuring the depreciation key. He has a unique requirement for calculating depreciation for the month of acquisition as well as retirement. Here is the requirement:If the asset is purchased from the 1st to the 15th of a month, the depreciation should be calculated for the full month. If the assets are purchased after the 15th of a month, then no depreciation for the month of purchase is calculated. However, depreciation should be calculated for the full month for subsequent months.

The start date and end date of depreciation are controlled through the period control method. You are assigning a calendar here to control how depreciation will be calculated for the acquisition month.
See your configuration by using transaction code OAVH (menu path: IMG → Financial Accounting → Asset Accounting → Depreciation → Valuation Methods → Period Control → Define Calendar Assignments).

SAP FICO ASSETS MANAGEMENT Issue - 46

Issue No.: 46
In January 2008, a user noticed that assets purchased in 2007 were not recorded in the books of account. In the meantime, the user closed the books of account for 2007. Now the user wants to disclose this asset in his books of account from January 2008. 

This issue can be handled in two different ways, depending upon user requirements, i.e., from which date the user wants to calculate depreciation expenses.

1. If the user wants to calculate depreciation from January 2008, then post the asset acquisition using transaction code F-90 with reference to a vendor or using transaction code F-91 through a clearing account.

2. If the user wants to charge depreciation starting from the original purchase date, then post the acquisition through transaction code ABNAN. Then enter that date, 07/01/2007 in this example, in the Orig. val.dat field as shown in

Figure Using transaction code ABNAN

SAP FICO ASSETS MANAGEMENT Issue -45

Issue No.: 45
The user wants to attach JPG pictures of assets to the asset master record. How can he do this?

You can attach JPG pictures to an asset master. From the asset master record menu, choose System → Services for Object → Create Attachment.

SAP FICO ASSETS MANAGEMENT Issue - 44

Issue No.: 44
The user acquired his first set of assets in the month of February 2008 and is trying to run depreciation starting from February. While running depreciation, the system returns the following message: "According to the posting cycle, you should post period 001 next. Either enter period 001, which corresponds to the posting cycle, or request an unplanned posting run explicitly for this parameter."

If your posting cycle is monthly, then your SAP solution expects depreciation to run for every period in sequential order. So, you can't run February until you have completed the January depreciation run. Since you have acquired assets in the month of February, you are not running depreciation for the month of January. However, SAP R/3 is expecting you to run depreciation for January also. To overcome this, you have to do one of the following:
(1) run depreciation for the month of  January and then the month of February or
(2) select the unplanned posting run for February. The unplanned run lets you skip over periods (in instances like this).

SAP FICO ASSETS MANAGEMENT Issue - 43

Issue No.: 43
Assume the following scenario in AA:
Life of the asset: 3 years
Original Cost: 60,000; Scrap Value: 15,000.
The configuration was done in such a way that the SAP solution was taking the original cost as the basis for calculating depreciation. Thus, it is calculating depreciation as follows:
1st Year: 20,000
2nd Year: 20,000
3rd Year: 5,000
However, the user requirement is that depreciation should be calculated based on original cost net of scrap value. That is, depreciation should be as follows:
1st Year: 15,000
2nd Year: 15,000
3rd Year: 15,000

This could be achieved by using T-code AFAMA in SPRO by resetting (for each depreciation key) the scrap value field as "Base Value is reduced by the Scrap Value Amount."

SAP FICO ASSETS MANAGEMENT Issue - 42

Issue No.: 42
Suppose that during year end, the period for both March and April are open and the depreciation run for April is also executed. The asset year closing for the previous year is not done. Now an adjustment in depreciation is to be made in the previous year (for the March period) and the user has to run depreciation once again for March. Is this possible?

Run a depreciation recalculation (transaction code AFAR) before you execute another depreciation run.

SAP FICO ASSETS MANAGEMENT Issue - 41

Issue No.: 41
The user is trying to create an asset master using transaction code AS01. He is able to see fields in the General, Time dependent, and Allocations tabs, but is not finding fields in the Depreciation Area tab. As a result, the user is unable to specify the depreciation key and life of an asset.

1. Check your screen layout for depreciation areas (transaction code AO21).
2. In T-code OAYZ, make sure that the depreciation areas are activated and a depreciation key is assigned. Also, check the screen layout rule for the depreciation area. It is the last column in the table after useful life and index. This is where you enter the depreciation screen layout.

SAP FICO ASSETS MANAGEMENT Issue - 40

Issue No.: 40
When you retire an asset, you only want the depreciation that has been posted to be reversed, i.e., accumulated depreciation up to the last month has to be reversed. However, the system is also taking the current month's unplanned depreciation into consideration when reversing accumulated depreciation and hence the profit and loss is calculated incorrectly. How can this be changed?

You assign the period control method in the depreciation key. The period control method controls how depreciation will be calculated during acquisition, retirement, etc. Check the period control method assigned to your depreciation key, which in turn is assigned to the asset master.

SAP FICO ASSETS MANAGEMENT Issue - 39

Issue No.: 39
The user is trying to post unplanned depreciation for an asset for depreciation area 33, i.e., the depreciation area for group currency, using the transaction type 643 and T-code ABAA. While posting, the following message pops up: "In Dep. Area 01, you can post manual depreciation up to the amount 0.00 only." The assets explorer shows the net book value as $1800.

This error generally appears after posting the unplanned depreciation when the net book value of those assets after considering the planned depreciation becomes negative. Depreciation does not allow negative book values.

SAP FICO ASSETS MANAGEMENT Issue - 38

Issue No.: 38
In AA the client has not closed the year 2005, and so 2006 cannot be closed. For 2005, there are errors and recalculations required for depreciation. However, if this is done, it will hit the FI and figures submitted for 2005will change in the SAP solution. From an audit perspective, this cannot be permitted. How can the user remedy this?

The corrections must be made to enable you to close FI-AA for 2005 and carry forward into 2006. If these corrections will significantly change your balance sheet, you can "neutralize" them by posting manual entries to bring your overall balance sheet back to what has already been reported, and then reverse these in 2006. And convince your auditor accordingly.

SAP FICO ASSETS MANAGEMENT Issue - 37

Issue No.: 37
While creating assets under asset class XXXX, the user is getting default depreciation terms and the system does not allow changing depreciation terms. The user does not want the default depreciation key. How can you resolve this situation?

It sounds as if the depreciation key has been set as the default for the asset class. Check this in the IMG by doing the following:

1. Go to the Depreciation Areas screen layout using T-code OA21. This transaction determines how fields of
depreciation areas in the asset master behave. This transaction code controls whether or not fields are editable.

2. Determine depreciation areas in an asset class using T-code OAYZ. This transaction code determines screen layout of the asset class and depreciation keys assigned to that asset class.

SAP FICO ASSETS MANAGEMENT Issue - 36

Issue No.: 36
While capitalizing assets, the user capitalized $10,000. During the year-end process, the user realized he has wrongly capitalized $10,000 instead of $7,000. Now the user wants to rectify this by posting a credit transaction through transaction code F-90. While crediting, SAP R/3 returns the following message: "acquisition value negative in the area 15." What does this mean? How can you solve this issue and correctly post the document? Is there any other way to decapitalize an asset? 

To see the negative book value check box, you will have to first activate it in the screen layout. To do this, go to Master Data → Screen layout for Asset depreciation areas, select the screen layout attached to the asset class to which the asset in question belongs, and click on Field group rules. Here you can make negative values optional. If you want to allow the negative book value for all of the assets created in that particular asset class, follow the menu path: Valuation → depreciation areas → Determine depreciation areas in the asset class. Select the asset class, click on the depreciation area, and check the negative book value check box.

If you want to allow negative book values only for a particular asset, you can use transaction code AS02. Go to the Depreciation tab, double-click on depreciation area 15, and then check the negative values allowed check box.