Search Results calendar_convert

Overview

The APPS.XLA_HIST_LEDGER_UPG_PKG package is an Oracle E-Business Suite upgrade utility that supports the migration of historical subledger accounting data into the Subledger Accounting (XLA) model introduced with the R12 architecture. Its principal business purpose is to convert and populate historical accounting entries for a primary ledger — and, where applicable, an associated reporting ledger — so that balances and journal lines originating from pre-R12 subledger processing remain consistent within the new accounting engine.

The package carries an OTHER API classification, indicating it is an internal upgrade and conversion utility rather than a public, supported integration API. It is intended for controlled, one-time upgrade execution rather than routine transactional use. The header version (xlahupg.pkh 120.4) dates to 2008, reflecting its origin in the initial R12 release cycle, and it remains catalogued in subsequent releases such as 12.1.1 and 12.2.2 for upgrade and diagnostic purposes.

Key Procedures and Functions

The documented interface exposes a driver procedure and a set of supporting procedures that collectively orchestrate validation, data population, and insertion:

• UPG_MAIN — The primary entry point. It receives parameters representing the primary ledger, reporting ledger, start period, reporting ledger type, conversion options, currency conversion details, and operating mode. It drives the overall historical upgrade flow and returns standard concurrent-program completion outputs (p_errbuf, p_retcode).
• PRE_VALIDATION — Performs prerequisite validation before the conversion begins, checking that the ledger, period, and setup conditions required for processing are satisfied.
• POST_VALIDATION — Confirms the integrity of data after the conversion and insertion steps have completed.
• POPULATE_RATES — Loads currency conversion rates used to translate historical amounts into the required reporting currency.
• VALIDATE_ALC and VALIDATE_SECONDARY — Validate the accounting ledger configuration and secondary (reporting) ledger setup respectively.
• ALC_INSERT and SECONDARY_INSERT — Insert converted accounting entries for the primary and reporting ledgers.
• MAP_CCID and CCID_CHECK — Resolve and verify code combinations, mapping historical accounts to valid Chart of Accounts identifier combinations.
• CALENDAR_CONVERT — Converts period and calendar references between accounting representations.
• LINE_NUM_RESEQUENCE — Renumbers accounting journal lines to preserve correct sequencing.
• INSERT_LINKS_SEGMENTS — Creates the segment and link associations required by the XLA data model.
• UPGRADE_ROLLBACK and CRASH_RECOVERY — Provide controlled rollback and recovery from interrupted runs.

Documentation of the deployed package additionally lists VALIDATE_RECOVERY_MODE, VALIDATE_FINAL_MODE, RETRIEVE_VALIDATE, INSERT_DATA, and HISTORIC_WORKER, which govern mode-specific validation, iterative validation retrieval, bulk insertion, and the worker routine that processes historical data volumes.

Tables Accessed

The package reads and writes reference and transactional tables through APPS synonyms:

• GL_LEDGERS, GL_LEDGER_RELATIONSHIPS — Identify the primary and reporting ledgers and their relationship.
• GL_PERIOD_STATUSES — Determine open and closed period status for the conversion range.
• GL_COA_MAPPINGS, GL_ACCTS_MAP_INT_GT — Supply account mapping rules and interim mapping data for code combinations.
• FND_CURRENCIES — Provides currency definitions used in rate conversion.
• XLA_RC_UPGRADE_RATES — Stores conversion rates populated by POPULATE_RATES.
• XLA_ACCOUNTING_BATCHES_S, XLA_AE_HEADERS, XLA_AE_HEADERS_S, XLA_AE_LINES, XLA_DISTRIBUTION_LINKS — The core XLA journal and distribution structures written during insertion.
• XLA_ACCTG_METHOD_RULES — Accounting method rules governing entry generation.
• XLA_HISTORIC_CONTROL, XLA_HISTORIC_MAPPING_GT — Control and interim staging tables that track upgrade progress and mappings.

Usage Notes

In practice, XLA_HIST_LEDGER_UPG_PKG is invoked as part of the historical subledger upgrade process during the transition from 11i to R12 and its later maintenance releases. It is typically launched through a concurrent program wrapper that supplies ledger, period, and mode parameters to UPG_MAIN. Because the package performs bulk conversion, failsafe procedures such as UPGRADE_ROLLBACK and CRASH_RECOVERY should be understood before execution, and the pre- and post-validation procedures should be run within the same controlled session. The package is referenced by no other database packages, reinforcing that it is a standalone utility rather than a building block for application extensions. Custom code should not depend on its procedures, as the interface is internal and subject to change across releases.