How To Fix RSEC668 - Creating A and M versions for new authorizations...

SAP Error Message - Details

• Message type: E = Error

• Message class: RSEC -

• Message number: 668

• Message text: Creating A and M versions for new authorizations...

What causes this issue?

New analysis authorizations are first generated from the old
authorizations from the reporting authorizations concept (from BW 3.0,
BW 3.1 and BW 3.5 releases); these analysis authorizations do not yet
have versions (the version and runtime status fields are empty).
In the next step, these analysis authorizations, which have no function,
are used to generate real active versions (including an additional
identical M version).
This second step is basically a migration of analysis authorizations
from SAP NetWeaver 2004s that also did not have versions.
Note that in this second step, all analysis authorizations in the system
are created as M and A versions.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSEC668 - Creating A and M versions for new authorizations... ?

  The SAP error message RSEC668 typically occurs when there is an issue with creating A (actual) and M (maintenance) versions for new authorizations in the context of SAP's authorization management. This error can arise due to various reasons, including configuration issues, missing authorizations, or problems with the underlying data.
  Causes:
  
  Missing Authorizations: The user attempting to create the A and M versions may not have the necessary authorizations to perform this action.
  Configuration Issues: There may be issues with the configuration of the authorization objects or the roles involved.
  Data Inconsistencies: Inconsistencies in the underlying data, such as missing or incorrect entries in the authorization tables, can lead to this error.
  Transport Issues: If the authorization objects or roles are being transported from one system to another, there may be issues with the transport itself.
  System Bugs: Occasionally, bugs in the SAP system can lead to unexpected behavior, including this error.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to create A and M versions. This may involve checking the user's roles and profiles.
  Review Configuration: Verify the configuration of the authorization objects and roles. Ensure that they are set up correctly and that there are no missing entries.
  Data Consistency Check: Run consistency checks on the authorization data. You can use transaction codes like SU53 (to analyze authorization failures) or SUIM (to check user information).
  Transport Management: If the issue is related to transport, ensure that all necessary objects have been transported correctly and that there are no missing dependencies.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve the issue.
  System Logs: Review system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SU01 (User Maintenance), PFCG (Role Maintenance), and SUIM (User Information System) for managing authorizations.
  SAP Documentation: Refer to SAP's official documentation for detailed information on authorization management and troubleshooting.
  Community Forums: Engage with SAP community forums or support channels where similar issues may have been discussed, and solutions shared.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis or Security team for further investigation.