How To Fix RSEC130 - Date authorization must only contain one asterisk (=all)

SAP Error Message - Details

• Message type: E = Error

• Message class: RSEC -

• Message number: 130

• Message text: Date authorization must only contain one asterisk (=all)

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

What causes this issue?

You have used more than one asterisk as a wildcard. The system assumes
that you want to set the validity to <ZK>Always Valid</>, meaning you
want to put a "*" (asterisk) in the placeholder.

System Response

How to fix this error?

If you want to use more complicated patterns, use "+" (plus) as the
wildcard for exactly one character. For two-digit dates, use two plus
characters.
You can find more information about using patterns in <ZH>SAP Note
1053989</>.

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 RSEC130 - Date authorization must only contain one asterisk (=all) ?

  The SAP error message RSEC130 indicates that there is an issue with the date authorization settings in your SAP system. Specifically, it means that the date authorization field is incorrectly configured to contain more than one asterisk (*), which is not allowed. In SAP, the asterisk is used as a wildcard character, and having more than one asterisk in the date authorization field can lead to ambiguity in the authorization checks.
  Cause:
  The error typically arises when:
  
  A user or role is assigned a date authorization that includes multiple asterisks.
  The configuration of the authorization object related to date fields is incorrect.
  
  Solution:
  To resolve the RSEC130 error, you should follow these steps:
  
  
  Check Authorization Objects:
  
  Go to transaction code SU21 to view the authorization objects.
  Identify the authorization object related to date fields (e.g., S_USER_AUTH or similar).
  
  
  
  Review User Roles:
  
  Use transaction code PFCG to check the roles assigned to the user experiencing the error.
  Look for any date authorization settings in the role that may contain multiple asterisks.
  
  
  
  Modify Date Authorizations:
  
  If you find that the date authorization contains multiple asterisks, modify it to ensure that it only contains one asterisk or a specific date range.
  For example, if the date authorization is set to *, change it to a specific date or a single * if you want to allow all dates.
  
  
  
  Test Changes:
  
  After making the necessary changes, test the authorization by logging in as the affected user and performing the action that previously triggered the error.
  
  
  
  Transport Changes:
  
  If you are working in a development environment, ensure that you transport the changes to the production environment after testing.
  
  
  
  Related Information:
  
  Authorization Concept: Understanding how SAP handles authorizations is crucial. Authorizations are defined using authorization objects, which consist of fields that determine access rights.
  Wildcards in Authorizations: In SAP, the asterisk (*) is used as a wildcard to represent all possible values. However, its use must be carefully managed to avoid conflicts and errors.
  Documentation: Refer to SAP Help documentation for more details on authorization objects and best practices for configuring them.
  
  By following these steps, you should be able to resolve the RSEC130 error and ensure that your date authorizations are correctly configured.