How To Fix EDPP090 - Business partner &1 installation &2: Contract not invoiced

SAP Error Message - Details

• Message type: E = Error

• Message class: EDPP -

• Message number: 090

• Message text: Business partner &1 installation &2: Contract not invoiced

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 EDPP090 - Business partner &1 installation &2: Contract not invoiced ?

  The SAP error message EDPP090 indicates that there is a contract associated with a business partner and installation that has not been invoiced. This error typically arises in the context of contract management and billing processes within SAP, particularly in modules like SAP IS-U (Industry Solution for Utilities).
  Cause:
  
  
  Uninvoiced Contract: The primary cause of this error is that there is a contract linked to the specified business partner and installation that has not yet been invoiced. This could be due to various reasons, such as:
  
  The contract is newly created and has not yet gone through the invoicing process.
  There may be issues with the billing cycle or billing plan that prevent invoicing.
  The contract may be in a status that does not allow for invoicing (e.g., it is on hold or inactive).
  
  
  
  Data Inconsistencies: There may be inconsistencies in the data related to the business partner, installation, or contract that prevent the system from processing the invoicing correctly.
  
  
  Configuration Issues: There could be configuration settings in the SAP system that are not set up correctly, affecting the invoicing process.
  
  
  Solution:
  
  
  Check Contract Status: Verify the status of the contract associated with the business partner and installation. Ensure that it is active and ready for invoicing.
  
  
  Review Billing Information: Check the billing information related to the contract. Ensure that all necessary billing data is complete and correct.
  
  
  Run Billing Program: If the contract is valid and should be invoiced, run the billing program to generate the invoice. This can typically be done through transaction codes like FPL9 (for billing) or FBL1N (for vendor line items).
  
  
  Correct Data Issues: If there are data inconsistencies, correct them in the relevant master data records (business partner, installation, contract).
  
  
  Consult Configuration: If the issue persists, consult with your SAP configuration team to ensure that the billing and contract management settings are correctly configured.
  
  
  Check for Open Items: Look for any open items or pending transactions that may be blocking the invoicing process.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as BP (Business Partner), EEDM (Contract Management), and FPL9 (Billing).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation related to contract management and billing processes for additional insights and troubleshooting steps.
  
  If the problem persists after following these steps, it may be beneficial to engage with SAP support or your internal SAP team for further assistance.