How To Fix FPS_CUSTDDIC_MSGS020 - Failed to get Columns List

SAP Error Message - Details

• Message type: E = Error

• Message class: FPS_CUSTDDIC_MSGS - FP: Messages

• Message number: 020

• Message text: Failed to get Columns List

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 FPS_CUSTDDIC_MSGS020 - Failed to get Columns List ?

  The SAP error message FPS_CUSTDDIC_MSGS020: Failed to get Columns List typically occurs in the context of data extraction or data modeling, particularly when working with SAP BW (Business Warehouse) or SAP HANA. This error indicates that the system is unable to retrieve the list of columns for a particular data source or table, which can be due to various reasons.
  Causes:
  
  Missing Authorization: The user may not have the necessary authorizations to access the data source or the underlying database tables.
  Database Connection Issues: There may be issues with the connection to the database, such as network problems or incorrect connection parameters.
  Data Source Configuration: The data source may not be properly configured or may have been deleted or modified.
  Technical Issues: There could be technical issues with the SAP system, such as inconsistencies in the data dictionary or problems with the underlying database.
  Transport Issues: If the data source was recently transported from another system, there may be inconsistencies or missing objects.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to access the data source. This can be done by checking the roles and authorizations assigned to the user.
  Verify Database Connection: Check the database connection settings in the SAP system. Ensure that the connection is active and that the parameters (like host, port, username, and password) are correct.
  Review Data Source Configuration: Go to the data source configuration in the SAP BW or HANA modeler and verify that it is set up correctly. Check if the data source is active and properly defined.
  Check for Technical Issues: Use transaction codes like SE11 (Data Dictionary) or SE80 (Object Navigator) to check for any inconsistencies in the data dictionary. You may also want to run a consistency check.
  Transport Check: If the issue arose after a transport, check the transport logs for any errors or warnings. Ensure that all necessary objects were transported correctly.
  System Logs: Check the system logs (transaction SM21) for any related error messages that could provide more context about the issue.
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Documentation: Review the official SAP documentation for the specific version of SAP BW or HANA you are using, as there may be version-specific considerations.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.