How To Fix FARRIC_OL012 - Sales document &: item & involves cross company process

SAP Error Message - Details

• Message type: E = Error

• Message class: FARRIC_OL - Revenue Accounting: Operational Load

• Message number: 012

• Message text: Sales document &: item & involves cross company process

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 FARRIC_OL012 - Sales document &: item & involves cross company process ?

  The SAP error message FARRIC_OL012 indicates that there is an issue related to a sales document and item that involves a cross-company process. This typically occurs in scenarios where sales documents are created that involve multiple company codes, and there are specific configurations or data issues that need to be addressed.
  Cause:
  
  Cross-Company Code Transactions: The error usually arises when a sales document (like a sales order or invoice) is created that involves items from different company codes. SAP requires specific configurations to handle such transactions.
  Missing Configuration: The necessary configuration for cross-company code transactions may not be set up correctly in the system.
  Inconsistent Master Data: There may be inconsistencies in the master data (like customer or vendor data) that prevent the system from processing the transaction correctly.
  Document Type Restrictions: Certain document types may not be allowed for cross-company transactions.
  
  Solution:
  
  
  Check Configuration: Ensure that the configuration for cross-company code transactions is correctly set up in the system. This includes checking the following:
  
  Cross-company code settings in the sales and distribution (SD) module.
  Inter-company billing settings if applicable.
  Ensure that the relevant company codes are linked correctly in the system.
  
  
  
  Review Master Data: Verify that the master data for customers, vendors, and materials involved in the transaction is consistent and correctly set up for cross-company transactions.
  
  
  Document Type Settings: Check the document type settings in the sales document configuration to ensure that the document type being used allows for cross-company transactions.
  
  
  Transaction Codes: Use transaction codes like VA03 (Display Sales Order) or VF03 (Display Billing Document) to review the sales document and identify any inconsistencies or issues.
  
  
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error message or provide additional guidance on handling cross-company transactions.
  
  
  Testing: After making the necessary changes, test the transaction again to ensure that the error is resolved.
  
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for detailed information on configuring cross-company code transactions in the SD module.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Support: If the issue persists, consider reaching out to SAP support for assistance, providing them with the error message and details of the transaction.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.