How To Fix RDSV_FI_XX026 - NR object &1 with subobj. &2, NR &3, to year &4 can no longer be used

RDSV_FI_XX026 - Overview

• Message type: E = Error

• Message class: RDSV_FI_XX - Regulatory Document and Signature Validation in FI

• Message number: 026

• Message text: NR object &1 with subobj. &2, NR &3, to year &4 can no longer be used

What causes this issue?

The number range object has been corrupted by a system crash or a system
recovery.
The number range must not be used for postings for company codes that
can generate digital signatures.

System Response

The system detects a corrupted number range interval by specific
application data and stops the processing.

How to fix this error?

The status of the number range interval (series) is irreversible.
Contact the system administrator since this error message cannot occur
for a correct customized document numbering.

Procedure for System Administrators

To enable the system to post with the relevant document type and company
code, you do the following:
Deactivate the digital signature generation for the corrupted or stopped
number range interval.
Enter and activate a new number range interval for the corresponding
document type and company code to use a different series.

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RDSV_FI_XX026 - NR object &1 with subobj. &2, NR &3, to year &4 can no longer be used ?

  The SAP error message RDSV_FI_XX026 typically indicates that a specific object (like a financial document or record) cannot be used for a certain year due to various reasons, often related to the status of the financial year or the object itself. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  Closed Fiscal Year: The fiscal year for the specified object has been closed, meaning no further postings can be made to that year.
  Archiving: The object may have been archived, making it unavailable for further processing.
  Data Consistency Issues: There may be inconsistencies in the data that prevent the object from being used.
  Configuration Settings: Certain configuration settings in the financial module may restrict the use of objects for specific years.
  
  Solutions:
  
  
  Check Fiscal Year Status:
  
  Verify if the fiscal year in question is closed. If it is, you may need to open it again (if your business processes allow) or post