How To Fix 1F123 - Account &1 / &2 being closed before the "valid to" date of the hierarchy

SAP Error Message - Details

• Message type: E = Error

• Message class: 1F - BKK: Beziehungen

• Message number: 123

• Message text: Account &1 / &2 being closed before the "valid to" date of the hierarchy

What causes this issue?

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

System Response

How to fix this error?

To include the account in the hierarchy until the time of account
closure, proceed as follows:
Set the "Valid to" date of the hierarchy to the date of the account
closure (Hierarchy -> Change interval).
Create a new hierarchy. To do this, use the hierarchy changed above to
copy from.
- "Valid from" - one day after account closure
- "Valid to" - old date of the original hierarchy
Delete the appropriate account from the new hierarchy or reassign
accounts as necessary.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 1F123 - Account &1 / &2 being closed before the "valid to" date of the hierarchy ?

  The SAP error message 1F123 indicates that an account (represented by &1) and a hierarchy (represented by &2) are closed before the "valid to" date specified in the hierarchy. This typically occurs in the context of financial accounting or controlling when trying to post transactions or make changes to account assignments that are no longer valid due to the account being closed.
  Cause:
  
  Account Closure: The account in question has been closed in the system, meaning it is no longer available for posting transactions.
  Hierarchy Validity: The hierarchy has a defined "valid to" date, and the account closure date is earlier than this date, which leads to a conflict.
  Posting Attempt: An attempt is being made to post a transaction or make a change that references the closed account while the hierarchy is still considered valid.
  
  Solution:
  
  Check Account Status: Verify the status of the account in question. If it is indeed closed, determine if it needs to be reopened for the transaction or if the transaction can be adjusted to use an open account.
  Review Hierarchy Dates: Check the "valid to" date of the hierarchy. If the hierarchy is still valid but the account is closed, consider whether the account should be reopened or if a different account should be used.
  Adjust Transactions: If possible, adjust the transactions or postings to reference an open account that is valid within the hierarchy.
  Consult with Finance Team: If you are unsure about the implications of reopening an account or changing postings, consult with your finance or accounting team for guidance on best practices.
  System Configuration: If this is a recurring issue, it may be worth reviewing the configuration settings for account closures and hierarchy management to ensure they align with business processes.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like FS00 (to check account master data) or OB52 (to check posting periods) to investigate further.
  Documentation: Refer to SAP documentation or help resources for detailed information on account management and hierarchy settings.
  Support: If the issue persists or if you need further assistance, consider reaching out to SAP support or your internal IT support team for help.
  
  By following these steps, you should be able to resolve the error and ensure that your financial postings are processed correctly.