Condition Type Pricing Procdure

Hi Gurus,
For Pricing Procedure i am creating CVD condition type for (% input) one for Modvatable and the other for Non Modvatable.What are all the differences i have to maintain in condition type creation.
Thanks in Advance.

Hi,
JCV1 is Non Modvatable and accurals is enabled for it
That means If Accurals is enabled then it is Non Modvatable.Plz clarify
Also if Cond.Category is enabled as Delivery Cost then Vendor in GR is enabling.Please explain what it is and what is the impact if we maintain the Vendor in GR.
Tks.

Similar Messages

  • Manual Pricing for Condition type pricing

    Hi experts,
      I am changing the price in sales pricing of cj20n transaction manually and it get updated, working good.
    Is it possible to get the updated manual pricing in all the transactions related to CJ20N transaction.
    Thanks&Regards,
    Vino

    Hi..,
    Yes. Its possible.
    I want give some function support on this as worked on condition types in another transaction.
    You needs to be check that if your pricing procedure is having that condition type or not and also you have to check that condition type is mannual or not.
    First get your pricing procedure...
    For this goto V/08 transaction code and select your pricing procedure there -> double click on control folder-> there you can get all condition types for that procedure -> and check ur condition type is mannaul or not.
    Thanks,
    Naveen.I

  • Requirements not fullfilled for Condition type - Pricing Procedure

    When I am doing the pricing procedure, the error thrown is "Requirements not fullfilled for Condition type". Can any one suggest how to fix this problem ?

    Hi Sunil,
         Please first of all check the condition type in Pricing Procedure. In condition type column check the requirement. Here conditon is,  once requirement is fulfilled which you have mentioned in the condition type then only it will be executed. Take a help of  ABAP'er regarding this requirement if it is customized requirement.
    We should know the purpose of requirement in condition type.
    Venkat.

  • Condition type-Pricing Procedure

    Hi Gurus,
    Kindly Clarify me the following.
    What is the impact when i maintained Condition Category as B -Delivery Cost
    What is the impact when i Enable the Accruals Indicator for a Condition Type
    What is the impact  when i Enable Statistical Indicator for the Condition Type in Pricing procedure.
    Thanks in advance.
    Rgds
    Ganapathysubramanian.V

    hi
    >What is the impact when i maintained Condition Category as B -Delivery Cost
    when u give delivery cost in condition , system give u field for vendor for assignment of that condtion value toa  specific vendor
    as delivery cost can have different vendors  freight,clearing ,octroi ect.
    >What is the impact when i Enable the Accruals Indicator for a Condition Type
    This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
    >What is the impact when i Enable Statistical Indicator for the Condition Type in Pricing procedure.
    u2022     This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
    u2022     It is used only for information purposes only.
    u2022     This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
    u2022     This is commonly used for condition types
    o     SKTO - Cash Discount
    o     VPRS - Cost (Moving average price/Standard Price).
    regards
    kunal

  • Configuring Condition Types - Pricing Date

    Greetings to all,
    we are trying to change the way the price conditions are found by using a different date determination within the Condition Type. i am looking at the screen "change view condition type" for a specific condition type (doesn't matter which) and specifically looking at the section "control data 2" and field "Pricing Date". it has a number of choices within it, including 1) blank - standard 2) A - date of service 3) B - price date, and so on. i have determined that this field v_t685a-kprdt (pricing date) has a domain KPRDT and the options for this field are hard coded within the domain (value range).
    my question, is there a way to configure this field so that i can use another date to key on the determination of the price condition?
    my concern is not with the standard SD or FI price condition lookup, but with a bolt on (automotive). it uses this funcitonality and the document has other dates, some customer defined.
    please and thank you.

    Hi Erik
    One option is to use the MV45AFZZ and in the form for KOMK
    pass what ever date you want to KOMK-PRSDT.
    Please try and this and let me know if this works.
    Thanks
    PG

  • Condition types (Pricing Procedures)

    Hi
    I am doing a review of our pricing procedures and have noticed two Pricing conditions linked to Pricing Procedures which we use quite extensively which allow manual changes to the price.
    There are also no tolerances set for any condition types.
    Is there a way to see if these conditions have been used and indeed if the price was manually changed?
    Also how do I ensure that Sales Orders and invoices are automatically priced in SAP using the price in effect at the time of order placement (not time of shipment).
    Thanks
    CT
    Edited by: Chris Townsend on Sep 23, 2008 3:55 PM

    Dear Chris
    Answer to your Q1
    To check whether any manual price change has taken place in billing, go to SE16, input table VBRP  and check the field MPROK
    Answer to your Q2
    Go to V/06, select the condition type and execute.  Maintain "D"  for the field "Manual entries"  so that whatever price you maintain in sale order, that will be copied in billing and cannot be changed manually, unless you change in VK11 and do manual selection of "Update" button in condition tab.
    thanks
    G. Lakshmipathi

  • Condition type not visible in billing document

    Hi
    We are currently in the process of making some changes to the pricing procedures.
    While processing an IC order, we find the following discrepancies,
    In VA03, when we enter the order details, the price shows the expected value and so do the condition details.
    However, in the billing document for the same, in VF03, we find that one of the condition types are missing, hence the value in the sales document and the billing document are different.
    I have checked the details in the condition types, pricing procedures and the access sequences, everything appears to be configured correctly.
    Please advice as to how this can be corrected.
    Thanks
    sap10

    Hi
    Check in pricing procedure (tcode V/08) if you have any Reqt.
    Other possibility, but I think that it doesn't matter in your case. See SAP Note 105621 - Authorization check for the condition screen, that it is used to hide conditions, but not for delete them.
    I hope this helps you
    Regards
    Eduardo

  • Condition type used for invoice list

    Hello Gurus,
            following condition type used for invoice list, why do they exit in invoice list:
             RL00    MW15.  LR00    RD01

    Hi,
    Please go through the below document
    When you work with invoice lists, you need to be familiar with the following concepts:
    Prerequisites for invoice lists
    Relationship to Pricing
    Structure of an Invoice List
    Changing header and item data
    Integration with financial accounting (FI)
    Prerequisites
    You can only process invoice lists if the following prerequisite data is defined by your system administrator in Customizing for Sales:
    Condition type RL00 (factoring discount) must be maintained and, if required, also the condition type MW15.
    An invoice list type must be assigned to each billing type that you want to process in invoice lists. The standard version of the SAP R/3 System includes two types of invoice lists: LR for invoices and debit memos, LG for credit memos.
    Copying requirements must be defined (for example, the payer, terms of payment and other fields that must be identical in the documents to be included in the invoice list)
    In addition, before you process an invoice list, you must maintain the following master data:
    A customer calendar must be defined, specifying the time intervals or dates on which invoice lists are to be processed.
    The customer calendar must be entered in the Billing Sales Area view of the customer master record.
    Pricing condition records for the condition type RL00 and, if necessary, (e.g. in Germany) the condition type MW15 must be maintained.
    Output condition records for condition types LR00 and RD01 must be created.
    Relationship to Pricing
    The system processes factoring discounts in invoice lists in exactly the same way as other kinds of pricing elements. The data for the factoring discount is stored in condition records. Controlling during document processing is carried out via condition types, pricing procedures and access sequences. This control data is defined in Customizing for Sales by your system administrator.
    For further information, see  Conditions and Pricing.
    Structure of an Invoice List
    An invoice list represents an individual billing document. It consists of a document header and document items. Each item represents a billing document that you have included in the invoice list. The header contains an overview of summary information, such as the net value of all documents in the invoice list, the value of the factoring discount, details of taxes, and so on. It also contains information on partners and output.
    Changing Header and Item Data
    You can change some of the header data - for example, the billing date - when you process the invoice list. You can change an item - either an individual or collective invoice - and display document details. However, you cannot change any data in individual billing documents once they are part of an invoice list.
    It is possible, however, to make certain global changes to output in all items in an invoice list.
    For further information on output, see  Communication in Sales and Distribution Processing.
    Integration With Financial Accounting (FI)
    The documents that you want to combine within an invoice list must already have been billed and forwarded to Financial Accounting. Here the billing documents intended for an invoice list are blocked for normal dunning transactions.
    The dunning block on FI documents is lifted as soon as you create an invoice list and transfer it to FI . The system then calculates the new dunning date for the invoice on the basis of the invoice list date.
    In addition, the system enters invoice list numbers in the FI documents as reference numbers. Invoice list numbers can then be entered for incoming payments.
    When you save the invoice list, the system automatically creates an accounting document for the factoring discount and possible taxes and posts it to the corresponding G/L account in FI.
    Regards,
    Murthy

  • Related to condition types and access sequence

    Dear all,
           i want to know abt one scenario, m using a pricing procedure with my service PO: ZVSTOT, in this Procedure, 12 condition types are there, during searching i found tat 3- 4 condition are are using different different access sequence, so i want to know tat in what procedure, we do it, what is use of it.?
    plz reply me.

    Hi Nisha,
    Prcing procedure configured in your service PO PO: ZVSTOT, Based on this pricing procedure system adopted the condition type in PO.
    Please go through this below link to better understanding the MM-Pricing procedure
    http://it.toolbox.com/wiki/index.php/Pricing_Determination_Process_-_MM
    http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
    CONDITIONS OR PRICING PROCEDURE or PRICE DETERMINATION PROCESS
    We deal with the Pricing Procedure for vendors.
    PB00 Gross Price (info record, contract, scheduled Agreement)
    PBXX Gross Price (PO)
    FRA1 Freight
    RA00 Discount on net
    RA01 Discount on Gross
    ZA00 Surcharge on net
    SKT0 Surcharge / discount
    ZPB0 Rebates
    MWVS Input Tax
    MWAS Output Tax
    BASB Base Amount
    RM0000 Calculation Schema or Pricing Procedure
    (PB00 & PBXX)
    RM0002 Calculation Schema or Pricing Procedure
    (PB00)
    PB00 --> AB00
    Copy the Standard one and create new one (ours)
    RM0000 contains all the condition types
    Pricing Procedure (PP)
    We define the pricing procedure to define condition supplement for the material price. The condition supplement specifies the discount, surcharge, freight etc that we want a system every time to access material price condition records.
    The total value of the material is calculated or based on all addition and subtraction i.e. discounts, surcharge, tax freight etc
    Condition Table
    It is a table, which defines the structure of condition record key.
    Condition Record
    It is a data record used to store conditions or condition supplements, i.e. condition like, discount, freight, and surcharge, Tax etc.
    Condition Type
    It is used for different functions. In Pricing the condition types leads you to differentiate different types of discounts, in output determination, batch determination, difference between two output types, such as delivery note or order confirmation, between different strategy types
    Access Sequence
    It specifies the order in which system searches or access the condition records from condition table
    Difference between PB00 & PBXX
    1. Condition maintained in PB00 is time dependent whereas PBXX is time independent.
    2. Condition type PB00 u2013 used for IR, RFQ, Contract, Schedule Agreement
    Condition type PBXX u2013 used for PO.
    Calculation Schema
    The main function of calculation schema is to provide framework of steps for the price determination process to specify the discounts, surcharge, freight rebate etc.
    It also determines the sequence of conditions that are to be followed and in which sequence.
    Schema Group Vendor
    The main function of it is to identify or to pick the right process and conditions for a particular vendor.
    Schema Group Purchasing Organization
    Key that determines which calculation schema (pricing procedure) is to be used in purchasing documents assigned to the relevant purchasing organization.
    Schema Group
    It allows to group together the purchasing organizations, which uses the same calculation schema.
    Steps: -
    1. Create Access sequence
    2. Create condition types
    3. Create pricing procedure or calculation schema
    4. Link pricing procedure & access sequence to condition type
    5. Create schema group for vendor
    6. Create schema group for purchase organization
    7. Assign schema group vendor-to-vendor master record in purchasing data view
    8. Assign schema group purchase organization to our purchase organization
    9. In inforecord purchase organization data enter condition types and pricing or calculation procedure
    CUSTOMIZE SETTINGS: -
    SPRO > IMG>MM>PUR>Conditions -->Define price determination Process
    1. Define access sequence
    2. Define Condition type
    3. Define cal. Schema
    4. Define schema group
    o Schema group vendor
    o Schema group purchasing group
    5. Assignment of schema group to PUR org
    6. Define schema determination à determine cal schema for standard PO.
    With Thanks,
    Thiru

  • Change required in Condition type definition.

    Dear Experts,
    My requirement is - I have defined one condition type [pricing procedure] with condition class extra pay. Calculation type - C Quantity. Calculation schema has been configured. Next processing Condition record creation and Service Po creation has been done. I have around 50 Service purchase orders in the system now.
    By some reasons, i have to change my condition type defintion. i have to change the calculation type from C to B [Fixed amount].
    please guide me on my requirement.

    Thanks Priyanka !
    Those POs cant deleted. Because of the missing condition type all the calculation will be incorrect in Service entry sheet as well
    Invoice Verification.
    Also i have to change my Key combination for condition records. Current key combination is Plant/ Activity/ Purchasing Organization,
    Vendor. But this condition value can be set at activity level. But i have condition records already maintained.
    Its a major change in configuration i know. but is required and received a permission from client. so whatever job is there,
    no problem.
    Please suggest me the solution on mentioned query.
    Thanks in Advance.

  • How to Know one condition Type (PR00) used in which pricing procedures

    Hi Friends,
    I have 20 pricing procdures I need information that condition type PR00 is used in which pricing procedures.
    by help of
      any report
      any table etc
    Thanking you
    Arun

    Dear Customer,
    in standard there is no report available for your requirement.
    In this case you can only create your own selection report therefore.
    regards
    Claudia

  • In import Pricing Proceedure,  Some Condition types added to Material Cost

    HI,
    In Import Pricing procedure, Some condition types (Like Basic Customs Duty,Edu Cess & Hier Edu Cess) are added to material cost. The remaining are not added. What is the configuration to add condition types to Material cost?
    Note -  we have added FR3 account key for all condition types. Then why few condition types are added to material cost and why others are not added to material cost?
    Can any one please help me on this..
    Thanks
    KB

    Assign key "NVV" to those condition types which are to be loaded to material cost.
    Hope this resolves ur problem

  • Pricing: New condition type not getting listed in options in product master

    Hi,
    I have created a new pricing procedure and also created a new condition type for it. I am trying to create a condition record in the product master for this  condition type but the condition is not there in the list of conditions. How can I inlcude it in the condition list?
    Even the new condition type I have created by copying 0PR0 is not getting listed in the options, whereas 0PR0 is getting listed.
    Regards,
    Meenakshi
    Edited by: Meenakshi Sawhney on Sep 9, 2010 8:27 AM
    Edited by: Meenakshi Sawhney on Sep 9, 2010 8:29 AM

    Hi Meenakshi,
    you need to enhance the condition maintenance group in the customizing, which is assigned to the product master. Please check: IMG: Customer Relationship Management -> Master Data -> Products -> Special Settings for Sales Operations -> Assign Condition Group to Application CRM and IMG: Customer Relationship Management -> Master Data -> Conditions and Condition Technique -> Condition Technique: Basics -> Create Maintenance Group.
    Best Regards,
    Michael

  • Pricing condition types in SRM 7.0

    Hi,
    We are using SRM 7.0, we have decided to go ahead with the pricing proceedure and the condition types which are there in ECC the same should be replicated to SRM.
    We have created the same pricing proceedure and the calculation scheema in SRM.
    Now my requirement is when i create a PO with the conditions and when i am transfering to ECC the PO should also be with the condition types. It should be a similar PO in ECC.
    Is this can be addressed.

    Hello All,
    As I have already mentioned the condition types in SRM are identically matched to ERP condition type hence the data is flowing correctly and even the idoc has the z-condition type Z123.The IDOC in backend ERP has status 53.
    On trial and error method we did unchecked the manual indicator check in the pricing schema for the relevant condition type and because of that now the Z-condiiton type can be seen in the backend ERP contract.
    If the indicator was checked, this means that this condition can be maintained only manually (directly in the transaction
    ME32K in ECC) and nothing can be transfer from other source.
    Note: If the same condition type is being used in more than one pricing procedure then ensure that the check bok is unchecked for agianst the relevant condition type.
    Thanks,
    Yatin

  • How to update the z-condition type in pricing procedure in a quote

    Hi Gurus,
    I need your help to solve my issue.
    I have created a RFC which will trigger any time there is a CRM Quote/ CRM Order create or change occurs. IN response of the RFC i will get the rate and rate type for the line items .
    When the service  returns with rate value the SAP system will insert this value by inserting z-condition type  in to the pricing structure. The normal pricing function module will then carry the process forward.
    Todo this ,Can i code the RFC call in Order_save badi ,but where can i get the pricing sturcure  data to update the returned rate values in the pricing.
    and also one more thing ,In ecc  I am using the CUCB_GET_CONFIGURATION to get product configurations. for the same which FM can i use in CRM.
    Please reply me ASAP.

    hei,
    you can use field KOMP-KZWI1 - KZWI6 to store your condition type. then it can be used for analysis in SIS.
    if you want to put more than one condition type to field KOMP-KZWI1, go to V/08 (pricing Procedure), put "1" in condition subtotal.
    Best Regard,
    Hendry

Maybe you are looking for