How To Fix FARR_CONTRACT_MAIN735 - POB &1 cannot have credit memo RAIs as it has simplified invoice flag

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 735

• Message text: POB &1 cannot have credit memo RAIs as it has simplified invoice flag

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 FARR_CONTRACT_MAIN735 - POB &1 cannot have credit memo RAIs as it has simplified invoice flag ?

  The SAP error message FARR_CONTRACT_MAIN735 indicates that there is an issue with a contract in the SAP system related to the handling of credit memos and simplified invoices. Specifically, the error states that a particular Purchase Order (POB) cannot have credit memo RAIs (Revenue Accounting Items) because it has the simplified invoice flag set.
  Cause:
  
  Simplified Invoice Flag: The contract or purchase order in question has been flagged for simplified invoicing. This typically means that the invoicing process is streamlined, and certain types of transactions, such as credit memos, may not be allowed.
  Configuration Settings: The configuration settings in the SAP system may restrict the use of credit memos for contracts that are set up with simplified invoicing.
  Business Rules: There may be specific business rules or policies in place that dictate how invoicing and credit memos should be handled for certain types of contracts.
  
  Solution:
  
  Review Contract Settings: Check the settings of the contract or purchase order to confirm if the simplified invoice flag is indeed set. If credit memos are necessary, consider whether the simplified invoice flag can be removed.
  Adjust Configuration: If the business process allows, you may need to adjust the configuration settings in the SAP system to permit credit memos for contracts with the simplified invoice flag.
  Consult with Business Stakeholders: Engage with relevant business stakeholders to understand the implications of changing the simplified invoice flag or the configuration settings. Ensure that any changes align with business processes and compliance requirements.
  Use Alternative Processes: If the simplified invoice flag cannot be changed, consider using alternative processes for handling credit memos, such as creating a separate contract or using a different invoicing method.
  
  Related Information:
  
  SAP Documentation: Refer to SAP's official documentation for detailed information on contract management, invoicing, and revenue accounting.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VA02 (Change Sales Order), FBL1N (Vendor Line Item Display), or FBL3N (G/L Account Line Item Display) to investigate related documents.
  SAP Notes: Check for any SAP Notes that may address this specific error or provide guidance on handling similar situations.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.