Variant Pricing Steps

Hello,
Variant pricing configuring steps
Can anyone explain the steps in details for configuring this with explanation of class type.
Full points will be awarded for good answers.
Thanks,
Anil Rajpal

Hi
STEP 1: CREATE CHARACTERISTICS: -   T.CODE: CT04
Logistics , central functions , classification , characteristics , create,
Go for value tab page
save it .
Go for the change mode and change the status to RELEASED
Create another characteristic Namely called CAR_COLOUR with char value as white and black and follow the same above procedure.
Step 2: Create Pricing Characteristic CT04
SAVE IT
Go for change mode and change the status to RELEASED AND SAVE IT
STEP 3: CREATE CLASS CL02
GO TO CHAR TAB PAGE
Save it
Again go for change mode and change the status to RELEASED
Step 4: Create configurable material with material type kmat: mm01
Go for mrp3 view
Give strategy group =25 ( make to order ) and rest as usual.
Step 5:
Create sub material masters for finished products
Like : white, black, normal, and disc.
Step 6: create BILL OF MATERIAL (BOM)
PRESS ENTER
SELECT THE LINE ITEM AND GO OF EXTRAS, OBJECT DEPENDENCIES , EDITOR,
SELECT SELECTION CONDITION
PUT THE SYNTAX AS CHARACTERISTIC = u2018CHAR VALUEu2019
CHECK THE SYSTAX ERROR (CRTL + F2)
IF NO ERROR  THEN SAVE.
STEP 7: CREATE CONFIGURATION PROFILE: CU41
SELECT MATERIAL AND PRESS ENTER,
SELECT THE LINE ITEM AND GOTO PROFILE DETAILS
Select the user interface tab page and click the setting button
Select the appropriate option as u like
No we have to link the characteristics and values
For the above , for the screen cu41, go for extras , object dependencies, editor
SYNTAX  : $ SELF.PRICING CHARACTERISTIC = u2018CHAR.VALUEu2019 IF $SELF.CHARACTERISTIC = u2018CHAR.VALUEu2019
Save it
Come back and again save it
Step 8:
Place the variant condition in the pricing procedure
Procedure zvaa01
Create condition record vk11
Save it
Now entire configuration was done for variant configuration
N0w create a sales order
Va01
Item category: TAC
Billing relevance : (A) : delivery related billing.
thanks
Kuntla

Similar Messages

  • Variant pricing - steps requested

    Hi,
    I created configurable material Envelope, assigned variant class 300 to material.
    then created characteristics, ZSIZE and gave values like DIN C4, DIN C5.
    then created class ZENVELOPE and assigned characteristics to it.
    I want to do variant pricing?.
    How to proceed?
    Thanks

    Here are the detailed steps
    - create another characterstics 'ZPRICE' and go directly to  Addnl data tab. enter table name as SDCOM and in field name enter VKOND. The system would copy required information from the data dictionary.
    - go back to characterstic ZSIZE. Go to value tab and select DIN C4.
    from menu bar select GoTo - Extras - Object Dependencies - Editor - select procedures.
    In front of 000010 enter $self.ZPRICE='DIN C4'.
    similarly repeat step for DIN C5.
    - go back to class ZENVELOPE and assign your newly created characterstic ZPRICE
    - go to VK11 and enter condition record as VA00 and give values for DIN C4 and DIN C5.
    - create your order and a pop box would come up giving option to choose DIN C4 or DIN C5. Basing on option you choose system would automatically determine price for this variant.
    - Remember to declare material price for your main item Envelope.
    - If you have any problems post your message again.

  • Variant Pricing _ each item price based upon main item.

    Hello,
    I request your help for inputs on Variant Pricing functionality for given scenario.
    Each material will have different price based upon different brand / main item.
    For example u2013 Inbuilt-Sat Nav will be priced different in Toyota Prius & Toyota Avensis.
    Let say, we have 2 products (Toyota Prius & Toyota Avensis.) each having 10 different options/ items which are charged separately.
    Hence would like to know how we can set up the price in variant based upon Main item & sub item.
    Toyota Prius / Customer / InBuilt Sat Nav = £1200
    Toyota Avensis / Customer / InBuilt Sat Nav = £1500
    Your inputs are appreciated.
    Thanks & best regards

    If you want to maintain seprate prices for each variants go to VK11 use the following condition types -
    VA00: this condition type expresses an absolute amount.
    u2013 VA01: this condition type expresses the surcharge/discount as a percentage
    above are based on sales org, material and variants combination, so as you said you requirement is based on customer will charge different prices, so create new condition table with customer combination and add in to same access sequesnce and condtion type.
    For more details check the below link:
    http://www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm
    regards
    Satish

  • Variant pricing in Sales order and Purchase Order for same Config material.

    Hi,
    I am stuck to a point wherein the varaint pricing is working either in Saler Order or in Purchase Order.
    The issue is that the Variant Condition Characteristics 'VARCONDMM' has MMCOM and VKOND in additional tab and in the multiple selection active (arrow) I have maintained SDCOM and VKOND.
    SO the variant pricing is active at the time of PO creation when 'VARCONDMM' is used and not at the time of SO creation.
    So I created  Variant Condition Characteristics 'VARCONDSD' has SDCOM and VKOND in additional tab and in the multiple selection active (arrow) I have maintained MMCOM and VKOND. and changed the dependencies accordingly for other characteristics.
    Then the variant pricing is active at the time of SO creation when 'VARCONDSD' is used and not at the time of PO creation.
    Any positive/quick inputs are highly appreciated.
    Regards,
    Abhilash

    Hi,
    did you check the code in dependency editor of the dependencies..? do they match between your previous system and new one?
    Regards,
    Raghu.

  • Variant Pricing - Passing a Z* condition to a quote

    Wondering if anyone knows how to pass a z condition to a quote from the configuration.  We have variant pricing working for the VA00 pricing conditions, but would like to pass across a Z condition.  Any ideas?

    So instead of VA00, we have Z-PG.  In a normal pricing procedure, I set the characteristic that is set to SDCOM-VKOND (VAR_PRICE) to the name of the VA00 condition and then do a $SET_PRICING_FACTOR.  How does it know to look at Z-PG instead of VA00? 
    Example of code of how we do the variant pricing for VA00:
    $SELF.VAR_PRICE = 'FCM_CHARGE'
    $SET_PRICING_FACTOR ($SELF, VAR_PRICE, 'FCM_CHARGE',CABLE_FIBERS)
    FCM_CHARGE is set up under VA00.
    How would the code look to find the condition under Z-PG?

  • Material Variant pricing

    Hello All,
        I have created a material variant from a configurable material. I would like to know if in the sales order I can pull up the variant pricing condition attached to the configurable material, or do I have to maintain separate conditions in PR00. thanks
    Atul

    Dear Atul,
    As per your Q i understand that you want a pricing to be pulled in sales order.
    The Pricing for the material will same as we do. i.e we need to maintain the record in PR00.
    But for Variant the pricing needs to be Maintaind in condition type VA00.
    All the variant needs to be maintained in VA00 only as this condition type get activated only when you are working with Variant configuration.
    Suhas

  • Pricing steps

    Hi experts,
    Please provide me pricing steps of mm in details as i am implementing pricing in sap mm.Please guide me in details.i want to know how to start and end pricing what are the steps to start pricing.
    Regards,
    Altaf

    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d09867e7-84d7-2c10-b9b7-da9e3b41392a
    OR
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d09867e7-84d7-2c10-b9b7-da9e3b41392a?quicklink=index&overridelayout=true
    or
    http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm

  • Variant pricing not working

    Hi,
    I created a variant material computer - KMAT type.
    created characteristics ZCOMPUTER with values monitor, keyboard,  mouse, price.
    created class - ZTOWER and assigned above characteristic values to this class.
    created condition records for computer & variants.
    created order and i don't see any price determination.
    please help where i am wrong.
    thanks

    You could base my reply below and use it you create your own variants as per your requirments.
    You should create separate characteristics for monitor, keyboard, mouse for example Zmonitor, Zkeyboard, Zmouse and assign values for them.
    You should create a separate characteristic for price for example ZPRICE.
    Delete characteristic Zcomputer.
    Material: computer of KMAT material type.
    Charactersics
    Zmonitor - values samsung, hp
    Zmouse - values wireless, optical
    zkeyboard - values microsoft, toshiba
    ZPRICE: just enter in Addl tab Table name as SDCOM & Field name as VKOND. System would copy info from data structure maintained in table SDCOM.
    Class
    ZTOWER and assign the above characteristics to this class.
    Now go back to characteristics Zmonitor
    select value 'samsung' from TAB values From Menu bar select Extras -> Object dependencies ->.Editor
    in line 000010 enter $self.ZPRICE='samsung'
    select value 'hp'
    in line 000010 enter $self.ZPRICE='hp'
    similarly do this for values in characteristic zmouse & zkeyboard.
    Now create a pricing condition record PR00 for material computer.
    create variant condition record VA00 in condition record VK11 for characteristic values samsung, hp, wireless, optical, microsoft, toshiba.
    create sales order and you would get a box to choose variants.
    please let me know if it works.

  • Table name for background job with report, variant and step user id list.

    Hello All,
    I need to generate the list of scheduled backgroung job with the list of Report Name, Variant, Step User Id called. Please any one tell the SAP Table name from which I can get these data.
    Thanks in Advance,
    Amit

    Hi Rohit,
    Thanks for your reply. But from TBTCO, i can't find program/report name and variant. Just the list of background job i can see.
    Regards,
    Amit

  • Multiple Variant pricing conditions in a Pricing Procedure

    Hi,
    I have a scenario regarding variant configuration pricing in a sale order. I need to attach multiple pricing condition like VA00 in my pricing procedure .
    A material M1 has many characteristics under the category Basic and Special for example.
    Under Basic I have the following characteritics and its respective values maintained in VK11
    B001- Basic Spec 1  USD 100
    B002- Basic Spec 2  USD 200
    B003- Basic Spec 3  USD 300
    Likewise under special category ,
    S001- Special Spec 1- USD 500
    S002- Special Spec 2- USD 1000
    In the pricing procedure the varaint condition VA00 will carry the price of the characteristics. My requirement is as follows
    1. The prices of the Basic spec should be added first and later the special spec
    VA00- Basic Spec 1      100
    VA00- Basic Spec 2      200
    VA00- Basic Spec 3      300
    Sub total Basic spec Value  600
    VA00 Special Spec 1    500
    total basic and special spec - 1100
    The problem I faced in the above format was that the pricing procedure will allow only one entry of VA00. To over come that I copied the condition VA00 and named a new one, for e.g, ZVSP.
    Now when I use the condition ZVSP, it does not fetch the values like VA00.
    Could any one suggest a method in which I can introduce varaint conditions in multiple levels in a pricing procedure.
    Thanks and regards
    Rasheed

    Hi,
    When you copied the VA00 condition type, did you also copy the associated access sequences? Your new condition type should have an access sequence with an access that transfers the value of the doc. field KOMP-VARCOND into the condition VARCOND; use transaction V/07 to check this.
    Regards, Jesper

  • Pricing Error: Variant Pricing

    Hi Experts,
    I have created KMAT material BOX. I have set all the pricing procedures and condition records correctly and when testing the material the pricing does come through correctly.
    E.g.
    Small = £50
    Medium=£150
    Large= £250
    When putting in material Box and selecting small the price will come through correctly as £50 however I still get a
    Price error u201CMandatory condition PR00 is missingu201D.
    I donu2019t understand why, as the material BOX doesnu2019t not have a standard price and there can only be three options. So I tried creating a condition for PR00 that was 0.00 but that doesnu2019t work either
    Please could you help?
    M.Patel

    Mr. Patel,
    There will be a Standard Basic price for all the materials that are created. In your example you can maintain the standard price in PR00 as $50, and maintain the other prices as Variant Price in VA00.
    Now the system will take the base price and depending on the other parameters (Size in you case), it can pick the Variant price(you need to maintain variant price as Mediun Size as $100 and Large as $200).
    Regards
    Vamsi Javaji.

  • Variant configuration steps

    Dear experts,
    I am using bom usage 1 for material bom for fert and variant material. now i when i create sales order the is bom should expold the material bom and i want to edit the bom values ie zero quantity the same bom should hit to production.
    vishal H K
    Thanks in advance
    Experts

    Hi Vishal,
    Here are the steps you have to follow then what ever you want to do the experiment u can do:
    1) MM01 with 25 strategy. (KMAT)
    2) assign it to KMAT material
    3) create BOM cs01
    4) create routing CA01
    5) Create Characteristics in CT04
    6) Create class 300 variant class CL01.
    7) assign characteristics to class in CL02
    8) Then go to CU41 Configuration profile and assign the 300 variant class.
    9) If you want to write dependencies u can give in characteristics.
    10) You can also give in BOM or maintain in BOM.
    11) Go to CS02 and give the variants you want and assign or create dependencies to them then the BOM can be called as Super BOM.
    12) Go to Routing and re-assign the operations then it can be called as Super Routing.
    13) Then create the sales order VA01 hope then you can select the variants if you maintained properly every thing ok.
    Hope it helps you any queries please revert me back.
    Regards,
    Madhu.G

  • Pricing step by step procedure

    Dear Experts,
    pls send me the pricing notes ( step by step procedures) at my mail id
    [email protected]
    always reward point ...
    Thanks b4 hand
    Vaibhav

    Hi Vaibhav,
    Following are the steps you need to follow for pricing.
    Reward if this helps you...
    PRICING (PG)
    This concept is based on condition technique.
    It’s the combination of:
    1)     Condition Tables
    2)     Access Sequence
    3)     Condition Types
    4)     Pricing Procedure
    1. Condition Tables: - Condition table contain the key fields for maintaining condition records.  I.e. in other words condition records are stored in condition table.
    Note: - A condition type can have multiple condition tables.
    Note: - A condition table can be used for multiple condition types.
    Defining condition tables: -
    SPRO
    Sales and Distribution
    Basic functions
    Pricing
    Pricing control
    Define condition tables [V/03]
    Create condition tables
    Enter a table number beyond 600
    From the field catalogue, which is there on the right side of the screen select the required key fields.
    To get the valid on / valid to fields while maintaining the condition records we need to check the field “with validity period”.
    Go to icon Technical View
    The fields which are marked, as footer field appears at the footer level at the condition records and the remaining fields appears at the key level.
    Select the Icon Generate for generating the condition table.
    To save the condition table, select the button Local object.
    2.     Access Sequence: - Access sequence is a search strategy with the help of which the system gets the valid condition records.  It contains the required condition tables in the required order.
    Note: - If required an access sequence can be used or assigned to multiple
    Condition types.
    Note: - The order in which the condition table are placed in access sequence
    is important generally it is most specific to most generic
    Defining Access Sequence: -
    SPRO
    Sales and distribution
    Basic functions
    Pricing
    Pricing control
    Define access sequences
    Maintain access sequences
    Go to new entries and define the access sequence.
    Select the defined access sequence and go to accesses.
    Go to new entries and place the condition tables in the required order
    While placing the condition tables check the field “exclusive”.  By doing so if the system finds a valid condition record in the first condition table it will not go to the next condition table
    Select the condition table and go to fields the system gives the warning message “the field assignment has not yet been made” say enter till we get the fields.
    Repeat the same step for all the condition tables and save it.
    Note: - After defining the access sequence assign it to the corresponding condition type.
    3. Condition Types: -
    Defining condition types: -
    SPRO
    Sales and Distribution
    Basic functions
    Pricing
    Pricing control
    Define condition types.
    Maintain condition types.
    Functionality of a condition type: -
    Access Sequence: - In this field specify the corresponding access sequence for the condition type.
    Condition class: - It is the preliminary structuring of condition types.
    Ex: - Surcharges or discounts and price
    Plus/Minus: - If we specify negative here a condition type becomes discount and if we specify positive it becomes surcharge.
    Calculation type: - Determines how the system calculates price discounts and surcharges in a condition type.
    For Ex: - the system can calculate a price as a fixed amount or as a percentage based on the quantity, weight, or volume.
    Condition Category: - It’s a classification of conditions according to pre-defined categories.
    Rounding Rule: - The rule that determines how the system rounds of condition values during pricing.
    Manual Entries: - Indicator which controls the priority with in a condition type between a condition enter manually and a condition automatically determined by the system.
    Amount / Percent: - If we check this field the amount / percentage of a condition type can be change during the document processing.
    Quantity Relation: - Specifies whether the conversion factors for the units of measure in the condition type can be change during document processing.
    Delete: - If we check this field the condition type can be deleted during the sales document processing.
    Value: - If we check this field the condition value can be changed during the document processing.
    Calculation type: - If we check this field the calculation type can be change during the document processing.
    Item condition: - If we check this field for a condition types it becomes item condition, which has to be enter at the item level only.
    Header condition: - If we check this field for a condition type it becomes header condition, which has to be entered at the header level only
    Ex: - RB00 (Discount).
    Note: - After entering the header condition type click on the button activate.
    Note: - The condition amount of the header condition is copied as it is to all the line items in the document
    Group condition: - If we check a header condition as a group condition the condition amount is distributed proportionately among all the line items in the sales document.
    Valid from & valid to: - specifies the beginning and ending of the validity date that the system automatically proposes when we create condition records for the condition types.
    Scale Basis: - Determines how the system interprets a pricing scale in a condition, for Ex: - the scale can be based on quantity weight and volume.
    Check value: - Indicates whether the sale rates must be entered in ascending or descending order.
    Note: - Header condition won’t be having access sequence.
    4. Pricing Procedure: - Pricing procedure contains all the required condition types in the required order.
    Defining Pricing Procedure: -
    SPRO
    Sales and Distribution
    Basic functions
    Pricing
    Pricing control
    Define and assign pricing procedures.
    Maintain pricing procedures
    Go to new entries and define the pricing procedure.
    Select the defined pricing procedure and go to control data
    Go to new entries and place the required condition type in a specified order.
    Step: - Specifies the number that determines the sequence of a condition type with in a procedure.
    Counter: - Specifies the sequence number of a condition type with in a step in the procedure.
    Condition type: - Specify the condition type.
    From & To: - If you specify the reference steps in these fields, the condition values of the two steps specified and the condition values of the steps in between are totaled.
    Manual: - If we check this field the condition type is only included in determination either if they are entered manually or if they are transferred from an external process such as costing.
    Mandatory: - Indicates whether a condition type is mandatory when the system carries out pricing using the pricing procedure.
    Statistical: - This indicator causes a condition type to be set in the document statistically only.
    Print ID: - Controls the issue of condition lines when printing the documents such as order conformations or invoices. [X]
    Sub Total: - Controls whether and in which fields the condition amounts or subtotals are stored.
    Requirement: - For the condition type to be executed in the sales document the requirement specified here must be satisfied. [2]
    Alternative calculation type: - Specifies the alternative formula to the calculation type in the standard system that determines a condition.
    Alternative condition base value: - Specifies the formula for determining the condition basis as an alternative to the standard.
    Account key: - This field along with few other fields enables the system to post the sales values to different General Ledger Accounts.
    Ex: -
    ERL          Sales Revenues
    ERS          Sales Deductions
    ERF          Freight Revenue
    Accruals: - This is exclusively for rebate condition types. [B001 & B002]
    Key, which identifies various types of General Ledger accounts for accruals posting.
    Note: - to maintain the requirements and routines use the transaction code
    [VOFM]
    Pricing Procedure Determination: -
    SPRO
    Sales and Distribution
    Basic Functions
    Pricing
    Pricing control
    Define and Assign Pricing Procedures.
    Define Pricing procedure determination [OVKK]
    We have to assign the pricing procedure to the combination of Sales Organisation, Distribution Channel, Division, Document Pricing Procedure and customer pricing procedure.
    Sales Organisations     Distribution Channels     Divisions     Doc. Pricing Procedure     Cus. Pricing Procedure
    1000     10     00     A     01 & 02
    2000     12     00     A     01 & 02

  • Insert new pricing Step

    Dear Members,
    I want to insert new condition type between 2  steps but unfortunately, I don;t have any number in between these 2. what is the alternative ?
    I have step 310 and step 311, Now I want to include a condition type between these 2 steps. Please let me know.
    Thank u.
    madhu

    Hi Madhu
    In pricing procedure we have a step Counter , so maintain those condition types in counter only
    So as you have step 310 go to new entries ->maintain step 310 counter 1 and maintain condition type and step 310 counter 2 and maintain 2nd condition type then those condition types will be between 310 and 311 steps only
    Regards
    Srinath

  • In variant pricing condion va00is not picking the  variants from dropdown

    hello all,
    wen i m preparing condition record in VK11 and using condition va00
    i m not getting variants for my materila
    as my PP guy has already made the variants but then also
    its telling a message no valu fount in variant colomn
    after that wen i m puting the same variant manualy not picking from drop down menu
    then also in sales order the vaoo is not coming with any price its comming as no price in it
    how to maintain ....................
    please help
    regards
    subrat
    [email protected]

    hi subrat,
    I think you have not maintained CA01 for vaiant char
    If not maintained  the configuration in ca01 for each variant char
    I am sending you the PPT with snap shot,  please go through.
    The configuration of ca01 is in slide 29
    regards,
    Arun Prasad C R

Maybe you are looking for

  • Crash in data transfer process, exception cx_rs_step_failed_callstack

    Hi, I am having problems with a data transfer process, i am getting the message: Extraction datasource Z_WMS_VRM    Prepare for extraction    Exceptions in Substep: Extraction Completed    Processing terminated When I click the button behind "Excepti

  • Business Packages + EAM

    Hi Guys   I am new to portals . My requirement is to download Business Packages for EAM . Could you please help me to look for Business Packages for EAM on market Place . Basically I need to learn the way to locate Business Packages on market place a

  • Opening a pdf produces a request

    Whenever I launch Reader Xl it requests an association with an email program. How can I do that? I am running Win 7 Home Premium.

  • HT201363 I can't access my account

    because of the security question and I am from libya so can't call Technical support and my email on yahoo is expired. can you just please delet my security questions

  • Sort a single filed

    Hiii, Can I sort a single field of a internal table without affecting other fields? ie the other fields should remain as it was before after the sorting...only the field written in the sort clause should be sorted. Reply urgently.