cancel
Showing results for 
Search instead for 
Did you mean: 

variant price not display

Former Member
0 Kudos

Hi,

Gays,

I have a problem in variants, i maintain variant price records (VA),but it did not display in order and PGI also not working.pls give some information to me.

Regards.

rao.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Dear Gauravjit.

It is always better to handle the variant key assignment to characteristic values using Procedures. Since direct assignment method (as told by you) has a limitation that this method will not work with Numeric characetristics.

Regards,

Gaurav Raghav.

Former Member
0 Kudos

Dear Gaurav,

For every query there are a number of resolutions and set-ups available. The set-up always depends at what level the set-up is needed.

In case, variant pricing can be set-up with non-numeric characteristics, then the set-up being mentioned by me can be used.

The <b>biggest advantage is that is much easier</b> to use and set-up rather than using the procedures to set up the variant pricing.

Regards,

Gauravjit.

Former Member
0 Kudos

Go to t-code CU50, In the characteristics assignment for the characteristics, select the desired characteristics value and click on the button, 'assign variant condition'. Enter a value here say 'example'.

Next go to the t-code VK30, create the key here as 'example'.

Next go to the VK11 and for your material use this key as the variant.

This would resolve your problem.

Regards,

Gauravjit.

reward points if the solution is helpful for you.

Reward points if the set-up helps.

Former Member
0 Kudos

Hi Rao.

Please check from the follwoing list if any step you might have missed:

1. make sure ur pricing procedure has VA00/VA01 as per the case.

2. your variant class has Reference char w.r.t. SDCOM-VKOND

3. you have maintained condition record for VA00/VA01

4. Your Material's Config. Profile has procedure with code like

$SELF.<ref_char> = 'Variant Key' IF $SELF.<required_char> = "desired value" .

5. all the objects have status set to 1.

6. variant key is case sensitive, so you have to mention it AS IT IS in the procedure.

Hope this resolves your problem. If not, then let me know the exact problem.

Plz reward if found useful.

Regards,

Gaurav Raghav.

Former Member
0 Kudos

Hi;

Pls check the Pricing Procedure in V/08 T code if the VA00 cond has been maintained as part of the procedure.

Or pls let us know wht is the error message you are getting when you do the analysis in the SO.

Regards,

Mani.