on 04-04-2018 11:31 AM
Hello,
we have created two pricing schema for purchasing.
I have one supplier but under siutation one pricing schema 1 should be used and under situation tow pricing schema 2 should be used. I see i can maintain plant specific the pricing schema.When i maintain plant specific the price schema group my assumation was that based on plant diffrent pricing schema can be found.
Can you help me to understand, if in general price schema group from LFM2 - plant specific - entry will be taken during Purchase order creation?
IF so what are the necessary step in configuration to activate plant specific field not only to be maintained but also to be used.. In gernal i see a lot of fields i can maintain in the plant specific data but its not taken into account during the PO processing..
Dear Tina,
You cannot have 2 different pricing schemas for 2 different plants because you can assign a pricing schemas to a vendor
or to purchasing org only. You can check and define schemas determination with transaction OLME
Conditions -Define Price Determination Process => Define Schema Determination.
For example:
Once you have assigned the pricing procedure schemas to the vendor, then you can create info records with specific to different plants with Material Info Record (Plant-Specific). This price can be maintain with transaction ME11.When create PO, it will pull the plant specific price from table A017. You can test in your system using standard pricing procedure RM0000 and assign to your vendor, then maintain price specific to plant.
Best Regards,
ian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Jurgen and Tina,
Good question.
Unfortunately, the field LFM2-KALSK is not available for input in the standard system. Vendor Schema Group is not available at Vendor Sub-range level for input in the vendor master.
Regards,
ian
If plant based pricing needed- you can create a pricing condition table(Z799) with plant as condition key with other necessary condition keys.
You also can create a new access sequence(ZSEQ) and assign newly created pricing table Z799
For your all condition types- you can assign this newly created access sequence ZSEQ
You can create a new pricing schema and heave those condition types in it, and complete all related master data setting including assigning schema group of vendor to vendor and maintain pricing condition record(MEK1) with plant as key.
Now create a new PO with your vendor and see how price pick base on your plant!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not possible. We have multiple discussions regarding the same scenario in community. Please search.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
7 | |
6 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.