How To Fix FAGL_SWITCH_LEAD_LDG104 - Check for company code &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FAGL_SWITCH_LEAD_LDG - Technical Changeover of Leading View in General Ledger (New)

• Message number: 104

• Message text: Check for 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_SWITCH_LEAD_LDG104 - Check for company code &1 ?

  The SAP error message FAGL_SWITCH_LEAD_LDG104 typically occurs in the context of the New General Ledger (New G/L) functionality. This error indicates that there is an issue with the settings related to the leading ledger for a specific company code. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Missing Configuration: The leading ledger for the specified company code is not properly configured in the system.
  Inconsistent Settings: There may be inconsistencies in the settings for the leading ledger, such as missing or incorrect assignment of the ledger to the company code.
  Migration Issues: If you are migrating from Classic G/L to New G/L, there may be issues with the migration process that have left the configuration incomplete.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or modify the settings related to the leading ledger.
  
  Solution:
  
  
  Check Ledger Configuration:
  
  Go to the transaction code OB22 (Define Ledgers) and verify that the leading ledger is correctly defined for the company code in question.
  Ensure that the leading ledger is assigned to the company code.
  
  
  
  Review Company Code Settings:
  
  Use transaction code OBY6 (Assign Company Code to Ledger) to check if the company code is correctly assigned to the leading ledger.
  Make sure that the settings for the company code are consistent with the requirements for the leading ledger.
  
  
  
  Check Migration Settings:
  
  If you are in the process of migrating to New G/L, ensure that all necessary steps have been completed and that the migration was successful.
  Review the migration logs for any errors or warnings that may indicate issues with the leading ledger configuration.
  
  
  
  Authorization Check:
  
  Ensure that the user encountering the error has the necessary authorizations to access and modify the ledger settings.
  Check the user roles and profiles to confirm that they have the required permissions.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional guidance on resolving it.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  OB22: Define Ledgers
  OBY6: Assign Company Code to Ledger
  OBY1: Define Company Code
  
  
  Documentation: Review SAP documentation on New G/L and leading ledger configuration for detailed guidance.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation and support.