Do you have any question about this error?
Message type: E = Error
Message class: FDT_TRANSPORT - Formula & Derivation Tool: Transport
Message number: 178
Message text: No BRFplus transport object found in the piece list
The after-import routine has been triggered by a transport, but no
standard BRFplus transport object entry of type R3TR TDAT FDT0000,
FDT0001 or FDT0002 could be found on the piece list.
If the current transport is a delivery transport, the after-import
processing for BRFplus objects is skipped with a warning. For all other
transport types, the after-import processing fails with an error
message.
Check the piece list for transport objects of type R3TR TDAT that
trigger the after-import routines FDT_AFTER_IMPORT or
FDT_AFTER_IMPORT_C, respectively. To accomplish this, use transaction
<DS:TRAN.SOBJ>SOBJ</>. Such transport objects typically exist for custom
expression types that represent extensions to the BRFplus framework.
If such transport objects exist, and if UUIDs of BRFplus objects are
recorded in the table key list, these objects need to be copied to a new
transport request that contains the missing BRFplus standard transport
object entries in its piece list. To accomplish this, we recommend using
report <DS:REPN.FDT_TRANS>FDT_TRANS</>.
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.
FDT_TRANSPORT178
- No BRFplus transport object found in the piece list ?The SAP error message FDT_TRANSPORT178 indicates that there is no BRFplus transport object found in the piece list during a transport request. This typically occurs when you are trying to transport BRFplus objects (Business Rule Framework plus) from one system to another, and the necessary objects are not included in the transport request.
Cause:
- Missing Objects: The BRFplus objects (like rules, functions, etc.) that you are trying to transport are not included in the transport request.
- Incorrect Transport Request: The transport request may not have been properly created or may not contain the necessary objects.
- Authorization Issues: There may be authorization issues preventing the inclusion of the BRFplus objects in the transport request.
- System Configuration: The system may not be configured correctly to recognize or include BRFplus objects in transport requests.
Solution:
Check Transport Request:
- Go to the transport request in the Transport Organizer (transaction code SE09 or SE10).
- Verify that the BRFplus objects you want to transport are included in the request. If not, you may need to add them manually.
Include Objects Manually:
- Use transaction code BRF+ to navigate to the BRFplus workbench.
- Identify the objects you want to transport and ensure they are included in the transport request.
- You can use the "Transport" option in the BRFplus workbench to add the necessary objects to the transport request.
Check Authorizations:
- Ensure that you have the necessary authorizations to create and modify transport requests and to access BRFplus objects.
Recreate Transport Request:
- If the transport request is corrupted or incorrectly configured, consider creating a new transport request and adding the BRFplus objects again.
Consult Documentation:
- Refer to SAP documentation or notes related to BRFplus transport issues for any specific guidelines or troubleshooting steps.
Check System Configuration:
- Ensure that the system is properly configured to handle BRFplus transports. This may involve checking settings in the BRFplus configuration.
Related Information:
If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FDT_TRANSPORT174
BRF+: Table &2 - Versioned Object ID delete for &1 lines executed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_TRANSPORT173
BRF+: Physical delete started for &1 versioned object IDs (table type &2)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_TRANSPORT179
An inconsistent transport piecelist was detected (Table type &1).
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_TRANSPORT180
Table '&1' on the piecelist is not registered for object type &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.