How To Fix AJ899 - Inconsistency: Indicator BICO is set incorrectly in billing

SAP Error Message - Details

• Message type: E = Error

• Message class: AJ - Billing program

• Message number: 899

• Message text: Inconsistency: Indicator BICO is set incorrectly in billing

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 AJ899 - Inconsistency: Indicator BICO is set incorrectly in billing ?

  The SAP error message AJ899 indicates an inconsistency related to the BICO (Billing Document Control) indicator in the billing process. This error typically arises when there is a mismatch or incorrect setting in the billing document configuration, which can prevent the successful processing of billing documents.
  Cause:
  
  Incorrect Configuration: The BICO indicator may be set incorrectly in the billing document configuration. This can happen if the settings in the billing type or the related master data (like customer or material master) are not aligned.
  Data Inconsistency: There may be inconsistencies in the data related to the billing document, such as missing or incorrect entries in the billing item or header.
  Custom Development: If there are custom developments or enhancements in the billing process, they may inadvertently cause this inconsistency.
  
  Solution:
  
  
  Check Configuration: 
  
  Go to the transaction code SPRO and navigate to the relevant configuration settings for billing documents. Check the settings for the billing type and ensure that the BICO indicator is set correctly.
  Verify the settings in the billing type configuration (e.g., Sales and Distribution -> Billing -> Billing Documents -> Define Billing Types).
  
  
  
  Review Master Data:
  
  Check the customer master data and material master data for any inconsistencies that might affect billing. Ensure that all necessary fields are filled out correctly.
  
  
  
  Analyze Billing Document:
  
  Use transaction VF03 to display the billing document that is causing the error. Look for any discrepancies in the document that might indicate why the BICO indicator is set incorrectly.
  
  
  
  Check for Custom Code:
  
  If there are any custom enhancements or user exits related to billing, review them to ensure they are not causing the issue.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that might address this specific error message. There may be patches or updates that resolve known issues.
  
  
  
  Testing:
  
  After making any changes, perform testing to ensure that the billing process works correctly without triggering the error.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SPRO for configuration
  VF03 for displaying billing documents
  SE80 or SE37 for checking custom code or function modules
  
  
  SAP Documentation: Review SAP Help documentation for billing processes and BICO settings.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be beneficial to involve your SAP Basis or technical team for further investigation.