Search Results pa_ci_impact_type_usage_pub




Overview
Explore in AI Chat

Overview

PA_CI_IMPACT_TYPE_USAGE_PUB is the public (PUB) API package for managing the relationship between Control Item impact types and their usage across Control Item type classifications in Oracle Projects. Control Items are the user-defined business objects that Projects uses to model additional information required at various points in the project lifecycle; each Control Item belongs to a Control Item type class, and each is subject to a set of impact types that determine how the item influences project data. The package body exposes the supported maintenance operations on the PA_CI_IMPACTS table, which stores those impact type usages, and it is the sanctioned entry point through which external callers—Oracle Forms, concurrent programs, or custom extensions—should create, update, or delete impact type usage records.

Key Procedures and Functions

  • CREATE_CI_IMPACT_TYPE_USAGE — Creates a new impact type usage row associating a given impact type code with a Control Item type class and specific Control Item type. In Release 12.1.2 and later the signature was extended with the P_IMPACT_TYPE_CODE_ORDER parameter, a numeric attribute that controls the display or processing sequence of impact types. The procedure returns the newly generated usage identifier and the standard return status, message count, and message data outputs.
  • UPDATE_CI_IMPACT_TYPE_USAGE — Modifies an existing impact type usage record, including reordering through the impact type code order attribute, and republishes the standard API output parameters.
  • DELETE_CI_IMPACT_TYPE_USAGE — Removes a specified impact type usage record from the repository.
  • DELETE_IMPACT_TYPE_USAGE_OK — A validation helper that determines whether deletion of a given impact type usage is permissible, allowing callers to enforce referential and business-rule constraints before invoking the delete operation.

Tables Accessed

  • PA_CI_IMPACTS — The primary table written by this package; it stores the mapping of impact types to Control Item type classes and Control Item types, including the ordering attribute introduced in the 12.1.2 setup enhancement.
  • PA_CONTROL_ITEMS — Referenced to validate the Control Item type context and to enforce integrity between impact type usage and the underlying Control Item definitions.
  • DUAL — Used for single-row lookups and housekeeping, consistent with standard PL/SQL API conventions.

Usage Notes

The package follows the standard Oracle EBS PL/SQL API pattern: it accepts P_API_VERSION, P_INIT_MSG_LIST, P_COMMIT, P_VALIDATE_ONLY, and P_MAX_MSG_COUNT, delegates processing to the private PA_CI_IMPACT_TYPE_USAGE_PVT package, and returns X_RETURN_STATUS, X_MSG_COUNT, and X_MSG_DATA. When P_VALIDATE_ONLY is set to 'T', no database changes are applied, which supports Forms-level validation before commit. The header comment confirms the ordering enhancement delivered in Release 12.1.2 (documented as 120.1), and the same source is shipped in 12.2.2. The package is referenced by one other package, so callers should treat it as a shared integration point and avoid direct DML against PA_CI_IMPACTS. Typical invocation is from the Control Items setup forms, from concurrent programs that mass-maintain impact type configurations, and from custom code performing data migration or setup replication across environments.