Search Results resequence_acct_seq




Overview
Explore in AI Chat

Overview

XLA_SEQUENCE_DATAFIX_PKG is a Subledger Accounting (XLA) diagnostic and corrective utility shipped in the APPS schema. Its business purpose is to repair gaps and inconsistencies in the accounting sequence numbering that Subledger Accounting assigns to accounting entries. Every journal created by XLA receives an accounting sequence value derived from the accounting date and the corresponding GL period; the Subledger Accounting Program (XLAPG) writes these values to the XLA_AE_HEADERS table. When a period is reopened, when an entry is manually manipulated, or when concurrent processing terminates abnormally, the stored sequence can fall out of alignment with the period it belongs to. This package provides a supported data-fix path to resequence those accounting entries without resorting to direct DML against the accounting tables.

The package carries the source header identifier xlaseqdf.pkb and was originally created in July 2004 by W. Shen as the "Package body for accounting sequence datafix." Version 120.3 dates from May 2006, indicating it is a long-standing, stable component of the XLA code line preserved through both 12.1.1 and 12.2.2.

Key Procedures and Functions

  • RESEQUENCE_ACCT_SEQ — the single documented entry point in the package and the object users locate when searching "resequence_acct_seq." It performs the actual resequencing of accounting sequence values for the affected accounting entries. It is the procedure invoked by the supporting data-fix script or concurrent program to recalculate and reassign sequence numbers so that XLA_AE_HEADERS rows reflect a contiguous, period-correct sequence.

The package body additionally defines private constants and logging infrastructure rather than public APIs. These include period-status constants (C, O, F, N, P) mirroring the GL_PERIOD_STATUSES status codes, FND_LOG level constants, and a module identifier ('xla.plsql.XLA_SEQUENCE_DATAFIX_PKG'). The presence of these period-status constants confirms that the resequencing logic evaluates the open/closed/future/permanently-closed state of the accounting period before acting — the procedure is effectively a no-op or refuses to run for periods in an ineligible status. The internal trace routine supports controlled debug output at statement, procedure, event, exception, error, and unexpected levels.

Tables Accessed

  • XLA_AE_HEADERS — the primary target table. This holds the subledger journal headers, including the accounting sequence column that RESEQUENCE_ACCT_SEQ repairs.
  • GL_PERIOD_STATUSES — read to determine the open/closed state of the accounting period, validating that resequencing is permissible for the period in question.
  • XLA_EVENTS_GT — a global temporary table used to stage the set of subledger events whose accounting entries are candidates for resequencing, allowing the procedure to scope its work to a defined population before updating headers.

Usage Notes

This package is not a runtime dependency of standard processing; the ETRM metadata records zero packages referencing it, which confirms it is invoked only on demand. It is normally driven by a data-fix script or a dedicated concurrent program supplied by Oracle Support, and is run in response to a Service Request where accounting sequence gaps or duplicates have been identified. Typical invocation is from SQL*Plus as the APPS user or through the concurrent manager under a diagnostic responsibility, never from standard Subledger Accounting forms. Because direct updates to XLA_AE_HEADERS are unsupported, RESEQUENCE_ACCT_SEQ should always be run against a restored backup or pre-cloned environment first, with the FND_LOG trace enabled, and only after confirming the relevant GL period status. Customers on 12.1.1 and 12.2.2 should verify the current patch level of xlaseqdf.pkb before executing, since the resequencing logic is version-sensitive.