How To Fix FKKRA072 - Business partner &1 locked in revenue accounting

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKRA - FI-CA Integration with Revenue Accounting

• Message number: 072

• Message text: Business partner &1 locked in revenue accounting

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 FKKRA072 - Business partner &1 locked in revenue accounting ?

  The SAP error message FKKRA072 indicates that a business partner is locked in revenue accounting. This typically occurs when there are certain restrictions or locks placed on the business partner that prevent transactions from being processed.
  Cause:
  
  
  Business Partner Lock: The business partner may be locked due to various reasons, such as:
  
  Manual locking by a user or administrator.
  The business partner is involved in a transaction that is currently being processed or is in a locked state.
  The business partner is marked for deletion or has been flagged for some other administrative reason.
  
  
  
  Configuration Issues: There may be configuration settings in the revenue accounting module that restrict the use of certain business partners.
  
  
  Data Consistency Issues: There could be inconsistencies in the data related to the business partner, such as missing or incorrect information.
  
  
  Solution:
  
  
  Unlock the Business Partner:
  
  Check the status of the business partner in the SAP system. You can do this by navigating to the business partner transaction (e.g., BP transaction code).
  If the business partner is locked, you can unlock it by changing the status or removing the lock. This typically requires appropriate authorization.
  
  
  
  Review Configuration Settings:
  
  Ensure that the configuration settings for revenue accounting are correctly set up to allow transactions for the business partner in question.
  
  
  
  Check for Ongoing Transactions:
  
  Verify if there are any ongoing transactions involving the business partner that might be causing the lock. If so, you may need to wait for those transactions to complete.
  
  
  
  Data Consistency Check:
  
  Perform a data consistency check to ensure that all required fields for the business partner are filled out correctly and that there are no discrepancies.
  
  
  
  Consult Documentation or Support:
  
  If the issue persists, consult SAP documentation or reach out to SAP support for further assistance. They may provide insights specific to your system configuration or version.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as BP (Business Partner), FBL1N (Vendor Line Item Display), or FBL3N (G/L Account Line Item Display) to investigate further.
  Authorization: Ensure that you have the necessary authorizations to unlock business partners or make changes to their status.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or patches that address known issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.