on 10-10-2008 10:34 PM
Hi all,
My requirement is to restrict PR Release department wise. For eg: If a person within the sales department creates a PR, then the Sales Dept. Head can only release requisitions created in his department.
Whats the standard way of implementing such an authorization?
I initially thought of creating a seperate Purchasing Group for Sales department, and thus perform authorization check on Purchasing Group Level for the tcode. But i need some clarification on what is the purpose of Purchasing Group? Is the purchasing group the people directly reponsible for negotiating with vendors? If this is the case am I right in saying that if a Purchasing Department has 4 people, then I would need 4 Purchasing Groups to differentiate the POs made by each other for reporting purposes. Or is Purchasing Group the departments within the organization?
Edited by: Godwin Coelho on Oct 10, 2008 11:34 PM
hi,
Purchasing group is a person or group of person resonsible for negotiating. its not neccessarily a department.
you can make authorisation purchase group wise.
Regards,
Vijay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The reason why i do not want to use Purchasing Group is because I need to use the Purchasing Group to determine via the standard reports to see who created which POs etc... The reason I do not want to use Purchasing Group for authorization level, then people making PRs will have to enter purchasing group as mandatory field, and when this PR gets converted to a PO, even this Purchasing Group will get copied to the PO. This way I cant differentiate between POs made by individual people in the purchasing dept.
Hope you are clear on this matter.
Hai,
You can map this by
1.Creating separate PR doc type for Sales department or by Requirement tracking number - SALES as a Characteristics.
2.Assign this to release strategy defined for SALES HEAD as a Release code.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
PS: I'm not sure if this is the right section to ask this question maybe in the basis section. But I have to provide this information to my basis guy. And I'm new to sap. Thanks once again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
6 | |
5 | |
5 | |
5 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.