Hi,
We have a requirement in which we need to restrict authorization for the product hierarchy based on secret products. The material object has an attribute called secret indicator which has Y/N values. We need to restrict the users based on this attribute. The restriction should be such that the users should not even be able to see the nodes for secret materials in the product hierarchy if they are not entitled to it.
Any pointers ?
Thanks
Shailesh
Can you create two different hierarchies, one with secret nodes and one without? Then you could create an authorization object on the Secret attribute and check the authorization in a user exit.
You would then use a user-exit variable that is filled automatically (no user input) and fill it depending on the authority check with hierarchy 1 or 2.
You could also write an ABAP that filters the secret products out of the first query. It is a bit complicated.
Best regards
Dirk
H Dr,
Thanks for the post. We do use 2 hierarchies today. We have 2 sets of queries for each query and they are published to different roles. What you suggest might be easier than that. Actually i was looking for a solution which will handle this while the authorization is generated. I did read a how-to on how to load authorization data via Flat Files to load an Authorization ODS, but was unable to figure out on how to apply that to my specific case.
Thanks
Shailesh
Add a comment