Skip to Content

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

Rsechie_string.png


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

/wp-content/uploads/2016/08/rsecval_string_1019292.png

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.

For example:

/wp-content/uploads/2016/08/auth_hash_1019293.png

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

/wp-content/uploads/2016/08/rsecvalview_1019294.png

and

RSECHIEVIEW

/wp-content/uploads/2016/08/rsechieview_1019295.png

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply