How To Fix RSEC660 - New entries added

SAP Error Message - Details

• Message type: E = Error

• Message class: RSEC -

• Message number: 660

• Message text: New entries added

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSEC660 - New entries added ?

  The SAP error message RSEC660 typically indicates that new entries have been added to a table or a data source that is relevant to the security or authorization checks in SAP. This message is often related to the SAP Business Warehouse (BW) or the SAP BusinessObjects environment, where security settings and authorizations are crucial for data access.
  Cause:
  
  New Entries in Authorization Objects: The error may occur when new authorization objects or entries are added to the system, and the existing roles or authorizations do not reflect these changes.
  Data Source Changes: If there are changes in the data source, such as new fields or new data being added, the existing security settings may not cover these new entries.
  Transport Requests: If new entries were transported from another system, the security settings may not have been updated accordingly.
  
  Solution:
  
  
  Update Authorizations: Review and update the relevant authorization roles to include the new entries. This may involve:
  
  Modifying existing roles to include new authorization objects.
  Creating new roles if necessary.
  Assigning the updated roles to the relevant users.
  
  
  
  Recheck Security Settings: Ensure that the security settings for the data source or the relevant objects are correctly configured to include the new entries.
  
  
  Use Transaction RSECADMIN: You can use transaction RSECADMIN to manage and maintain authorizations in BW. This transaction allows you to analyze and adjust the authorizations as needed.
  
  
  Transport Changes: If the changes were made through a transport request, ensure that the transport was successful and that all necessary objects were included.
  
  
  Testing: After making changes, conduct thorough testing to ensure that users can access the data as intended without encountering the error.
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to RSEC660 for any specific patches or updates that may address this issue.
  Documentation: Review SAP documentation on authorization management and security settings in BW or the relevant module you are working with.
  Community Forums: Engage with SAP community forums or support channels for additional insights or similar cases.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or Security team for further investigation.