Quantcast
Channel: SCN : All Content - SAP ERP - Logistics Materials Management (SAP MM)
Viewing all articles
Browse latest Browse all 6446

VAT code in inboud INVOIC02: Can we override OBCD with EKPO-MWSKZ?

$
0
0

Dear Experts,

 

We are processing intercompany billing through INVOIC02 idoc generated as output message from SD invoice and then posted as LIV in the buying company. The billing is between EU countries. We have an issue with determining input VAT code in the buying company:

- The selling company has one tax code for 0 % tax - EU export (used on all types of goods)

- In trans. OBCD, we can only link this code to one target code in the buying company

- However, the country of the buying company has different rates per types of products - so whatever we choose will be wrong for some of them. (They are obliged to calculate and book a "reverse charge", KTOSL = ESA / ESE, with an equal input and output tax according to their domestic rates.)

 

The best solution for us would be to use the VAT code that is automatically filled in the purchase order item (EKPO-MWSKZ) through conditions in calculation schema. Indeed, if we try to post the incoming invoice manually (trans. MIRO), then this code is proposed. However, it does not work for EDI:

- When OBCD is filled "correctly" then the code from OBCD is used (one for all articles - we do not like it)

- When the target tax code is blank or the whole OBCD record is removed, then it gives an error "Assigning a new tax key for XY and VAT 0 not possible" (FD-008)

- When I manually deleted segments E1EDK04 and E1EDP04 (in WE19), then I got an error "Enter a tax code in item 000001" (M8-755).

 

Neither of the messages can be controlled in trans. OBA5. It did not even help to tick "Calculate tax" or even "Park document" in trans. OBCE. And it would be very inconvenient to break down tax classifications of articles (for use in table MLAN) to cover all combinations of standard / reduced / deeply reduced / zero taxes across various countries where we do business.

 

Has anyone faced a similar issue? Is there a standard solution, or only an enhancement (which one)? All we need is to use EKPO-MWSKZ (from PO item) instead of T076M-MWSKZ (from OBCE) for incoming invoices from certain (intercompany) partners - which is what the standard MIRO does. How to make it work on EDI?

 

Thanks in advance!


Viewing all articles
Browse latest Browse all 6446

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>