on 07-12-2007 7:13 PM
We are on SRM 2.0/EBP 3.5 and I am fairly new in the SRM area.
I was able to prevent changes by requestor to SC while in approval by implementing BBP_WFL_SECUR_BADI. However this does not work once SC is approved.
In the thread , Yann Bouillut mentioned the following:
<b><i>If you do not want this behavior, you have to forbid in SRM Transaction PFCG.
In the single role for your user, uncheck the "delete" activity.</i></b>
Can someone let me know how and where exactly the above needs to be performed?
TIA,
Ramki.
Hello Ramki,
I think the solution from Yann is removing the authorization for SC Delete.
Transaction: PFCG,
Single Role: SAP_EC_BBP_EMPLOYEE,
Authorization Tab,
Authorization data: SRM: Process Shopping Carts
Activity: Delete
Regards,
Masa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For the Role SAP_EC_BBP_EMPLOYEE:
Cross-application Authorization Objects
Business Partner: BP Roles
Business Partner Relationships: Relationship Categories
IMG: New authorizations for projects
Authorization Check for RFC Access
Transaction Code Check at Transaction Start
BBP Component
Authorization for "Create Attachment Master"
Int. PO Confirmation in Enterprise Buyer
Int. Invoice Entry in Enterprise Buyer
Procurement card master data
Basis: Administration
Authorization for file access
Table Maintenance (via standard tools such as SM30)
User Master Maintenance: User Groups
Basis - Central Functions
BC-SRV-KPR-BDS: Authorizations for Document Set
SAPoffice: Authorization for an Activity with Documents
SAPoffice: Authorization to Create Shared Folders
SAPoffice: Office User Attribute
Authorization Object for Sending
SAPoffice: Transaction Code Authorizations
Workflow: Handling of Integrated Inbox View
Workflow: Work Item Handling
Human Resources
Personnel Planning
HR: Transaction codes
Resolved by implementing BBP_DOC_CHANGE_BADI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.