Search Results apply_ci_impact_type_usage




Overview
Explore in AI Chat

Overview

The package APPS.PA_CI_IMPACT_TYPE_USAGE_PVT_W is a private PL/SQL wrapper used by Oracle Projects (PA) to manage the mapping between customer interface (CI) impact types and the impact usages that reference them. In Oracle EBS, an "impact type" defines a category of project or contract impact — for example cost, revenue, or scheduling effects — that can be recorded against a customer or project. Each impact type may be consumed by one or more usages, and this package provides the programmatic entry point for applying that usage configuration. The _PVT_W suffix identifies it as a private wrapper: the underlying business logic resides in a private package body, while this wrapper exposes a controlled, Rosetta-style interface suitable for service-oriented or bulk invocation. The package is compiled with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the owning APPS schema. The header comment (revision 120.0.12010000.1, dated 2009) confirms it is a long-standing, non-shipped ("noship") internal artifact.

Key Procedures and Functions

  • APPLY_CI_IMPACT_TYPE_USAGE — The principal public procedure. It accepts API versioning, message-list and commit control flags, a validation-only switch, a maximum message count, a UI mode indicator, the CI class code, and the CI type identifier, together with a PL/SQL table of impact-usage values passed through the Rosetta array mechanism. It returns the standard concurrent-style output parameters: return status, message count, and message data. This is the procedure a user reaches when searching for apply_ci_impact_type_usage.
  • ROSETTA_TABLE_COPY_IN_P9 — A generated helper that copies an incoming JTF_VARCHAR2_TABLE_100 collection into the strongly typed impact_tbl_type record structure used internally. The "_P9" suffix denotes the parameter position it serves within the Rosetta-generate
  • ROSETTA_TABLE_COPY_OUT_P9 — The complementary helper that copies the internal impact_tbl_type back out into a JTF_VARCHAR2_TABLE_100 collection for the caller.

Tables Accessed

The documented table referenced through APPS synonyms is PLITBLM, the PL/SQL message table used for storing and retrieving error and diagnostic messages generated during execution. Access to it is a consequence of the standard message-handling pattern implemented by the API, allowing the procedure to accumulate messages up to p_max_msg_count and return them via x_msg_count and x_msg_data. The actual CI impact-type usage records are manipulated by the underlying private package rather than directly here.

Usage Notes

This wrapper is not intended for direct customer invocation. It is typically called by other Oracle Projects components — most likely a private business-layer package or a service invocation generated according to the Rosetta integration pattern — when impact-type usage data must be validated or persisted for a given CI class and type. Because p_validate_only is exposed, callers can use the procedure in dry-run mode to check input before committing. The p_commit and p_init_msg_list parameters follow the standard EBS API convention, letting the caller decide transaction control and message-stack initialization.

Customizations should avoid calling this private wrapper directly; the supported approach is to invoke the corresponding public API or service that encapsulates it. The ETRM metadata records zero packages referencing it, and its classification is OTHER, reinforcing its role as an internal, unsupported interface. When troubleshooting impact-type usage behavior, this package name is useful mainly as a search anchor to locate the real business logic in the associated private package body.