Pricing Control

Hi Gurus,
I have defined the pricing control as example, below:
10 ZK9A
20 ZK9B
30 ZK9C
40                            subtotal that is equal 10 until 30          
50 ZKBB
60ZKBC
70ZKBD
How to do with that o step 70 (zkbd) received the value of step 40?.
Thanks,
Wilson

Hi Wilson
Now your query is clear.
What I need is that Condition Type ZKBD receive: Conditon value and Amount of line 40.
For your requirement, you must require a calculation routine.
Calculation routine you can define under VOFM>Formulas>condition value.
You require ABAPer's help to achieve it, tell your ABAPer, to add step 40 value to the condition value coming automatically.
Finally assign this routine to your step 70 in pricing procedure under "Calculation type".
try, test and revert.

Similar Messages

  • For pricing control 'S' Moving average price is changing automatically.

    Dear All,
                I have maintained the pricing control 'S' For finished goods. and the standard price also maintained for the same. we are not doing purchase for this material. only production and sales happening for this material.
    but for this material MAP is gone upnormally..
    it should not update MAP for this material. why MAP is gone upnormally?..
    i have checked in the following steps:
    1. i have analysed MB51 everything gone correcdtly with correct value.
    2. i have downloaded the MR51 material accounting documents its also updated correct value..
    why MAP is gone up normally...
    Regards
    Anand

    Hi Anand,
                     As very well being explained by so many people, when ever you take S as price control, and maintain the standard Unit price, then syatem will keep on updating the MAP(V), but it will be of no relevance, all the transaction will be based on the standard moving price.
    whereas when you maintain the MAP(V), then there will be no Standard price,
    this is the standard functionality,
    as you are saying that MAP is increasing continously, there might have been some mistake in any transections, like GR with wrong price, please check that also, it will also result in increased MAP, whereas standard price will not chage.
    hope it helps,
    YK

  • Pricing control from billing to sales

    Hello All:
                I have a requirement about the pricing control as below.
                Credit memo request is expected to be created refer to billing, but I don't want to use all the condition types of billing.
                Actually I plan to assign a new pricing procedure to credit memo, but the pricing procedure is copied from billing doccument as default.
                Is there any configuration can cover this?
                Stephen
    Stephen

    Create a new data transfer routine as recommended in the following note:-
    Note 14136 - Pricing procedure for credit memo with reference
    G. Lakshmipathi

  • SD: Pricing control

    Hi all,
    In a pricing  schema control, If I have in the control setting the calculation of condition with requirement and AltCty, how the system determines the value. My situation if this:
                     From        to           subtotal  Reqt     AltCty
    Total loan      115     115      A           936        0
    I can't exctaly understand, how subtotal, reqt and Altcty workfor the determinatin of condition
    thamks in advance

    Hi
    The pricing control can be explained for better understanding as below.,
    1.When the sales order is created, based on the combination of Sales Org-DC-DIV-DocPP-CusPP .... a pricing procedure will be determined in the hearder of the sales document.
    2. The system access this pricing procedure and it accesses all the condition types in the procedure one by one in the sequence maintained in the procedure.
    3. It tries to access PR00 and before entering the access sequence to find the valid condition records - the requirement stops the system and if the requirement is stisfied, then only it can access the condition tables. The requirement -2 says 'Item with Pricing'. Then the system checks the field PRICING in the corresponding Item Category and if the value is X - standard pricing, then the system is allowed to access the condition tables to find valid condition records.
    Another example is with Requirement 55 for R100 condition type. It specifies that if the value in the field Pricing of that corresponding Item Category is B - Pricing for Free goods - this condition type can be accessed for finding  valid condition records. If the Item category is TANN then the value will be B and hence R100 is determined for free goods line items only (with Item category TANN).
    WHile determining the condition records, system uses Alt Cal type and Alt condition Base value for caluculations and these terms are well explained in the above replies.
    Hope this gives you some clarity about the pricing control.
    Thanks,
    Ravi

  • Old / New pricing control

    Hai SAPeans,
    Greetings.
    My client's requirement at a Depot is as follows:
    As of 01.01.2009
    Material: X          Quantity: 50pcs           Selling Price (PR00): INR 10.00
    On 05.01.2009 Stock received as follows:
    Material: X          Quantity: 25pcs           Selling Price (PR00): INR 11.00
    Now the total stock in the Depot is 75pcs. If the user wants to sell any or all the stock with any of the 2 selling prices, he can simply change the Pricing date in the order and execute and at the volume that our client deals per day, no one can cross check this. If he wants, he can sell all the 75pcs at INR 10.00 which is not acceptable to the management.
    How to prevent this and ensure that the first 50pcs which were received when the SP was 10.00 will be sold at 10.00 and the other 25pcs that were received at 11.00 will be sold at 11.00 ONLY.
    The stock does not have batches and there is no individual identification to differentiate one piece from the other. For everyday example we can take a Toothpaste tube which has a price printed on it and then imagine my scenario. The end user at the Depot has the instruction to sell the old material at the old price only.
    Hope some one can help me in this matter.
    Thanks and regards.
    Venkat - Hyd

    Hi
    I hope, it can be solved through material determination.
    First you have to add the field "Material price"into the field catalog. You may take the help of your ABAPer for this.
    Then create a new condition table taking the two fields "Material entered" and "Material Price".
    Assign this new table to your Access sequence and complete the field assignment and save it.
    Create a condition record for material determination(VB11) taking this new key combination.
    In the condition record, maintain two substitutes( both same material) with two different price and specify the reason of substitution as "0005" i.e, "Manual".
    Now, when you will create a Sales order system will give you the pop-up of the material with different price.
    I hope, this may help.

  • Important controls in pricing

    Dear Friends,
                      Plz let me know all important controls in pricing procedure..........

    Hi,
    In SD, the steps to configure Pricing procedure are as under:
    Step 1:
    Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
    Step 2:
    Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
    Step 3:
    Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
    Step 4:
    a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
    b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
    5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
    Reward points if useful
    Regards,
    Amrish Purohit

  • New Field Addition in  Allowed Field Catalogs -Pricing.

    *Hi,
    We have requirement of having Material Description field in the Allowed Field Catalogs in SPRO --> SD --> Basic Functions --> Pricing --> Pricing Controls --> Define Condition tables --> Allowed Field Catalogs in order to fetch the same for Pricing Condition Table creation with Mtrl Description as Key Combination.
    Hence, as a first step, have added the MAKTX field inside the "ZStructure" (which was created before) inside Main Structure KOMP and activated the same. Then i have added the same field MAKTX in Allowed Field Catologs of Pricing using New Entries.
    Now i have tried to create a new Pricing Condition Table with field catalog of Material Description (the added field), but there is no such field is available for selection.
    Is there anything i missed to do, so that the newly added field is available during New Condition Table Creation with key combination of the added field.
    Appreciate your promot response.*
    Rgds,

    Hi,
    Thanks for your response.
    Have added the required field in Structure KOMG now and it is available for selection in Condition Table Field Catalogs. However, am allowed to select this field only when creating a New Condition Table and if i want to add this field in the already created condition table in change mode, it thows an error message - "Function Code cannot be selected".
    How to proceed further.
    Rgds,

  • About pricing and value added tax

    Dear Friends,
    In the standard customer order screen (VA01), when I enter Price value, I want SAP to determine
    *Value Added Tax(standard%18) automatically.
    Can anyone tell how to accomplish this step by step?
    Sincerely,

    Hi,
    Yes, this is there in standard SAP.
    You can configure it in your pricing procedure so that when you enter the price (PR00) system will automatically calculate the VAT percentage for that and display.
    IMG path:
    SPRO - > Sales and Distribution / Basic Functions / Pricing / Pricing Control / Define And Assign Pricing Procedures / Maintain pricing procedures
    Go in to that node.
    Then select the relevant pricing procedure (Check: RVAA01 as a example)
    Double click on "Control Data" node
    You can see PR00 appear as the price condition
    If you go down in the procedure you should be able to see condition MWST appear in the procedure.
    MWST is same as VAT (Tax condition)
    If you want to use different condition other than MWST, copy MWST and do that.
    Then you need to maintain VAT % in VK11 as well. In this case, go to VK11 enter MWST and maintain 18% there for relevant customer and material tax combination.
    Then try with a new sales order. You should be able to see the Tax calculation once you enter price.
    Best regards,
    Anupa

  • Relation between Tax procedure and Pricing procedure

    Dear All,
    I would like to get more clarity on Tax procedure, Pricing procedure.
    a) Why do we have Tax procedure and assigned to Country?
    b) If the tax procedure has been created and assigned to Country-IN (in FI module), then why do we need to create pricing procedure with same condition type for purchasing in MM module?  We are even creating lot of pricing procedure for Sales in SD module.
    Regards
    Manivannan R

    Hi
    Tax
    During SD document transactions, tax calculation procedure TAXUSX is only relevant to determine the tax liability accounts for output sales tax. Notice that in pricing procedure RVAXUS, the condition types XR1 - XR6 carry the tax rates and tax amounts - resulted from the external tax system calculation - which is posted to tax G/L accounts. However, the tax accounts are not specified in the pricing procedure but rather in the tax calculation procedure.
    Tax codes are the link between pricing procedure and tax calculation procedure.
    Pricing
    The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
    Which sub-totals appear during pricing
    To what extent pricing can be processed manually
    Which method the system uses to calculate percentage discounts and surcharges
    Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
    Example
    Example of a Pricing Procedure
    If a sales department processes sales orders for a variety of foreign customers, the department can group the customers by country or region. A pricing procedure can then be defined for each group of customers. Each procedure can include condition types that determine, for example, country-specific taxes. In sales order processing, you can specify pricing procedures for specific customers and for sales document types. The system automatically determines which procedure to use.
    Pricing Procedures in the R/3 System
    The standard system contains pre-defined pricing procedures, which contain frequently used condition types along with their corresponding access sequences. You can, of course, modify these procedures or create your own from scratch.
    Creating and Maintaining Pricing Procedures
    You create or maintain pricing procedures in Customizing for Sales. For more information on creating pricing procedures, see the online Implementation Guide for Sales and Distribution.
    To reach the pricing procedure screen from SD Customizing:
       1. Choose Basic Functions
       2. ® Pricing ® Pricing control ® Define and assign pricing procedures.Select the transaction that you want to execute.

  • Explain the Pricing Procedure

    Hi Friends
    Explain how the pricing is determined for an item, starting from the sales order
    Discuss the full cycle also make a mention  on  the Condition type controls, and Maintain pricing procedure controls.
    Kindly explain it with an example.
    Thanks

    Pricing Procedure is indeed an heart of SD module, reason being if everything else is working fine, but price is not being calculated correctly, the purpose of billing fails.
    An Overview of Determination & Configuration of Pricing Procedure is as follows:
    In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
    In SD, the steps to configure Pricing procedure are as under:
    Step 1:
    Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Table (select the required fields combination, which will store condition record).
    Step 2:
    Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
    Step 3:
    Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
    Step 4:
    a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Maintain Pricing Procedure.
    b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Determine Pricing Procedure.
    Step 5: Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

  • How to configured pricing procedure to sales order type

    Dear Sir,
    Please tale me how to configure / change pricing procedure to sales order type. we have required to change pricing procedure from a to b for particular sales document type.
    Regards
    BK GAIKWAD

    HI
    Create a new document pricing pricedure
    SPRO>sales & distribution>basic functions>Pricing>Pricing Control-->Define And Assign Pricing Procedures
    and in the same path assign to your document
    and assign it to your document and also then to your Pricing procedure determination in OVKK
    regards
    Prashanth
    Edited by: Prashanth@SD on Jan 29, 2011 11:00 AM

  • Pricing procedure determination

    Dear Gurus,
    Pricing procedure determination :
    IMG-> SD-> Basic Functions-> Pricing-> Pricing control-> Define and assign pricing procedure-> Define pricing procedure determination
    Sales Org + Dis. Ch. + Div + Customer Pricing Procedure + Document Pricing Procedure => Pricing procedure
    Question :
    When we do the above assignment there is one more column "CType" (condition type) is available.
    What is the significance of this field and how it is helpful?
    Please commnet soon with example.
    Thank you very much in advance.
    Regards,
    Ashish

    Hi Ashish,
    Refer this links to understand links b/w the tables.
        http://www.sap-img.com/general/sap-r3-tables.htm.
        http://www.sap-img.com/sap-sd/important-tables-for-sap-sd.htm
    Thanks,
    Swamy H P

  • Pricing procedure  change the condition value

    Hi,
    My pricing procedure determines the Tax in %basis.Now i have a rewuirement wherein i should be able to enter the amount in AMOUNT COLOUMN in condition tab. This value should be the condition Value for the condition type.
    Now my pricing procedure doesnt allow me to make any changes and the condition type is greyed out. how can i calulate the tax in amount instead of % and be able to enter the value manually?
    Thanks,
    Challa

    Hi Challa,
    Price can be maintained either on percentage basis or on amount basis.
    So you have to make changes in condition type to convert it from percentage to amount.
    Go to IMG u2013 sales and distribution u2013 master data u2013 basic function u2013 pricing u2013 pricing control u2013 define condition type.
    Select maintain condition type from the options.
    Now select your condition type and click on detail.
    Change the calculation type from A (percentage) to B (Fixed amount) and save it.
    Now go to VK11 and maintain the new condition record for that condition type.
    Now create the sales order and go to condition tab and check out the pricing it will be amount.
    Please do this method if you find any difficulty then tell us.
    Regards
    Raj.

  • Pricing procedure execution...

    Hi Folks,
    How SAP reads the pricing procedure..
    Example
    Con.Type      Requirement        Routine
    ZSAA            601                     901
    ZSAB            602                     902
    Doubt 1: -Is system reads this pricing procedure line by line or coulmn by column?, In the debug we noticed it goes column by colmun? why?
    Doubt 2: - I want to know the value found for ZSAA during the execution of 602 requirement. Example scenario is if ZSAA is more than 100$ don't execute ZSAB.

    Pricing Procedure:
    Determination of Pricing Procedure:
    In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
    Configuration of Pricing Procedure:
    Step 1:
    Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
    Step 2:
    Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
    Step 3:
    Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
    Step 4:
    a. Pricing Procedure (T.Code: V/08):  It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
    b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
    5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
    Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
    Regards,
    Rajesh Banka
    Reward suitable points.

  • How to assign a pricing type to the pricing procedure ?

    Business Scenario : When the prices change from the time the order is taken to the time the invoice is created, how can setup the system to  handle the changes automatically ? 
    I would like to know How to create a pricing type and How to assign a pricing type to the pricing procedure so that I can use the 'new pricing document' function in the sales document and 'Update prices' on the condition screens in the Billing document.
    Thanks for your input in advance.
    Oscar

    Hi !! Oscar,
    1) For pricing type definition you would require the help of a developer.
    2) However, most of the commonly occuring requirements are supplied with  standard SAP.
    You can assign a pricing type to pricing procedure as follows:-
    IMG>S & D >Basic Functions>Pricing>Pricing Control>Define & Assign pricing procedures>Maintain pricing procedure> Here, locate your pricing procedure , in the fourth coloumn using the drop down list, you can assign a pricing type to the pricing procedure.
    Now you can use the 'new pricing document' function in the sales document and 'Update prices' on the condition screens in the Billing document !
    Regards,
    PATHIK
    Message was edited by:
            Pathik Pandya

Maybe you are looking for

  • How to find out which hdd is \Device\Harddisk#\DR# ?

    I have few similar (same model) usb external hdds, one of them apparently isn't stable and I see that in event viewer, How can I found how which hdd is it? Many thanks!

  • Pin definition for TV OUT Connector (C&S)

    I`ve bought graphic card MSI GeForce4 Ti4200 TD 64MB but there was no the cable for TV connecting. I`ve bought the cable, but it does not work. Do anyone knows the pin definition for " TV_OUT Connector (C&S)", because I can`t find it in user`s guide.

  • Business Place and Section Code - Validation

    Dear All, While posting a document through Tr Codes FB60/F-43/MIRO, Business Place and Section Code should be Mandatory fields, the system should not move forward to other screen untill and unless, entire this fields. Provide me the Validation steps

  • Change a link with Image Swap?

    Okay so far I have my website designed. Here is what I have so far... ... I have successfully managed to have all the thumbnails keep their rollover behaviors while also making the main image change whenever any of the thumbnails are clicked. So that

  • Dynamic components

    Hi, In the case where I don't know how many buttons I'll need until runtime how can I dynamically generate button names? It would be something like this, in a shell script: i = 0 n = <generated at runtime> while (( i<n )) do     JButton b_$i = new JB