How To Fix FMCA_TTF_DESIGNTIME035 - No DDIC information found for scenario &1, table group &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FMCA_TTF_DESIGNTIME -

• Message number: 035

• Message text: No DDIC information found for scenario &1, table group &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 FMCA_TTF_DESIGNTIME035 - No DDIC information found for scenario &1, table group &2 ?

  The SAP error message FMCA_TTF_DESIGNTIME035 indicates that there is no Data Dictionary (DDIC) information found for a specific scenario and table group. This error typically arises in the context of SAP's Flexible Real Estate Management (RE-FX) or similar modules where table groups and scenarios are used to manage data.
  Cause:
  
  
  Missing DDIC Entries: The most common cause of this error is that the required Data Dictionary entries for the specified scenario and table group do not exist in the system. This could happen if the configuration was not completed properly or if the necessary transport requests were not imported.
  
  
  Incorrect Configuration: The scenario or table group may not be correctly configured in the system, leading to a mismatch between the expected and actual entries.
  
  
  Transport Issues: If the relevant objects were transported from a development system to a production system, there may have been issues during the transport process, resulting in missing or incomplete data.
  
  
  Version Mismatch: If there are version differences between the systems (e.g., development, quality assurance, production), it may lead to inconsistencies in the DDIC information.
  
  
  Solution:
  
  
  Check DDIC Entries: Verify that the necessary Data Dictionary entries for the specified scenario and table group exist. You can do this by using transaction codes like SE11 (Data Dictionary) to check the relevant tables and structures.
  
  
  Configuration Review: Review the configuration settings for the scenario and table group in the relevant customizing transactions (e.g., SPRO). Ensure that all necessary settings are in place.
  
  
  Transport Validation: If the issue arose after a transport, check the transport logs to ensure that all objects were transported successfully. If any objects are missing, you may need to re-transport them.
  
  
  Recreate Missing Entries: If you identify that certain DDIC entries are missing, you may need to recreate them manually or adjust the configuration to ensure they are generated correctly.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific module you are working with. There may be specific instructions or known issues that can help resolve the error.
  
  
  SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance. They can provide guidance based on the specific details of your system and configuration.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE80 (Object Navigator), and SPRO (Customizing).
  SAP Notes: Search for SAP Notes related to the error message or the specific module you are working with. SAP Notes often contain fixes or workarounds for known issues.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed. Other users may have encountered the same error and can share their solutions.
  
  By following these steps, you should be able to diagnose and resolve the error message FMCA_TTF_DESIGNTIME035 effectively.