How To Fix 1F098 - Account &1 &2 will be closed on &3. However, upper interval limit is &4

1F098 - Overview

• Message type: E = Error

• Message class: 1F - BKK: Beziehungen

• Message number: 098

• Message text: Account &1 &2 will be closed on &3. However, upper interval limit is &4

What causes this issue?

The account closure date may not be before the interval upper limit of
the hierarchy.

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 account closure, proceed
as follows:
1. Set the "Valid to" of the hierarchy to the account closure date
(Hierarchy - Change interval) - note the old date
2. Enter the account in the hierarchy and save
3. Create a new hierarchy - use the hierarchy changed above as a
reference copy
- "Valid from" - one day after account closure
- "Valid to " - old date of original hierarchy
4. Delete the appropriate account from the new hierarchy and
move 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 1F098 - Account &1 &2 will be closed on &3. However, upper interval limit is &4 ?

  The SAP error message 1F098 indicates that a specific account (identified by &1 and &2) is set to be closed on a certain date (&3), but the upper interval limit for that account is set to a different value (&4). This typically occurs in the context of financial accounting, particularly when dealing with account closures or adjustments in the fiscal year.
  
  Cause:
  
  Account Closure Date: The account is scheduled to be closed on a date that is not compliant with the defined upper interval limit.
  
  Configuration Issues: The upper interval limit may not be correctly configured in the system, or it may not align with the intended closure date.
  Data Entry Errors: There may be a mistake in the data entry for the closure date or the upper limit.
  
  
  Solution:
  
  Review Account Settings: Check the configuration of the account in question. Ensure that the closure date is within the permissible range defined by the upper interval