How To Fix FDT_CORE234 - Transport object '&1' for type &2 does not exist

FDT_CORE234 - Overview

• Message type: E = Error

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

• Message number: 234

• Message text: Transport object '&1' for type &2 does not exist

What causes this issue?

You need to create transport objects for each of the table types
supported in the BRFplus (see constants GC_TABLE_TYPE in
IF_FDT_EXPRESSION_TYPE). Transport objects are created with transaction
SOBJ. You can use the BRFplus transport objects FDT0000 (C), FDT0001 (S)
and FDT0002 (T) as a reference.
The transport objects for BRFplus expression types need to be of type T
("Individual Transaction Object").

System Response

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

How to fix this error?

Specify correct transport objects for your expression type.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FDT_CORE234 - Transport object '&1' for type &2 does not exist ?

  The SAP error message FDT_CORE234 indicates that a transport object specified in the system does not exist. This error typically occurs in the context of SAP Fiori or SAP UI5 applications when there is an attempt to transport a specific object (like a configuration, UI element, or other development objects) that the system cannot find.
  
  Cause:
  
  Missing Transport Request: The transport request that is supposed to contain the object has not been created or is missing.
  Incorrect Object Name: The object name or type specified in the transport request may be incorrect or misspelled.
  Object Deletion: The object may have been deleted or not properly saved in the system.
  Transport Directory Issues: There may be issues with the transport directory or the transport management system.
  Development System Issues: If you are working in a development environment, the object may not have been properly released for transport.
  
  
  Solution:
  
  Check Transport Request: Verify that the transport request containing the object