How To Fix FAGL_ITAXBUPLA014 - Objects other than segments still assigned to company code &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FAGL_ITAXBUPLA - Messages for Commercial Business

• Message number: 014

• Message text: Objects other than segments still assigned to company code &1

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 FAGL_ITAXBUPLA014 - Objects other than segments still assigned to company code &1 ?

  The SAP error message FAGL_ITAXBUPLA014 indicates that there are objects other than segments still assigned to a company code in the context of the new General Ledger (G/L) accounting. This error typically arises when you are trying to activate or change the settings for the new G/L, and it finds that there are still legacy objects (like accounts, cost centers, etc.) that are not compatible with the new G/L structure.
  Cause:
  The primary cause of this error is that certain objects in the system are still linked to the company code, which prevents the system from fully transitioning to the new G/L accounting structure. This can include:
  
  Legacy G/L accounts that have not been migrated.
  Open items or balances that are still associated with the old structure.
  Other financial objects (like cost centers, profit centers, etc.) that are not properly aligned with the new G/L settings.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Identify the Objects: Use transaction codes like SE16 or SE11 to check the tables related to the company code and identify which objects are still assigned. Common tables to check include:
  
  SKA1 (G/L Account Master Data)
  CSKS (Cost Center Master Data)
  CE1XXXX (Profit Center Master Data)
  
  
  
  Review Assignments: Check the assignments of the identified objects to the company code. You may need to look for any open items or balances that are still linked to the old G/L.
  
  
  Clear Open Items: If there are open items, you may need to clear them or migrate them to the new G/L structure. This may involve posting adjustments or clearing transactions.
  
  
  Deactivate Legacy Objects: If certain legacy objects are no longer needed, consider deactivating or deleting them from the company code.
  
  
  Check Configuration: Ensure that the configuration settings for the new G/L are correctly set up. This includes checking the settings in the Financial Accounting (FI) and Controlling (CO) modules.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the new G/L migration process for any specific steps or considerations that may apply to your situation.
  
  
  Testing: After making the necessary changes, test the configuration to ensure that the error no longer occurs and that the new G/L is functioning as expected.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or updates related to this error message.
  Transaction Codes: Familiarize yourself with transaction codes like OBY6 (for company code settings) and OBD2 (for G/L account settings) to manage your configurations effectively.
  Migration Tools: If you are migrating from classic G/L to new G/L, consider using SAP's migration tools and guides to ensure a smooth transition.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP Financials for further assistance.