Search Results delete_impact_type_usage_ok

Overview

The APPS.PA_CI_IMPACT_TYPE_USAGE_PUB package is a public PL/SQL API within Oracle Projects that governs the relationship between control item impact types and control item type classes. It allows callers to define, modify, and remove records that associate a specific impact type code with a given control item type, thereby controlling which impacts are considered applicable to particular classes of control items. The package is owned by APPS and is classified as a public (PUB) API, meaning it is intended for supported external invocation rather than internal-only use. It is declared with AUTHID CURRENT_USER and is referenced by one other package in the environment. The header comment dates the source to 2002, reflecting a long-standing, stable interface carried forward into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

• CREATE_CI_IMPACT_TYPE_USAGE — Creates a new association between an impact type and a control item type. The caller supplies the impact type code, control item type class code, and control item type identifier, along with standard API control parameters. The procedure returns the generated x_ci_impact_type_usage_id together with the standard x_return_status, x_msg_count, and x_msg_data outputs. Default creation and last-update audit values are sourced from FND_GLOBAL.
• UPDATE_CI_IMPACT_TYPE_USAGE — Modifies an existing impact type usage record. It is documented in the package metadata as one of the four public entry points, adjusting the attributes of a previously created association identified by its usage identifier or its natural key attributes.
• DELETE_CI_IMPACT_TYPE_USAGE — Removes an existing impact type usage record. It accepts the usage identifier or the combination of impact type code, control item type class code, and control item type identifier, and returns the standard return status and message outputs.
• DELETE_IMPACT_TYPE_USAGE_OK — A validation function that answers whether deletion of a given impact type usage is permissible. It accepts a p_impact_type_code and a p_ci_type_id and returns a VARCHAR2 result. This is the object most commonly referenced in the context of the search term delete_impact_type_usage_ok, since it allows a client to pre-check deletability before invoking the destructive delete procedure.

Tables Accessed

• PA_CI_IMPACTS — The primary table holding the impact type usage records created, updated, or deleted by this package.
• PA_CONTROL_ITEMS — Consulted to validate and resolve the control item type and its class against which impact types are associated.
• DUAL — Used for single-row evaluations, such as computing a boolean-style deletability result within DELETE_IMPACT_TYPE_USAGE_OK.

All three tables are accessed through APPS synonyms, consistent with the package's AUTHID CURRENT_USER declaration and its placement in the APPS schema.

Usage Notes

The package is typically invoked from Oracle Projects setup and maintenance flows, such as the control item and impact type configuration screens, as well as from concurrent programs and custom extensions that need to programmatically manage impact type usage. The API follows the standard EBS PL/SQL API pattern: callers should pass p_init_msg_list, p_commit, p_validate_only, and p_max_msg_count, then inspect x_return_status and retrieve messages via FND_MSG_PUB when x_msg_count exceeds zero. Because DELETE_IMPACT_TYPE_USAGE_OK returns a VARCHAR2 rather than raising an exception, callers should test the returned value before attempting DELETE_CI_IMPACT_TYPE_USAGE. As a PUB-classified API, it is the supported interface for these operations, and direct DML against the underlying tables should be avoided to preserve referential integrity and audit behavior.