Knowledge Management

Question:
Does anyone know how the tax code (on the invoice tab at the item level of the purchase order) is determined?
Any help would be gratefully appreciated.
Answer:
Hi,
It is determined based upon the setting in Transaction FTXP (definition of Tax Code); OBYZ (creation of Tax Procedure) and OB40 (Mapping of Transaction/Event Key with G/L account).
Cheers,
HT
Answer:
Ok - so in transaction FTXP, I define the tax codes (V1, V2 etc). How is this code determined in the purchase order? At the moment V1 is defaulted in on the invoice tab of the purchase order. This may be incorrect. At present we manually change this in MIRO when doing invoice recognition. Is there a way to determine this tax code automatically?
Answer:
Hi,
The tax code is always copied from the purchasing info record.
Cheers,
HT
Answer:
Hi
At present we manually change this in MIRO when doing invoice recognition. Is there a way to determine this tax code automatically?
In case of MIRO the tax code is defaulted from settings in OMR2 .
Please check in settings whether V1 is defined or not. This tax code gets defaulted in MIRO header level.
Thanx
Prasad
Answer:
Hi Prasad,
I would recommend to set up this customizing for unplanned delivery costs instead of material costs (which should be copied/defaulted from PO). The process that I think would be applied is to start from info record ---> PO and then IR (through LIV). In case, the info record is not maintained, it is also possible to look at the utilization of condition record for automatic default into PO.
Cheers,
HT
Answer:
Hi Ha Tran
I do agree with you . I was just giving the reason why the tax code V1 gets defaulted in MIRO header level .
We use OMR2 settings for unplanned delivery cost only.
Thanx
Prasad
Answer:
Hi
The tax code can be determined at line item in the PO in 2 different ways.
(1) Default in the tax code from the info-record or contract.
(2) Using the condition technique.
- By setting up condition records for condition type NAVS you can populate the tax code at item level within the PO however you see fit. If the SAP standard key combinations do not satisfy your requirements then you can create new condition tables and assign them as new steps in the associated access sequence linked to condition tyoe NAVS.
Regards,
Roos
Answer:
>>>>>>>>>>>>>>>>>>>>
By setting up condition records for condition type NAVS you can populate the tax code at item level within the PO however you see fit
>>>>>>>>>>>>>>>>>>>>
I set up NAVS condition record CC>Region>Tax cat level and tax is populated correctly in the PO.We are also using scheduling agreement for the same material and vendor combination but tax code is not copied for SA items.Why this is happening.
For specific reason we won't be using tax code at info record level and we want to get it only from NAVS condition record level for schedule agreement items.
Regards
Answer:
Hi,
It is determined based upon the setting in Transaction FTXP (definition of Tax Code); OBYZ (creation of Tax Procedure) and OB40 (Mapping of Transaction/Event Key with G/L account).
Cheers,
HT
Hi Ha Tran,
Do you know if the tax code (BSEC-SCD1) of a OTA vendor can be included in PO?
I found where to include it in a invoice in MIRO, but I need to include that information in a PO.
(I'm not refering about the fees we pay to for buying. I refer to the international code that identify the vendor in his own country when it pays his taxes)
Thanks, Emilio
Answer:
Hi,
(I'm not refering about the fees we pay to for buying. I refer to the international code that identify the vendor in his own country when it pays his taxes)
I am not quite sure if you can use the item tax to capture this info. Besides, I don't know which particular field in vendor master data record did you use to keep this info.
Cheers,
HT
Answer:
Hi,
(I'm not refering about the fees we pay to for buying. I refer to the international code that identify the vendor in his own country when it pays his taxes)
I am not quite sure if you can use the item tax to capture this info. Besides, I don't know which particular field in vendor master data record did you use to keep this info.
Cheers,
HT
Well, the field description says for LFA1-STCD1:
Tax number 1
Specifies the tax number.
Use
Enter the appropriate tax number:
Country Tax Number
Argentina CUIT number or CUIL number
Belgium Trade register number
Brazil CNPJ number
Bulgaria Unified identification code
Chile RUT number
China VAT registration number (shui wu deng ji
hao)
Colombia NIT number
Croatia Legal persons: company identification
number
Natural persons: JMBG number
......
Dependencies
In the Philippines, enter the taxpayer identification number with a V or
N at the end, as follows:
o If the business partner is liable to VAT: 999-999-999-999V
o If the business partner is not liable to VAT: 999-999-999-999N
In our legal terms, we have to include the tax number in the PO. It's easy in regular national vendors because we defined the tax number as the Vendor Account Number, but in OTA vendors I don't have a field to store the tax code in PO. I think I will have to use a text field in PO header ....
Thanks, Emilio