How To Fix FB680 - Individual request only relevant for cross-company code correspondence

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 680

• Message text: Individual request only relevant for cross-company code correspondence

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 FB680 - Individual request only relevant for cross-company code correspondence ?

  The SAP error message FB680 ("Individual request only relevant for cross-company code correspondence") typically occurs when you are trying to process a financial document that is not set up correctly for cross-company code transactions. This error is often encountered in the context of intercompany transactions where different company codes are involved.
  Cause:
  
  Incorrect Document Type: The document type you are using may not be configured to allow cross-company code transactions.
  Company Code Configuration: The company codes involved may not be set up correctly for intercompany transactions.
  Transaction Type: The transaction you are trying to execute may not support individual requests for cross-company code correspondence.
  Missing or Incorrect Settings: There may be missing or incorrect settings in the configuration of the financial accounting module.
  
  Solution:
  
  
  Check Document Type: Ensure that the document type you are using is configured to allow cross-company code transactions. You can check this in the configuration settings for Financial Accounting (FI).
  
  
  Review Company Code Settings: Verify that the company codes involved in the transaction are correctly set up for intercompany transactions. This includes checking the settings in the company code configuration.
  
  
  Use the Correct Transaction: If you are trying to process a transaction that is not meant for cross-company code correspondence, switch to the appropriate transaction type that supports it.
  
  
  Consult Configuration: If you have access to the SAP configuration, check the settings related to cross-company code transactions. This may involve looking at the settings for intercompany billing, reconciliation accounts, and other related configurations.
  
  
  Error Message Documentation: Refer to the SAP documentation or help files for more detailed information on the error message and its implications.
  
  
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They can provide insights based on the specific configuration and version of your SAP system.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB01 (Post Document), FB50 (G/L Account Document), and others that may be involved in the process.
  Intercompany Transactions: Understand the principles of intercompany transactions in SAP, including how they are processed and the necessary configurations.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide patches or additional guidance.
  
  By following these steps, you should be able to identify the cause of the FB680 error and implement a solution to resolve it.