Requirements in pricing

[Former Member]

Dear Gurus

in our scenario we have TAX caliculation on MRP in some cases and on Stokist price in other cases

and further, whenevr it is Tax on MRP even the Free goods are considered for Tax caliculation.

unlike this If it is tax on PTS free goods are exempted for TAX caliculation.

we have defined different condition types for all above. we have called requirement '2' (Item with pricig') agaist Tax conditoion 'JLST' in pricing procedure. whre as for ZVAT(MRP based TAX condition) type no requirement has been called.

but now we need ZVAT(MRP based TAX condition) to neglect Free goods in (Chattisgud state).

can some body tell how can we make this condition behave in two ways

Regards,

Jim

[ivano_raimondi · Accepted solution]

Hello Jim,

just to be sure about your request:

- you have the same item category for both "normal" items and free-goods item

- in pricing procdure thare are two tax conditions:

-- JLST with requirement 2

-- ZVAT without requirement

You want ZVAT NOT determined in the free-goods item, but determined in normal item.

Is it correct my understanding ?

Best regards,

Ivano.

[Former Member · Accepted solution]

Hi Ivano

we have diffrent item categories for each i.e 'YP15' for Normal and 'YP16' for free.

JLST ( Tax on VAT)has requirement '2'

where as ZVAT( Tax On MRP) doesn't, as this needs to be caliculated on both Normal and Free.

but the same ZVAT needs to neglect Free goods in on state as per thier local Agreements.

Hope i'm clear now!

Regards

Jim

[Former Member · Accepted solution]

Hi,

You can use tax classification indicator to cater the requirement and maintain the condition record as per tax classification

So at order -item level you can change it and make non taxable.This will resolve ur problem

Regards,

Krishna O

[Former Member · Accepted solution]

Hi O Krishna

that sounds great

would you pls eloborate a bit more on this

can you tell how it can be done little more clearly!

Regards

Kiran

[Former Member · Accepted solution]

Hi,

Create two classification indicator ( 0- tax exempt ,1-liable for tax).

Now assign this to tax relevancy customer and material master in IMG.

Maintain the condition record as per the tax classification for customer and material .

Now lets say for one material you dont want to have tax applicable ,so go to billing tab at item level and change the tax classification to 0 or vice a versa.

Hope this will resolve ur issue.

REgards,

Krishna O

[Former Member · Accepted solution]

Hi

thanks for that!

that was very helpful

but still can't resove as the field in billig agaist normal item is editable but the same for the free goods is gryed out

so can't change the tax class key

more over in our case there will be somany items in each document so changing for every item manually is quite a time taking task!

so waht do you sugest!

Regards

Jim

[Former Member · Accepted solution]

hi

i just want to know whether we can go for a new requirement creation with the help of abaper!

if so what do you sugest?

can we create, what implications it will have?

regards

jim

[Former Member · Accepted solution]

Hi,

yeah you can go ahead and create a routine for requirement in pricing in VOFM.

Regards,

Krishna O

[Former Member · Accepted solution]

If you are using a same document type for free goods then you are left with the item category to pick up a specific Tax Code which will have a 0% rate which can automate the process. You need to add an access in the access sequence which you are using for ZVAT where you need to have an item category as one of the parameter. Since item category is not in the standard pricing field catalog so you need to have the following enhancement:

a. Call the ABAP Dictionary (transaction SE11) and create the data type ZZPSTYV. Select PSTYV as the domain. As the short description, you can use 'ZZ - Sales Document Item Category' (for example) and as the field labels, you can use the field labels of the data type PSTYV. Save, check and activate your entries.

b. In the ABAP Dictionary (transaction SE11), enter the structure KOMPAZ, switch to change mode and make the following entries:

Component Component type

ZZPSTYV ZZPSTYV

Save, check and activate the change.

c. Note: Due to the changes in the structure KOMPAZ, the field ZZPSTYV is now known in the structures KOMG and KOMP because the structure KOMPAZ is included in both structures.

d. Call transaction SPRO. Go to 'Sales and Distribution > Basic Functions > Pricing > Pricing Control' and execute 'Define Condition Tables'. Select 'Conditions: Allowed fields' and enter ZZPSTYV as a new entry.

e. Note: When you create the condition table Axxx, you can now use the field ZZPSTYV as a key field.

f. Populate the new field you defined by including the following source code line in the user exit USEREXIT_PRICING_PREPARE_TKOMP:

MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.

In order processing, the user exit is available in the include MV45AFZZ, and in billing document processing, it is available in the include RV60AFZZ.