How To Fix FB660 - & does not exist in comp.code &; block indicator is not transferred

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 660

• Message text: & does not exist in comp.code &; block indicator is not transferred

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 FB660 - & does not exist in comp.code &; block indicator is not transferred ?

  The SAP error message FB660 typically indicates that there is an issue with the financial document you are trying to post, specifically related to the company code and the block indicator. Here’s a breakdown of the cause, potential solutions, and related information for this error:
  Cause:
  
  Company Code Not Defined: The company code you are trying to use in the transaction does not exist in the system or is not properly configured.
  Block Indicator Issue: The block indicator for the document is not being transferred correctly, which may be due to configuration settings or missing data.
  Document Type Restrictions: The document type you are using may have restrictions that prevent it from being posted in the specified company code.
  Authorization Issues: The user may not have the necessary authorizations to post documents in the specified company code.
  
  Solutions:
  
  
  Check Company Code Configuration:
  
  Go to the transaction code OBY6 to verify that the company code exists and is properly configured.
  Ensure that the company code is active and has all necessary settings (like fiscal year variant, currency, etc.) configured.
  
  
  
  Review Block Indicator Settings:
  
  Check the configuration for the block indicator in the relevant financial document type settings.
  Ensure that the block indicator is set up correctly in the document type configuration (transaction code OBY6 or OBA7).
  
  
  
  Document Type Verification:
  
  Verify that the document type you are using is allowed for the company code in question. You can check this in the configuration settings for document types (transaction code OBY6).
  
  
  
  User Authorizations:
  
  Ensure that the user has the necessary authorizations to post documents in the specified company code. This can be checked with the help of your SAP security team.
  
  
  
  Check for Customizations:
  
  If there are any custom developments or enhancements in your SAP system, ensure that they are not interfering with the posting process.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message. There may be patches or updates that resolve known issues.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB01 (Post Document), FB50 (G/L Account Document), and OBY6 (Company Code Global Parameters).
  SAP Documentation: Review SAP documentation for financial accounting to understand the configuration and posting processes better.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP Financial Accounting.