How To Fix FDT_EXCEL_API013 - Invalid boolean string &1; boolean value expected (like 'true'/'false')

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_EXCEL_API - Messages related to SFDT_EXCEL_API Package

• Message number: 013

• Message text: Invalid boolean string &1; boolean value expected (like 'true'/'false')

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_EXCEL_API013 - Invalid boolean string &1; boolean value expected (like 'true'/'false') ?

  The SAP error message FDT_EXCEL_API013 indicates that there is an issue with a boolean value being processed in an Excel file. Specifically, the error message states that an invalid boolean string was encountered, and it expected a valid boolean value such as 'true' or 'false'.
  Cause:
  This error typically occurs when:
  
  The Excel file being processed contains a cell that is expected to have a boolean value, but the content of that cell does not match the expected format.
  The value in the cell might be a string that does not conform to the expected boolean values (e.g., "yes", "no", "1", "0", or any other non-standard representation).
  There may be leading or trailing spaces in the cell that prevent it from being recognized as a valid boolean.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Excel File:
  
  Open the Excel file that is causing the error.
  Locate the cell(s) that are expected to contain boolean values.
  Ensure that the values in these cells are strictly 'true' or 'false' (case-sensitive) without any additional characters, spaces, or formatting.
  
  
  
  Data Validation:
  
  If you have control over the data input, implement data validation in Excel to restrict the input to only 'true' or 'false'.
  You can use Excel's Data Validation feature to create a dropdown list for these cells.
  
  
  
  Trim Spaces:
  
  If there are leading or trailing spaces, you can use the TRIM function in Excel to clean up the data.
  For example, if the boolean value is in cell A1, you can use =TRIM(A1) in another cell to remove any extra spaces.
  
  
  
  Reformatting:
  
  If the boolean values are represented in a different format (like "yes"/"no" or "1"/"0"), you may need to convert them to 'true'/'false' before processing.
  
  
  
  Testing:
  
  After making the necessary changes, save the Excel file and try to reprocess it in SAP to see if the error persists.
  
  
  
  Related Information:
  
  SAP Documentation: Check SAP's official documentation or help resources for more details on handling Excel files and data types.
  SAP Notes: Look for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Community Forums: Engage with SAP community forums or support channels for insights from other users who may have encountered similar issues.
  
  By ensuring that the boolean values in your Excel file are correctly formatted, you should be able to resolve the FDT_EXCEL_API013 error.