please don't hate me for asking in this forum - I don't know which one is appropriate but I know here is where the experts are...
Tricky: In sales order creation, we exchange the system-calculated tax value, because in the interface we get the tax values from outside system. For rounding (and other) reasons they may differ from the calculated values.
This is done via userexit in pricing procedure and works fine.
In customizing of copy control (VTFA) for the respective Target billing type, Source sls doc. type and Item category, we already tried Pricing Type D and E. But when we create a billing for the order, calculation of taxes is carried out again.
Any good idea how to suppress pricing calculation os welcome! Or is it just simple cutomizing??
Thanks in advance,
Are you sure your configuration is correct? Here is what the documentation says about 'D' and 'E' and fits exactly to your requirement.
<i>D: Copy pricing elements unchanged. The system
copies the pricing elements unchanged with automatically determined or manually entered surcharges and discounts from the reference document (scales are not read again). This means that the value remains unchanged even if the billing quantity is different to the order quantity
<b>does not redetermine the taxes</b>
E Copy pricing elements and values unchanged. The system
copies the pricing elements and values and automatically determined or manually entered surcharges and discounts from the reference document without changing them (scales are not read again). This means that the value remains unchanged even if the billing quantity is different to the order quantity.
<b>does not redetermine the taxes</b></i>
Check if your document types and item categories are correctly identified.
Also check if your billing document is created referring to a delivery document, not a sales order. In that case, this setting should be done in the 'Copying control: Delivery document to billing document' activity.
If nothing works, may be you can try using the copying requirements to control the taxes.
there is an OSS note (24832) explaining the pricing types in detail. Our first try with 'E' did not look good for whatever reason. Now after transporting to QA it seems to work. We will know tomorrow after severe integration test of the whole interface - more news possible then.