How To Fix RMPS_IMPORT021 - Row &1: Error when creating access list (&2)

SAP Error Message - Details

• Message type: E = Error

• Message class: RMPS_IMPORT - Error Messages for Fileplan Import

• Message number: 021

• Message text: Row &1: Error when creating access list (&2)

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 RMPS_IMPORT021 - Row &1: Error when creating access list (&2) ?

  The SAP error message RMPS_IMPORT021 typically occurs in the context of the SAP Project System (PS) or related modules when there is an issue with creating an access list for a specific row in a data import process. This error can arise due to various reasons, including data inconsistencies, configuration issues, or problems with the underlying database.
  Causes:
  
  Data Inconsistencies: The data being imported may have inconsistencies or invalid entries that prevent the system from creating the access list.
  Missing Authorizations: The user executing the import may not have the necessary authorizations to create or modify access lists.
  Configuration Issues: There may be configuration settings in the SAP system that are not correctly set up for the import process.
  Database Issues: There could be issues with the underlying database, such as locks or corruption, that prevent the creation of the access list.
  Incorrect Mapping: The mapping of fields during the import process may not align correctly with the expected structure in SAP.
  
  Solutions:
  
  Check Data Validity: Review the data being imported for any inconsistencies or invalid entries. Ensure that all required fields are populated correctly.
  Review Authorizations: Verify that the user has the necessary authorizations to perform the import and create access lists. You may need to consult with your SAP security team.
  Configuration Review: Check the configuration settings related to the import process and access list creation. Ensure that all necessary settings are correctly configured.
  Database Check: Investigate the database for any locks or issues. You may need to perform a database consistency check or consult with your database administrator.
  Mapping Verification: Ensure that the mapping of fields in the import file aligns with the expected structure in SAP. Correct any discrepancies in the mapping.
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. SAP Notes often provide detailed troubleshooting steps and solutions.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE38 (ABAP Editor) or SE11 (Data Dictionary) to analyze the data structures involved.
  Logs and Traces: Review application logs (transaction SLG1) and system logs (transaction SM21) for additional error messages or warnings that may provide more context about the issue.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the problem persists after trying the above solutions, it may be beneficial to escalate the issue to SAP support for further assistance.