How To Fix GTCN_MESSAGE353 - Export invoice &1 has not been completely matched

SAP Error Message - Details

• Message type: E = Error

• Message class: GTCN_MESSAGE - GTCN: Message Class

• Message number: 353

• Message text: Export invoice &1 has not been completely matched

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 GTCN_MESSAGE353 - Export invoice &1 has not been completely matched ?

  The SAP error message GTCN_MESSAGE353, which states "Export invoice &1 has not been completely matched," typically occurs in the context of the Global Trade Services (GTS) module when there is an issue with the matching of export invoices to the corresponding documents, such as delivery notes or goods movements. This can happen for various reasons, including discrepancies in the data or incomplete processing of related documents.
  Causes:
  
  Incomplete Document Processing: The export invoice may not have been fully processed or matched with the relevant delivery or goods movement documents.
  Data Discrepancies: There may be discrepancies in the data between the export invoice and the associated documents, such as differences in quantities, values, or item details.
  Missing Documents: Required documents that need to be matched with the export invoice may be missing or not yet created.
  Configuration Issues: There may be configuration issues in the GTS settings that affect how invoices are matched with other documents.
  
  Solutions:
  
  Check Document Status: Verify the status of the export invoice and related documents (e.g., delivery notes, goods movements) to ensure they are all processed correctly.
  Review Data Consistency: Compare the details of the export invoice with the associated documents to identify any discrepancies. Ensure that quantities, values, and item details match.
  Complete Missing Documents: If any required documents are missing, create or complete them as necessary to allow for proper matching.
  Reprocess the Invoice: If the invoice was not fully processed, consider reprocessing it to ensure it is matched correctly with the relevant documents.
  Consult Configuration Settings: Review the GTS configuration settings to ensure that they are set up correctly for invoice matching. This may involve checking the settings for document types, matching criteria, and other related configurations.
  Check for Updates or Notes: Look for any SAP Notes or updates related to this error message, as there may be patches or fixes available that address known issues.
  
  Related Information:
  
  SAP GTS Documentation: Refer to the official SAP GTS documentation for detailed information on invoice processing and matching.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance, providing them with detailed information about the error and the steps you have taken to resolve it.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.