Pricing conditions ---- routine

Hi folks,
i got requirement like there is a material Base price tht is maintained at Pricing conditions according to the sales order ,
Then at the time of material Dispatch the price may vary. So i have to develop a
ZTABLE and maintain base price factors and if user enters a varied price ..
the difference between the variedand base price should be calculated ... like wiseit has to be displayed in the output.
Can u help me in this task. I have no idea of routines. How to attach a routine.. to standard one..
regards,
reddy

Hi,
The procedure to create the new VOFM.
1. Go to VOFM transaction
2. Page down until you find a new spot on the page to put in the VOFM number and description.
3. Put in the VOFM number and the description of the VOFM.
4. Now the VERY IMPORTANT part of the process. Double click on the VOFM description not the VOFM number to create this as a Development/Correction and not as a repair. If you double click on the number then this copies some existing code and prompts you for a repair.
5. Activate and generate the VOFM routine. Note: Configuration must be setup by the OM team for this step.
for example Go to the routine number that needs to be copied.
Put your cursor on the routine number field that needs to be copied.
Overwrite that number with your new routine number and hit enter.
The new routine will be created as a copy of the old routine and you can modify the new routine as you need it.
Ex.
You have to copy routine 104 to 904
Routine number Description Active
104 Bill.bus.item data X
Put your cursor on 104 and then change it to 904 and hit enter.
904 will be created as a copy of 104 and you can make your changes in 904.
Don't forget to activate it after you are done.
refer the below link
https://forums.sdn.sap.com/click.jspa?searchID=3604222&messageID=994791
Reward points
Regards

Similar Messages

Pricing condition,automatic display without doing VK11 firstly, how ?

Hi all, another question.
I have a pricing condition in my sale order. and its value is determined by Pricing Conditions Routines with Conditions Value.
How can it automatic display in the condition of my sale order, without doing VK11 firstly.
My english is poor, so I hope u can understand these.

Hi
As I said in my previous thread , go to VOFM->Pricing, and check in the requirements if any standard requirements are meeting your requirement or not .If it is not meeting then create a new requirement with the help of technical consultant. and assign the requirement in the Pricing procedure requirement feild for the condition type and then check wheather it is capturing the price or not in the sales order and billing documents.
Regards
Srinath

Pricing condition redetermination for sales order created with reference

Hi,
Are there any exit or routines that can be used to redetermine MWST pricing condition alone when creating sales order with reference to another sales order? The pricing from preceeding sales order is copied but we need only MWST to be redetermined after saving the order
This is because we are making changes so that while saving the sales order the material tax classification is defaulted to M based on some conditions so that MWST picks up the value M
Regards,
Vin

Hello Vinod ,
did you tried following options :-
1.Using Exit ( MV45aFzz) and re calculte pricning using FM 'PRICING'.
2.or Using Copy Control (Tcode : VOFM ) while creating order with Ref.
regards
Prabhu

Pricing Condition in scheduling agreement

Hi Gurus,
I'm working with scheduling agreements and I figured that whenever I create scheduling agreements, pricing condition PB00 gets defaulted to the scheduling agreement,
Can you guys be kind enough to tell me what configuration is driving this?? How can we make changes to the config settings so that I can have a condition type of my choice assinged to the scheduling agreenment??
More over I have a requirement to have a tiered pricing in scheduling agreement. I do know that this is driven by SCALES in SAP however as per my requirements I need to have SCALES per formulas. In the condition type configuration we do have a field for SCALES where we can assign the formulas but whenever I click on this field a screen pops up with some ROUTINES.
Can someone tell me how can I define the ROUTINES and the ABAP formula for this ROUTINE so that I can have my tiered pricing conditions accomplished??
Any feedback on this will be highly appreciated!!
Thanks folks,
Dhaval Joshi

Hi Ramesh,
Thanks for the heads up. I looked at the config for the schema dtermination and I see that the pricing procedure RM0002 has not been assinged to any vendor POrg schema in this configuration.
I then looked at the config for the condition type PB00 --> pricing procedure RM0002 has been assigned to the condition type PB00 and since we don't have any entries maintained for RM0002 in the schema determination config I was just wondering if this is what is influencing the automatic proposal of the condition type PB00 in my scheduling agreement.
Also can you please tell me what is a difference between a Purchasing Document (BIG) and Purchasing Document (Small) in the schema determination config.
All I wanted to accomlish here is my teired pricing to work when I assign scales on the condition type in the scheduling agreement ( not in the PIR)
What currently happening in my case is ....
Example: Scale From 1 pc - 100.00 USD
from 50 pc - 90.00 USD
from 100 pc - 80.00 USD
Target quant. 100 pc
schedule lines 30 pc
20 pc
The problem is that the goods receipt of 30 pc is valuated at the price 80.00 USD It always takes a lowest price on the scale.
I've tried looking for OSS notes and also looked enough on the forums but I could not get any resolution to this question.
I would appreciate if I could get any heads up from your side.
Cheers,
Dhaval

Scheduling Agreement pricing condition PB00 value

Hi Experts.
Within pricing schema I do have pricing condition PB00 that is manually put in by the user. I have created a routine in order to calculate the PB00 value based on some logics and assign it to PB00 within the pricing schema.
So, if the custom logic are found, the price value should be change accordingly, if not the value put by the user will be kept.
The problem is that, at end of my routine the price is correctly calculated (let's say the user writes 2 and my routine calculates a price of 3) and the price is correctly updated on the scheduling agreement line field NETPR. But if i go inside the item to see the conditions I still see PB00 with the not-changed value.
Can anybody suggest? I am manipulating xkomv-kbetr and konp-kbetr.

Hi, Thanks for answering.
They are set so. But i need in any case to change the value of PB00 accordingly to my routine.The problem is that, at end of my routine the price is correctly calculated. PB00 value is 2 and it correctly recalculated by my routine to 5. on the SA item I see hte net price equal to 5, but if I go in the details I see condition PB00 still equal to 2.
Do you have any hints? thanks.

Change header pricing condition in sales order

Hi,
I have an requirement in VA01 and VA02 to automatically edit one header pricing condition. The user can able to change the value of that condition type in header not in items . Does anyone know what user exit I can use for this requirement.
Thanks

Hi Sunil,
Plealse find below 2 methods to change header pricing conditions in sales order.
1.Goto SE38, give prog name as MV45AFZZ and in that write logic under USEREXIT_PRICING_PREPARE_TKOMK . (OR)
2) The same can be done by creating a Alt Calculation type routine through VOFM and writng the logic in the routine, which will then be assigned to the pricing procedure in the condition type which will automatically calculate the condition.
Try with the options mentioned above..
Regards,
KK

Change of pricing condition in sales after delivering or invoicing of a sub

Hello,
I have to change the pricing condition of a sales order item, condition type PR00, after a sub quantity had been delivered or invoiced to the customer. BAPI_SALES_ORDER change I tried with did not work but also I got no error.
w_inx-updateflag = 'U'.
w_cond-itm_number = '000010'.
w_cond-cond_type = 'PR00'.
w_cond-cond_value = 999.
w_cond-currency = 'EUR'.
APPEND w_cond TO t_cond.
w_condx-itm_number = '000010'.
w_condx-cond_type = 'PR00'.
w_condx-updateflag = 'U'.
w_condx-cond_value = 'X'.
w_condx-currency = 'X'.
APPEND w_condx TO t_condx.
w_vbeln = p_in. <--- from input parameter
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
 EXPORTING
 salesdocument = w_vbeln
 order_header_inx = w_inx
 TABLES
 return = t_ret
 conditions_in = t_cond
 conditions_inx = t_condx.
How can I change the price and trigger a new pricing for the sales order?
Thank you for your time
Regards
Norbert

Hi
In the transaction VOFM, tab -> Formulas -> Condition Value , create a new routine, no need to copy from existing as you will be writing your own logic.
In this new routine, set xkwert to your required value.
Ask your SD functional to assign this formula to ZAS2 condition in the transaction V/08.
I hope this might help.
Best Regards,
Nikhil Patil

How to change pricing conditions

Hello Experts,
i'm trying to change pricing conditions in routines.
SPRO --> SD --> System Modifications --> Routines --> Define Copying Requirements (double click any activities) --> it will open "Maintain Requirement and Formula"
select from menubar "Formulas --> Condition Value"
Routine Number --> 36 - Cumulation condition.
i want to change conditions in this Routine 36, so i copy this routine and create a new routine name
901 - Cumulation condition
i want to change Pricing Conditions in this routines. this standard routine adding all sub-total pricing values. but i want to display all sub-total pricing value separately in there respective field.
i'm checking this result in VA11.
any ideas? i know i have to change code in this copied rotines for this calculations. but i'm not finding any clue where this value is getting added in each sub-total field level.
if any more clarification needed, please ask.

Hi Rabindra
For Net Price you can refer this Note 80183.
Neha

To make the Pricing Condition types inactive in Pricing Procedure

Hi Experts,
I am facing a senario where, in a sales order, pricing procedure, if one of the pricing condition type does not exist, then two other condition types (even though they are determined by condition records), should be either made inactive or should not appear in the pricing procedure.
Example: If I have 3 condition types in Pricing Proc say
YYY1, YYY2, YYY3, then the scenarios are
a. If one of the condition types YYY1 is not determined, then, YYY2 and YYY3 should not be either determined in the sales order or should be made inactive. This same logic applies to both YYY2 and YYY3.
b. If all three condition types are determined in Pricing Proc of the sales order, then, the price should be considered.
If it was just YYY1 then, I could have done it in VOFM by writing a routine and assigning it to YYY2 and YYY3 in pricing proc. However, the scenario is to check the other condition types as well and make YYY1 inactive if any of the other condition type does not exist. Both condition types are determined after YYY1 which is another difficulty.
I tried creating a dummy condition type and assigning it to Pricing Proc (at the end of Pricing Proc). For this dummy condition I put in a pricing requirement which checks for all three condition types and if one does not exist, then it make other conitions inactive.
However, this does not work in VA02 and VA03 as XKOMV is either not getting filled up or even if is getting filled, it is not having the condition type. It some times has condition records, and sometimes not... (not very sure why)
So, I was thinking of using user exit for the same. However, I was unable to find a suitable user exit for the same where KONV table can be read or XKOMV can be filled.
Can you please suggest if any user exit can be used for this or if we can implement it in a different way?
Regards,
Mukund S

Hi,
I think you can use condition exclusion functionality to select best pricing condition from a set of conditions in pricing. You can compare conditions in many ways.
I believe you can plot a solution with little research. The below link is for your reference.
[http://help.sap.com/saphelp_40b/helpdata/fr/93/743483546011d1a7020000e829fd11/content.htm]

Pricing Condition for Serivce Line Item

Hi Experts,
I'm trying to create a service PO with 1 Service line item and this service line item actually contains more than 1 service number. Using BAPI_PO_CREATE1, how can I define the pricing condition for each of the service number?
Currently, I'm able to define the pricing condition of the service item as a whole through this input parameter table POCOND.
Thanks.
Best Regards,
Weishan

Its really tricky requirement, when you are going for manual condition type.
- the best alternative to cater your requirement is to go for maintenance of condition record, which you can upload at mass with the help of LSMW. Also, will be really helpful in having report for pricing. Finally, reduce time to create sales order. Thus, discuss & encourage your user to maintain pricing based condition record. Only header condition should be on manual bases.
- If hard to convince your client on condition record. Then develop a routine with the help of ABAPer in your team. Where you can put logic. If the condition is manual enter and system is able find already entered value for material, then copy the price the slots where system don't find manually entered condition value.
Regards
JP

Pricing Condition VPRS

Hi guys,
I'm receiving the following error in a Standard Sales Order: OR against pricing condition: VPRS - Error in quantity/value determination.
I believe I have to set this up either in the payment terms table OBB8 or against the material. Could anyone give me a walkthrough of the steps required to set this up please?
Points awarded for helpful responses.
Many Thanks,
Philip Johannesen

Hi,
Some more info for routine 4 which must be assigned to VPRS in pricing procedure.
An order is placed that contains both stockable and non-stock items. Non-stock items are represented in the sales order with the item category TAX. TAX has been configured so that the cost is not determined during pricing of that item in the sales order. Stockable items have been configured to determine costs so that the net sales price can be compared against the cost price. Requirement '4' is assigned to the cost condition type in the pricing procedure so that the cost price is only accessed if the item category is relevant for cost determination
Regards,
Amrish Purohit

Duplicate pricing conditions due to contract supplements

Hi all,
 
We want our pricing conditions to appear automatically on a normal purchase order and on a purchase order with reference to contract, but they should only be on the purchase order once. We're experiencing difficulties since the condition is fetched and displayed twice (once coming from the condition supplement via the contract and a second time via the standard purchasing procedure).
 
Let me sketch the scenario.
 
We have two procedures used for purchasing: 
- procedure ZM0000 as standard purchasing procedure 
- procedure ZM000S as contract supplements procedure
 
Both procedures contain conditions ZA00, ZR01, ZR02, ZR03, ZR04, ZR05 and these conditions are not indicated as a manual condition.
 
For condition type ZA00 the pricing procedure ZM000S is defined so that condition supplements can be added in the purhcase contract. There is also an Access Sequence for this condition to prevent it from appearing twice on a purchase order with reference to a purchase contract.
 
When we create a normal purchase order, we get all conditions from the ZM0000 procedure without any problem.
But when we create a purchase order with reference to a contract with condition ZA00 and condition supplements ZR01, ZR02, ZR03, ZR04, ZR05; then we see these ZRxx condition appearing twice instead of once. 
It's displayed once coming from the ZM0000 procedure and a second time due to the ZM000S procedure.
 
I've had a look at the standard procedures, at sap notes and searched on the forums and can't find a feasible solution for this.
 
One way it is commonly solved is to make the ZRxx conditions a manual condition but that means the user will have to add these conditions manually to the purchase order. When we're talking about 50 or more conditions then it becomes a cumbersome to add all these conditions (if required) manually one by one for each purchase order that the user creates --> not feasible.
 
I guess another solution would be to create an access sequence for all ZRxx conditions based on purchase order type and then create condition records for all ZRxx conditions for the purchase documents without reference to a contract. That way the condition will be displayed once (from the condition record) on a normal purchase order and once (from the contract, since the condition record can't be found) in case of a purchase order with reference to a contract. When we're talking about 50 or more conditions and more then 2 document types, then maintaining all these condition records is quite some task --> not really feasible, not the prefered solution.
 
As an alternative to SAP standard we've found the following enhancement point in LV61AA11 where we could possibly delete the "duplicate" condition from KONV if the condition origin (KONV-KHERK) is not equal to "Condition supplement" (F) in case of purchase document type that references to a contract... but this is not the prefered solution.
 
----- 
get pricing result from database table 
ENHANCEMENT-SECTION KONV_EINLESEN_02 SPOTS ES_SAPLV61A. 
select * into table hkomv 
 from konv 
 where knumv = komk-knumv 
 order by primary key. 
END-ENHANCEMENT-SECTION. 

 
Also, it's not a feasible solution to put a requirements formula on all these ZRxx condition because we're talking about more then 50 conditions.
 
Does anyone know a solution to this problem? 
How can we make sure the condition is displayed only once? (be it on the standard purchase document or on the purchase document with reference to the contract) 
Is there a standard approach for this?
 
Thanks in advance for your time.
Edited by: Kevin Coquel on Apr 15, 2010 3:34 PM

Bernhard, 
Thank you, but as I mentioned in my starting post, this is not feasible as this is concerning over 50 conditions (some of which already have other requirements formulas). 
Using requirement routine for all is an option we want to avoid at all costs. 
It would mean we need to have edit our existing requirement routines to also include routine 15 (as you can only have one requirement routine per condition in a pricing procedure). 
 
Hardik, 
Thank you for pointing us to EXIT_SAPMM06E_013. 
Preferably we would like to solve this using SAP standard before turning to ABAP development. 
 
I'm a bit surprised not being able to find a SAP standard solution to this problem. Since it's not possible to define a different pricing procedure per purchasing document type I would expect a) there is a way to avoid duplicate conditions (coming from the contract supplements) when you're in a purchase document with reference to a contract and b) that the conditions will appear by default in a normal purchase document (instead of having to add them manually one by one when you use "Manual" in the pricing procedure).

Help with pricing condition??

Hi Guyz,
I have a requirement with my client, the want to supply material to an external customer at an intercompany price(ZPR9). So whenever a sales order is created for this specific customer it should pull the price from Intercompany price(ZPR9). I have a option to create new pricing procedure and new pricing condition but this condition should pick up the price from ZPR9 so that we don't have to define the price manually like we do in PR00.
I can't able to assign ZPR9 to my new pricing procedure because ZPR9 is use for intercompany and this customer doesn not belong to any of our company code.So the situation is i have to define new pricing procedure and new pricing condition but this condition should pull the price from ZPR9.
when I see the details of ZPR9(condition type) its condition category is assigned as 'Y' which is customer reserve Y. I am not sure what this is.So could you plz advice how to handle this whole scenario. Appreciate your help.
thanks
Mohammed.

mohammed,
This type of requirement is hard to handle and if you do it in a wrong way, whoever support this process later will have a hard time.
Anyway, I think one of the twisted ways of doing this is to use Alternative Culculation routine and put the logic to get the condition right out of price condition table (A*) of ZPR9. This is not flexible at all because this involves hard coding, so I do not recommend this.
The message I can get from your client is "We don't want to maintain the same condition here and there," but sometimes they have to deal with it, because the nature of the condition type is very different from business point of view.
Having said that, in order for them to have easier way to create the condition, maybe you can develop a custom ABAP to copy ZPR9 condition into the new condition you might be creating, and either have them run the program every time they update ZPR9 or schedule the job.
Hope this helps.
Akio

Pricing Condition type triggering based on other condition type

Hello sir,
There are some pricing condition types in our system.
Based on condition records you can trigger one condition type based on other    condition type.
For eg: PR00 condition type is there and amount is suppose 1000rs and other condition type is JBED and we made a condition record and put it some percentage so as soon as we some value in PR00 ,JBED condition type is automatically manipulating the value on the base condition record.
Now i want other than condition record can we trigger one condition type based on other condition type through defining user routine under requirement.
Suppose we have condition type ABC and some amount i have given and other condition type DEF , i want that amount of DEF condition type should automatically come from the Condition type and it should manipulate according to my routine .
eg Condition type    Amount
       ABC                  1000
       DEF                    40
The value 40 should come as 4% of 1000.
I am not maintaing any condition record and i want that this should trigger through some requirement created by me.
i created my routine no 905 and i putted the code inside it.
if komtl-kschl = 'DEF'.
komv-kbetr =   ( komv-kbetr * 4) / 100.
endif.
Now problem is that this code is getting trigger when i m giving value in DEF condition type then it is showing 4 % of it.
But i want as soon as i give value for the condition type ABC and some value 1000
then after pressing enter , one condition type DEF should automatically come with value 40 that too in display mode ,not in change mode.
Please suggestions and solutions regarding this matter , I will be grateful to you.
Manish

hi
In V/06 in the calculation type you can see the entries for "D-gross weight" & "E-net weight"
For the required condition type select the calculation type as gross weight or net weight. Save it.
In MM01 - create material master, here in BASIC DATA 1 SCREEN you have fields for gross weight & net weight.
Maintain the condition record in VK11 for the required condition type.
You can also maintain the scales as required like u said
1 to 10 kgs - 100 rupees,
11 to 25 kgs - 1000 rupees.
Another way could be
The BEST practice to do it is, use of VOFM routine for price calculation (VOFM-->Formulae).
Take help from ABAPer and write a routine such that
if weight = 1 - 10
price = 100.
else if weight > 8.
price = 1000.
else
price = 100.
end if
but the maintainnance of routine is big problem as u might be having many records
Hope this will help you
Vishal

MM - Purchasing Information Record/Pricing Condition

Hello MM world,
I'm taking this opportunity to log an issue I can't find an answer for and I would appreciate to know if someone out there would share his/her knowledge with me.
So here's the question:
I'm trying to determine an additional pricing condition type (discount) during the creation of a purchasing info record (me11). The default PB00 gross price condition type is automatically proposed. Attached to that condition type, you can indicate a pricing schema/procedure that has what they refer to as condition supplements. The condition supplements pricing schema looks like an ordinary pricing procedure, however, SAP has confirmed that condition technique or access sequence determination does not work within the info record due to conflicting validity period between the info record and the additional pricing condition types. So, what I am wanting to do is write both a requirement and alternative condition routine for the ZPIR condition to calculate the discount amount. This will work fine, however we can only hit the routines IF the ZPIR condition supplement is automatically proposed. If the condition type is presented, we can hit the routines without a problem..the challenge is, we cannot figure out how to automatically propose the condition supplements, in our case ZPIR, without clicking the icon during create.
So, what I am wondering is if it is possible to write something in the requirement or alt condition routine attached to PB00 to programmatically add ZPIR to the info record, which would then invoke the requirement and alt condition routine that would determine the discount value.
Or is there anything else we can do to make this work?
Thanks a lot, I appreciate any input.
Mo

Hi Mo Arabat,
Looks good .Once agarin check up your configuration throug this link.
http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
Cheers
Hareesha k

Pricing conditions ---- routine

Similar Messages

Maybe you are looking for