Sie sind auf Seite 1von 5

Counter Measure for Case there is down payment exist for the same vendor

Ive created a new company by EC01 transaction. I cant modify its name. Could anyone help me? The solution is: o o o o o
Go to SAP IMG SPRO > Enterprise Structure > Definition > Financial Accounting > Edit, Copy, Delete, Check Company Code Double click on Edit company code data Double click on copied company code Shift + F5 (Address data) last address button

When I am posting vendor invoice or vendor payment, SAP system is not giving message Down payment exist for vendor when there is down payment exist for the same vendor, I have selected commitment warnings check box in OBYR transaction for the same special gl indicator. Please let me know, I need to do any other settings in order to get SAP information message. The solution is:
Please check t he message type of F5096 via OBA5 transaction. If it is with message type S, then problem ocurred may be due to the overlapping of other messages. It also means that this message will not appear if another message is sent by the program directly later. You may change the message type S to typeI (always appears) using transaction OBA5, then confirm whether this message is generated correctly or not

Im trying to find a report in SAP FI that will give me Document Number, G/L Account, Amount and Transaction Code. I can find the first three columns in FBL3N transaction but not the transaction code. Does anyone know of a report that gives this info? I know I can get it from BKPF but our users dont have access to SE1 6 transaction. The solutions are:
You can append additional field to FBL3N via customizing step OBVU transaction. In OBVU transaction you must add BKPF-TCODE field. Then call SE38 transaction and run RFPOSXEXTEND program. After these actions, you can select transaction code field in FBL*N reports Execute O7R3 transaction, add field BKPF-TCODE and save. Now, when you execute FBL3N, transaction code will be in the available fields when you try to change the layout

I want to carry forward a ONLY single GL balance to next year. Which SAP transaction code will be using for it?

The SAP report is SAPF011

I am planning to do the fiscal year change using transaction AJRW. I understand that I can continue to keep both the fiscal years open and I can use AJAB transaction and close the old year later. I want to know, if I make any postings in the old year, would it get posted in period 12 or start using period 13. Solution:
It depends on which period is open for posting. If 12 is open it will get posted in 12. Check OB52 transaction for open/close periods in SAP FI module and post accordingly

Is there any standard SAP report for FI-AA that shows assets with acquisition year and acquisition month/period?
SAP Transaction code: S_ALR_87012050

We can create Sort Versions ( OAVI transaction) and add field PRGJR (fiscal year) from SAP table: ANLAV and others as per your requirement. Then use this sort variant in this SAP report.

How to: Set default FI document type in ABAON/ABAVN

SAP Transaction code: AO74 use t o set a default FI document type for retirement transaction in FI-AA (Asset Accounting Module)

I am facing one SAP problem that I have deactivated one of my asset in year 2008 which is showing date as 14.05.2008. And when I am running AR03 transaction. It is showing balance Rs..0.00/- for year 2008. But same when I am running for 2009 it is showing value in Cumulative Acquisition Value column. Please can any one tell me how this happen ? And my client wants to remove that value for year 2009. I believe your Asset which is deactivated does not have any value. that is its net book value is Zero and was deactivated in 2008. Now if it is showing up in 2009 with some acquisition value. The solution are as follows:
1. 2. 3. Check if someone has activated it again and put some acq in 2009. (though it is not a pssobility its worth checking. Try to run a report RACORR55 which should make correct entries in all the asset tables. Even after this if your problem exists then your Asset work list (AR03) has got some problem while deriving values from table. check if there is any OSS note else you can also write to SAP.

I have purchased an AuC of Rs. 107491.40. Now as I am running the Depreciation Posting through AFAB transaction, it is calculating depreciation of 0.40 paisa. Although the depreciation key assigned is 0%. It is calculating the depreciation of 0.40 paisa. What can be the solution for it?
Use the standard depreciation key 0000? or create a own depreciation key with the base method 0002. and Classe 0 No assignment When you use a key with 0 % you have still the risk of rounding differences

Is there any standard SAP report or Transaction code to know the Useful life of the Assets in the SAP system? Check both SAP tables as follows: o o
Table ANLB Table ANLC

When trying to create a new asset with reference to an existing asset in SAP. In this case, the new asset will be in a different asset class from the original asset. The two asset classes have been configured for different depreciation terms. However when I use AS01 transaction and enter the reference asset, the depreciation terms on the new asset now become the same as the reference asset. The depreciation term of new asset can be changed while creating. However, if there is a simple config step that says dont copy the depreciation keys from the existing asset, use whatever the new asset class is configured for. The solution is:
Go AO21 transaction then un-select the copy box against depreciation key indicator

We are currently trying to do transfers in our system. We are substituting the cost center for the assets and are using substitutions for the same. The issue we are facing is that for assets with Capitalised Date On in the current year, the transfers are not taking place. I get an error Field Original Asset is not ready for input. On double clicking the error message, the explanation is:
While creating or changing an asset using function module ASSET_MASTERRECORD_MAINTENANCE, you tried to assign a value to field Original asset. However, field Original asset is not ready for input.

I am facing the above issue only for assets in the current fiscal year. The transfers take place properly in ABT1N transaction for assets with Capitalised Date On in the current year,. The SAP issue seems to be with AR31 transaction.

The solution is: Go to asset master data screen layout and make the field AIBN1 original asset as optional (instead of suppressed).

F1 help on this field says:

This field contains the number of the original asset, which was transferred to the asset being displayed.

Asset under construction field is the original asset field. Make it as either Option or Display

You can create cost element group in KAH1 transaction. These cost elements groups are created at Controlling area level. The cost element groups are created in order to group together the similar expenses. This would be more help in reporting and in the areas of configuration.

The SAP steps to create cost element group are:

1. 2. 3. 4. 5. 6. Go to KAH1 transaction Enter Controlling Area Enter the name of group you want and press Give the description of cost element group Give the range of Cost Element to be inserted or give individual cost element Save

Symptom For a fixed asset, the useful life (or the depreciation key) is changed during the fiscal year. This change affects the planned depreciation of all fiscal years opened in Asset Accounting. For example: Acquisition value: 50 000; useful life: five years (straight-line depreciation across the remaining life); Depreciation start date: January 01, 2001 After the end of the period 03 in the fiscal year 02, the useful life of the fixed asset is changed to three years. The system calculates the depreciation of the year 02 on the basis of the net book value for the fiscal year start date and remaining life. (Net book value: 40 000 / remaining life: two years). However, you require a depreciation calculation for the net book value for the time of the change (net book value: 37 500 /remaining life one year and nine months). Reason and Prerequisites The depreciation calculation is always carried out on an annual basis. Therefore, a useful life change always affects the planned depreciation of the entire fiscal year. Already posted depreciation values (periods of the past) are not affected by the useful life change. Solution The depreciation calculation within Asset Accounting works on an annual basis. In practice, it shows that the useful life changes are frequently made as per the fiscal year start date. However, if you want to display a depreciation calculation with the net book value at the time of the change in the system, proceed as follows. 1. Create a new fixed asset or an asset subnumber with the updated useful life (three years). 2. Post a retirement for the original fixed asset (for which the useful life must be changed). 3. Post an acquisition to the new fixed asset or asset subnumber with a transaction type that permits the entry of proportional values. Post an acquisition with acquisition and production costs of 50 000 and an accumulated depreciation of 12 5000. Use the acquisition posting, for example, the acquisition transaction "ABZO". This permits the entry of proportional values. With the transaction type 158 "Gross interco.transf.acquis.prior-yr acq.", you can enter proportional values. Therefore, in the current year depreciation is calculated only for nine months, the acquisition per day 01 period 04 should be entered. In addition, the depreciation key should use the period control "pro rata per period start". Therefore on the new fixed asset or asset subnumber, 37 500 is calculated with the net book

value, the depreciation key should use the base value "27" (net book value with proportional accumulated deprecations). The procedure described above is certain only for the recommended cases, in which a significant affect on the monthly or quarterly results is due to the useful life change. In all other cases, you should consider the option of an unplanned depreciation or write-up. How do subsequent acquisition and production costs affect the depreciable life of a fixed asset? Reason and Prerequisites * Solution One basically must distinguish whether the depreciation calculation refers to the net book value or to the acquisition value of a fixed asset. The following examples refer to a fixed asset with five years of useful life, an original acquisition of 100 on 1/1/1 and an further acquisition of 50 on 1/1/3. During depreciation of the net book value, the depreciation is always distributed to the remaining life. This causes the net book value to be always zero after the end of the useful life. This effect occurs with subsequent acquisitions within the useful life. This depreciation method (net book value distributed to remaining life) is only defined within the useful life. Acquisitions after the end of the useful life can no longer be depreciated with this method. A conversion to 'after the end of useful life' is absolutely necessary for this. Base value year net book value depreciation 01 100 20 (100 / 5) 80 02 80 20 (80 / 4) 60 03 110 37 (110 / 3) 73 04 73 37 (73 / 2) 36 05 36 36 (36 / 1) 0 During depreciation of the acquisition value, a subsequent acquisition causes an increase of the base value as of this point in time. The point in time of complete write-off on net book value zero changes along the whole planned useful life (if the calculation key allows it). In no case, however, the subsequent acquisition is depreciated with same useful life as the original acquisition. Such a depreciation extension is only achieved by posting the subsequent acquisition to a new fixed asset or a new subnumber. Base value year net book value depreciation 01 100 20 (100 / 5) 80 02 100 20 (100 / 5) 60 03 150 30 (150 / 5) 80 04 150 30 (150 / 5) 50 05 150 30 (150 / 5) 20 End of useful life 06 150 20 (150 / 5) 0