Restrict Double entry of condition type

Hi All,
How to control double entry of condition type at Item & header level in sales order????....any solution
Thanks & best regards
Umed

Condition type settings V/06, Changes which can be made section maintain B- Automatic entry has priority , if condition record exist then system will not accept to enter manually.(If yours is autoamatic condition type.)
If your condition type is manual and if you maintain 'C' - Manual entries has been priority or Blank - No lomitations, then i think we can not stop this.
Regards,
Ramesh

Similar Messages

Defining the Fields for Manual Entries in Conditions Type

Dear Team,
I want to define new fields in the Option Manual Entries in Condition Type eg PR00 . Can you tell me the Setting where do we define those settings and where are they control.
Thanks,
Prashant

Hi
The option provided for Manual Conditios are Hard Coded by the SAP, and you can not add any new option. If you want to check, pl. check the value range of Domain KMANU, where it is maintained.
What is your requirement? May be you can fulfill your requirement by some other mean, like USER EXIT.
Regards
AA

Making manual entries - In condition type

Hi All,
Can you please explain in detail about _ , A and C ? This is the value we give in manual entries in Condition type ? Plz give a business scenario.
<<
Indicator which controls the priority within a condition type between a condition entered manually and a condition automatically determined by the system.
Make the following entries according to your requirements:
_: No limitations
A: Freely definable
C: The manual entry has priority. When you enter the condition
manually, the system does not check whether a condition record exists.
>>

Hi,
No limitation means it is free to do all the changes,overwrite etc.
C means even if the condition record is present and you enter the condition manualy,manual entry has priority over the condition record.
Reward points if useful
Regards,
Amrish Purohit

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

Restrict the input in condition type

Hello Friends,
In my PO there are six condition types used for freight calculation my requirement is when user enter value in any condition type thn all the remaining 5 condition types should not allow any entry(it should become grey).
pls let me knw how we can achieve this?
Sunny

Hi
Try using the Condition Exclusion Groups
SPRO-> IMG-> MM-> Purchasing-> Conditions-> Define Price Determination Process-> Define Condition Exclusion
If several condition records are valid in the price determination process, you must define rules stipulating which conditions are selected and which are disregarded. To do this, use the condition exclusion mechanism.
The exclusion of condition records is controlled via exclusion groups. An exclusion group is a list of condition types that are compared with each other during the price determination process. The result may be the exclusion of a whole group of conditions or the exclusion of individual conditions within a group.
The result of the price determination process can thus be influenced with regard to a desired criterion (for example, the lowest price) by the exclusion of certain condition types, whereas others are taken into account in this process.
Example
You can define a condition exclusion process that determines the most favorable price and excludes less favorable but fundamentally possible pricing results. The lowest price then overrides the condition type priorities that would have been dictated by the access sequence.
In the calculation schema you define the procedure by which selection within or between the condition exclusion groups takes place. The following possibilities are available:
Selection of the most favorable condition type within a condition exclusion group.
Selection of the most favorable condition record of a condition type if more valid condition records exist (for example, selection from different condition records of condition type PR00)
Selection of the most favorable of two condition exclusion groups (in this case, all condition types of the two groups are cumulated and the totals compared with each other)
The tables for the exclusion of conditions are supplied empty. You must therefore work through the following points if you wish to use the condition exclusion facility:
Define condition exclusion groups
Assign condition types to condition exclusion groups
Enter condition exclusion groups in the calculation schema and define a procedure for the determination of the condition types to be excluded.
Activities
1. Create a condition exclusion group by entering an alphanumeric key that is max. four characters long, together with a description.
2. Assign the condition types to a condition exclusion group. A condition exclusion group can contain any number of condition types.
3. Enter the condition exclusion group in the calculation schema that you will be using for price (or cost) determination purposes.
4. In the process, note the sequence (consecutive numbers) in which the exclusion groups are to be processed.
Using this yuou can achive your requiremnt .
Thanks & Regards
Kishore

Restriction required on the condition type on base amount

Hi All,
Client want an restriction on condrion type (freight)
Amended Formula : 1.01 * (Basic Price or BPXX + Freight Actual if Fright is less than 20% of BPXX or if more than 20% than restrict it to max 20% of BPXX + Insurance or INS2)
they want freight will not exceed more than 20% if it will exceed then system should restrict.
Regards
Sachin

Hi,
Check in the Pricing procedure V/08 whether any Requirement was set or not.
Also check Whether the Statistical option was set, if it was sest , change it to either Mandatory or Optional.
thanks,
santosh

Entry for condition type missing in table PRCC_COND_CT

Hi guys,
I got this error message in my BDoc.
It ask me to
"Fill the table PRCC_COND_CT bu using a Customizing download, and then restart the rolled back block in the inbound queue."
I am not too sure what is a customizing download.
Can you guys help me out?
Cheers
Lawrence

Hi,
Firstly please apply the note 1003793 and then run the customizing load again and check for errors.
then if you get any errors like
"It is not possible to change client-independent Customizing objects Message no. CND_MAP204 "
Then log into SCC4 transaction and then make the following change
"changes to repository and cross-client customizing allowed" under Cross-Client Object Changes.
Thanks,
Abishek

User Exit for eliminating double condition type in sales order

Sir,
In SE38, Program SAPMV45A, I am using user exit ( Userexit_pricing_prepare_tKomp ) to avoid double entry
of condition type like PR00 in sales order . But i am not getting how to write code.
Please, help me how to write code in user exit.
thanks,
Manoj.

Thanks for replay.
Sir, I want to impliment it in sales order (VA01 OR VA02 )
for pricing . Here I want to avoide double condition types like PR00, packing forwarding, frieght ....etc
in sales order pricing.
Here i want to give logic that codition type is already exit and you canot enter same condition type
again. means if condition type is already exit then system should not allowed to enter again the same condition type
in sales order pricing.
Thanks
Manoj.

How to rescrict the user to enter a manual condition type once in pricing

Hi All,
We are using a condition type ZSP1 in our pricing procedure. I want that the user should be able to enter the condition type only once during pricing.
eg Suppose the user has entered ZSP1 as 100 in the sales order , then he should not be able to enter ZSP1 again in the pricing. Only one entry should be allowed for the condition type ZSP1
Please respond if you need any further clarification.
Regards
Adity

Hi,
you can Restrict the entry of Condition type Twice with Following User Exit
USEREXI
USEREXIT_PRICING_PREPARE_TKOMK
USEREXIT_PRICIN
we have Implemented for one our Client

Condition types restriction at only certain combination like Country/Tax

Dear All
In FV11/12, with object V_KONH_VKS we can restrict users accessing certain condition types (field - KSCHL). My query is that I have few condition types accessed by various Plants i.e. common across Plants/Company Codes. Hence would like to restrict users at Key combination level.
For eg.
Condition Type JMOP - Key combination u2018Country/Tax Codeu2019 and u2018Tax Classificationu2019. Certain users should be allowed to change this combination and other users can change other key combinations i.e u2018Plant/Vendor/Materialu2019, Plant/Material Groupu2019 etc.
Request your help asap.
Regards & Thanks
Guru Prasad

>
P Arpan wrote:
> Hi
>
> Shekar wrote :
>
I dont think it is possible to restrict on specific key combinations
>
> I have checked and found that authorization check is not getting done by key combination. It is checking for condition type only.
>
> Arpan
>
> Edited by: P Arpan on Mar 29, 2010 12:54 PM
Hi Arpan,
wasnt that what i mentioned in the previous post? You cannot make a restrcition on the access of the pricing procedure (key combination as all of us refer it to). You can make restrictions on the condition table and the condition type but not on the different accesses of the condition table itself

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

Condition type check in va01 transaction

Hi friends,
I have a requirment.
in va01 transaction , at the line item level iam entering a material number and order quantity and when i press enter i get the corresponding values for that particular line item.
now iam double clicking on that particluar line item(matnr) and clicking on the conditions tab.
there in the condtion type i will get what all the condition types are maintianed for that particular line item.
now my requirment is i need to add another concdtion type manully
say 'ZABC' and hit enter. the pricing for that particlular contion type 'ZABC' will be Determined.
Now can any one tell me in which internal table will i get all the condition type,
coz i need to do some additional check for the the manual entry'ZABC' (condition type ) which i have given .
which user exit should i use it.
remember i need user exit for condition type check but not for pricing bsaed on the contion type
Regards
Priyanka.

Hi priyanka
If you want to Check then check in the KOMK and KOMP tables
As you want to go for user exit use any one of the user exits as per your requirement USEREXIT_PRICING_PREPARE_TKOMK or USEREXIT_PRICING_PREPARE_TKOMP
But can you tell what exactly you want to change and why you want to go for user exits
Regards
Srinath

OVKK--Condition Type?

Hello All,
When you define the determination of pricing procedure in txn OVKK, there is a field 'Condition Type'. What is this used for..?
The F1 says:
Proposed condition type for fast entry
The condition type that the system automatically proposes in the double-line entry screen during sales order processing.
Now, what exactly does this mean?
Someone, plz explain...
Rgds,
Rags.

Hello Rags,
In OVKK the condition type which you specify is displayed in the sales order at the line item level in the "CnTy" field & the adjacent field "amount" shows its condition record. This will be shown per piece.
Say your sales executive needs to inform the customer about the base price (condition type PR00) of the item for that particular sales order, then he/she does not need to check at the item level pricing. He/she can directly check at the line item level & tell the price. If the condiiton type is not maintained in OVKK, then the respective fields will be blank in the sales order.
With best regards,
Allabaqsh G. Patil.

Excise duty condition type and Purchase Order Print Issue

Dear Friends,
We have a issue related to Purchase order print out.
We are maintaining TAXINN.
We have implemented CIN and we are maintaining Excise Conditions i.e. Basic Excise in JMOP
In FV11 we are maintaining values for JMOP with plant and material Group combination.
In Purchase Order Tax calculation is happening correctly.
But issue is to find the value of taxes for Purchase Order Print.
We are using function module CALCULATE_TAX_FROM_NET_AMOUNT
and passing values of Company Code, Country, Currency, and Base amount to get the entries in condition types.
But we are not getting any entry even after passing the values.
How we can get these values in JMOP.
Regards
Kant

Why do you want to calculate the taxes during the PO Print when you are getting correct values in PO itself?
Modify your print program with pulling values directly from EKPO/ EKKO Tables and display it to Spool.
check with ur ABAP Person

MM-PUR default scales for condition types for service (ME31K

Hi,
We have faced the following problem:
The business case was, to have default scales for certain condition types for a service for a purchasing contract.
We didn't find it in SAP, so we wrote an OSS. SAP answered that it's not possible now, nor in the future.
So we decided to look around in SAP, and found out that it was half possible.
I've abused the exit USEREXIT_XKOMV_BEWERTEN_INIT of program RV61AFZB.
In this exit I provide the internal table staffel for program SAPMV13A with the correct information (via ASSIGN ('(SAPMV13A)STAFFEL[]') to <staffel>.)
In this way, if a user adds a service, this exit will get reached and the scales are filled. If the user then clicks on conditions and then double clicks the condition type with the scales, all the default scales are shown to the user. If you then click on save, the next screen is the service screen, if you then click on save again, all the date is stored in the database. (bit of a work around, but this works)
However, I can't figure out how to save the scales data, when you only add a service and then push the save button without viewing the conditions. Quite logically actually because I'm skipping two whole screens with pbo and pai modules, in these modules internal converting takes place.
Has anyone encountered this problem before and how did you solve it then ?
Alternatively what is the SAP standard way to add pricing condition scales on condition types of a service of a purchasing contract? As you know there is no BAPI yet to change/create a purchasing contract.
I was thinking, to add the scales by updating the tables directly via ABAP, I know that's not a clean way to do it, although it isn't too risky.
Kind regards, Rob Dielemans

Dear Rob,
Is this solution properly working for you?
I think my problem is similar: purchasing outline agreement (contract) refuses to apply relevant scale prices in the item line. Always uses the first price - without considering order quantity depencies.
Regards,
Tamás
Edited by: Tamas Szabo on Mar 31, 2009 3:50 PM

Restrict Double entry of condition type

Similar Messages

Maybe you are looking for