Requirement

[former_member534411]

Hello Guys:

Can you explian the what things has to be done for the following requirment.

The VAT calculation should cover specific PDK relations. In PDK a number of additional services (ie priceconditions) as basis of VAT calculation, where the product is not a VAT-product.

A requirement and a basis formula should be coded. The requirement: Read the conditions for which a intermediate-total (KZWIW) is transferred to the field: XWORD:

Basis formula: VAT is to be based on the value of the XWORD field - this is for the calculation of VAT of the additional services.

Furthermore specific combinations of products and additional services making products normally not VAT relevant becoming due to VAT calculation. The VAT code on the product is to be overwritten by 1, ie the field TAXKM should in the condition be set to 1, if it is actually 0. In that way the VAT calculation will find the proper VAT procedure, S1 which is 25% VAT.

[christian_wohlfahrt]

Hi Suresh,

first the most important part:

<b>never read conditions in requirements (or formulas)</b>.

They are executed many times in one document. If you need additional values, use UE for TKOMK, TKOMP filling and use these values in requirements. You can add own fields in includes KOMPAZ and KOMKAZ, if needed.

(I don't find a intermediate-total KZWIW - I use KZWI1 as example.)

If there is a already a subtotal line in your calculation, you don't need any additional condition base formula - just define subtotal line in field STUNB of VAT-line. Leave field STUN2 empty.

If there is a wild list of conditions (not grouped) adding values to one intermediate-total, then you don't need a requirement. Just create a condition base formula (transaction VOFM, formula, 2nd line), where XKWERT = KOMP-KZWI1. Standard formula 5 is exactly doing this.

Filling XWORD in a requirement should not be done - value assignments should be placed in condition formulas (base / value).

I think there was a standard base formula, where XKWERT = XWORD was assigned - this is probably the reason, why you should fill this now, too.

Just use different formula (like no. 5) instead - there is no need for XWORD.

TAXKM overwriting has to be placed in TKOMP-user-exit (or BADI, depending on your release).

Normally you would have additional lines with service articles - instead of adding service condition values to normal articles. By this way, service can always be tax relevant, no matter which normal products you are handling. (In Retail some different possibilities for automatic service article appends are a available).

In total:

make a review of your concepts, otherwise you will be in trouble (can't garantee correct VAT-value, performance problems in document).

Regards,

Christian

[former_member534411]

Christian Thank you very much for understand the fucntionality requirement...and i will try implement as explained you and let you know if any thing requires from you.

Thanks once a again.

Suresh Babu Karanam