How To Fix /FTI/WEBGUI_MSG120 - Primary subobject will not be considered for Object Types V, C, and T

SAP Error Message - Details

• Message type: E = Error

• Message class: /FTI/WEBGUI_MSG -

• Message number: 120

• Message text: Primary subobject will not be considered for Object Types V, C, and T

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 /FTI/WEBGUI_MSG120 - Primary subobject will not be considered for Object Types V, C, and T ?

  The SAP error message /FTI/WEBGUI_MSG120 indicates that there is an issue related to the primary subobject not being considered for certain object types, specifically V (Vendor), C (Customer), and T (Material). This error typically arises in the context of using the SAP Fiori or Web GUI interface when trying to perform operations that involve these object types.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Incorrect Configuration: The system may not be configured correctly to handle the primary subobject for the specified object types.
  Missing Data: The primary subobject data may be missing or not properly defined in the system.
  Authorization Issues: The user may not have the necessary authorizations to access or modify the primary subobject for the specified object types.
  Business Logic Restrictions: There may be business logic in place that restricts the use of primary subobjects for these object types.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Configuration:
  
  Review the configuration settings for the object types V, C, and T in the relevant customizing transactions (e.g., SPRO).
  Ensure that the primary subobject is correctly defined and linked to the object types.
  
  
  
  Verify Data:
  
  Check if the primary subobject data exists in the system. You can do this by navigating to the relevant transaction codes (e.g., SE11 for data dictionary) and verifying the entries.
  If data is missing, you may need to create or update the entries accordingly.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to access and modify the primary subobject. You can check this in transaction SU53 or by consulting with your security team.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific object types and the error message. There may be specific guidelines or patches available.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with the error message details and any relevant context.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SPRO (Customizing), and SU53 (Authorization Check).
  SAP Notes: Search for SAP Notes related to the error message or the specific object types in the SAP Support Portal.
  Community Forums: Check SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.