Reference Condition type

Hi,
Can someone share with me on the usage of the reference conditon type field in the condition type field? If i put in the PR00 as the reference condition type in PB00?
How this will affect the price determination?
Still quite new to price determination in MM. Hope someoneone can give me some guidance on it.
Thanks.

hi
A condition type which can be used as a reference so that you only have to create condition records once for condition types that are very similar.
Ex: AMIW and AMIZ, these both condi types are used for minimum order value.
If  u maintain AMIW- (min ord value) condition type We have to assign this condition type to AMIZ (surcharge value) cond type as reference condition type. then only it will work it.
Edited by: Roddick Redy on Apr 21, 2008 7:29 AM
Edited by: Roddick Redy on Apr 21, 2008 7:32 AM

Similar Messages

  • Reference condition type wrt IV01 and PI01..

    Hi PPL,
    Can u plz explain Referrence Pricing condition wrt to the condition types :
    IV01  and PI01,
    Both are condition tyres pertaining Inter company ,IV01 has a Reference condition Type PI01 assigned to it.
    What does it mean in the inter company scenario.Points for sure..:-)
    Best Regards,
    Subbz..

    Hi,
    PI01 condition type represents costs to Ordering company code (in other words revenue to supplying company code).
    It is statistical condition type & meant for information purpose only.
    Condition records for PI01 are created with the following key combination:
    Ordering sales Org + Supplying Plant + Material
    PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
    The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
    The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
    Hope this provides you with your answer,
    Regds,
    Rupali

  • In what scenarios does Reference condition type is being used?

    In what scenarios does Reference condition type is being used?
    Please provide inputs.

    <b>Reference condition type</b>
    A condition type which can be used as a reference so that you only have to create condition records once for condition types that are very similar.You may need to use different condition types for the same condition. These can differ in the access sequence, the description, the reference stage of the pricing procedure or the calculation type, for example, you can enter the condition type under which the condition records are created.
    <b>Refer below example</b>
    Condition type MWSI only differs with condition type MWST in the calculation type. For this reason an entry is made in field ReferenceCondTypeMWST for condition type MWSI . Now, condition records only need be created for condition type MWST and not additionally for MWSI.
    Thanks and regards

  • How to implement the Reference Condition Type

    Dear Friends,
    My Client is using the Refernce Condition type ZMWS which is referencing MWST condition type. He has implemented the same for one company code already. When I am creating a Sales Order, I am able to get the condition type MWST for the newly created condition type ZMWS through the condition record maintained for MWST.
    But when I am doing the same for other company code I am getting a pricing error as it is saying mandatory condition ZMWS is missing.
    I am not getting any clue what to do. Do I need to maintain any settings?
    Thank you,
    Prakash K M

    Dear Prakash,
    In V/06, detail screen of condition type, under under master data you have to give the reference condition.
    Regards,
    Abhee.

  • How to create Reference Condition Types

    Hi ,
                 Please tell me how to create Ref.Condition Types?
    I have a requirement.."I should create a Zdiscount(13%) which should be copied to the sales order automatically based on PR00"
    How to do that?
    Points for sure
    RamChandra

    Hi,
    You can use condition supplement functionality.
    Check the link [Condition Supplements|http://help.sap.com/saphelp_47x200/helpdata/en/93/7432de546011d1a7020000e829fd11/frameset.htm]
    You can also check the field RefConType for the discount condition type in SPRO -> Sales and distribution -> Basic functions ->Pricing -> Pricing control ->Define condition type.
    Regards,

  • Determination of Base price condition type depending on Item Category

    Dear All,
    The requirement I have is as stated below:
    There are two materials A and B that are individually sellable materials. But during a specific time period the company decides to give a scheme where in Material B is given as free when a particular quantity of material A is purchased. Irrespective of the scheme, material B can also be individually purchased during the scheme period.
    Now in the former scenario where material B goes free with material A in the same order, the base price of material B should not go to revenue G/L but to a different G/L called Scheme G/L. To counter this scheme G/l there is another counter G/L into which 100% discount on base price to material B goes.
    In the latter case, if material B is sold individually, then the base price should go to Revenue G/L and not scheme G/L and the 100% discount is not applicable.
    Can you please guide me on how to configure this.
    The approach I have taken is as follows:
    The condition types for base price are ZBPR and ZBP1(reference condition type of ZBPR)
    Item Categories to be considered: ZTAN and ZTNN (for material B going as free during the scheme)
    The requirement is such that, whenever the item category for a particular material is ZTAN, the condition type to be picked must be ZBPR while the condition type ZBP1 must be deactivated.
    Similarly, if the item category for the line item is ZTNN, then the condition type to be picked must be ZBP1 and the condition type ZBPR must be deactivated

    Dear All,
    I have fulfilled this by doing rev acct determination in vkoa using item category and moving it up the order. Also I used a requirement in v/08 for 100% discount on free material.
    This has resolved my issue and i am now closing this thread.
    Thanks and Regards,
    Rohan
    Edited by: Lakshmipathi on Apr 2, 2011 10:53 AM
    Since you have arrived at a solution, please change the status of the thread to "Answered"

  • Condition Types In pricing

    Hi,
    While creating new condition types in pricing, we create them by copying them from exsting condition types.
    So while doing this which reference condition types should we select for copying new one?

    Hi
    SAP provides you different condition types which you can you use in your pricing procedure.if those condition types are not fullfilling ur requirement then you need to create new ones .
    Now while creating the condition types you have keep lot of the things in mind :
    Which pricing elements such as prices, discounts, surcharges, taxes, or delivery costs--condition class
    Whether it is quantiy / value based--- calculation type
    whether it is item conditon or header condition
    whther manual has priority
    regards
    Sunny

  • Selecting the best Price for a condition type but only for some customers

    Hi All,
    I have this situation where we have condition type ZPPR (COPY OF PR00) with 5-6 Condtion tables.
    in Access sequence for ZPPR, we have Exclusion Indicator set for all the conditiona tables so if first price is found, it doesn't search for others.
    Now I have a requirement that we should search for all the condition records and choose the lowest price. But this should happen for only a certain type of customers and not for everybody.
    Spefically we have:
    1. Contract Price
    2. Plant/Material price
    Normally, if contract price is found, it doesn't look for Plant/Mat price but we want to offer our customers(some of them) an option where they could choose the lower of the two price. We set both the prices every day based on some inputs.
    Regards,
    Luke
    Edited by: Lukesh Singla on Dec 21, 2011 8:49 PM

    Hi Luke,
    We have multiple option for this implementation:
    Option 1: If possible based on access sequence. Not sure if this is suitable considering you mentioned that ZPPR has 5-6 access sequence.
    1) Store Contract price in condition type ZPPR and store  Plant / Material Price in new condition type say, ZPPX.
    2) Have separate pricing procedure and determine them based on customer type. In first pricing process XXXX01, configure Condition exclusion with the setting that ZPPX should be deactivated if ZPPR is present, condition exclusion procedure D (exclusive) . In second pricing procedure XXXX02, configure condition exclusion with the setting that compare ZPPX and ZPPR and activate best condition type for the customer by using condition exclusion procedure C (Best condition between two exclusion groups ).
    Option 2:
    1) Copy  ZPPR and its access sequence to a new condition type and access sequence say ZPPX without checking exclusion indicator in the access sequence. In the condition type control for condition type ZPPX >> Master data section >> Reference Condition type = ZPPR so that master data records  need not be duplicated.
    2a) Assign the current procedure to the set of customers which should get the first price. Create a new procedure with condition type ZPPX instead of ZPPR keeping other parameters similar and assign the new procedure to other set of customers who should get the best price.
    OR
    2b) if 2a is difficult in terms of future  maintenance, add condition type ZPPX in the same procedure and create 2 new pricing requirement validating the customer segments and assign them to respective condition type in procedure ZPPR and ZPPX.
    3) Maintain condition exclusion for condition type ZPPX with B ( Best condition within Condition type).
    Hopefully it helps. Let me know if you need any other help in implementation of the solution.
    Regards,
    Naveen Aggarwal

  • PI01-Condition Type

    Hi Friends,
    STO between two plants of different company codes.
    US-Receving Company Code
    India-Supplying Company Code
    The scenario is like this:
    Sales order is created in US.
    Based on the Sales order, US will generate Purchase Order(STO) to India.
    Plant(India) will transfer(VL10B/VL02N)the goods to Plant(US).
    Plant(India) will raise the Intercompany invoice to Plant(US).
    *Condition type IV01 is the Revenue and Cond.type VPRS is the Cost to INDIA*
    ****Pricing PRocedure is ICAA01***
    MIGO and MIRO in US Company.
    As the goods were received in US plant they will deliver the goods to the Customer in US w.r.t. Sales Order.
    Then Billing to Customer in US by US Company.
    **Cond. type PI01 is the Cost to the Receving Company Code(Revenue to the Supplying Company Code which is having cond.type IV01 copy of Cond.type PI01)
    ****Pricing Procedure is RVAAUS**
    1)I want to know that if cond.type PI01 is the cost to receving co.code(US) then cond.type VPRS is?
    2)In Pricing Procedure RVAAUS do we need to have Cond.type PI01 and VPRS?
    with regards
    Azeez.Mohd

    Hi,
    PI01 condition type represents costs to Ordering company code (in other words revenue to supplying company code).
    It is statistical condition type & meant for information purpose only.
    Condition records for PI01 are created with the following key combination:
    Ordering sales Org + Supplying Plant + Material
    PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
    The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
    The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
    Hope this provides you with your answer,
    Regds,
    Rupali

  • Condition types doubling/tripling/...when sales documents created with reference to other documents

    Hi,
    When I create a sales order with reference to a Quote, the pricing condition types are duplicating. Same is happening when subsequent documents like Billing, credit memo request and credit memo are created. Particularly, the condition types  are doubled/tripled/.... in the subsequent documents. Because of this, pricing net value is calculated wrong. For example, freight charges getting added twice. I searched the forum and found similar issue was discussed at Condition types - Doubling UP  raised by forum member Sridhar Vijjhalwar, however there is no solution added in it.
    Has any other member came across this issue and resolved?
    I have checked the access sequence and exclusive indicators are checked. Copy controls are also checked, looked good and I tested by adding copying type D/G. Checked OSS note also and found one OSS note 1459807 - Invoice has missing/incorrect conditions when created from a sales order.
    but it is not solving the problem either. Issue also elevated to SAP for their investigation. Our system is SAP ECC 6.0 - EHP6.
    Quote Pricing:
    Sales order Pricing:
    I appreciate any pointers to resolve the issue.
    Regards,

    what was the scenario, and how did you replicate?
    It is a configuration for a new project (France country), however we found that the same issue popping up for existing business processes also. As for replicating, we just tried the same procedures, the issue is found in subsequent documents.
    If you have observed one notable thing is - all the condition types which duplicated were Z Conditions, and the standard conditions were never duplicated at least in my case.
    In our case even standard condition types like MWST, SKTO, GRWR, VPRS also shows duplicating.
    if you can throw about the business process?
    As you have mentioned order created with reference to quote was only the straight forward scenario?
    I tested other scenario also, like creating a sales order, then delivery and then billing. In this case in billing document, the condition types are duplicating. If I create a credit memo request against the billing document, then it further duplicating.
    I am not sure what is causing this. I initially thought it may be copy control settings pertaining to the new project, however other business documents also has the same issue. Other business are using different document types.
    Thanks for your follow-up.
    Regards,

  • Create a new condition type, which reference to another condition type

    I have a condition type Z002, which is reference to another condition type Z001 (Z001 is always negative, I have set the condition limit from -0.01 to -99,999,999), but with opposite sign.
    User need to maintain only condition record for condition type Z001.
    e.g. value for Z001 is -100, then value for Z002 is 100.
    I have set Z002 reference to condition type Z001, but how to setup so that they always have opposite sign?
    Thanks.

    Go to pricing procedure in t.code V/08. Against condition type Z002, maintain routine number 164 (Basis * -1)in the column Alternative formula for condition base value. If this routine is not available, you can develop one in t.code VOFM (you can get help from ABAP'er) with required logic and assign here.
    Regards,

  • Different base value reference steps for same condition type

    Dear Gurus
    I have a scenario where I have single pricing procedure for normal sale and Intercompany billing.
    Condition type GRWR should take the base value from step 350 in standard scenario
    But in Inter company billing it should take the base value from a different step.
    Want to check the possible way to determine these.
    Regards,
    Neeraj Srivastava

    In the pricing procedure, in the step that you're interested in intercompany billing put in the subtotal field the indicator "carry over value to KOMP-KZWI". Make sure that the KOMP-KZWI field that you'll choose is not used in any other step.
    Then with the help of an ABAPer you should maintain a routine (Tc VOFM -> Formulas -> condition base value) that in the case of intercompany billing (if billing-type is XXX  ... etc) will take the KOMP-KZWI* value that you chose previously.
    Then back in the pricing procedure, assign your new routine in the field "Alternative formula for condition base value" (BasType).
    Agis

  • Can we take standard report for all sales orders based on the condition typ

    Hi all,
    Based on the condition type, we need to take a report for sales orders on the particular date.
    Thanks and Regards.....VM

    Hello again.
    Searching for a solution, I found a Logical Database for sales orders, that have all the information that you need.
    Using like reference the post of Bhagavatula, in the same transaction SQVI you can use, instead of the suggested join, you can select a logical database called VAV in Data source.
    This logical database links the tables, VBAK, VBAP, VBUK and KONV that is the central point of the question.
    You can list the information of logical database using the transaction SLDB.
    In 'Logical Database' inform VAV.
    Press F8 to list all the fields.
    More information about logical database in:
    Link: [SAP Logical Database|http://help.sap.com/saphelp_46C/helpdata/EN/9f/db9b5e35c111d1829f0000e829fbfe/content.htm]

  • Header condition type value not displayed in sales order output

    Hi gurus,
    I have observed a strange issue regarding a header condition in a sales order.
    we have a set up like following:
    1. If the Header condition XXXX is used in sales Order then this value should be printed on sales order output.
    2. If the Header condition mentioned in above point is not maintained in sales order it should print the total price of all line items.
    Though i have maintained the header condition value in Sales Order Header its not displayed in SO output.
    That is , I have a sales order and it has one HEADER condition type entered with 3500 USD.
    In fact this value is used for some business purpose and is being printed on the sales order output for a specific output type.
    But where as in a sales order this header condition value is not getting printed on the output though I am using same data as of the sales order which is having the header condition value printed on its output.
    According to business,we must have the header condition value printed on  sales Order output.
    Please suggest how to proceed.
    Thanks in advance.

    Not sure if you are using costom smartform to print invoice, if yes then ask developer to debug and find the root cause and fix it.
    You might need to give him condition when it shuld be printed and when not.
    You can take reference of another output type for which it is printing

  • Condition Type to be excluded whil creating Return sales Order from invoice

    Hi Frnds,
    I have the following requirement.
    Sales order order is created and its delivered and invoiced too. This sales order has some freight pricing condition types (RCD1, RCD2...)included since its shipped to customer.
    When the customer wants to return the goods, there is a return sales order is created with reference to the invoice created above. Now, the RCD1 and RCD2... should not get copied to return sales order.
    How do i achieve this? Please let me know any user exit, BAdi or Enhancement spot where i can add code to avoide these condition types from being picked up.
    SAP system is ECC 6.0
    Regards.,
    Karthick C

    It can be achieved by implementing a custom requirement routine. If you go to the the transaction VOFM, you will find "requirement" in MENU. You select 'Pricing' on drilling-down it. Following document may help you in creating requirement routine..
    http://saptechsolutions.com/pdf/VOFMCopyRequirementRoutines.pdf
    All requirement routines has similar pattern of writing... Your code may look like as follows:
    FORM KOBED_901.
    sy-subrc = 4.            "By deault condition is false.
    If NOT XKOMK-AUART = 'RE'.                   "RE is returing order type.
       sy-subrc = 0.        "This means For other than returning orders all others condition is true.
    endif.
    ENDFORM
    Once you activate routine, ask functional consultant to attach this to the Condition RCD1 and RCD2. Then, You'll not get RCD1 and RCD2 for Return sales Order.
    Please check and confirm and revert back if you want further details..
    Edited by: Pikle Audumbar on Oct 17, 2009 1:09 AM

Maybe you are looking for