How To Fix FSSC_RDS_DIMA002 - Company code &1 only exists in ERP backend &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FSSC_RDS_DIMA - FSSC-DIMa Enhance for Cust/Vend Compare

• Message number: 002

• Message text: Company code &1 only exists in ERP backend &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 FSSC_RDS_DIMA002 - Company code &1 only exists in ERP backend &2 ?

  The SAP error message FSSC_RDS_DIMA002 indicates that a specific company code (denoted as &1) is only available in the ERP backend system (denoted as &2) and is not recognized in the current context, typically in the context of SAP S/4HANA or SAP Fiori applications.
  Cause:
  This error usually occurs due to one of the following reasons:
  
  Configuration Issues: The company code may not be properly configured in the system where the error is being encountered.
  Data Synchronization: There may be a lack of synchronization between the ERP backend and the frontend system (like SAP S/4HANA or Fiori).
  Authorization Issues: The user may not have the necessary authorizations to access the specified company code.
  System Landscape Issues: The company code exists in the backend but is not properly linked or recognized in the frontend system.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Company Code Configuration:
  
  Ensure that the company code &1 is correctly configured in the backend system &2.
  Verify that the company code is active and has all necessary settings (like fiscal year variant, currency, etc.).
  
  
  
  Data Synchronization:
  
  If you are using a system landscape with multiple systems (like an ERP backend and an S/4HANA frontend), ensure that the data is synchronized.
  You may need to run data replication jobs or check the configuration of the data transfer between systems.
  
  
  
  Authorization Check:
  
  Verify that the user encountering the error has the necessary authorizations to access the company code.
  Check the user roles and authorizations in both the backend and frontend systems.
  
  
  
  System Configuration:
  
  Check the configuration settings in the frontend system to ensure that it recognizes the backend company codes.
  If applicable, review the settings in the SAP Fiori Launchpad or any other relevant configuration areas.
  
  
  
  Consult Documentation:
  
  Refer to SAP Notes or documentation related to the specific error message for any additional troubleshooting steps or patches that may be required.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  SAP Notes: Look for specific SAP Notes related to the error message for any known issues or fixes.
  Transaction Codes: Use transaction codes like OBY6 (to check company code settings) or SICF (to check service activation) to troubleshoot further.
  System Logs: Check system logs (transaction SLG1) for any additional error messages or warnings that may provide more context.
  
  By following these steps, you should be able to identify and resolve the issue related to the error message FSSC_RDS_DIMA002.