|
Нота 9861
Symptom
Key word: Cash management and forecast
For the MM data that is updated in cash management and forecast, the amounts without taxes are listed in cash management and forecast, even though the amounts including taxes are required.
Comment:
This note also applies to Cash Budget Management.
Other terms
Liquidity forecast, FF7B
Reason and Prerequisites
For purchase orders, Materials Management (Purchasing) can only provide the tax amounts/tax rates to cash management and forecast if the taxes are NOT deductible. Taxes are generally not taken into account for purchase requisitions.
Cause:
While tax determination may be performed in Purchasing under certain circumstances:
the tax amounts are not saved in the purchase order
this amount is only available as a total in the purchase order when the input tax cannot be deducted.
Solution
There are no solutions at present. You will have to manually add the tax amounts to the display of MM data in cash management and forecast.
Alternatively you can select the parameter 'distribute amounts' at the liquidity forecast and enter a percentage larger than 100 in View V_T038V for the levels that belong to purchase orders and purchase requisitions. (The columns for plus/minus signs and days remain empty in the view as you merely want to increase the displayed amount rather than actually distributing the amounts.)
Note: the amounts from SD are displayed including tax.
Нота 214151
Attention:: Note not current in language English
Symptom
The tax which cannot be deducted is calculated in the purchase order and is set as a condition, however, this is not valid for the deductible part. Particularly, in the standard system the function is not provided to display or to print the value-added tax.
Other terms
ME21, ME22, ME21N, ME22N, non-deductible tax, value-added tax,
EKPO-MWSKZ, EKPO-NAVNW, NAVS, NAVM, MWST, MWVS, tax code, input tax
Reason and Prerequisites
Up to now no function was provided to display the tax in the purchase order completely.
The following describes how tax is dealt with in purchasing:
1. Determination of the tax code
The tax code is defaulted from the purchasing info record in the purchase order item, however, it can also be determined via the conditions. During the determination via the condition technique an access sequence is assigned in the standard system of condition NAVS. With the latter, different tax codes can be stored via the normal condition maintenance depending on tax indicators (material, plant, account assignment, origin). Basically this access sequence can also be assigned to other condition types. The tax code is only transferred to the purchase order if class "D" (taxes) is the condition type. If several condition types of this type exist in the purchase order item, the first one that contains a tax code is transferred.
2. Calculation of the tax amount
The system only calculates the non-deductible part of the tax. This amount should be regarded as an additional cost item of the procurement because the tax authorities do not refund this amount unlike the deductible part of the tax. Therefore, the non-deductible part of the tax is added to the stock value during the inventory posting. In the purchase order item, the non-deductible tax amount is saved in field EKPO-NAVNW and (if available) in the first condition type of the type "N" (non-deductible tax). In the standard system, these are condition types NAVS and NAVM. For this reason, calculation rule "B" (fixed amount) must be set for the condition type (also refer to Note 138434). You must also bear in mind that the non-deductible tax amount is calculated within the program by means of function module CALCULATE_TAX_ITEM. The calculation does not occur within the price determination. As a result of this, the tax amount is only calculated after you have returned from the condition screen and is not calculated on the condition screen when you change the price.
3. Condition categories supported
In purchasing, only tax condition types of condition category "D" (tax) or "N" (non-deductible input tax) are supported.
4. Display of the tax percentage rate and tax amount
In the standard system, the tax percentage rate and the entire tax amount is not issued: neither in the conditions nor in the purchase order printout.
Solution
It is possible to put the tax amount into a condition with the attached program change which is delivered per Support Packages in Releases 3.1I, 4.0B, 4.5B, 4.6B, and 4.6C. The same applies to the determination of the amount as mentioned in (2).
In Customizing of price determination for purchasing, you must define a new condition type with the following attributes:
Condition class "D" (taxes)
Calculation rule "B" (fixed amount)
Condition type "D" (taxes)
Manual entries "D" (cannot be edited manually)
Item condition "X"
Do not assign an access sequence if another tax condition type with access sequence is already available (this is condition type NAVS in the standard system).
This condition type must be included in the calculation schema. For this, consider the following:
Assign at the end, in particular after the effective value.
Mark as a statistical condition.
Important:
Do not mark as a manual condition.
Do not enter formulas for the condition basis and condition value.
No appropriate condition type is delivered in the standard system. In particular, note that condition types MWST and MWVS are not to be used for this because they are required for the volume rebate settlement.
Нота 501054
Symptom
This text contains a list of frequently asked questions on topic taxes in purchasing.
Questionnaire
1. How is the tax indicator determined in purchase orders?
2. How is the tax jurisdiction code (tax jurisdiction code) determined in purchase orders?
3. How is the tax amount calculated?
4. What must I take into account for Customizing of a tax condition type for purchasing?
5. The deductible tax amount is not to be considered as a cost item of the procurement. Is it nevertheless possible to display it when printing a purchase order, for example?
6. How is the tax determination in purchasing linked with the tax determination in the service (MM-SRV)?
7. For the automatic specification of the tax indicator in purchase orders, I defined an access sequence with own condition tables in Customizing. Why does the system not determine the tax indicator again when changes are made to a purchase order which affect fields of these condition tables?
8. I use a tax handling that works with tax jurisdiction codes. Is it possible to determine the tax jurisdiction code depending on the actual delivery address and to use it for the tax calculation?
9. I use a tax handling that works with tax jurisdiction codes. At the same time, I defined plants with a foreign location for company code in the system. However, the tax handling for purchase orders for these plants does not work or does not work correctly.
10. You create a purchase order for a plant abroad or change such a purchase order. The system generates an error message and/or the tax indicator is not determined correctly.
--------------------------
1. Question:
How is the tax indicator determined in purchase orders?
Answer:
In the standard system, the system consideres the following sources for the tax jurisdiction code (in this sequence): Reference item, contract, request for quotation, info record. It can also be entered manually.
Furthermore, the tax jurisdiction code can be automatically determined via the condition technique.
For the determination of the tax indicator via the condition technique, condition type NAVS with assigned access sequence 003 is available in the standard system. With Transactions MEK1/MEK2, depending on tax indicators (material, plant, account assignment, origin) you can define different tax indicators in the condition tables.
In principle, you can assign this access sequence also to other condition types. The tax indicator is only copied to the purchase order if it is a condition type of class 'D' (Taxes). If there are several condition types of this class in the condition schema, then the first condition schema which contains a tax indicator has priority.
--------------------------
1. Question:
How is the tax jurisdiction code (tax jurisdiction code) determined in purchase orders?
Answer:
You activate the tax handling with tax jurisdiction codes in FI Customizing (transaction OBCO). In the standard system during the creation of a purchase order, the system consideres the following sources for the tax jurisdiction code: Reference item, request for quotation, contract, plant account assignment object. The system always overwrites the previous value in this list. If you maintained a tax jurisdiction code, for example, with account assignment object for a purchase order item, this entry has priority over the entry in the plant table. Besides this, the tax jurisdiction code can be entered manually.
If you use the function from Note 493515, also the tax jurisdiction code from the delivery address can be taken into account (see below.).
--------------------------
1. Question:
How is the tax amount calculated?
Answer:
Only the non-deductible part of the tax is calculated. This amount is to be regarded as additional cost item of the procurement as it is not refunded by the tax authorities in contrast to the deductible part of the tax. The non-deductible part of the tax is therefore added to the stock value during stock posting. In the purchase order item, the non-deductible tax amount is saved in field EKPO-NAVNW and, if existing, it is saved in the first condition type of category 'N' (non-deductible tax). In the standard system, these are condition types NAVS and NAVM. Due to this reason, it is also essential that 'B' (fixed amount) is set as a calculation rule (see also Note 138434) for the condition type. Moreover, you have to take into account that the non-deductible tax amount is calculated with function module 'CALCULATE_TAX_ITEM' program-internally. The calculation is not executed within the price determination. As a result, the tax amount is only calculated again after you have returned from the condition screen and not on the condition screen if you change the price there.
--------------------------
1. Question:
What must I take into account for Customizing of a tax condition type for purchasing?
Answer:
In order to ensure that the tax indicator is transferred to the purchase order and that the tax amount is calculated correctly, you should make the following settings:
Condition class: 'D' (Taxes)
Calculation rule: 'B' (Fixed amount)
Condition category: 'D' (Tax) or 'N' (Non-deductible input tax)
Scale type: ' ' (must remain empty, this means 'can be maintained in condition record')
In addition, take into account that you have to set the tax record which is assigned to a tax indicator in purchasing in FI Customizing (transaction FTXP).
--------------------------
1. Question:
The deductible tax amount is not to be considered as a cost item of the procurement. Is it nevertheless possible to display it when printing a purchase order, for example?
Answer:
This is possible. For this, proceed as described in note 214151.
--------------------------
1. Question:
How is the tax determination in purchasing linked with the tax determination in the service (MM-SRV)?
Answer:
For detailed information on this, refer to Note 495316.
--------------------------
1. Question:
For the automatic specification of the tax indicator in purchase orders, I defined an access sequence with own condition tables in Customizing. Why does the system not determine the tax indicator again when changes are made to a purchase order which affect fields of these condition tables?
Answer:
In order to determine the tax indicator again, the price determination must be triggered again. Due to performance reasons, in the standard system not all changes are taken into account in the header and item fields. As of Release 4.6B using Business Add-Ins (BAdIs) you can, however, define additional fields the change of which triggers a new price determination (see note 495264).
--------------------------
1. Question:
I use a tax handling that works with tax jurisdiction codes. Is it possible to determine the tax jurisdiction code depending on the actual delivery address and to use it for the tax calculation?
Answer:
This is possible. As of Release 46B, by means of a Business Add-In (BAdIs) you can define that and how the tax jurisdiction code defined in the delivery address is to be considered at the tax calculation in the purchasing (cf. Note 493515). This, however, only applies to the 'new' SAP ordering transaction ME21N.
--------------------------
1. Question:
I use a tax handling that works with tax jurisdiction codes. At the same time, I defined plants with a foreign location for company code in the system. However, the tax handling for purchase orders for these plants does not work or does not work correctly.
Answer:
The purchasing uses the FI function for the calculation of taxes. In order to ensure that the tax handling for foreign plants works, you must activate and set the option "Plants abroad" in the FI Customizing. However, this option is not compatible with a tax handling with tax jurisdiction codes. You cand find additional information in the Notes 332499 and 335816.
--------------------------
1. Question:
You create a purchase order for a plant abroad or change such a purchase order. The system generates an error message and/or the tax indicator is not determined correctly.
Answer:
For this application area, the following notes exist:
492935: ME21N ME22N FICORE 704 with company code change
423019: ME21N Incorrect tax jurisdiction code after change of plant
494420: ME21N Incorrect price determination when plant is abroad
 |
|
Вход
Регистрация
FAQ пользователя
Поиск
