Search Results pa_ci_impact_type_usage_pkg




Overview
Explore in AI Chat

Overview

PA_CI_IMPACT_TYPE_USAGE_PKG is an Oracle Application Object Library package owned by the APPS schema that supports the Oracle Projects (PA) application, specifically the Capitalized Interest (CI) subsystem. Capitalized interest processing in Oracle EBS allows organizations to calculate and capitalize interest costs associated with capital projects in accordance with accounting standards such as FAS 34. The impact type usage construct defines how a given capitalized interest impact type is applied or restricted across project classifications, project types, or other usage dimensions that determine the eligibility of interest calculation.

This package is a declarative, table‑maintenance API classified as OTHER in the EBS Technical Reference Manual (ETRM). It provides the standard Data Manipulation Language (DML) primitives—insert, update, delete, and a locking routine—that manage rows in the underlying Capitalized Interest impact type usage tables. It is not a business‑logic engine; rather, it encapsulates row‑level access so that the corresponding Product‑Specific View (PVT) layer and Oracle Forms can persist configuration data safely and consistently.

In both EBS 12.1.1 and 12.2.2 the object is reported with status VALID, and the 12.2.2 ETRM metadata identifies four documented procedures and confirms dependencies on SYS.STANDARD only. The package is referenced by one other package, PA_CI_IMPACT_TYPE_USAGE_PVT, which indicates the layered PL/SQL architecture typical of Oracle Projects.

Key Procedures and Functions

  • INSERT_ROW — Inserts a new impact type usage record, establishing the association between a capitalized interest impact type and the usage dimension it governs. It is the entry point for creating new configuration rows, typically generated by the maintenance form when a user adds a usage definition.
  • LOCK_ROW — Acquires a row‑level lock on an existing impact type usage record prior to modification or deletion. This enforces concurrency control so that two concurrent sessions cannot update the same usage definition simultaneously.
  • UPDATE_ROW — Modifies the attributes of an existing impact type usage record. This is invoked when a user or interface changes the properties of an existing association without creating a new row.
  • DELETE_ROW — Removes an impact type usage record, retiring the association. Deletion is subject to any referential or business validation enforced by the calling form or PVT layer.

The package contains no additional documented functions or procedures beyond these four DML wrappers.

Tables Accessed

  • PA_CI_IMPACT_TYPE_USAGE — The primary transactional table storing impact type usage definitions. All four procedures operate against this table.
  • PA_CI_IMPACT_TYPE_USAGE_S — The corresponding Oracle Applications sequence table used for surrogate key generation. INSERT_ROW typically derives the primary key from this sequence.

Both tables are accessed through APPS synonyms, which is the standard pattern for Oracle Applications packages so that code remains schema‑independent.

Usage Notes

This package is invoked indirectly rather than by end users directly. The primary caller is PA_CI_IMPACT_TYPE_USAGE_PVT, the product‑specific view layer that wraps these DML primitives with validation logic and exposes them to Oracle Forms and concurrent programs. The ETRM dependency list confirms that only PA_CI_IMPACT_TYPE_USAGE_PVT references the package.

Typical invocation paths include:

  • Oracle Projects Capitalized Interest setup forms where administrators define and maintain impact type usage configuration.
  • Concurrent programs or batch interfaces that load or migrate Capitalized Interest impact type usage data.
  • Custom extensions that need to manipulate impact type usage records programmatically; such code should call the PVT layer rather than this package directly to preserve validation and audit behavior.

Because the package is a low‑level DML wrapper, direct modification of the underlying tables or bypassing the PVT layer is not recommended. Version compatibility spans 12.1.1 and 12.2.2 with no documented change in the procedure surface, indicating a stable interface across releases.