Question:
Hi,
Our client have a requirement to restrict the standerd price field change/ display authorization in material master change transaction for a perticular ID.
Material master- accounting data view- standerd price field doesn't have a authorisation object. so we have created a new object for the same in Tcode SU21. We assigned this object to Tcode MM02. Then we created one role and assined the Tcode MM02 to this role. And again we assigned this role to a newly created user ID.
When we execute the Tcode MM02 system doesn't check the object which we have created. Is it possible to force the system to check this object while executing the Tcode MM02 ?
Clould anybody suggest me that how can we unable this functionality.
Welcome for your valuable and prompt reply.
Manish Jindal
_________________
Cheers
Answer:
The check must be in the code the assignment to SU24 does nothing but bring the object into PFCG when you maintian a role and add the tcode to the menu. If you did not all code to perform the check you accomplish nothing.
Material master change does not contorl on field, if you can change you change all.
Answer:
Thank You very much Mr. John for your prompt reply. Could you please tell me, can we force the system to check this perticular object. If it requires to include in code, then how to do it.
Thanks
Manish Jindal
_________________
Cheers
Answer:
1. Determine the risk ( loss to the company), it potential for occurance and match it to the cost to contorl.
2. Ascertain if this is a training problem versus a real security breach.
I would say the risk is low,( there are change documents recorded on all changes so you know who and when it was done), the potential is low and the loss probably low compared to the "re-write" of the SAP screen handeling.
3. If the customer still insists, use tcode SHD0 to create a tcode that locks the field into display and give the user that tcode and not MM02 and not persue changinf SAP code.
4. If you must use MM02, you will have to look for a user exit in SMOD or BF03 ( though there may not be one at the point you want to check the field and "protect" it. If non available you will have to find a skilled ABAPer to change SAP code, NOT RECOMMENDED.