Condition type restriction

Hello Sap Guru's,
In the scenario, how to restrict condition type for manual entries to a particular user?
Regards,
JP

Hi Ashish,
Version 5 of the note 105621 is the earliest still visible one, from the year 2000... which is even before SDN itself
Much of the note is occupied with how to create a custom authorization object to be able to add own code to the exits for doing "whatever" to the condition types.
The later note transfers these exits to BADI's, and keeps the authorization concept previously implemented, albeit it still describes using manual profiles in the reference to the older note - where PFCG roles are the prefered weapon of choice now-a-days.
Yes, I understand that you wanted to "simplify" that part of the blog to concentrate on the general possibility of adding logic based on the condition type.
I think many developers, when faced with the requirement of using an IF statement and not having any understandable authorization concept to work with, have reached out for the bluntest tool in the box to use: sy-uname. But for others this only makes it worse and even less understandable what is going on.
It always reminds me of [this scene|http://www.corbisimages.com/images/42-20041107.jpg?size=67&uid=2597837E-FED2-4E85-AE4C-CECF92B67B45] when I see such things... as do the new sy-unames of Amit and his clones...
Thanks for your patience with my rant and following up on the topic, so that others who use the search can see the full picture and the different (better) options (techniques).
A merry christmas and may all your authority-checks return sy-subrc = 0 in the new year 2010
Julius

Similar Messages

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

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.

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 same condition type in pricing procedure

Is there a way to restrict the condition type so that there can only be one occurrence of the same condition type in a order item?
Example:
System reads condition type ZXXX from system, then a user adds the same condition type on the same order item. I would like the system to then give a error message saying ZXXX can only occur once.
Kind regards

Hi,
As this is manual condition and the user are inputing it by themselves then you won't like to change the way the manual changes are maintained/allowed.
What you want that is user have given it once then they should not be able to input is again in the same sales order item. For this you should take help of requirement. Preapre logic that before the condition system check if there is existing condition of this type in this sales order item.
Hope it helps ..

To Restrict Duplicate & Without Value Manual Condition Type in ME21N

Hi Friends,
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 & repeat entry for the same condition type?
I have triedu2026.
1. At pricing procedure, there ZMRP is required entry.
2. 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.
3. Since this is a Header Condition, so canu2019t restrict at Access Sequence level.
This is only has to put manually by user according to the instruction of sales department.
Got Suggestion to change at user exit level to put check at delivery to not to allow printing or invoicing by putting 0 value/without any value.
Please suggest at configuration level only as itu2019s difficult to create User Exit for all requirement.
Srivastav
+91-9694096833

Hi,
You must update the forum how did you solved the issue as it will help others also in future.
This is good practice.
Regards
Sanjay

Restrict referance of pricing and condition type from latest PO.

Hi Experts,
I am creating Purchase order and at the time of creation of purchase order system is copying prices and condition types from latest PO.
Which is not desirable to our business process, when I dig out I found out that in standard SAP system
The system looks at pricing in the hierarchy order as below:
u2022     Contracts/scheduling agreement
u2022     Condition records
u2022     Info Records
u2022     Last purchase document
So can some one help me with information how to restrict system to follow this referance of pricing.
I want to enter price as well as condition type manualy every time user create a purchasing document.
Also i want to know can it be restricted specificaly for few document type.
Thanks
Best Regards
Ritesh

Hi sir
can we try this
Use the user parameter EVO to indicate that no price adoption from last Purchase Order must take place:
IMG: MM -> Purchasing -> Environment data -> Default values for Buyers
-> Setting for Default values.
Select or setup a default value and on the "price adoption" tab you may choose how copying of conditions from last purchase order must behave. Select "Do not copy".
Then assign this default value to the user, using the EVO parameter.
[http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/price-to-flow-from-info-record-at-plant-level-813066]
[Re: new info record with same details as archive one.;
check following notes it may helfull
569885 About Info Record Update indicator (EKPO-SPINF)
13127 Update in info record from PO, quotation, contract
430543 FAQ: Purchasing info record
675523
456691
Regards
Kailas ugale

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 calculation for condition type in Subtotal

Hi Experts,
In my organisaion i have a requirement to retrict the calculation of Subtotal value in the pricing calculation.
I have two Internal price condition type VPRS & ZCST.
VPRS is calculated in Step20
ZCST is calculated in Step30
The subtotal is calculated in Step40 (The subtotal is calculation From 20 to 30)
Now my requirement is to restrict the calculation of sub-total. Eventhough the subtotal is calculated from 20 to 30. I need to have the subtotal value only for 20. I need to exclude fro step 30.
Example:
VPRS - 100
ZCST - 100
Subtotal - 200
My requirement is the subtotal value should be only 100 not 200.
Regards,
Jagadish

Hi Jagdish,
Please try the follwing.
1: Enter 20 in the From column and leave To column blank
or
2: Enter 20 in both the From and To columns in the pricing procesdure.

Restriction for condition type

Hi,
I want to restrict some users to do not change the basic price (PR00) in sale order (VA01/VA02), Plz let me know how I can do this.
regards,
sps.

The objects concerned have to be:
V_KOND_VEA Maintain condition: Auth. for use/appl./cond.type/table -- (Deals with condition records)
V_KONH_VKO Condition: Authorization for Sales Organizations
V_KONH_VKS Condition: Authorization for Condition Types
But in the standard system VA02 has these objects set to No check in SU24. You may have to modify this to Check/maintain and then maintain the values in the users role. Like you can have:
Object : V_KONH_VKS Condition: Authorization for Condition Types
Condition Type: PR00
Actvt : 03
Thanks & Regards
JP

How to mantain restriction on condition type range

Hi,
Our sd consultant want to make restriction on condition type on discount range,
under VA01 when we create the sales order, there we give discount, which should fall under some range , say about 1 to 15 not beyond that,
please assist how to go about it.
Regards,
SM

hello, friend.
when you create condition records for prices and discounts using VK11 or VK31, you can define upper and lower limits for your condition type. in the FAST ENTRY screen, just highlight the condition type and click on DETAILS. you will be brought to another screen where you can enter the limits.
there are also settings in IMG. will give you more details if this is helpful. also, please do reward if so.
regards.

Restricting access for condition types in VK11

Hi
ZWX1 and ZWX2 are SD discount condition types, I should use these condition types only for sales deal , hence , I will create condition record only in VB21 with reference to sales deal.
Some other users may create condition records in VK11 mistakenly, I need to avoid it, so these condition types should not be accessible to create condition records in VK11 or anywhere except VB21.
Any thought ? how can I achieve this ?
thanks

Hi
If you want to restrict the access for the condition types then you give the authorization for VK11 for maritaining the condition records only to those users who has to maintain the condition records for that condition types.So you have to take the help of BASIS team
Regards
Srinath

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

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

Stastical Condition Type is not working in Purchase Order

Hi All,
I created a pricing procedure and Bank charges are created as a condition type which is stastical. I assigned a account Key and Accural key for the same condition type. We activated Purchase Account Management
Purchase order is raised with USD 100, ank charges(%) which will be calculated on Base price, for example Bank charges is 1% then bank charges will be USD1.
I want these bank charges should not be added to the material cost. But when we are doing GR accounting entries as below.
Stock account 101     +
GR/IR     100     -
Pur acc     100     +
Pur Offset     101     -
Bank chargesAccount key     10 +
Accural     10     -
In the above Bank Charges are added to Stock account which is not required.
Even though I created the Bank charges Condition type as Statical still the value is adding to the stock account.
Thanks and Regards
durga

Hi Durga,
Most importantly whenever we create a condition type with statistical check box it means that value will not be included in Net price calculation this is the only purpose of statistical check box.(Like any freight charges it will go to your stock a/c even though statistical check box is there in your Pricing procedure)
When you create condition type for any charges with Cond.category B Delivery costs and Accrual check box in M/06 by default it will go to stock account, but you can restrict that by using a functionality
Check this link for complete process
http://wiki.sdn.sap.com/wiki/display/ERPLO/PostingplanneddeliverycosttoNon-inventoryaccount

Condition type restriction

Similar Messages

Maybe you are looking for