Skip to Content
avatar image
Former Member

0MATERIAL as authorization relevant in Retail company

Hello Gurus,

I have a doubt about which infoObject is more convenient to use to set it as authorization relevant.
I'm in a retail company and we have a universe of 130k articles in 0MATERIAL catalog.

The doubt consists if exists a significant performance issue if we use this object 0MATERIAL, even if we using a hierarchy to classify our 130k articles in 220 material groups.

One important point is that the "security level" needed is only until Material groups.

The other option is to set as "authorization relevant" the 0MATERIAL__0MATL_GROUP and replicate the same hierarchy in this object but just until material groups classification but I don't know how much is the performance impact using a navigational attribute as "authorization relevant" with big data/retail company.

I'll appreciate your suggestions and comments.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jan 11, 2015 at 11:03 AM

    Hi Ricardo,

    In my opinion making 0MATERIAL__0MATL_GROUP authorization relevant should not have an impact on performance. The authorization check will check the selection(s) in the query (i.e. the WHERE clause in the SELECT statement) against the authorization. If your selection fits within the authorization, then you can continue, otherwise it will issue "no authorization".

    Maybe you setup a test case in a QA system or so. If you have here the same or representative master data, then you can measure performance prior to applying it in the Production environment.

    Best regards,

    Add comment
    10|10000 characters needed characters exceeded