How To Fix FCOM_PLANNING_CORE068 - InfoObject &1 was not transported

FCOM_PLANNING_CORE068 - Overview

• Message type: E = Error

• Message class: FCOM_PLANNING_CORE - Messages for Package FCOM_PLANNING_CORE

• Message number: 068

• Message text: InfoObject &1 was not transported

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_CORE068 - InfoObject &1 was not transported ?

  The SAP error message FCOM_PLANNING_CORE068 indicates that a specific InfoObject (identified by &1) was not transported. This typically occurs in the context of SAP BW (Business Warehouse) or SAP Analytics Cloud environments when there are issues with the transport of objects between different systems (e.g., from development to quality assurance or production).
  
  Cause:
  
  Missing Transport Request: The InfoObject was not included in the transport request when it was created or released.
  Transport Errors: There may have been errors during the transport process that prevented the InfoObject from being successfully transported.
  Dependencies: The InfoObject may have dependencies on other objects that were not transported, leading to its exclusion.
  Manual Changes: The InfoObject might have been manually created or modified in the target system without being transported from the source system.
  
  
  Solution:
  
  
  Check Transport Request:
  
  Verify if the InfoObject is included in the transport request. You can do this by checking the transport logs or the transport request itself in