Search Results pa_task_name_invalid

Overview

PA_CI_IMPACTS_PUB is the public application programming interface for Oracle Projects control item impacts. A control item (CI) represents a project-level change control object — for example, an approved change order, a scope change, or a baseline revision — that affects one or more tasks within a project. The PA_CI_IMPACTS_PUB package exposes the business logic required to create, update, and delete records that describe the impact of those control items on individual project tasks. It wraps an underlying private package, PA_CI_IMPACTS_PVT, which owns the actual insert, update, and delete DML and validations; the public package is responsible for API plumbing such as message list initialization, call validation, savepoint handling, commit control, and return-status communication through the standard FND_API conventions.

Key Procedures and Functions

The package documents three public procedures, each corresponding to a lifecycle operation on control item impact records:

• CREATE_CI_IMPACT — Creates a new impact record linking a control item to an impacted project task. The procedure accepts the control item identifier, impact type code, status code, descriptive text, implementation date and responsible party, and either an impacted task identifier or an impacted task name. When a task name is supplied instead of an identifier, the package resolves the name to a task_id. It exposes standard API parameters for validation-only mode, message list initialization, commit control, and maximum message count, and returns the generated impact identifier together with return status, message count, and message data.
• UPDATE_CI_IMPACT — Modifies an existing control item impact record, allowing attributes such as impact type, status, description, implementation date, implementer, and impacted task to be changed. It follows the same API conventions as CREATE_CI_IMPACT.
• DELETE_CI_IMPACT — Removes an existing impact record from the repository. It likewise observes the standard initialization, validation, and commit parameters of the package's public API contract.

Supporting logic in the body includes a local cursor, get_task_id, which resolves an impacted task name to its task_id by joining PA_TASKS to PA_CONTROL_ITEMS on project_id and matching the supplied task name and control item identifier. If no matching task is found, the message PA_TASK_NAME_INVALID is raised and the return status is set to error.

Tables Accessed

The package operates on three tables through APPS synonyms:

• PA_CI_IMPACTS — the primary transactional table holding impact records; written by create, update, and delete operations.
• PA_CONTROL_ITEMS — the control item master, referenced to establish the project context of the control item being acted upon.
• PA_TASKS — the project task master, queried by the get_task_id cursor to translate a task name into a task identifier.

Usage Notes

The package is classified as a public (PUB) API and is referenced by two other packages, indicating it is intended to be called by other application modules rather than consumed directly by end users. Typical invocations originate from Oracle Projects forms, concurrent programs, or custom PL/SQL extensions that need to register or maintain control item impacts programmatically. Callers should pass p_init_msg_list = 'T' to reset the FND message stack, use p_validate_only to perform validation without persisting changes, and set p_commit only when the caller wants the package to commit the transaction; otherwise the caller manages the commit boundary. Return status should always be checked against FND_API.G_RET_STS_SUCCESS, and message details retrieved via the standard FND_MSG_PUB retrieval routines.