Search Results igc_cc_reval_fix_process_pkg




Overview
Explore in AI Chat

Overview

The APPS.IGC_CC_REVAL_FIX_PROCESS_PKG package is a PL/SQL server-side component within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It forms part of the Oracle Grants / Contracts (IGC) application family, specifically the Contracts Core (IGC_CC) module. The package addresses the business requirement of revaluing and correcting contract commitment accounting entries that have already been interfaced or processed. In practical terms, it provides the technical mechanism to recalculate, adjust, or repair commitment control records when the original revaluation or period-close processing produced incorrect balances, misapplied rates, or incomplete accounting distributions. Its primary role is remedial, offering a programmatic pathway to reconcile contract commitments against General Ledger periods and to re-drive processing through the interface tables when standard concurrent processing has failed or produced inconsistent results.

Key Procedures and Functions

The ETRM metadata documents two procedures/functions within this package, neither of which exposes a documented parameter list. Accordingly, the descriptions below reflect purpose rather than signature.

  • REVALUE_FIX_MAIN — Serves as the main entry point or driver procedure for the revaluation correction process. It is logically responsible for orchestrating the overall fix workflow: identifying the period scope (via General Ledger period definitions and statuses), gathering the affected contract commitment records, invoking the core corrective logic, and managing the population of exception records when revaluation cannot be resolved automatically.
  • REVALUE_FIX — The core worker procedure that performs the actual revaluation adjustment against the identified contract commitment data. It is expected to read the source commitment distributions, recompute revalued amounts, and update the relevant accounting and interface records, while logging outcomes and exceptions for auditing and troubleshooting.

Both procedures rely on the SQL statements and package body logic embedded in the package, and the package is itself referenced internally by its own body as well as by IGC_CC_REP_YEP_PVT, a reporting/private API belonging to the same IGC Contracts Core module.

Tables Accessed

The package references the following base tables through APPS synonyms. Each is accessed for the reasons noted below.

  • FND_APPLICATION — Resolves the application context (application ID) required for concurrent and security processing.
  • GL_PERIODS, GL_PERIOD_STATUSES, GL_PERIOD_TYPES — Identify the valid accounting periods and their open/closed statuses, ensuring revaluation corrections are applied only to appropriate periods.
  • IGC_CC_HEADERS, IGC_CC_ACCT_LINES, IGC_CC_DET_PF — The core contract commitment header, accounting line, and detail/performance obligation records that hold the balances subject to revaluation and correction.
  • IGC_CC_ACTIONS, IGC_CC_PROCESS_DATA, IGC_CC_PROCESS_EXCEPTIONS — Drive processing state, retain intermediate results, and capture errors or exceptions that prevent successful revaluation.
  • IGC_CC_INTERFACE, IGC_CC_PERIODS — The interface staging table and contract commitment period table that connect the corrective revaluation to period-end processing.
  • PO_HEADERS_ALL — Supplies the associated purchasing document header information for commitments originating from procurement activity.

Usage Notes

This package is an internal processing utility rather than a user-facing form. It is typically invoked through:

  • Concurrent programs within the Contracts Core and Commitment Control processes, where administrators run revaluation and period-close remediation jobs.
  • Private API calls from sibling packages such as IGC_CC_REP_YEP_PVT, which reference it to obtain corrected revaluation figures for reporting.
  • Custom remediation scripts executed by technical consultants when standard commitment revaluation fails or produces out-of-balance results during month-end or year-end close.

Because the package writes directly to commitment accounting and interface tables, it should be executed only under controlled conditions, with prior validation of period statuses and appropriate database backups. Rows flagged in IGC_CC_PROCESS_EXCEPTIONS after execution require review before the correction is accepted.