How To Fix FDT_CORE133 - &1 is not a data dictionary (DDIC) table type

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 133

• Message text: &1 is not a data dictionary (DDIC) table type

What causes this issue?

You have tried to bind the dictionary table &v1& to the current BRFplus
table data object. However, table &v1& is not categorized as a table
type in the dictionary.
Dictionary tables can be assigned to different categories, like cluster
table, transparent table, or table type. Only table types can be used
for data binding in BRFplus.

System Response

Dictionary table &v1& cannot be used for data binding.

How to fix this error?

To solve the issue, proceed as follows:
In the backend system, start transaction SE11.
In the <LS>Database Table</> field, enter <ZH>&v1&</>.
Choose <LS>Utilities -> Where-Used List</>.
In the search criteria dialog, choose <LS>Table Types</> and start the
search for referencing objects.
Depending on the search result, proceed as follows:
If referencing table types already exist, use one of them for the data
binding in BRFplus.
If there are no referencing table types for &v1&, create a new table
type with reference to &v1&.
Set up the data binding for the current BRFplus table by entering one of
the referencing table types that you have found or created in the
previous step.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FDT_CORE133 - &1 is not a data dictionary (DDIC) table type ?

  The SAP error message FDT_CORE133 indicates that the specified object (in this case, &1) is not recognized as a Data Dictionary (DDIC) table type. This error typically arises in the context of using the SAP Form Data Tool (FDT) or when working with data models that expect a DDIC table but receive an incompatible object type instead.
  
  Cause:
  
  Incorrect Object Type: The object you are trying to use is not a DDIC table. It could be a structure, view, or some other object type that is not compatible with the expected input.
  Typographical Error: There might be a typo in the name of the table or object you are referencing.
  Missing Table: The table may not exist in the system or may have been deleted or renamed.
  Authorization Issues: Lack of proper authorizations to access the DDIC table can also lead to this error.
  
  
  Solution:
  
  Verify Object Type: Check the object you are trying to use. Ensure