ESH_AU_AUTHORIZATION - ESH: Checking for authorizations
The following messages are stored in message class ESH_AU_AUTHORIZATION: ESH: Checking for authorizations.
It is part of development package S_ESH_ENG_AUTHORIZATION in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Authorization".
It is part of development package S_ESH_ENG_AUTHORIZATION in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Authorization".
Message Nr ▲ | Message Text |
---|---|
000 | |
001 | Authorization object &1 successfully read from local system |
002 | Authorization object &1 successfully read from RFC destination &2 |
003 | Authorization object &1 not found in local system |
004 | Authorization object &1 not found via RFC destination &2 |
005 | No authorization object name provided |
006 | No RFC destination found for logical system &1 |
007 | Profile parameter auth/new_buffering is not set for immediate update |
008 | Client &1 could not be registered for user update for ESH |
009 | Registration of modified user data was unsuccessful in current client &1 |
010 | User does not have authorization. Trace on the Auth.Check (TA ST01) |
011 | Error while calling method for invalidation of runtime buffer |
012 | Enterprise Search runs in hub mode. No user info will be passed to BW |
013 | Method &1 of class &2 does not exist or is not implemented |
014 | Software component &1 has no templates defined in Enterprise Search |
015 | No connectors available for soft. comp. &1. No user info passed to BW |
016 | User has authorization to work with the selected activity |
017 | Reference roles do not exist. Authorization check cannot be performed |
020 | Error while user invalidation in ESH share memory for client &1 |
021 | Wrong parameter combination while calling the program &1 |
022 | User invalidation completed successfully in ESH share memory client &1 |
023 | Method &1 of class &2 was successfully executed in all clients |
024 | Method &1 of class &2 was successfully executed in the current client |
025 | Method &1 of class &2 was successfully executed for the changed users |
026 | User invalidation successful in ESH share memory for changed users |