RSEC*-Tables and IO AUTH_HASH
Old or Pre BW 7.4 Database-Tables for Hierarchy Entries within Authorizations
RSECHIE Status of Authorization Hierarchies
RSECHIE_CL Authorization Hierarchies Changes Change Log
Database-Table after Upgrade to BW 7.4:
All newly created Hierarchy Authorizations will be saved within this new table.
RSECHIE_STRING Status of Authorization Hierarchies
Old or Pre BW 7.4 Database-Tables for Value Entries within Authorizations
RSECVAL Authorization Value Status
RSECVAL_CL Authorization Value Change (Change Log)
New Database-Table after Upgrade to BW 7.4:
All newly created Value Authorizations will be saved within this new table.
RSECVAL_STRING Authorization Value Status
As seen from the screenshots there is a new Infoobject within both tables called: AUTH_HASH.
With BW 7.4 a hash value is created for every entry within an authorization. Depending if its a hierarchy node authorization or a value authorization the hash value is saved to the respective table. For every entry combination there is one hash value. Not to mistake with the entire authorization. An authorization contains different hash values but there is one hash value for one compination.
This hash value can be used for comparing entries within authorizations and furthermore for cleaning purposes within the authorization-concept.
The Infoobject is also used for Database-Tables:
RSECVALVIEW Join of USERAUTH, RSECVAL and RSECBIAU: All ACT & A-Versions