How To Fix FCOM_PLANNING_CORE058 - All saved InfoObjects activated

SAP Error Message - Details

• Message type: E = Error

• Message class: FCOM_PLANNING_CORE - Messages for Package FCOM_PLANNING_CORE

• Message number: 058

• Message text: All saved InfoObjects activated

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 FCOM_PLANNING_CORE058 - All saved InfoObjects activated ?

  The SAP error message FCOM_PLANNING_CORE058 typically indicates that there is an issue related to the activation of InfoObjects in the context of SAP BW (Business Warehouse) or SAP Analytics Cloud (SAC) planning scenarios. This error suggests that all saved InfoObjects have already been activated, and there may be a problem with the planning model or the data flow.
  Cause:
  
  InfoObject Activation: The error usually arises when the system detects that the InfoObjects you are trying to use in your planning model are already activated. This can happen if there are changes made to the InfoObjects that have not been properly reflected in the planning model.
  Data Model Issues: There may be inconsistencies in the data model or planning model that prevent the system from recognizing the current state of the InfoObjects.
  Transport Issues: If the InfoObjects were transported from one system to another (e.g., from development to production), there might be discrepancies in the activation status.
  
  Solution:
  
  Check Activation Status: Verify the activation status of the InfoObjects in the InfoObject catalog. Ensure that they are indeed activated and that there are no pending changes.
  Re-activate InfoObjects: If you suspect that the activation status is incorrect, try reactivating the InfoObjects. You can do this by navigating to the InfoObject maintenance transaction (e.g., RSA1) and reactivating the InfoObjects.
  Check Planning Model: Review the planning model to ensure that it is correctly configured and that all necessary InfoObjects are included. If there are any discrepancies, adjust the model accordingly.
  Clear Cache: Sometimes, clearing the cache can resolve issues related to activation. You can do this by using transaction code RSADMIN and clearing the relevant cache.
  Transport Check: If the issue arose after a transport, check the transport logs for any errors or warnings related to the InfoObjects. Ensure that all necessary objects were transported correctly.
  Consult Documentation: Refer to SAP documentation or notes related to this specific error message for any additional troubleshooting steps or patches that may be required.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or fixes related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  System Logs: Review system logs for any additional error messages or warnings that may provide more context about the issue.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.