Results for “delete_staffed_assignment”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PA_STAFFED_ASSIGNMENT_PVT is a private PL/SQL package body in the Oracle E-Business Suite Projects (PA) module that encapsulates the core business logic for creating, modifying, and removing staffed resource assignments on projects. It functions as the implementation layer beneath the public assignment APIs, holding the procedural code that validates assignment attributes, derives denormalized resource data, and persists rows into the underlying project assignment and resource assignment tables. Because it is classified as a PVT (private) package, it is not intended for direct invocation by external callers; instead it is called by the public API surface and by other PA packages that need to manipulate assignment records within a controlled, validated transaction context.

The header comment (version 120.8.12010000.3, dated 2008/11/28) confirms that the package was maintained through the 12.1 code line and carried forward into 12.2.2. A debug profile option, PA_DEBUG_MODE, is initialized at package scope and controls the verbosity of diagnostic output, reflecting the package's role in high-volume, transactional assignment processing where traceability matters.

Key Procedures and Functions

The documented package exposes three procedures, each corresponding to a lifecycle operation on a staffed assignment:

• CREATE_STAFFED_ASSIGNMENT — Inserts a new assignment for a resource on a project. The declaring signature shows it accepts an Assignment_Rec_Type record from PA_ASSIGNMENTS_PUB, an assignment creation mode, an unfilled assignment status, resource source and location attributes (city, region, country code), a summarize-tasks flag, a budget version identifier, and commit/validate-only control flags. It returns the new assignment identifier, the ROWID of the inserted row, the resolved resource identifier, and the standard API return status.
• UPDATE_STAFFED_ASSIGNMENT — Applies changes to an existing staffed assignment, re-validating affected attributes and propagating any dependent denormalized values.
• DELETE_STAFFED_ASSIGNMENT — Removes a staffed assignment and performs the associated referential cleanup required to keep project resource data consistent.

The internal logic visible in the excerpt uses local variables to hold the working assignment record, a source assignment record for copy or reference scenarios, schedule basis flags, and message-collection state. This structure indicates that the package performs multi-step validation and accumulates messages before returning the API status to the caller.

Tables Accessed

The package references a broad set of APPS synonyms. Assignment data is written to and read from PA_PROJECT_ASSIGNMENTS and PA_RESOURCE_ASSIGNMENTS, with PA_PROJECT_PARTIES holding project-party relationships. Resource identity and attributes are resolved through PA_RESOURCES, PA_RESOURCES_DENORM, PA_RESOURCE_LIST_MEMBERS, PA_RESOURCE_TXN_ATTRIBUTES, and PA_RES_FORMATS_B. Location values are validated against PA_LOCATIONS. Budget and version context is drawn from PA_BUDGET_VERSIONS, while project context comes from PA_PROJECTS_ALL, PA_PROJECT_STATUSES, PA_PROJ_ELEM_VER_STRUCTURE, and PA_PROJ_WORKPLAN_ATTR. The package also reads PER_ALL_ASSIGNMENTS_F, linking the project assignment to the underlying HR assignment of the resource.

Usage Notes

PA_STAFFED_ASSIGNMENT_PVT is invoked indirectly. Standard entry points include the assignment-related Oracle Forms in the Projects suite, concurrent programs that mass-create or mass-maintain staffing, and the public PA_ASSIGNMENTS_PUB API, which delegates to this private body. Because two other packages reference it, customizations should avoid calling the PVT package directly; callers should use the public API so that validation, message handling, and commit semantics remain consistent. When debugging assignment creation failures, enabling the PA_DEBUG_MODE profile option surfaces the internal trace produced by this package. The validate-only and commit flags allow callers to perform dry-run validation before committing, which is the recommended pattern for bulk loading or integration with external staffing systems.