SAP OSS Note 61726 version 0012 contains details of a know issue related to RSSM: No profile assignment if Central User Administration
. This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.
...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.
In a Business Warehouse (BW) system, you use transaction RSSM or the
report RSSB_GENERATE_AUTHORIZATIONS to automatically create autho
rization profiles from ODS (Operational Data Store) objects and assign
these profiles to users ( Note: These are manual profiles that
are maintained using transaction SU02). User assignment fails if the BW
system is part of a Central User Administration. In this case,
the profile is created without user assignment.
If the BW system is not integrated in a Central User Administration,
this error does not occur.
If you use the new analysis authorizations that are available as of BW
Release 7.00, this note is not relevant for you.
Up to the correction contained in Note 841612, the profile assignment
was always executed, independent of whether the BW system is par
t of a Central User Administration (CUA) or not. If it was, an
inconsistency occurred that had to be corrected by retransferring the p
rofile assignments in transaction SCUG.
After you implement the corrections mentioned above, the system uses the
regular interface BAPI_USER_PROFILES_ASSIGN for the profile a
ssignment. However, if the BW system is part of a Central User
Administration, this module does nor work and no profile assignment is
Use transaction SNOTE to implement the correction instructions or import
the relevant Support Package.
The corrections contained in this note restore the previous system
The system executes the profile assignment only locally in the BW
system, but does not automatically transfer it to the central system
. You must then carry out the transfer manually using transaction SCUG.
To be able to implement an automatic transfer, a correction in the user
management area is not sufficient. An additional extensive adj
ustment of the BW function would be required.
We have decided not to make this extensive adjustment for the following
1. This would result in a dependency between corrections of different
software components. After implementing the change using the Sup
port Package for SAP_BASIS, you would have to import the relevant
Support Package for SAP_BW to avoid runtime errors.
We cannot inform all BW customers about the dependency in time before
they import Support Packages.
2. The analysis authorizations that were introduced with BW Release 7.00
are independent of the classic user management and the classi
c authorization management, that is, they are also independent of the
CUA. We consider the use of the new concept to be binding (see N
ote 1125108) so that the problem described in this note will become less