Duplicate pricing conditions due to contract supplements

Question

Hi all,
<br><br>
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).
<br><br>
Let me sketch the scenario.
<br><br>
We have two procedures used for purchasing:<br>
- procedure ZM0000 as standard purchasing procedure<br>
- procedure ZM000S as contract supplements procedure
<br><br>
Both procedures contain conditions ZA00, ZR01, ZR02, ZR03, ZR04, ZR05 and these conditions are not indicated as a manual condition.
<br><br>
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.
<br><br>
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.<br>
It's displayed once coming from the ZM0000 procedure and a second time due to the ZM000S procedure.
<br><br>
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.
<br><br>
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.
<br><br>
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.
<br><br>
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.
<br><br>
<span style="font-family: Lucida Console">-----<br>
get pricing result from database table<br>
ENHANCEMENT-SECTION     KONV_EINLESEN_02 SPOTS ES_SAPLV61A.<br>
  select * into table hkomv<br>
           from konv<br>
           where knumv = komk-knumv<br>
           order by primary key.<br>
END-ENHANCEMENT-SECTION.<br>
</span>
<br><br>
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.
<br><br>
Does anyone know a solution to this problem?<br>
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)<br>
Is there a standard approach for this?
<br><br>
Thanks in advance for your time.
Edited by: Kevin Coquel on Apr 15, 2010 3:34 PM

Answer 1

Bernhard, <br />
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). <br />
Using requirement routine for all is an option we want to avoid at all costs.<br />
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).<br />
<br />
Hardik, <br />
Thank you for pointing us to EXIT_SAPMM06E_013.<br />
Preferably we would like to solve this using SAP standard before turning to ABAP development.<br />
<br />
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).