Search Results pa_ci_impact_tu_exist




Overview
Explore in AI Chat

Overview

APPS.PA_CI_IMPACT_TYPE_USAGE_PVT is a private PL/SQL package body within the Oracle E-Business Suite Projects (PA) module that manages the association between Control Item impact types and specific Control Item type definitions. Its central purpose is to maintain the PA_CI_IMPACT_TYPE_USAGE intersection entity, which records which impact types are valid or applicable for a given control item type class and control item type identification. This package is classified as a PVT (private) API, meaning it is not intended for direct external invocation but rather acts as the internal implementation layer beneath a corresponding public wrapper package, PA_CI_IMPACT_TYPE_USAGE_PKG, whose insert_row, update_row, and related procedures it calls to perform physical DML on the underlying table.

The user search term "delete_ci_impact_type_usage" corresponds directly to one of the four documented procedures in this package, indicating the user is likely investigating how impact type usage records are removed from the system, whether through a form, a concurrent process, or custom extension code.

Key Procedures and Functions

The package exposes four documented procedures, each following the standard EBS PL/SQL API conventions of p_api_version, p_init_msg_list, p_commit, p_validate_only, and the standard x_return_status, x_msg_count, and x_msg_data OUT parameters:

  • CREATE_CI_IMPACT_TYPE_USAGE — Validates that a duplicate association does not already exist for the given impact type code, CI type class code, and CI type ID combination. If a duplicate is found, it raises error message PA_CI_IMPACT_TU_EXIST and sets x_return_status to FND_API.G_RET_STS_ERROR. When validation succeeds and p_validate_only is not 'T', it invokes the public package's insert_row to persist the new record and returns the generated x_ci_impact_type_usage_id.
  • UPDATE_CI_IMPACT_TYPE_USAGE — Modifies an existing impact type usage record, applying the same duplicate-check semantics before delegating to the public package's update logic.
  • DELETE_CI_IMPACT_TYPE_USAGE — Removes a specified impact type usage record from PA_CI_IMPACT_TYPE_USAGE. The procedure accepts the identifying keys (impact type code, CI type class code, CI type ID, or the surrogate ID) and performs a delete through the public package after validating the record exists. This is the target of the user's search.
  • APPLY_CI_IMPACT_TYPE_USAGE — Propagates or applies the impact type usage configuration, likely cascading the association logic to related control item impact records in PA_CI_IMPACTS.

Tables Accessed

  • PA_CI_IMPACT_TYPE_USAGE — The primary table this package creates, updates, and deletes rows in. It stores the valid impact type / control item type combinations.
  • PA_CI_IMPACTS — Referenced in the apply logic to propagate impact definitions across control items.
  • PA_CI_TYPES_B — The base table defining control item types; used to validate the ci_type_id and ci_type_class_code foreign key values.
  • PA_CONTROL_ITEMS — Provides the control item context against which impact type usage is applied.
  • DUAL — Used in existence-check cursors such as check_exists for duplicate detection.
  • PLITBLM — The standard EBS PL/SQL index-by table type used for message handling.

Usage Notes

Because this is a PVT package, it is invoked indirectly. Oracle Projects forms (such as the Control Items setup form) call the public package PA_CI_IMPACT_TYPE_USAGE_PKG, which in turn calls these private procedures. Three other packages reference this package, indicating it serves as a shared implementation dependency. Custom code should never call the PVT package directly; instead, developers should invoke the public API, which preserves the same parameter contract while handling message stack initialization via fnd_msg_pub.initialize and error stacking via pa_debug.set_err_stack. The p_commit and p_init_msg_list flags allow callers to control transaction boundaries and message list lifecycle, making the procedures composable within larger transactional units.