Search Results create_ci_impact

Overview

PA_CI_IMPACTS_PVT is a private (PVT) PL/SQL API package body in the Oracle E-Business Suite Projects (PA) product family. It provides the core implementation logic behind the management of "CI impacts" — records that capture the effects of a change or change initiative against impacted project entities. In Oracle Projects terminology, "CI" refers to the change impact tracking that links a change (such as a scope change, engineering change, or project change) to the tasks, statuses, descriptions, and implementation details that are affected. The package follows the standard EBS PL/SQL API architecture: a public wrapper package normally exposes the calls, while this private package (_PVT) holds the actual insert, update, and delete logic and may be referenced directly only by other internal packages.

The source header ($Header: PACIIPVB.pls 120.1) indicates this is a long-standing, stable object delivered with the product and classified as "noship," meaning it is not shipped to customers for direct modification. It is relevant across EBS 12.1.1 and 12.2.2, both of which retain the PA_CI_IMPACTS data model.

Key Procedures and Functions

The ETRM metadata documents three procedures in the package body:

• CREATE_CI_IMPACT — Creates a new change impact record. It accepts the owning change identifier, impact type code, status code, description, implementation date, implemented-by user, implementation comments, and impacted task ID, and returns the generated CI impact ID plus standard API return status and message outputs. It first validates that a record with the same change and impact type does not already exist, raising error message PA_CI_IMPACT_EXIST if a duplicate is found. It initializes the FND message list, supports a validation-only mode, and delegates the physical insert to PA_CI_IMPACTS_pkg.insert_row.
• UPDATE_CI_IMPACT — Modifies the mutable attributes of an existing CI impact record, such as status, description, implementation date, implemented-by, and implementation comments.
• DELETE_CI_IMPACT — Removes an existing CI impact record. This is the procedure most commonly searched for as delete_ci_impact and is the supported programmatic route to eliminate a change impact row from PA_CI_IMPACTS.

Each routine adheres to the standard EBS API signature conventions: API version, message list initialization, commit control, validation-only flag, and consistent standard OUT parameters for return status, message count, and message data.

Tables Accessed

The package operates against the following documented tables through APPS synonyms:

• PA_CI_IMPACTS — The primary table, holding the change impact records created, updated, and deleted by this package.
• DUAL — Used in the existence-check cursor to detect duplicate change/impact-type combinations before creation.
• FND_USER — Referenced to resolve or validate the implemented-by user identity.
• HZ_PARTIES — Referenced for party-related detail, typically for person or organization information associated with the impact or its implementing user.

Usage Notes

Because this is a private API, application logic should not call PA_CI_IMPACTS_PVT directly. Instead, it is invoked through the corresponding public API package, which is itself called by Oracle Projects forms, concurrent programs, and any custom extensions that maintain change impact data. The package is documented as being referenced by two other packages, confirming its role as a shared internal component rather than an entry-point API.

Custom code that needs to remove a change impact should invoke the public delete API rather than issuing a direct DELETE against PA_CI_IMPACTS, so that the package's validation, message handling, and auditing behaviour are preserved. As with all EBS APIs, callers should supply a valid API version, honour the commit flag to control transaction boundaries, and inspect the returned status before proceeding.