SAP

SAP Releases Very High Priority Note 3782335 for S/4HANA General Ledger Archiving

SAP Note 3782335 fixes a Very High priority issue in S/4HANA General Ledger archiving where FINS_ARC compression may incorrectly determine totals by company code, potentially causing loss of JVA fields.

Luca Molinari

Luca Molinari

— 1 min read
Share
SAP S/4HANA General Ledger archiving with a Very High priority security and reliability alert for SAP Note 3782335 affecting FINS_ARC compression.
SAP Note 3782335 has been released with a Very High priority, addressing a critical issue in SAP S/4HANA General Ledger archiving (FI-GL-GL-E). Organizations using FINS_ARC compression should review and implement the correction promptly to prevent potential data inconsistencies.

SAP has released SAP Note 3782335 with a Very High priority for the FI-GL-GL-E (General Ledger Archiving) component, addressing a program error that can lead to data inconsistencies during FINS_ARC compression runs.

What is the issue?

According to SAP, during the FINS_ARC compression process, total fields are not determined based on the company code. As a result, Joint Venture Accounting (JVA) fields may be lost after the compression run, potentially impacting archived financial data.

The issue is classified as a program error and affects the General Ledger archiving framework.

Affected Releases

The correction applies to the following SAP S/4HANA software components:

  • S4CORE 104
  • S4CORE 105
  • S4CORE 106
  • S4CORE 107
  • S4CORE 108
  • S4CORE 109

Resolution

SAP recommends either:

  • Implementing the automatic correction instructions provided in SAP Note 3782335, or
  • Upgrading to the appropriate Support Package.

The note also requires several prerequisite SAP Notes, including:

  • 2954933 – Compression Run: Totals do not match. Rollback Work
  • 3087651 – Compression Run: Error Messages to be captured only for the packages that cannot be compressed
  • Additional prerequisites depending on your S4CORE release.

Why this matters

Organizations using SAP S/4HANA Financial Accounting archiving should review this note promptly. Although the issue only affects systems performing FINS_ARC compression, incorrect total determination can lead to the loss of accounting-related fields during archive processing.

Given the Very High priority assigned by SAP, Basis teams should assess whether their landscape is affected and plan the correction according to their maintenance procedures.

Final Thoughts

If your SAP S/4HANA system performs General Ledger archiving with FINS_ARC, this note deserves immediate attention. Reviewing your current S4CORE release, validating the listed prerequisites, and implementing the correction can help prevent data inconsistencies during archive compression.

Read more