Duplicate Condition

Hi Expe
In the system while PO creation in the condition tab, the system allowed us to take the same duplicate Condition again.....
my requirement is this is someone pick the same condition again,the system should show error or warning message as as duplicate Condition Types not allowed
regard
nabil

Dear Nabil
Remove all duplicate condition by T Code ME2K (plant + material ) level and check the same.
Regards
Dishant

Similar Messages

Restrict duplicate condition type in va01

Hello Experts.
I want to restrict user from entering duplicate condition types in tcode va01, how can I go about it?
Is there any user exit or BADI available, if yes please let me know how to go about it
Thanks in Advance...

HI deven,
Check any one from the below :
Enhancement
V45S0001                                Update sales document from configuration
V45S0003                                MRP-relevance for incomplete configuration
V45S0004                                Effectivity type in sales order
V45W0001                                SD Service Management: Forward Contract Data to Item
V46H0001                                SD Customer functions for resource-related billing
V60F0001                                SD Billing plan (customer enhancement) diff. to billing plan
SDAPO001                                Activating Sourcing Subitem Quantity Propagation
V45A0001                                Determine alternative materials for product selection
SDTRM001                                Reschedule schedule lines without a new ATP check
V45A0002                                Predefine sold-to party in sales document
V45A0003                                Collector for customer function modulpool MV45A
V45A0004                                Copy packing proposal
V45P0001                                SD customer function for cross-company code sales
V45L0001                                SD component supplier processing (customer enhancements)
V45E0002                                Data transfer in procurement elements (PRreq., assembly)
V45E0001                                Update the purchase order from the sales order
Business Add-in
BADI_SD_SCH_GETWAGFZ                    Scheduling Agreement: Read WAGFZ from S073
Regards
Abhii

Restrict to insert Duplicate Condition Types

Hi,
During PO creation with Freight Condition - ZFR1, user is able to insert this condition TWICE.
Means Freight Condition is showing 2 times in Conditions...due to this My purchase register report get incorrect data...
How to restrict user to insert Duplicate Condition Type???
Please guide..

Hi,
If you want Freight Condition - ZFR1 should not enter again or not possible to enter by user & select D {Not possible to process manually} in Manual entries in M/06 t.code in 'Changes which can be made' segment'
NOTE:
As you needed keep Freight Condition type- ZFR1 to be appeared in the PO as automatic, so then maintain the condition record (t.code MEK1) with condition type ZFR1
OR check routine or design to write a routine & assign to Freight Condition - ZFR1 in M/08( in MM Schema), so it should not enter again or not possible to enter by user(can appear only once).
Regards,
Biju K

Duplicate condition type in contract header

Dear Experts,
In contract (VA43) header, i am getting duplicate Condition type (zcondition type). This condition type is not duplicate at Item level.
Also at header level where dupluicacy is there, it has both Statiscal indicator marked and unmarked rows. No access sequence has been assigned for the condition type.
My requirement is there should not be duplicate condition type at header level. Find below screenshot for the same.
Please guide me what should be the required steps to rectify the error.
Best Regards,

You can also create conditions at header level, however, these can only be discounts or surcharges. These master conditions are used by Pricing in SAP Enterprise Buyer to determine a gross price. For details, check SAP help at
http://help.sap.com/saphelp_srm30/helpdata/en/ee/d9df3bbcce4b37e10000000a114084/content.htm
The following thread might be useful to you as well Pricing Condition in Contract

Need to delete duplicate condition types from ME22N

Hi Experts,
I have a requirement to delete duplicates from ME22N, header and item.
Scenario : On adding condition in header the same will be reflected in items and vice versa.
I tried using ME_PROCESS_PO_CUST and userexit RV61AFZB.but not resolved.
Kindly suggest.
Regards,
Mohammed Samiuddin.

Hi -
The CHECK method gets triggered when you click 'SAVE' and 'CHECK' in ME21N / ME22N but may not trigger when you press 'enter'.
PROCESS_HEADER triggers incase any change to header details but not (always) for change in header conditions. PROCESS_ITEM get triggered when change in item data for a particular item.
If you to use CHECK method.
You can get the header as well as item conditions, you can get in this method.
DATA:   lw_header_data       TYPE mepoheader,
              li_items            TYPE purchase_order_items,
             lw_items             TYPE LINE OF purchase_order_items,
               lw_item_data         TYPE mepoitem,
            li_item_data        TYPE STANDARD TABLE OF mepoitem,
              li_item_conditions TYPE mmpur_tkomv.
   IF im_header IS NOT INITIAL.
      CALL METHOD im_header->get_data
        RECEIVING
          re_data = lw_header_data.
      CALL METHOD im_header->get_items
        RECEIVING
          re_items = li_items.
      LOOP AT li_items INTO lw_items.
        lv_items = lw_items-item.
        CLEAR lw_items-item.
        CALL METHOD lv_items->get_data
          RECEIVING
            re_data = lw_item_data.
        APPEND lw_item_data TO li_item_data.
        CLEAR lw_item_data.
CALL METHOD lv_items->get_conditions
          IMPORTING
            ex_conditions = li_item_conditions.
    ENDLOOP.
ENDIF.
But I am not sure if you will able to set the conditions in the check method. You can try.

How to restrict duplicate condition type in sales order

Hi All
Is there any standard method to restrict user for adding a particular discount condition type more than once in sales order. condition type is manual and its records are also being maitained manually.
Else would I will have to create userexit at sales order level or a routine in pricing procedure. I doubt on creating a rotuine in pricingprocedure because in pricing procedure there is already a restirction to add similar condition type more than once.
Thanks

create a routine and add this routine to the discount condition type only.

Duplicate condition type in sales order

hi.,
I will enter the rate for particular material in PR00.agian i will enter the rate for same material.the system will allow the two condition record in manually.
I want should not enter the seconfd time.
lakshmanan

hi
yes it is possible.
when u raise the sales orde double click the lin item goto CONDITION TAB
enter Ctype PR00 it values save t
regards
krishna

Duplicate condition records with BAPI_SALESORDER_CREATEFROMDAT2

you don't have to pass the bapisdls at all. Just don't pass the bapisdls. make sure that you're passing kschl, kbetr kmein kwert in the conditions_in parameter to the bapi. That should do it.

Hi Fuad,
I think there can be two ways.
1. Create SAles order as you are creating without pasing any value for this condition type. and then change this condition value ( which is being determined automatically) by using BAPI_SALESORDER_CHANGE wher you can use Update flag as 'X' In parameter CONDITIONS_INX of this BAPI.
OR
2. If you want to happen this chage at the time of sales order creation, then I think , this particual condition type should be "manual" and not "Automatic" One.
Hope this helps.
Regds,
Akshay Bhagwat
Note: Pls mark helpful answers.

Duplicate condition types in processing rebates

Hi,
I have created two rebate agreements in the system right now.
Whenever i run a sales cycle the condition type BO01 is used twice instead of once which results in giving discount twice for the same order.
Is there any way to avoid duplication of condition types.
How to solve this issue, pl help..

Hi
You have maintained two rebate arrangemnts here and sytem is determining accordingly.
Thats the reason you need to ensure the combination being used in the condition type.
If both the records are valid i am not seeing an issue here.
If your issue is same condition type. then you need to maintain different condition types for different combinations,.
For example: Key Combination -> Condition type
Customer/ Material - B001
Customer/ Sales area - B002
Maintain two condition types for both combinations instead of maintaining it is the same.
So they get determined accordigly.
Thanks & Regards
Kishore

Duplicate Condition Record Number !

Hi Experts,
I have a question on condition record number:
I have a Material SH00001 in more than one Sales Orgs. Example: MTD and NTD.
1. Is it possible SAP generates the same condition record number (field- KNUMH) for both sales organisation when I created two records separately at VK11 for each sales orgs for price?
2. Is it possible SAP automatically generates two condition record numbers when I create a ccondition record at VK11 (for price )
for a material SH00001 for a sales org MTD for two unit of measures. (e.g PC and KG)
3. Is it possible SAP automatically generates two condition record numbers when I change a ccondition record at VK12 (for price )for a material SH00001 for a sales org MTD from one unit of measure KG to PC??
Thanks

Hi
For one condition record in VK11, system will create one number. And if your are creating new record with slight difference, new number will generate.
Conclusion, no two condition records can have same number.
Secondly, if you change record in VK12, record number will not change.

Avoid duplicate Condition Type.

Hi Master,
I have some problem with condition type in sales order document, let say i have condition type ZRP for Retail Price and this condition is define manually. i want to make this condition only define once in every item, the user cannot add that condition type again. Can you help me how to setting the configuration for that case ?
Thanks & Regards,
L - SAP

Dear S Navaneetha Krishnan
While making a stock transfer (purchase order) by ME21N from supplying plant (Factory) to other plant (depot), if user make mistake & donu2019t put value for Manual condition type ZMRP, system accept & save the order.
Afterwards when he realizes the same or immediately come to know about not putting value & put again, system take that second line entry also & create double entry.
When invoice come then it pick the value from first line & show in negative.
How it is possible to restrict it at order level only to not to allow 0 value entry?
I have tried
At pricing procedure, there ZMRP is required entry.
Condition Type - ZMRP, there is _ No Limitations
We can not put D Not possible to process manually or fix this condition type as then we have to maintain condition record & prices are varies depot to depot & day by day.
This is only has to put manually by user according to the instruction of sales department.
Please provide me a solution at configuration level as user exit is difficult to do for all requirements.
Rgds
Srivastav
+91-9694096833

Duplicate condition type at item and header level

hi all,
please help me to implement this
issue:
PO condition type for header and item should be checked for duplication.
atanu

Hi
I am not sure whether we can do this with IMG.
Need to use User exit MM06E005 (do not be confused with the description of this enhancement..you can use it)
Best regards
Ramki

Duplicate Condition from Condition Exclusion procedure

Hi Team- I have a condition Exclusion procedure with Type B- Best condition within the same condition type which is assigned to my PP, Condition Type Used is ZZZ1. Everything is working fine as expected in my sales order. Where as the ZZZ1 is showing twice in the order one with inactive and other with active indicator on. Due to some reasons we do not want show or list the inactive one in the sales order. How to do this?
Reg
Siva

Hi Siva
Try to use standard requirement 5 or 6 in condition ZZZ1 in pricing procedure definition.
Regards,
ZP

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).

BAPI_PO_CREATE1 condition type are creating duplicate records

Hello Experts,
Currently I am creating Purchase orders using BAPI_PO_CREATE1 . When I am passing Condition related records to the same BAPI , second line item onwards , it creates multiple records of same condition type .
I have also looked into threads in SDN for the same , and they have suggested to create PO using BAPI_PO_CREATE and later use BAPI_PO_CHANGE to pass condition records. I have tried the same , but still second line item onwards it creates multiple records. Please tell me how do I resolve this issue.
Thanks
Trishna

Hello All,
This duplicate condition record creation may happen due to a setting in the MM configuration, where the system tries to pull in the history condition records ,based on the same set of condition record determination parameters.
Please contact the MM functional consultant in your team for settings change in detrmination of condition records under " MM-Purchasing " section.
Best Regards,
Kumaar.S

Duplicate Condition

Similar Messages

Maybe you are looking for