How To Fix FTI_LDB_MESSAGE029 - Error selecting by product type (Customizing error)

SAP Error Message - Details

• Message type: E = Error

• Message class: FTI_LDB_MESSAGE - Messages for TR OLTP Reporting Using Logical Databases

• Message number: 029

• Message text: Error selecting by product type (Customizing error)

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 FTI_LDB_MESSAGE029 - Error selecting by product type (Customizing error) ?

  The SAP error message FTI_LDB_MESSAGE029 typically indicates a customizing error related to the selection of product types in the context of the Financial Transaction Management (FTI) module. This error can occur when there is an issue with the configuration settings for product types in the system.
  Cause:
  
  Missing Customizing Settings: The product type may not be properly defined or configured in the system.
  Inconsistent Data: There may be inconsistencies in the data related to product types, such as missing entries in the relevant tables.
  Authorization Issues: The user may not have the necessary authorizations to access the product type data.
  Transport Issues: If the customizing settings were transported from another system, there may have been issues during the transport process.
  
  Solution:
  
  
  Check Customizing Settings:
  
  Go to the customizing transaction (SPRO) and navigate to the relevant section for Financial Transaction Management.
  Verify that the product types are correctly defined and that all necessary settings are in place.
  
  
  
  Review Data Consistency:
  
  Check the relevant tables (e.g., TFI_PRODUCT_TYPE) to ensure that all required entries exist and are consistent.
  Use transaction codes like SE11 or SE16 to view the data in these tables.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the product type data. This can be checked in transaction SU53 or by consulting with your security team.
  
  
  
  Transport Check:
  
  If the issue arose after a transport, verify that the transport was successful and that all necessary objects were included.
  You may need to re-transport the customizing settings if there were issues.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that resolve known issues.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the program or transaction that is generating the error to identify the root cause.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO (Customizing), SE11 (Data Dictionary), SE16 (Data Browser), and SU53 (Authorization Check).
  SAP Documentation: Review the official SAP documentation for Financial Transaction Management for more detailed information on product types and their configuration.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the problem continues after following these steps, it may be beneficial to reach out to SAP support for further assistance.