Results for “index_ffs”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.HXC_ARCHIVE_RESTORE_UTILS package is a utility package within the Oracle E-Business Suite Time and Labor (HXC) module. Its primary business function is to support the archive and restore operations performed against the core Time and Labor transactional tables. Time and Labor maintains large volumes of high-transaction data (timecards, time building blocks, attributes, and detail links), and the archive/restore process is used to offload and subsequently reload this data for performance, retention, and purge management. This package provides the validation, counting, and integrity-checking logic that surrounds those archive and restore operations, allowing the application to confirm that the number of rows in core tables and their corresponding backup (archive) tables match before and after the operation.

The package header is dated 2005 (version 120.4), indicating long-standing stability across the EBS 12.1.1 and 12.2.2 releases. It is classified as API type "OTHER" and is referenced by three other packages, positioning it as a shared infrastructure component of the Time and Labor archiving subsystem rather than an end-user-facing API.

Key Procedures and Functions

The documented package exposes eight procedures and functions, described below by purpose:

• CHECK_MAX_ERRORS — A function that evaluates the current error count against an allowed threshold, returning a Boolean result. It governs whether an archive/restore run should continue or abort based on the volume of accumulated errors.
• CHECK_DATA_CORRUPTION — A function that verifies data integrity for a given data set, returning a Boolean outcome. It detects mismatches or corruption introduced during an archive or restore cycle.
• CORE_TABLE_COUNT_SNAPSHOT — A procedure that captures a count snapshot of the primary (core) HXC tables, returning multiple OUT count values for each core transactional table. These counts form the baseline for later reconciliation.
• BKUP_TABLE_COUNT_SNAPSHOT — A procedure that captures a parallel count snapshot of the backup/archive (_AR) tables. Together with the core snapshot, it enables comparison of before/after row volumes.
• COUNT_CHUNK_CHECK — A procedure that performs chunk-level count comparisons, taking in the archive and core counts to validate that processed chunks are consistent.
• COUNT_SNAPSHOT_CHECK — A procedure that compares previously captured snapshots to determine whether the archive/restore result is valid.
• INCOMPATIBILITY_PG_RUNNING — A procedure that determines whether an incompatible concurrent process is currently running; it is used to prevent conflicting operations from executing simultaneously.
• UPD_WF_NOTIF_ATTRIBUTES — A procedure that updates Workflow notification attributes, supporting the notification behavior associated with the archive/restore lifecycle.

Parameter lists are intentionally omitted here; the caller should refer to the package body for exact signatures, as the header documents them inline.

Tables Accessed

The package reads and writes the following documented tables (via APPS synonyms):

• HXC_TIME_BUILDING_BLOCKS and HXC_TIME_ATTRIBUTES — the core timecard building blocks and attribute values that constitute Time and Labor transactional data.
• HXC_APP_PERIOD_SUMMARY, HXC_APP_PERIOD_SUMMARY_AR, HXC_TIMECARD_SUMMARY — summary and archived summary records used for reporting and period rollups.
• HXC_AP_DETAIL_LINKS, HXC_AP_DETAIL_LINKS_AR, HXC_TC_AP_LINKS, HXC_TC_AP_LINKS_AR, HXC_LATEST_DETAILS, HXC_TIME_ATTRIBUTE_USAGES — link and usage tables that connect timecards to attributes and periods.
• HXC_DATA_SETS — identifies the archive/restore data set being processed.
• FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS — used to detect running concurrent requests and to check for incompatible programs.

Usage Notes

This package is not intended for direct end-user invocation. It is most commonly called from the Time and Labor archive/restore concurrent programs and their supporting logic, where the count snapshots and integrity checks are executed automatically as part of the batch run. It may also be invoked from custom code or from other HXC packages that need to validate row counts or detect incompatible concurrent activity before performing maintenance. Because it depends on FND_CONCURRENT_REQUESTS, its checks are sensitive to the current concurrent manager state, and because it operates on high-volume transactional tables, invocation should be scheduled during controlled batch windows.