Search Results pa_ci_impact_type_usage_pvt




Overview
Explore in AI Chat

Overview

PA_CI_IMPACT_TYPE_USAGE_PVT is an Oracle EBS Applications private PL/SQL package (AUTHID CURRENT_USER) residing in the APPS schema. It supports the Oracle Projects Control Item impact-type usage framework, which governs how change orders and change requests affect projects, tasks, and control items. The package encapsulates the business logic required to associate impact types with control item type classes and control item types, and to persist, modify, apply, or remove those associations.

The header source identifies several global constants that mirror the standard API action vocabulary used throughout Oracle EBS: G_CREATE, G_UPDATE, G_VIEW, and G_ISSUE. Two additional constants, G_CHANGE_ORDER ('CHANGE_ORDER') and G_CHANGE_REQUEST ('CHANGE_REQUEST'), are directly relevant to the search term "g_change_order." These constants classify the change vehicle driving an impact-type usage record, distinguishing formal change orders from change requests during processing. The package also declares G_EXCEPTION_ERROR and G_EXCEPTION_UNEXPECTED_ERROR for structured error handling, plus the PL/SQL record type impact_rec_type and the collection type impact_tbl_type, both based on columns of PA_CI_IMPACT_TYPE_USAGE. These structures allow bulk processing of impact-type code sets.

Key Procedures and Functions

  • CREATE_CI_IMPACT_TYPE_USAGE — Creates a new impact-type usage record linking an impact type to a control item type. Parameters include the impact type code, CI type class code, and CI type ID, along with standard API parameters (p_api_version, p_init_msg_list, p_commit, p_validate_only, p_max_msg_count) and auditing attributes. A later enhancement added P_IMPACT_TYPE_CODE_ORDER to control display or processing sequence.
  • APPLY_CI_IMPACT_TYPE_USAGE — Applies the defined impact-type usage to the appropriate change context, evaluating whether the usage is triggered under a change order or change request and propagating the resulting impacts.
  • UPDATE_CI_IMPACT_TYPE_USAGE — Modifies an existing impact-type usage record, including changes to the impact type code or ordering, with standard validation and commit handling.
  • DELETE_CI_IMPACT_TYPE_USAGE — Removes an impact-type usage association, typically when a control item type no longer requires the given impact type.

Tables Accessed

  • PA_CI_IMPACT_TYPE_USAGE — The primary table holding impact-type-to-control-item-type usage definitions; the record and collection types are derived from its columns.
  • PA_CI_IMPACTS — Stores the impact records generated when usage is applied.
  • PA_CI_TYPES_B — Supplies base control item type definitions referenced by the CI type class and CI type ID.
  • PA_CONTROL_ITEMS — Provides control item context for validating and applying usages.
  • DUAL and PLITBLM — Utility tables used for single-row selects and PL/SQL table handling.

Usage Notes

As a PVT-class API, this package is not intended for direct customer invocation; it is called internally by the three referenced packages that form the public-facing control item change order processing layer. It typically executes from Oracle Projects forms (such as control item setup and change order entry) and from concurrent programs that process change order and change request impacts. The presence of p_commit and p_validate_only parameters allows calling code to control transaction boundaries and perform validation-only passes. The G_CHANGE_ORDER and G_CHANGE_REQUEST constants are used internally to branch logic based on change vehicle type. Customizations should target the calling public APIs rather than this private package, since its signature may change between patch levels.