Valuation Variant - Quotation Price via Condition Table

Hi all,
Regarding cost estimate in SAP, there are valuation variants. The strategy sequence "Price from Purchasing Info Record" is one step in the material valuation strategy sequence of our  valuation variant PP01. There is also a sub strategy sequence with this Puchasing Info Record Valuation called "Quotation Price via Condition Table".
What does the mean, where can I find this condition table and how will the price be calculated??? Can anybody help me please?
Thanks,
Anne

Create origin group via Tcode OKZ1 and then assign the conditions that you want to include in product costing in Tcode OKK4.
In OKK4 by clicking delivery costs or create new icon you will get a popupform which can be used to input chosen conditions as follows.
PB00     0     200     1000     1000     1000     PR01
We are using it to calculate material price excluding excise duty (sort of withholding tax which can be reclaimed so will not form part of material cost)

Similar Messages

  • Wrong priority, valuation variants

    Hi all,
    We are having two costing variants and valuation variants (maintained in transaction code OKP8), one for ordinary calculation and one for planning. The one for ordinary we have the following priority:
    1. L Price from purchasing info record
    2. 4 Planned Price 1
    3. 1 Standard price in previous period
    Sub-strategy: A Quotation Price via Condition Table
    For the planning valuation variant we have the following priority:
    1. L Price from purchasing info record
    2. 4 Planned Price 1
    3. 7 Valuation price according to price control in Mat. Master
    4. 1 Standard price in previous period
    Sub-strategy: A Quotation Price via Condition Table
    Our problem is that; for the planning valuation variant the system choose priority 3, 7 Valuation price according to price control in Mat. Master instead of the info record that we have maintained. Planning price is not maintained thatu2019s why the system don´t choose that price. For the ordinary valuation variant the system choose priority 1. L Price from purchasing info record.
    We wonder if:
    1.Is that not possible to choose price from purchasing info record in two valuation variants, that you can´t combine this two?
    2.If this not is possible, are we forced to maintain a planning price?
    Best regards Lisa

    Hi,
    In your case as u have two different costing variants, generally there wont be any issue in having two different valuation variants for these two.
    Genearlly system picks up the purchase info record even for plan based on the valuation variant u assigned.
    Picking up the purchase inforecord is based on MM settings for material sourcing. check with MM how they maintained. Also recheck u r routing in planning.
    Regards
    Sudhakar Reddy

  • CK11N User exit for valuation strategy sequence Price Purchase info records

    Hi,
    When ck11n is executed for a particular material whose purchase order is created then only price from purchase info records is considered. As the sub strategy selected is purchase order price via condition table.
    Requirement: CK11N should consider purchase info record even if there is no purchase order against that material. As the check of valid  agreement is done outside SAP.
    Can anyone sugest a solution ? eg any user exit
    BR,
    Ameya

    Hi
    I lost my notes on this somewhere.... Just to refresh my memory - Can you tell me whats the difference between Net Quotation price, Gross quot Price, eff price from Quotation and Quot price via cond table
    I compiled it actually, but lost it somewhere
    br, Ajay M

  • Table entry for Valuation variant for material prices

    We want to define a valuation variant for costing run.  In that we need to select the material price based on the plan price.  We have provision of entering three plan prices in the Costing tab-2 in the material master.  But we want to enter plan  prices for more than three dates. For this, we propose to enter the dates and prices in a separate table and that table needs to be accessed in the valuation variant for material prices closest to the date of valuation.  How we can go about this ?

    Hi
    When you create Valuation Variant, choose Strategy U i.e. Price from userexit
    Then code the exit COPCP0005 with the help of ABAP consultant
    The logic should be:
    a. Refer the "costing date from" entered in Ck11N
    b. refer the Z table... and pick the price relevant on that date
    br, Ajay M

  • Valuation price with user exit/BADI/Enhancement Spot (In valuation variant)

    Hi all,
    i am facing problem finding enhancement when creation of sales order of Valuation price with user exit/BADI/Enhancement Spot  (In valuation variant)
    For refferenece:
    When going to t.code VA03, select one item and go to extras in the menu bar and select costing then you find some amounts calculation i.e valuation price automatically.
    So when creation of sales order i am giving material and that material price automatically takes from material master and creating sales order.
    My customer requirement is to get the valuation price of the input material from Z-table during the sales order cost estimate.
    This Z-table contains the material code, plant , grade  of the material.
    Ex:
    Material         Plant   Grade Price
    A                1000    XYZ     25000
    A                1000    PQR     35000
    A                1000    BCD     45000
    Suppose it depends on sales document type and which grade price i have to take.
    So first of all i am unable to find enhancement where to change this code to get change the valuation price.
    Does anybody have any idea , is there any user exit/BADI/enhancement for this.
    So please help me in this issue.
    Thanks & Regards,
    lokeshgoud

    pls allow me to post the questions

  • Loading custom price condition table

    We have a custom price condition table for intercompany price.
    This table needs to be updated monthly from a file generated from another system not on SAP.
    BDC is one way of doing it, but that takes too much time.
    Is there any other simpler way of achieving the same ?

    Hi
    Have your tried LSMW.  You can upload conditions using LSMW.
    Regads
    Yatin Thakkar

  • MM Request For Quotation Condition tables

    Hi experts,
      I am writing a Report, which i have requirment like Comparision of Vendor Quotations, for this i need MM Quotation condition tables,
    I was searching for knumv in EKKO table but the value was not updating in EKKO. please tell me where i can find the Quotation Conditions and it's  value.
       i am waiting for ur replys.
    Thanks & Regards.
    Murali Papana.

    Hi!
    Try to run ST05 (SQL trace) for the transaction, where the quotation appears. You'll find all used tables with this way.
    Regards
    Tamá

  • Condition Price to be picked in GR from the condition table MEK1

    Dear All,
    I have a requirement like
    I have 3 different condition type say ZPBS,ZSPL,ZADD.I have maintained these condition with a new acess seq.For these conditions i maintained some fixed value in MEK1,say 500,20,10 respectively.
    After that i did a PO with these conditions with the condition table value say 500,20,10 i.e 530.But after that i changed the value to 600,30,20 say 650.Prior to that i have changed the condition control to "GR date-5" in PO item.
    So after that i did the GR,the value of GR is coming as 650.
    My requirement i want the condition table value 500,20,10 i.e 530 is to be come after doing the GR.
    So pls suggest any specific solution if possible for this.
    Regards,
    DD

    Hi,
    Make date valid check (From & To) in MEK1 for the Values so that based on the valiadity it will be process for GR.
    pherasath

  • Metal Prices Condition Table#85

    Hi
    M/06 Display Condition table (pricing purchasing)
    Currently selection field is : Company Code
    I want to maintain Material specific condition for GAU1 & GAU2.
    Does it possible and make sense ?
    regards
    RG

    Hi,
    You will have to create a new condition table between the range 501 to 599 in the Tcode - M/03. In this double click on the field "Material" from the field catalog displayed on the right hand side.This field will get selected and displayed to your left hand side.Then Click on "Generate" option on the top.Once the table has been created , go to Tcode M/07 for creating Access sequence. Include the Condition table created above.Assign this Access sequence to the condition type for which you want the values to be determined based upon material code. Maintain the condition records in Tcode - MEK1.

  • Need to add new fields to the condition table

    Hello All,
    The requirement is to create the new condtion table for MM containing the following fields and maintain the entries in this table:
    - client
    - characteristic
    - class
    - internal characteristic.
    THe condition tables are created via tcode M/03 or through the customizing path
    Material Management > Purchasing > Conditions > Define Price Determination Process > Maintain Condition Table.
    The problem which i am facing is as follows :
    -SAP has the standard procedure for the generation of the condition tables . Selected fields are made available by SAP in the field catalog and we can select only from the those available fields. Once we select the required fields the condition table is automatically generated in the background.
    -As the requirement is, we need to have 4 fields in the generated condition table (client, characteristic, class and internal characteristic), but the problem is that none of these fields are available in the field catalog which is provided by SAP (in tcode M/03, M/04 and M/05).
    -Designing of the Z table wonu2019t be useful as we would not be able to use the Z table as the condition table.
    Can you please suggest how can we add the desired field to the existing field catalog in M/03 or is there any other alternate solution to this ?
    Thanks in advance for your help.

    >
    Rinkesh Doshi wrote:
    > Hello,
    >
    > The specific ABAP question which I have is :
    >
    > Is there any way in which we can enhance the existing field catalog in M/03 tcode to include the 4 new fields (client ,characteristic,class,internal characteristic) ?
    >
    > Thanks.
    Please post your code which you developped until now and show us where the problem is. I cant see any ABAP related question.

  • Cannot find a field for creating a condition table

    Hi all,
    I m trying to create a shipment scenarios which involves shipment cost based on prices,boxes,material....etc. to start with i tried to create a condition table, here the key combination needs to have the filed 'boxes' in it. I am not able to find it even in the master table. Is there any other place whr i can find it or how can i add this into the list?(master table)
    any input is highly appreciated.
    regards/aryan.

    Hi
    Try to ad the filed from the field catalog ,In case the required combination field is not there u can add the field through the following process to filed catalog and create the condition table.
    It is most common that one or other time we need to use this function while configuring multi tasking & complex Pricing Architecture.
    Here Aim giving a simple guide to add fields to the Pricing Field Catalogues:
    For example you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.
    When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
    Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.
    Reason and Prerequisites
    For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').
    Proceed as follows:
    1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.
    2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
    Component Component type
    ZZPSTYV ZZPSTYV
    Save, check and activate the change you made.
    3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.
    4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'.
    Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.
    5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
    6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
    MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
    In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.
    Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.
    For header fields, use structure KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.
    For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040.

  • Condition Tables with Release status

    When we create condition tables, we have the option of creating them with release status or without release status. What is the difference? What is release status?
    Thanks,
    Venkat

    hi,
    The release status for condition records in a sales deal enables you to limit the use of records that have already been created.
    Release status has the following characteristics:
    no entry: released
    A: blocked
    B: released for price simulation
    C: released for price simulation and planning
    The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.
    Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.
    When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.
    A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.
    The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.
    If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.
    The release status of conditions in an agreement can only be changed, if
    the condition record has release status in the key
    the agreement has the release status released
    Otherwise the condition record always has the release status of the agreement.
    The processing status is always directly assigned to a release status. If conditions are assigned to an agreement, the agreement passes the release status on to all related conditions. The related processing status is then set accordingly.
    If you have several processing statuses assigned to a release status, the condition record receives the first (alphabetical) suitable entry as a processing status.
    The processing status, which the conditions have received indirectly from an agreement via the release status, can only be changed in the case of released agreements.
    source : Library.
    regards

  • ZPUP condition tables

    hi all,
    I have  a question related to finance.I want to populate the periodic unit price to ZPUP condition tables..in se12 i dont find any table with the name ZPUP.
    so can anyone tell me what is the sap table where the periodic unit price will he stored for the material /plant combination.
    points wil be rewarded ...your help is appreciated

    Hi,
    MBEW  : Material Valuation  (Transpatrent Table)
    the field name is
    VERPR     Moving average price/periodic unit
                    price (CURR 11.2)
    Reward if helpful.
    Regards,
    Karthick.

  • Costing variant/valuation variant

    dear gurus,
        can any body explain the costing variants,valuation variant,costing sheet,costing type,how it is integrated in production order in controlling tab.can any body explains the customizing part of product costing and overview.
    if any body is having the product costing material please send to [email protected]
        please through some light on product costing
                                                                            -gide

    Hi,
    Every cost estimate we create is based on the costing variant.
    In the costing variant we define the control parameters and settings for costing
      Settings contains info such as prices that will be used to cost the materials and activities
    Control parameters are used for the automatic determination of of qty str ie Bom and Routing
    Every costing variant contains a valuation variant and a costing type , date control , qty str control.
    Valuation variant:
    Valuation variant defines the price with which the material and activities are valuated
    determines 1.which price is taken from material masterrecord to calculate the material cost
    2.
    which price is taken from cost center accounting to calculate the costs for internal activities
    3. which price is taken from purchasing info rec to calculate the the costs for ext activities / subcontracting
    4. which costing sheet is used to calculate the over head costs
    Costing type:
    costing type defines the valuation view to be costed and defines the purpose of costing.
    Date control :
           controls the validity of the cost estimste , qty str date.
    Valuation class:
    For material costing the valuation class controls the cost element to which the planned cost of the material are assigned and the cost element under which the actual costs are updated when the material produced is delivered to stock
    Valuation category:
      specified the criteria according to which partial stocks are distinguished from one another
    Price control indicator:
      the price control indicator specifies whether the stock of the material is valuated with standard price or moving avg price
      costing sheet:
                The costing sheet links all the functions for overhead calculation.
        In the costing sheet we determine the following
        1.The direct costs to which the over head is applied
        2.The condition under which the over head is applied
        3.Whether the over head is applied as a percentage basis or on a qty basis
        4.The amt of overhead percentage
        5.The validity period of the over head
        6.Which object is credited ( order , cost center) and which cost element in the case of actual posting
       We enter  the costing sheet in the valuation variant in customising
    Regards,
    nandha

  • Creating New condition table.

    Hi all,
    I want to create conndition table with new fields. I have added those Zfields to VBAP, KOMPAZ.
    Do i need to code anything in userexit_pricing _prepare_tkomp for populating the fields in list of allowed fields while creating while creating condition table?
    Thanks & regards,
    NarsiReddy.

    If any field to be considered for condition table, the same would be done via V/03 where you can add any fields that are missing from standard.  But once you save, system will ask for Access Key without which, it won't flow in condition table.  Hence, user exit is not necessary.  But it would be ideal if you explain the business process as to why you were looking for adding some new fields.  Hope, you are not reinventing the wheel.
    G. Lakshmipathi

Maybe you are looking for