How To Fix /MOC/CONFIG120 - &3; Launchpad Customizing not updated; role &1 or instance &2 missing

SAP Error Message - Details

• Message type: E = Error

• Message class: /MOC/CONFIG -

• Message number: 120

• Message text: &3; Launchpad Customizing not updated; role &1 or instance &2 missing

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 /MOC/CONFIG120 - &3; Launchpad Customizing not updated; role &1 or instance &2 missing ?

  The SAP error message /MOC/CONFIG120 &3; Launchpad Customizing not updated; role &1 or instance &2 missing typically indicates that there is an issue with the configuration of the SAP Fiori Launchpad or the roles and instances associated with it. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  
  Missing Role or Instance: The error suggests that either the specified role (&1) or the instance (&2) is not found in the system. This could happen if:
  
  The role has not been created or assigned properly.
  The instance is not defined in the system.
  There are inconsistencies in the configuration.
  
  
  
  Authorization Issues: The user may not have the necessary authorizations to access the specified role or instance.
  
  
  Transport Issues: If the configuration was transported from another system, there may have been issues during the transport process that led to missing roles or instances.
  
  
  Solution:
  
  
  Check Role Assignment:
  
  Go to the SAP GUI and check if the role specified in the error message exists in the system.
  Use transaction PFCG to verify the role and ensure it is correctly assigned to the user.
  
  
  
  Verify Instance Configuration:
  
  Check the instance configuration in the Launchpad settings. Ensure that the instance specified in the error message is correctly defined and active.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to access the role and instance. You can use transaction SU53 to analyze authorization issues after the error occurs.
  
  
  
  Transport Check:
  
  If the configuration was transported, check the transport logs for any errors or warnings that might indicate issues with the role or instance.
  
  
  
  Reconfigure Launchpad:
  
  If necessary, reconfigure the Launchpad settings to ensure that all required roles and instances are properly set up.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific version of SAP you are using for any known issues or additional troubleshooting steps.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific notes related to the error message /MOC/CONFIG120. SAP frequently updates their knowledge base with solutions to common issues.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Fiori Launchpad Configuration: Familiarize yourself with the Fiori Launchpad configuration guide, which provides detailed steps on setting up roles and instances.
  
  By following these steps, you should be able to identify and resolve the issue causing the error message. If the problem persists, consider reaching out to SAP support for further assistance.