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

Issue No.: 48
When the user is processing asset impairment through transaction code ABMR, the system pops up with the Depreciation Areas screen. The user does not want this pop-up screen. Is there any way of turning off this popup and defaulting to the appropriate areas?

Additional settings for period control OAVH

It is ideally advisable not to change this configuration. This pop-up window lets you select your desired depreciation areas for asset impairment. If you want to avoid this, you have to change the configuration through transaction code OA81. In this transaction code, you are setting automatic posting.

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.

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 ASSETS MANAGEMENT Issue - 33,34

Issue No.: 33
After running depreciation posting for a few months, a user found that a few assets were created in the wrong asset class. The user wants to reclassify these assets to the correct asset class.
Or
Issue No.: 34
The user wants to move assets to another class because the assets were created under the wrong asset class. The old asset is capitalized on 08/01/2008. Since the depreciation key is 000, there is no depreciation running for that asset. Now the user wants to transfer the asset to another class, so the old asset is removed (or may be retired) with an acquisition date of 08/01/2008, so that the depreciation expenses can be calculated from 08/01/2008.

This is a case of reclassification of assets. In transaction code ABUMN, = enter the APC and the accumulated cost along with an asset value date of 08/01/2008. In the receiver asset master screen, enter the desired depreciation key and the depreciation start date.

SAP FICO ASSETS MANAGEMENT Issue - 32

Issue No.: 32
The user wants to post a transaction in the year 2008 through transaction code F-90. While posting the transaction, the system returns the following error: "You cannot post to asset in company code 9999 fiscal year 2008 Message no. AA347."

Diagnosis:
"A fiscal year change has not yet been performed in Asset accounting for company code 9999."

Procedure:
Check the asset value date.

It looks like the user entered an asset acquisition in fiscal year 2008 for company code 9999, for which the assets accounting (AA) fiscal year change has not been carried out.

For AA, it is required that the user carry out the fiscal year change before entering a transaction in the new year.

Run transaction code AJRW to change the fiscal year. The latest date you can run this transaction code is the last business day of a financial year.

SAP FICO ASSETS MANAGEMENT Issue - 31

Issue No.: 31
While running the year-end closing process through transaction code AJAB, the system gives the following errors:

"Asset is incomplete and has to be completed. Message no. AU083"

Diagnosis:

The asset 000000100001-0000 is marked as incomplete. The asset was created by someone who did not have the ‘asset accountant’ asset view. When this is the case, the system expects that certain required fields are not maintained.

Procedure:
You can add the necessary specifications using the master data change transaction and the needed asset view.

The system gives this type of error when the asset master was not properly maintained. You can execute transaction code AUVA to get the list of incomplete assets. After getting the list of incomplete assets, maintain the necessary data for the asset master and rerun transaction code AFAB.

SAP FICO ASSETS MANAGEMENT Issue - 30

Issue No.: 30
After the depreciation run, the user changed the capitalized date and the depreciation start date in the asset master. After making changes in the asset master, the user once again ran depreciation in "repeat run" mode. But changes made to the asset master did not hit depreciation, and the difference value is appearing as a planned value when checked in T-code AW01N.

If you are making any changes in the asset master that affect depreciation that is already posted, you must follow this procedure:
1. Recalculate depreciation using T-code AFAR.
2. Repeat the depreciation run using T-code AFAB.

SAP FICO ASSETS MANAGEMENT Issue - 29

Issue No.: 29
The user wants to transfer an asset from one asset class to another asset class. A depreciation expense of the new asset class is assigned to another account determination. The user wants to transfer APC, accumulated depreciation, and depreciation expenses to G/L accounts that are assigned to the new asset class. Transaction code ABUMN has fields for ACP and accumulated depreciation. The user is wondering how depreciation expenses will be transferred from the old accounts to the new account.

Through transaction code ABUMN, you can reclassify assets. In the reclassification process, you can only transfer APC and accumulated costs to a new asset class with immediate effect. Depreciation expenses will be transferred to the new G/L when you run depreciation. However, during the depreciation run, you can't transfer previous depreciation expenses that were already charged to the cost center. But you can transfer current-year depreciation to the new depreciation expenses account. While entering the transaction in transaction code ABUMN, enter in the value date field the date on which you want to transfer your expenses to the new account.

SAP FICO ASSETS MANAGEMENT Issue - 28

ASSETS MANAGEMENT (AM)
Issue No.: 28
During data migration, the client forgot to transfer two assets whose book values are zero. Now the client wants to bring those assets to the asset portfolio for reporting purposes. The client needs both acquisition cost and accumulated depreciation in FI, including information from the AM module. As the data migration is already done and the company code in question is already in the Go-live stage, how can you bring these two assets to FI— including the Asset module?

The solution for this ticket would be:
1. Set the company code status to "1" Asset data transfer not yet completed.
2. Update legacy data using T-code AS91.
3. Enter the acquisition cost and accumulated depreciation using T-code OASV

SAP FICO ACCOUNTS PAYABLE Issue-27

Issue No.: 27
It is not possible to post multiple customers in transaction code FB70. Can you use F-21?

After starting with FB70 and making as many entries as you wish, if you need to post to other customer accounts you can  press F6, which switches you back to the "old-style" data entry screen where you can post to as many other customer accounts as you wish using the old "posting key" method.

SAP FICO ACCOUNTS PAYABLE Issue-26

Issue No.: 26
The user defined multiple payments in the vendor master, i.e., "C" and "E." As per business requirements, if the business is paying $10,000 or less, the check will be issued to the vendor. For a payment of more than $10,000, the business will pay though wire transfer. As a FICO consultant, the user is looking to you for guidance.

You can define multiple allowed payment methods for the vendor by assigning the payment method in the vendor master. While configuring the payment program through transaction code FBZP, you specify your allowable minimum and maximum dollar amounts for your payment method in the Payment Methods in Company Code step.

Figure  Using transaction code FBZP

Follow these steps to resolve this issue:
1. Set the minimum to 0 and the maximum to 10000 for payment method "C."
2. Set the minimum to 10001 and the maximum to any larger amount for payment method "E."

SAP FICO ACCOUNTS PAYABLE Issue-25

Issue No.: 25
The user has executed transaction code F110 to pay 50 vendors, but he only has 20 checks left. Hence, when he ran the program, it printed the checks with random numbers. Now the problem is he is unable to cancel the payments, as there is no check number. How can he reprint or cancel the checks?

The check printing program generated more checks than there are available check numbers. To handle this issue, follow these steps:

1. Before proceeding, ensure that you have maintained a new check lot through transaction code FCHI. Be sure to correct your check lot before you do anything.
2. In transaction code F110, enter the payment run ID and payment run date.
3. Go to the Printout/data medium tab and place the mouse curser on variant field against print program.
4. From the system menu, choose Environment → Maintain Variants

Figure Using transaction code F110

5. SAP R/3 will show the Maintain variant: XXXX screen, at the bottom of which you will see the section shown in Figure

Figure Using transaction code F110

6. Select Void and reprint checks from payment run already printed. This procedure will void all of the checks
generated through this particular payment program.
If you want to void and regenerate a particular set of checks, enter the check numbers you want to void along with a  void reason code.
7. Save the variant and come back to the payment run screen. Click on to

  generate the desired checks.

SAP FICO ACCOUNTS PAYABLE Issue-24

Issue No.: 24
In transaction code F-33 (bills of exchange discounting), the user entered all data. When this is executed, the user receives a message that A/C No. 400400 (Interest account) requires an assignment to a CO object. What does this mean?

When a controlling area is active, the user has to assign a valid cost object while posting expenses. In this case, bank interest is an expenses account, while posting selects a valid cost object.

SAP FICO ACCOUNTS PAYABLE Issue-23

Issue No.: 23
While posting a transaction through T-code F-58, the user sees this error message: "Changes for vendor XXXXXX not yet confirmed."

In SAP R/3 configuration, you define certain fields as sensitive to have proper control and tracking on master data changes. If the user changes these sensitive field(s), someone other than the user who changed the master data has to confirm these changes. Until such confirmation, the SAP R/3 system does not allow any transactions with that trading partner. For example, you configure payment term as a sensitive field. To accommodate business requirements, user XXXXX updates the payment term with a new payment term ID. In order to carry out any transactions with this business partner, the changes have to be approved by another user.

To confirm this change, the user has to use transaction code FK09. Follow this procedure before executing
transaction code F-58.

SAP FICO ACCOUNTS PAYABLE Issue-22

Issue No.: 22
The user wants to make a check payment for petty expenses like stationery, travel, etc. Transaction code F-02 provides facility to capture check information. Without check information, the user can't do bank reconciliation.The user is wondering if there is any workaround to deal with this situation.

The user can use transaction code F-53 with doc type GZ (General Payments). In the Post Outgoing Payment: Header Data screen, the user has to provide bank data and the check number in the assignment field. After entering this information, the user can switch screens using F-02. To switch the screen, the user must follow these steps:

1. From the system menu, choose Goto → Document overview

Figure Using transaction code F-53

2. After selecting Document overview, the user will get a new screen, in which he can enter expenses by entering the posting key and expenses G/L accounts. For bank reconciliation, the user can choose internal algorithm 15 or 13 for the system to check the assignment field for check numbers.

SAP FICO ACCOUNTS PAYABLE Issue-21

Issue No.: 21
The user wants to print a check for a vendor down payment. To use T-code F-58, the system needs an open item. When the user makes an advance payment, there will not be any open items in the vendor account.

Executing transaction code FCHU

Transaction code F-58 is used to process payment for existing open items. This transaction code can't be used for processing advance payments. You have two options to handle this situation: (1) create an advance payment request and pay through an APP or (2) create an advance payment document through transaction code F-48 and print a check through transaction code FBZ5. Here are the steps for both options:

Option 1:
1. Create a down payment request through transaction code F-47.
2. Run the payment program through transaction code F110

Option 2:
1. Use transaction code F-48 for advance payment to vendors.
2. Based on the posted document number, print a check using transaction code FBZ5

Issue No.: 20
The client needs to update a reference field in the header of a payment document with the check number generated by the system. Is there any way to update the payment document with the check number?

Normally, you follow this process when you have issued a check that is written outside of the SAP solution. To maintain the check register, you have to update the payment document with check numbers. You can achieve this through transaction code FCHU, which will update the payment document with check information. Follow these steps:
1. Go to transaction code FCHU.
2. Fill out the company code, house bank, and account ID areas and give the check number and payment document number for which you want to update the check number.
3. Now, in the Target field selection of the check number section, select the field on which you want to update the check number.
4. Then execute.

SAP FICO ACCOUNTS PAYABLE Issue-19

Issue No.: 19
A user made an advance payment of INR 20000 through a special G/L transaction and deducted withholding taxes, at 2% (Rs. 400.00). Later the user received an invoice for Rs. 30000. Now the client wants to deduct withholding tax on the balance amount, i.e., Rs. 10000, not on the entire amount. If the user uses T-code F-43, it deducts the tax on the full invoice value of Rs. 30000, which is Rs. 600, whereas the user wants the advance payment taken into account and wants to pay Rs. 200 (Rs. 600-Rs. 400).

The user needs to deduct the tax on the entire amount at the time of invoice posting. While adjusting the advance payment against the invoice, the SAP R/3 system will reverse the tax you have deducted.
However, the user needs to make the following configuration in the payment withholding type for this tax reversal to take place:
1. Follow the menu path: IMG → Financial Account Global setting → Withholding tax → Extend withholding tax → Calculation → Withholding Tax Type → Define withholding tax type for payment posting.
2. Select the withholding tax type. At the bottom is a Central invoice window, in which the user will select the last radio button— Central inv. prop

SAP FICO ACCOUNTS PAYABLE Issue-18

Issue No.: 18
A client posted a new document using T-code FBR2. Using T-code F110, payment was also posted for this invoice. After this transaction, it was found that the discount base was wrong and the system had taken the value based on the reference document. How can you reverse a payment posting and change the baseline date?

You have posted a vendor invoice through transaction code FBR2. This transaction code is used to post a new document with reference to an existing document. While posting a new document through transaction code FBR2, SAP R/3 will copy all of the fields from the reference document; however, you can change whatever is needed. After having posted the vendor invoice, you also processed payment for the said document. To correct the baseline date, you have to correct the vendor document. Follow these steps to resolve this:

1. Cancel the payment check via transaction code FCH8 (if the check is in your possession). This transaction voids the check, resets the clearing process, and reverses the payment document.
2. Reverse the vendor document and post a new document with the correct discount base date.

SAP FICO ACCOUNTS PAYABLE Issue-17

Issue No.: 17
A vendor has requested that charges for services and materials be paid through separate bank accounts. For example, Vendor X supplies both services and materials and maintains two bank accounts—one for services and another for materials. The vendor requests that your client pay for services through bank account XXXXX and materials through bank account YYYYY. Is this possible when payments are made through an APP?

A vendor may have multiple bank accounts. The SAP system provides the functionality to store and use information from multiple vendor bank accounts in the Payment transactions screen of the vendor master general data via transaction code FK03.
Figure

You can use the BnkT (bank type) field in the vendor master to enter text differentiators for identifying the vendor's bank accounts. If you leave the bank type field blank for a bank account in the vendor master, it serves as the default bank if the bank type information is missing in the vendor invoice.

In this situation, you maintain information on both banks through the identifiers XXXXX and YYYYY. While entering the vendor invoice for services, select bank identifier XXXXX and for materials, select YYYYY. Now when you are paying through an APP, you will find you are remitting payment to two different bank accounts for the vendor for different services.

SAP FICO ACCOUNTS PAYABLE Issue-16

Issue No.: 16
While posting outgoing payments through T-code F-53, the client received the error message ‘The entry 1210 is missing in table T043G’ and the system did not allow the posting payment document.

The SAP R/3 system returns this error when it doesn't find vendor/customer tolerance for your company code. In this example, you are processing an outgoing payment for a company code for which the vendor tolerance group is not defined. Create vendor tolerance through transaction code OBA3 (menu path: Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Outgoing Payments → Manual Outgoing Payments → Define Tolerances (Vendors)) for your company code.

SAP FICO ACCOUNTS PAYABLE Issue-15

ACCOUNTS PAYABLE (AP)

Issue No.: 15

The client printed 50 checks, of which 10 checks are spoiled or torn. Now the client wants to reprint the checks using the same APP. Is this possible? Or do you have to void those checks that are spoiled or torn?

There may be times when the payment run has successfully posted payment documents and generated checks, but for some reason or other, the checks are not valid. In this situation, you have to void all of the printed checks and reprint them.

To void and reprint, follow these steps:

1. Execute transaction code FCH7. You may navigate to FCH7 through the payment run.
2. Execute transaction code F110, enter the payment run ID and run date, then follow the menu path: Environment →Check information → Change → Reprint Check (t-codeFCH7).
3. Enter the following details:

• Paying company ode
• House bank
• Account ID
• Number of the check to be voided
• Void reason code
• New check number

4. Choose the path: Check → Reprint from the menu.
You must follow this process in a situation where you have issued checks, but the checks are lost in post.

SAP FICO Issue-14

Issue No.: 14
What is ranking order in an APP?

Ranking order represents priority assignments to each house bank. This helps the APP choose the house bank for payment in case there is more than one bank account satisfying the payment program parameters.

SAP FICO Issue-13

Issue No.: 13
While analyzing accounts, the user found that certain document numbers are not appearing or are missing. For
example, number range 17 is assigned to document type KA, which has the range 1700000000–1799999999 valid up to 9999. The current status shows that the next available number is 1790000000. During analysis, the user found that documents 1780000000–1780000010 are missing.
The user wants to know why document numbers are missing.

There are several reasons for missing document numbers. Here are two scenarios for this issue:
1. One possible reason could be that these documents were initially parked and later deleted. In this case, those document numbers cannot be reused.
2. The documents probably don't exist. SAP solutions will set aside numbers for use when the system detects multiple document creation. If someone is creating documents, the system will make available, for example, the next 10 numbers, "reserving them," in essence. If the user only creates eight documents, two document numbers will be missing.

You may use the following programs/reports to find out the reason for the missing documents:

•  Program RFVBER00 provides a list of transactions that failed while updating the database.
•  Program RFBNUM00 shows gaps in the FI number range.

SAP FICO Issue-12

Issue No.: 12
After a transaction was posted, the client learned that an account that was classified as a balance sheet account should have been a P&L account. Now the client wants to reclassify the G/L account. Is this possible?
The reclassification of G/L accounts from a balance sheet account to a P&L account or vice versa is possible. Here are the
steps for such a conversion:
1. You can reclassify a G/L account when its balance is zero. So clear all open items and bring your account balance to zero.
2. Through T-code FS00, change the account type from a BS account to a P&L account. In a standard SAP system, you will get an error message. Note the message numbers.
3. Change the message control by following this menu path: SPRO → Cross-Application Components → Bank Directory → Change Message Control (transaction code OBA5).
4. Enter FH in the Area box (note that this is just an example) and press Enter for the next screen. In the New Entries: Overview of Added Entries screen, enter the two message numbers from step 2 and set the message to W (for Warning).

5. Once you have completed step 4, reclassify your G/L account as mentioned in step 2 This time, the system will issue a warning message and your account will be reclassified once you save your changes.
6. If your books of accounts are closed for the previous year, run program SAPF0110 to carry forward your balance to
the new year.The reclassification of G/L accounts is advisable at either the end or beginning of the year.

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

Issue No.: 7
While creating G/L accounts, some of the G/L accounts were wrongly kept as open item management. Now the
user wants to remove open item management functionality through transaction code FS02, but the system is giving the following error message: "This account does not balance to zero."


System Response:
You cannot switch the open item management specification on or off with this transaction.

Procedure:
If you want to switch this function on retroactively for a certain account, you should create a new account with
the correct setting and use this to make a transfer posting of existing items.

While creating the G/L master, you have to pay utmost attention to the setting of G/L master attributes. The situation here
is changing the attribute of G/L accounts after posting the transaction. For this, you have two options:

 Standard solution:
1. Create a new G/L account.
2. Transfer the account balance from the old G/L account to the new G/L account.
3. Switch off open item management for the old account and retransfer the G/L balance from the new account to the old account.

Without making the account balance zero, you can't switch an open item attribute of a G/L account.

Consulting solution:
As an alternative, the user could try program RFSEPA03, depending on his SAP release. The user may have to copy the program to the "Z" program and remove the piece of code that prevents its use. Before adopting this procedure,make sure the user reads the program documentation and related SAP advice.

SAP FICO Issue-6

Issue No.: 6
There are a few G/L accounts where line item displays are not activated. The client would like to see what
entries are actually hitting these accounts. 

There are two possible solutions regarding this problem. SAP recommends the first solution because only standard means are used. The second solution requires the usage of a correction report and is therefore a consulting solution.

Standard solution:
1. Create a new account and set the options according to your requirements. Be sure to set the line item display indicator (SKB1-XKRES).
2. Transfer the items from the old account to the new account. You can only do this for accounts that you cannot automatically post to. As an alternative, you can transfer the balance completely.
3. Lock the old account for postings.
Consulting solution:
1. Manipulate all documents that were posted in the past. You can use the correction program RFSEPA01
(contained in the standard system as of release 3.0D). Read the document carefully.
2. For releases prior to 3.0D, a corresponding correction program is available on SAPSERV3.
While creating the G/L account, utmost care should be taken with the open item management and line item management attributes of the G/L account.

SAP FICO Issue-5

Issue No.: 5

The user wants to add a trading partner as selection criteria in the F-03 screen. This does not come with the
standard screen.

You are using transaction code F-03 to clear open items for a particular G/L account. While offsetting debit transactions with credits, depending upon business requirements, the user will select one of the selection options provided in that screen. The SAP R/3 system will pull all open items based on the selection criteria. The standard SAP R/3 system comes with very limited selection criteria; however, you can include a new selection field and change the sequence of the selection criteria. To add a new selection field or change the selection criteria sequence, you have to configure the SAP R/3 system through transaction code O7F1.

SAP FICO Issue-4

Issue : 4
How can you add a new column in an open item clearing transaction with T-code F-03? Right now you have a document number, document date, document type, posting key, and amount. You need to add a posting key and amount in the transaction fields in the screen.

1. Go to the Clearing G/L Account Process Open Item screen using T-code F-03 from the menu bar.
2. Select --Settings and Change line layout
3. Select the Create button.
4. Give the line layout a name and description, and press Enter
5. Select the Insert after button to view the available fields.
6. Select the required field by double-clicking on that field. The required field is automatically listed under your own layout.
7. Repeat the process for each field required to create your layout and save.
8. Go back to the Clearing G/L Account Process Open Item screen, and select the Editing option button under the line layout variant for the G/L account clearing transaction.
9. Give your variant a name and save.

SAP FICO Issue-3

Issue No.: 3
My client raised a PO at USD 13 for 50 qty. A goods receipt MIGO transaction was done at that price. Now my client wants to do a MIRO transaction at USD 14 for 50 qty.
 
This situation can be handled in two different ways: (1) price difference or (2) reversing MIGO and repost MIGO with correct price.

1. At the time of the MIRO transaction, you have an option to post a price difference. In the MIRO transaction, enter the G/L account for price difference and amount (i.e., $1).

2. Reverse the MIGO entry, make changes in the PO, then once again do the MIGO and MIRO transactions.

SAP FICO Issue-2

GENERAL LEDGER (G/L) ACCOUNTING
Issue No.: 2
The user is not getting the drop-down list of G/L accounts that he defined through FS00 while posting through transaction code FB50/F-02.
While entering a transaction, the user usually presses F4 to select a G/L account from the chart of account (COA). The SAP R/3 system displays all available accounts that are created for the desired company code and COA in question. If the user is not getting the G/L account in the drop-down list, try one of the following:

1. Check if the G/L accounts have been created in the company code you are posting.
2. Make sure you have selected the correct company code in T-code FB50.
3. The drop-down has a personal list and a global list. If you are in the personal list, switch to the global list.

SAP FICO Issue-1

Issue No.: 1
The user is trying to create a vendor for a particular company code. In the initial screen for the customer, the company code was set to the default and the user is trying to create another company code. 

 

For rapid data entry, some important parameters such as company code and controlling area are set as the default while setting the user profile. If the security role allows, the user can reset or define his own parameters through transaction code SU01. In transaction code SU01, you will find a Parameter tab; this is where you make all default settings. Check the default value for parameter ID BUK. If you don't want any default values, remove them.

SAP FICO Issues Overview

Issues and Resolutions

OVERVIEW

A ticket is a generic name for claims made by the end user to technical support. At the very least, the end user has to send

an email with a description of the issue, the transaction code, and the program or report name. There are some

applications available to manage these jobs, such as Quality Center from HP, ClarifyCRM , and Manage Now , among

others. The tickets usually have a priority scale: T1 (meaning the issue must be handled the same day, T2, T3, etc. The

person in charge of each module for analysis and resolution handles those tickets. If it involves configuration, when you

have missing e.g. cost center, currency or customized reports discrepancy or for third part as ABAP developers for debug

or include functionality. Depending on the nature of the ticket and resolution, necessary code changes will be done in the

development server. Once the SAP team is satisfied with unit testing, changes will be promoted to the quality environment

for user testing acceptance. Once changes are approved by the user, the SAP team deploys the changes in the production

environment.

This chapter presents issues that may arise while using SAP solutions and discusses ways to resolve those issues.