Scrol

SAP Trainings contact sap.sreeram@gmail.com or 091-9916083157, 001-210-399-8414

Showing posts with label sap training in bangalore. Show all posts
Showing posts with label sap training in bangalore. Show all posts

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 - 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.

SAP FICO ASSETS MANAGEMENT Issue - 35

Issue No.: 35
Is it possible to integrate the sale of assets with the SD module? It will involve some sales tax and also the client wants to generate an invoice in the SAP solution. Can the SD module be used for this?

Follow these steps for selling assets with integration with the SD module:

1. Retire the asset without customer (T-code ABAON). This will credit the APC and debit the clearing account (which is a P&L account).
2. Then take a nonvaluated material for asset sale purpose, and sell the same using SD. Make sure you have a
separate pricing procedure/SD document type, etc., where the account key ERL will post to the clearing account mentioned in step 1. You can collect sales tax/excise, etc., as usual.

SAP FICO Issue-11

Issue No.: 11
A company code was assigned to an alternative COA. While creating a new G/L, the user keyed the alternative
G/L in the G/L master. But while saving, the following error occurred: "Alternative Account number already
assigned to account xxxxxx, cannot save." What would be the reason and how can you solve this?


The error is due to the assignment of the operating G/L account to the country COA. You can't assign multiple operating G/L accounts to one country COA G/L account. The relation between the operating G/L and country COA G/L is 1:1. When you are creating the G/L account with reference from some existing account, the alternative COA is also copied here; however, the country COA G/L is already assigned to an operating COA G/L account. This rule is not valid for group COA G/L accounts.

SAP FICO Issue-10

Issue No.: 10
The user is posting monthly entries through T-code FBS1 and reversing them on the first of the next month through T-code F-81. The user wants to automate the reversal procedure.

SAP solutions do come with automatic reversal of accrual entries, but the user has to execute transaction code F-81 for accrual reversal. Accrual entries are made through transaction code FBS1. SAP R/3 includes functionality to enter reversal dates while posting transactions. Once you are executing transaction code F-81, SAP R/3 will provide a list of accrual entries to be reversed. Instead of executing transaction code F-81 manually at an interval, you can create a batch job with a suitable variant and schedule it.

SAP FICO Issue-9

Issue No.: 9
The user has posted the documents without a business area. Now he wants to update them. You know that once a document is posted, the business area cannot be changed in the document overview. How can you solve this issue?

To update the business area, you have two options:

 With the help of ABAP, you can update the business area in the posted document's BSIS table.


Or you could just reverse the original entry and repost the entry with business all the necessary details.
It is advisable to use the second option.


SAP FICO Issue-8

Issue No.: 8
The client processed a bank statement and one of the line items in the bank statement overview in transaction
FEBA shows the status as "Complete." However, the client used a wrong posting rule here. How can you change to the correct posting rule and process the transaction again so that the status is changed to "Posted"

There are two ways to handle this situation:
  •  With a reverse bank reconciliation posting document.
  • By deleting the bank statement from the SAP R/3 system. To delete the bank statement, follow these steps:
1. In T-code SM38, enter RFEBKA95 and execute the program. It will open the posted bank statement.
2. Deselect all and select the statement that is wrongly posted to delete it.
3. Repost the bank statement through T-code FF67.

SAP FICO TCodes (Transaction codes) List -2


FI General Ledger
FB50 Creating and Posting General Journal Entries
F-04 Post with Clearing
F-06 Post Incoming Payments
F-07 Post Outgoing Payments
FBD1 Recurring Document
FB08 Individual Reversal
FV50 Edit or Park G/L Document
FBRA Reset Cleared Items
F.14 Execute Recurring Entries
FBL3N Display/Change Line Items
F-03 Clear General Ledger Account
FS10N Display Balances

SAP FICO TCodes (Transaction codes) List -1


FI Master Records
FS00 Create/Edit GL Account Master Centrally
FD01/XD01 Create Customer
FD02/XD02 Change Customer (Centrally)
FD04/XD04 Display Changes to the Customer Master
FD05/XD05 Block/Unblock Customers (Centrally)
OV50 Customer Master Data Comparison
FI03 Display Bank Master Record
AS01 Create Asset Master Record
AS02 Change Asset Master Record
AS11 Create Asset Subnumber
AS06 Delete Asset Master