How To Fix FDT_CORE818 - &1 &2 is explicitly not allowed in the current object context

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_CORE - Formula & Derivation Tool: Core

• Message number: 818

• Message text: &1 &2 is explicitly not allowed in the current object context

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 FDT_CORE818 - &1 &2 is explicitly not allowed in the current object context ?

  The SAP error message FDT_CORE818 typically indicates that a certain action or operation is not permitted in the current context of the object you are working with. This error is often related to the use of Field Data Tool (FDT) or similar functionalities within SAP, where certain fields or operations are restricted based on the context of the object.
  
  Cause:
  
  Context Restrictions: The error usually arises when you are trying to use a field or perform an operation that is not allowed in the current context of the object. For example, you might be trying to access a field that is not relevant for the specific transaction or object type you are working with.
  
  Configuration Issues: There may be configuration settings in the FDT or the underlying data model that restrict the use of certain fields or operations.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to perform the action on