How To Fix FTR_TEX1790 - Line item check unsuccessful (raw exp. ID: &1; item ID: &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: FTR_TEX1 - Messages for raw exposures

• Message number: 790

• Message text: Line item check unsuccessful (raw exp. ID: &1; item ID: &2)

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 FTR_TEX1790 - Line item check unsuccessful (raw exp. ID: &1; item ID: &2) ?

  The SAP error message FTR_TEX1790, which states "Line item check unsuccessful (raw exp. ID: &1; item ID: &2)," typically occurs in the context of financial transactions, particularly in the area of treasury and risk management. This error indicates that there is an issue with the line item check for a specific raw exposure.
  Cause:
  The error can be caused by several factors, including:
  
  
  Data Inconsistency: There may be inconsistencies in the data related to the raw exposure or the line item being processed. This could be due to missing or incorrect information.
  
  
  Configuration Issues: The system configuration for treasury management or the specific transaction type may not be set up correctly, leading to validation failures.
  
  
  Missing Master Data: Required master data (such as currency, account, or business partner information) may be missing or incorrect.
  
  
  Business Rules Violations: The transaction may violate certain business rules or validations defined in the system, such as limits on exposure or incorrect accounting entries.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check the Raw Exposure ID and Item ID: Review the specific raw exposure ID and item ID mentioned in the error message. Look for any discrepancies or missing information.
  
  
  Validate Data: Ensure that all relevant data for the transaction is complete and accurate. This includes checking master data, transaction details, and any related documents.
  
  
  Review Configuration: Check the configuration settings in the treasury management module to ensure they are set up correctly. This may involve consulting with your SAP configuration team.
  
  
  Run Consistency Checks: Use SAP tools to run consistency checks on the relevant data. This can help identify any inconsistencies or errors in the data.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific error message for additional guidance and troubleshooting steps.
  
  
  Contact SAP Support: If the issue persists after performing the above checks, consider reaching out to SAP support for further assistance. Provide them with the error message details and any relevant transaction information.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP that pertain to treasury management, such as FTR_CREATE, FTR_EDIT, and FTR_DISPLAY.
  SAP Notes: Search for SAP Notes related to FTR_TEX1790 for any known issues or patches that may address the error.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.