How To Fix FAGL_SWITCH_OP027 - Company code &1: Inconsistency in table BSAS

SAP Error Message - Details

• Message type: E = Error

• Message class: FAGL_SWITCH_OP -

• Message number: 027

• Message text: Company code &1: Inconsistency in table BSAS

What causes this issue?

Table <AB>BSAS</> contains cleared items. In company code &V1&, this
table contains entries for account &V2&. This means that open item
management was at one time active for this account, clearings were made,
and open item management was deactivated later on.

System Response

Company code &V1& is not considered during the conversion.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FAGL_SWITCH_OP027 - Company code &1: Inconsistency in table BSAS ?

  The SAP error message FAGL_SWITCH_OP027 indicates that there is an inconsistency in the table BSAS for a specific company code. This error typically arises during the execution of financial operations, particularly when switching to the new General Ledger (G/L) accounting or during the execution of certain financial reports or transactions.
  Cause:
  The inconsistency in table BSAS can be caused by several factors, including:
  
  
  Data Migration Issues: If data was migrated from an older system or from a different module, inconsistencies may arise if the data was not properly aligned or if there were errors during the migration process.
  
  
  Manual Data Entry Errors: Incorrect manual entries or adjustments in financial documents can lead to discrepancies in the BSAS table.
  
  
  Incomplete or Incorrect Configuration: If the configuration settings for the new G/L or the company code are not set up correctly, it can lead to inconsistencies.
  
  
  Posting Errors: Errors during posting transactions, such as missing or incorrect account assignments, can also lead to inconsistencies.
  
  
  Solution:
  To resolve the FAGL_SWITCH_OP027 error, you can follow these steps:
  
  
  Check for Inconsistencies: Use transaction codes like SE16 or SE11 to check the contents of the BSAS table for the specified company code. Look for any anomalies or missing entries.
  
  
  Run Consistency Checks: Use the SAP transaction code FBRA (Reset Document) or FAGL_CHECK to run consistency checks on the financial documents. This can help identify and correct inconsistencies.
  
  
  Reconcile Data: If the inconsistency is due to data migration, you may need to reconcile the data between the old and new systems. This may involve comparing balances and transactions to ensure they match.
  
  
  Review Configuration: Check the configuration settings for the new G/L and ensure that all necessary settings are correctly configured for the company code in question.
  
  
  Consult SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error. There may be patches or updates that can resolve known issues.
  
  
  Contact SAP Support: If the issue persists after performing the above steps, consider reaching out to SAP Support for further assistance. They can provide more specific guidance based on your system configuration and the nature of the inconsistency.
  
  
  Related Information:
  
  BSAS Table: This table contains line item data for accounting documents. Inconsistencies here can affect financial reporting and the integrity of financial data.
  New G/L Accounting: If your organization is transitioning to the new G/L, ensure that all necessary steps for migration and configuration are followed.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FBL1N (Vendor Line Item Display), and FBL3N (G/L Account Line Item Display) to analyze the data further.
  
  By following these steps, you should be able to identify and resolve the inconsistency causing the FAGL_SWITCH_OP027 error.