Skip to Content

SD Pricing : Cross Module Reference Condition Type (Config)

Hi Team,

Some times we may need to copy price from MM Condition record to SD condition Record. There can be various reasons as mentioned below:

1) In India, Excise calculation Base needs to be kept same for Intra Company STO / Inter Company STO and Billing Document.

2) Base Price needs to be kept same Bet’n STO and Invoice.

3) Certain Discount or Surcharge needs to be copied from MM to SD or Vice Versa.

When first time I tried , I faced difficulty but got successful in the same, so thought to share it with you also.

Below are the steps which I had followed:

  1. Created Identical Condition Type in SD and MM. It needs to be identical considering SAP needs controlling point like Condition Class / Calculation Type.

MM Condition Type:

MM Condition Type.JPG

MM Access Sequence:

MM Access Sequence.JPG

SD Condition type : (It is identical to MM Condition type, Only Ref. Condition Type field is updated with MM Condition type and Application as Purchasing.)

SD Condition Type.JPG

SD Access Sequence : (Observe here, I have used Same Condition Table which was created in MM., If you will press F4, You will not see those Condition Table but If you will directly enter the same, System will allow MM Condition Table in SD as well.)

SD Access Sequence.JPG

SD Pricing Procedure :

SD Pricing Procedure.JPG

2) Maintain Condition Record for MM Condition Type by MEK1 T-Code.

MM Condition Record Maintenance.jpg

3) Maintain Condition Record for SD Condition type by VK11 with Zero Price. (Why Do we need to maintain this ?? Ans: In SAP For Populating condition value from Other Module condition record, system search that if this condition has been proposed in Pricing or not. That’s why we need to maintain Condition record with Zero value so it get’s Populated in Pricing.)

SD Condition Record Maintenance 1.JPG

SD Condition Record Maintenance 2.JPG

4) Create STO and reach till Billing Creation with Standard way. Check the Pricing now in Invoice.

SD Pricing in Invoice.JPG

Sd pricing in Invoice 2.JPG

Sd pricing in Invoice 3.JPG

As per above Screenshots, system has called MM Condition record to SD Pricing.

Hope this will useful and Helpful to all.



You must be Logged on to comment or reply to a post.
  • Dear,

    Nice document 🙂 .

    Note : I think,you have very good knowledge on SAP modules .Rather than go by this type of concepts ,come with what you have faced Issues in your experience .It would be very helpful to all users or else choose any unique concepts ( like any good / new scenarios ) .



  • Hi Jani,

    Very nice document. thanks for sharing,keep on sharing your knowledge some more documents like this 🙂 .



  • Dear Jani ur document is simply super,,,, 🙂 🙂

    1)In India, Excise calculation Base needs to be kept same for Intra Company STO / Inter Company STO and Billing Document.

    2)Base Price needs to be kept same Bet’n STO and Invoice.

    3) Certain Discount or Surcharge needs to be copied from MM to SD or Vice Versa

    It is very helpful if you discussed a little bit more , more beneficial i mean exact where

    we can use , 

    • Hi Mozzam / Venu / Srini,

      Thanks for your feeback.

      Hi Venu,

      Some more latest examples where, I have used.

      In my current FMCG Client, Excise is based on Highest MRP of Product. Now For STO from Excisable plant, MRP needs to be referred in MM also. so by the use of Ref. Condition type User will maintain condition record in SD and subsequently it will be referred in STO as well.

      Another example, In my pricing procedure, I am supposed to derive Base Price, by deducting Excise in Excisable Plants and later to be added again. This is just for calculation purpose.

      User will maintain Excise condition type only once and subsequently it will be derived via Ref. Condition type in the same pricing procedure wherever I need to use the same. (Design is in the way where, I can not use Subtotal effectively so this was other option to fulfill our purpose)



      • Dear ..Mahendra

        One doubt if we copy price from  MM. C. record then how company will get profit bz MM. Means exact price how much they have to pay to vendor so same price if we get Then what is the profit to company

        • Hi Geetha,

          Actually Ref. Condition type functionality is for copying value from Condition Record of One condition type to another. (Please refer the examples given in starting of document and also in comments)

          It is very obvious point that we will not copy the same price from MM on which we have bought the material and sell it to customer. Probably we may add some Margin.

          But if we need to copy ever any value from Cross Module condition type to SD or vice versa, above functionality will be useful.

          Hope I have cleared your point.



      • Dear mahendra jani

        step 4:  You have maintained 2 Base price condition types in vk11 right

        one is Pr00 55

        and ZAS2 With Reference to (ZAS1 500 RS) But 0 value in vk11 it is copying from MK01

        My doubt is Generally if we maintain 2 base price condition in vk11 automatically system will pick i mean last condition type only active mode and first condition type will be in active mode

        ex : in your case PR00–55

        ZAS1                               500

        SO system will show both condition types but active mode is obly for 500 rs

        so in this case we have to go v/06– select pr00 — condition class select price

        and next condition type ZAS1( IT IS COMING from zas2) so we have to maintain surcharge or discount in condition class

        Then only system will show all are active mode

        This setting you have done or automatically both conditions are active mode ?

        thanks for replaying 

        • Hi Venu,

          Conceptually you are very much correct about behavior of Condition types with Class of Price.

          See Screen Shot 1 and 3 where I have shown condition types in V/06. I have took both condition type Class as Discount and Surcharges.

          Ignore the description because I had created that scenario specially for this documentation only.



  • Dear Mahendra,

    This is good information, but this can be use only in specific business model, in general business process it is not needed. Correct me if i am wrong.

    Buy any was thanks for sharing it.



  • Good Job Mahendra,

    Just want to add some inportant information.

    in my previous project I have worked on same area, basically this is used in inter company STO and PO – SO process, where client want to reflect some pricing condition from PO to Inter company Billing (in inter company STO) and PO to Sales order (in PO – SO process).

    important thing if this condition is able to change in PO/SO than changes does not reflect on counter document. however we can control it using through some exit as well.


    Prashant Sharma

  • Hi Mahendra,

    What if I want to use some fields in the MM condition tables (like purchase organization) which are not available in the SD namesapce? I tried to assign a condition table created for MM (with fields – Purchase org and Vendor) to the SD access sequence. But system is throwing error that Purchase Org is not available in the namespace. How to solve this issue?