How To Fix FINS_BCF_EN026 - Subpackages for ledger &1, company code &1 are not correct

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_BCF_EN - Balance Carry Forward

• Message number: 026

• Message text: Subpackages for ledger &1, company code &1 are not correct

What causes this issue?

In the set of subpackages, created by the Business Add-In (BAdI)
<AB>BADI_GVTR_PACKAGE</>S, there are subpackages either with overlapping
range intervals or with gaps in the range intervals.
For ledger &V1& and company code &V2& the number of entries in ACDOCA
for the complete package does not equal the number of entries in the set
of subpackages (All entries: &V3&, Sum of entries: &V4&).

System Response

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

How to fix this error?

Adjust the coding of BadI <AB>BADI_GVTR_PACKAGES</> accordingly.
Ensure that the selection criteria for each subpackage is correct. The
combined data in the resulting set of packages should be equal to the
package from which the subpackages were created. There shouldn't be any
missing or duplicate data in the subpackages.

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 FINS_BCF_EN026 - Subpackages for ledger &1, company code &1 are not correct ?

  The SAP error message FINS_BCF_EN026 indicates that there is an issue with the configuration of subpackages for a specific ledger and company code in the SAP system. This error typically arises in the context of the SAP Financial Closing cockpit or when dealing with the new General Ledger (G/L) accounting functionalities.
  Cause:
  The error message suggests that the subpackages assigned to the specified ledger and company code are not correctly configured. This could be due to several reasons, including:
  
  Incorrect Configuration: The subpackages may not be properly defined or assigned in the system for the specified ledger and company code.
  Missing Subpackages: The required subpackages for the ledger and company code may not exist or may not be activated.
  Inconsistent Data: There may be inconsistencies in the configuration data related to the financial closing process.
  
  Solution:
  To resolve the error, you can follow these steps:
  
  
  Check Configuration:
  
  Go to the SAP Customizing Implementation Guide (IMG) and navigate to the relevant configuration settings for Financial Closing.
  Verify that the subpackages for the specified ledger and company code are correctly defined and assigned.
  
  
  
  Define Subpackages:
  
  If the subpackages are missing, you may need to create or define them. This can typically be done in the configuration settings for the Financial Closing cockpit.
  
  
  
  Review Assignment:
  
  Ensure that the subpackages are correctly assigned to the ledger and company code in the system. This can usually be checked in the settings for the Financial Closing cockpit.
  
  
  
  Check for Updates:
  
  Ensure that your SAP system is up to date with the latest support packages and notes, as there may be fixes or enhancements related to this error.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the Financial Closing cockpit and subpackage configuration for any specific instructions or guidelines.
  
  
  
  Testing:
  
  After making the necessary changes, test the configuration by attempting to execute the financial closing process again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes such as SPRO (to access the IMG), OB52 (to check period control), or F.01 (to run financial reports) depending on your specific needs.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for the error message number or related keywords in the SAP Support Portal.
  User Roles: Ensure that you have the necessary authorizations to make changes to the configuration settings.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further assistance, or to reach out to SAP support for more specialized help.