How To Fix 8I357 - Vendor Exc.Inv. & Exists For The &, & Combination.

SAP Error Message - Details

• Message type: E = Error

• Message class: 8I - Localization India

• Message number: 357

• Message text: Vendor Exc.Inv. & Exists For The &, & Combination.

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 8I357 - Vendor Exc.Inv. & Exists For The &, & Combination. ?

  The SAP error message "8I357 Vendor Exc.Inv. & Exists For The &, & Combination" typically occurs in the context of invoice verification or processing in the SAP system. This error indicates that there is an issue with the vendor and the invoice combination being processed. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Vendor and Invoice Combination: The error suggests that there is an existing invoice for the specified vendor and the combination of other parameters (like purchase order, material, etc.) that is causing a conflict.
  Duplicate Invoice: The system may have detected a duplicate invoice entry for the same vendor and purchase order combination.
  Incorrect Data Entry: There may be incorrect or incomplete data entered in the invoice or vendor master records.
  Configuration Issues: There could be configuration settings in the SAP system that are not aligned with the business processes, leading to this error.
  
  Solutions:
  
  
  Check for Existing Invoices: 
  
  Go to the invoice verification transaction (e.g., MIRO) and check if there are any existing invoices for the same vendor and purchase order combination.
  If a duplicate invoice exists, you may need to reverse or delete the duplicate entry.
  
  
  
  Review Vendor Master Data:
  
  Ensure that the vendor master data is correctly maintained and that there are no discrepancies.
  Check if the vendor is blocked or has any restrictions that might affect invoice processing.
  
  
  
  Correct Data Entry:
  
  Verify that all the required fields in the invoice are filled out correctly and that there are no typos or incorrect entries.
  Ensure that the purchase order number and other related fields are accurate.
  
  
  
  Consult with SAP Support:
  
  If the issue persists, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any known issues or patches related to this error.
  
  
  
  Configuration Review:
  
  If you have access to configuration settings, review the settings related to invoice verification and vendor management to ensure they align with your business processes.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MIRO (Invoice Verification), ME23N (Display Purchase Order), and XK03 (Display Vendor).
  SAP Notes: Check SAP Notes for any updates or specific fixes related to this error message.
  Documentation: Review SAP documentation or user manuals related to invoice processing and vendor management for best practices and troubleshooting steps.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.