Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Authorization restriction on WBS in MIGO

Former Member
0 Kudos

Hi All,

We wanted to check authorizations on WBS element in MIGO using available BADi spot. We have developed a custom auth object to check authority on field data element MAT_PSPNR. The problem is this fields conversion routine because of which we are not able to put authorization on this object (PFCG doesnt allow to use field that have masking/conversion routine).

Could anyone help in how we can put restriction on WBS element in MIGO ? or have better ideas ?

I had a look into this thread but it doesnt give complete solution details on how restriction has taken place for WBS element in MIGO.

Regards,

1 ACCEPTED SOLUTION

martin_voros
Active Contributor
0 Kudos

Hi,

have you looked at other fields that are usually maintained on WBS element? The fields like profit or cost center. So instead of doing check against WBS element you would do it against corresponding cost center. Your requirement is quite unusual because usually you have many projects and it would be impossible to update role whenever there is a new project. It;s like doing authorization check against PO number.

If you still need to do it on WBS level then you can maintain value on WBS element and perform check against this field. Basically, something like authorization groups.

Cheers

1 REPLY 1

martin_voros
Active Contributor
0 Kudos

Hi,

have you looked at other fields that are usually maintained on WBS element? The fields like profit or cost center. So instead of doing check against WBS element you would do it against corresponding cost center. Your requirement is quite unusual because usually you have many projects and it would be impossible to update role whenever there is a new project. It;s like doing authorization check against PO number.

If you still need to do it on WBS level then you can maintain value on WBS element and perform check against this field. Basically, something like authorization groups.

Cheers