Authorization for conditions in PO

Hello,
I would like to limit the authrorizations that a user has to enter conditions in PO (Me21n).
Which authorization object to use?
Thank you.

Hi,
first of all please check the note note 105621 - Authorization check for the condition screen.
Note 105621 was written for SD but MM uses SD for its condition maintainance, so implementing 105621 should give you what you wish.
Regards,
Edit

Similar Messages

Authorization for condition type

I came across a requirement where the sales executive should enter less than or equal to 5% discount from his user id.only the sales manager can enter the more than 5% discount from his user id. is there any authorisation for entering pricing discount.

hi,
may be maintain two different condtion types ( DIS1 and DIS2 )one for executive and one for manager and fixt the upper and lower limits accordingly so that the executive cannot give more than 5 % disc. As well fix a lower limit for the manager as 5 % and so that he can give only more than that.
Let the executive enter value only for DIS1 and manager for DIS2. Try it.
Thanks
Sadhu Kishore

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 give authorization for create and change particular Condition Type

Hi...
In my requirement is , Only one user can be authorized to create and change a particular condition type 'ZABC' in vk11 and vk12 .
For remaining condition type can be used as in normal .
How to do this ? How to give authorization for a particular user for particular condition type ?
Plz guide me ..
Thanks in advance .
Deepa .

Hi Deepa ,
u can check A.Object V_KOND_VEA, in user profile u can assign condition type or tables.
have a word with ur basis guy , so he can help u in better way.
aand also ref FM SD_COND_AUTH_CHECK
Regards
Prabhu

Missing authorization for processing condition

Hi All,
We are having a problem with our pricing procedure zxxx.
we created a pricing procedure and connect it to a java formula.
this formula return an error message :
" Missing authorization for processing condition zxxx "
in debug we see that this message come from the formula and not some kind of authorization check.
( even a user with "sap all" get this message ).
does any one know how to solve this?
or:
does any one know how to debug the java formula ?
thanks,
Lilach.

Hi,
Check with your basis consultant whether the authorization is change ?
Regards,
Chetan.

Authorization for discount condition type

Hi Experts
1)when create a sales order client want flexibility for discount condition type
like 10% ,15% , 20% it should not be manual and end user can choose from drop down and
2) If they want to give excess discount there should be authorization any supervisor can give excess discount
how to map this authorization to condition type
Regards

hello again, friend.
go to IMG > SD > Basic Functions > Pricing > Pricing Control > Define Cond Types... here you will find the settings for the upper and lower limits. please note that the larger discount rates would be represented by the lower limit. for surcharges, the lower rate is the lower limit.
scales in pricing allows you to set different discount/surcharge rates or fixed amounts depending on either value, quantity, weight, etc. in the same pricing condition record (using VK11 or VK31). if you look inside your condition type using V/06, you will see under sub-tab Scales if this has been set.
example: condition type Z007, with Scale 'Quantity'
you can set a discount of 2% if item quantity is from 0 to 100 pieces
you can set a discount of 3% if item quantity is from 101 to 200 pieces, and so forth...
regards and thanks.

Authorization level check for Condition records.

Hi,
Hi Gurus,
Pls help me out in the the following scenario.
I want to activate Authorization level check for Condition records.
For example, Product price PR00 is being entered by first level.
After verification done by second level only, that condition record to be used for sales order processing.
I have gone through Process status & Release Status. But once it is Blocked i am not able to release it...
Rgds,
Amol

Amol,
Please confirm transaction code you are using in this scenario to release. I can help with this, just a little more detail.
Thanks,
Jay

No conditions determined (no authorization for input)

Hi Friends,
I am trying to create a PO but i am getting a error message that "No conditions determined (no authorization for input)" and I am unable to view the conditions tab.
Can anyone please guide how do I rectify the error.
Regards,
Wasim.

Hi,
When I run the t-code SU53 it says "The last authorization check was successful" But the problem still exists.
Regards,
Wasim,

What's the best way to do authorization for my app?

The authorization situation is somewhat complicated for my app.
Each component of the app is authorized based on not only the user, but also the page number, the value of at least one P0_ITEM.
From what I've seen so far, there are two different options of setting the authorization for the component:
1. Set its Condition
2. Set its Security Authorization Scheme
Here is my understanding for each (from my limited experience with APEX):
1. Set its Condition
+ Can pass in parameters such as :APP_USER, page numebr, P0_ITEM. So I can just create one function that does all the authorization
- Have to combine the SQL query with the component's non-authorization display conditions, if any.
2. Set its Security Authorization Scheme
+ By name, it seems like it should be used for authorization
- Cannot take in parameters relating to the page, such as the page number --> therefore I will need to create many different schemes, for all the different pages.
#2 will end up with a long list of schemes (each with its own SQL queries) for different pages, which doesn't seem as efficient as #1 with far fewer SQL queries and just take in parameters.
Which one should I pick?
Thanks!

953006 wrote:
Thanks fac586 for the detailed response, and also everyone else who replied. You guys are very helpful and respond promptly. And we'd appreciate it if you changed "953006" into a real handle promptly.
Andre mentioned using conditions:
The way I work around this is to have two functions, one which is used at the page level as a normal authorization scheme and one which can be passed variables which is called as a Condition and the name of the item is one of the variables, in effect giving it "self awareness".But fac586 said:
You can't pass "parameters" to authorization schemes. Use application items, APEX collections or application contexts to set current context before the authorization scheme is evaluated, and access these values in the functions.Does this mean, fac586, that we can avoid conditions altogether? No, it means that I prefer to use Authorization Schemes to control access to resources based on user privileges and security, and Conditions to control rendering and processing for functional reasons. Using the approach described above I have found it possible to maintain this separation.
Say if a page has two buttons, Button_A and Button_B. Button_A has a set of requirements for displaying and Button_B has its own set of requirements (some of which are shared with Button_A). So far, the only way that I can see of using pure authorization is to write 2 different authorization schemes, and set the authorization schemes for the two buttons respectively.What's the problem with that? Consider a more concrete example using a standard APEX report/form pattern for customer maintenance. Page 6 contains the report, and page 7 is the maintenance form with P7_CREATE and P7_SAVE buttons. Only users entitled to create new customers should have access to P7_CREATE, and only users able to edit customers access to P7_SAVE. This would be controlled by the CREATE_CUSTOMER and EDIT_CUSTOMER authorization schemes respectively. Functionally, conditions are used to show P7_CREATE if the P7_CUSTOMER_ID is null, and P7_SAVE if it's not null. We don't mix non-functional security considerations with functional requirements.
The CREATE_CUSTOMER and EDIT_CUSTOMER authorization schemes are of type PL/SQL Function Returning Boolean. These are implemented using package functions. Exactly how a user has create/edit customer privilege is determined in the package. Determinants that are shared by multiple schemes can be combined at this level. These implementations can be changed as necessary without requiring changes to the application.
The authorization schemes are reusable across pages and components. On page 6, CREATE_CUSTOMER can be used on the "Create New Customer..." button; EDIT_CUSTOMER on the report column containing the "Edit" links.
Each component of the app is authorized based on not only the user, but also the page number, the value of at least one P0_ITEM. So I guess this goes back to my original concern with Authorizations:
[Using purely authorizations] will end up with a long list of schemes (each with its own SQL queries) for different pages [and page items] ....
Re: VPD policies. Note that in the example above there's no need for the authorization schemes to "know" which pages/items are being evaluated. The P7_SAVE button and the page 6 link column are involved with the EDIT_CUSTOMER operation, so that authorization scheme is applied to them.

How to validate rate for condition types

Dear All
While pricing the material in sales order, some times by mistake user creates wrong condition records for excise & TAXES
exampl- when creating condition records for excise by mistake user creates records like 14% rate which should be 8%
is their any way that i can customize for condition records that it should not take excise duty more than 8%
and same thing for , VAT 4 % & CST2%
please let me know is their any way out
Thanks&Regards
JAHANGIR

Hi Jahangir
I agree 100% with Lakshmipati. Actually this rates are to be changed only once a year when the budget is declared. Beyond that there is no need to touch this condition types. So the best thing to do is to give authorization to right person. Then once it is maintained check the same by going into VA01. Then release the system to users for order entry. Writing routines and exits for every single field will become pain to maintain in future and there will be no track whats happening when.
Regards
Yatin Thakkar

Authorization for MM

Our business scenario demands that a particular user should be able to access the T.code"Me23n(Display P.O)" but shouldn't be able to view condition tab in the "item detail",how to set up the authorization for this, please mention the detailed steps.

Hi Shashi,
I would recommend you to look under M_BEST_BSA authorization object in the role.If you are not able to restrict the user from viewing the Conditions tab with this approach then it is something to do with MM Configuration.
Hope this helps.
Regards,
Kiran.

Display only for Conditions tab in ME22N

I have a situation where certain users need to modify PO's, but need to be restricted from modifying anything in the conditions tab. Is there a way through authorization's to restrict modification to the conditions tab within ME22N without restricting functionality to anything else in ME22N?
The same result is required for ME12, but ME12 contains condition authorization objects that can be set to Activity 03 resulting in a display of conditions.
I have tried adding these authorizations to the authorization-check, with no functionality change.
I have also tried removing the display prices (activity 09) from certain authorization objects and this hides the conditions tab, but it also hides prices.
Modifying screen settings in SPRO for ME22N will not work as there are users that require modification of the conditions.
I am trying to find a solution that doesn't involve creating a custom transaction to check for condition authorization objects.

David,
Check BADI definition (se18) ME_PURCHDOC_POSTED & Interface IF_EX_ME_PURCHDOC_POSTED. In that you have method posted. In that you have both the tables Old & the current. You can put a validation there & prevent users.
Hope this helps.
Bipin

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

Authorization for Intercompany Sales

Hi,
I have an intercompany situation, company A and company B. UserA can perform sales transaction for company A only. Now with intercompany sales, i want UserA to view sales order for company B but cannot see the pricing condition for company B.
May I know how to perform authorization for this?
UserA have authorization for sales org A. How to restrict pricing condition to sales org A only, but still can view sales order for sales org B?
regards,
zl

Hi,
VA03.
UserA can VA03 for all Sales Order for Sales Org A. For Sales OrgB, UserA can view using VA03 but the pricing condition tab should not be accessible.
How to do this?
Thank you.
regards,
zl

Process Status & Release Status for Condition Record

Hi Gurus,
Pls help me out in the the following scenario.
I want to activate Authorization level check for Condition records.
For example, Product price PR00 is being entered by first level.
After verification done by second level only, that condition record to be used for sales order processing.
I have gone through Process status & Release Status. But not getting full clarity on this.
Rgds,
Senni.B

Hi,
Please go through the following information.
[Relase Procedure for Condition Record|http://help.sap.com/saphelp_47x200/helpdata/en/a4/af9e78e69611d2ace10000e8a5bd28/frameset.htm]
[Release Procedure for PR|http://www.sap123.com/showthread.php?t=59]
Reward if helpful.
Thanks and Regards,
Naveen Dasari

Authorization for conditions in PO

Similar Messages

Maybe you are looking for