Results for “get_assignment_measures”

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

Overview

PA_ASSIGNMENT_UTILS is a foundational PL/SQL utility package in the Oracle EBS Projects (PA) module, owned by the APPS schema. It provides the core reusable logic that governs project resource assignments — the records that link people (and other resources) to projects and tasks with a defined role, start and end dates, and a staffing status. In Oracle EBS 12.1.1 and 12.2.2, this package underpins assignment validation, status classification, competency checking, and person-assignment retrieval throughout the Projects suite.

The package is classified as a utility (OTHER) API rather than a public business API. It is consumed by twenty-one other database objects across the Projects and related modules, making it a low-level service layer relied upon by higher-level packages such as PA_ASSIGNMENT_APPROVAL_PUB, PA_TASK_ASSIGNMENT_UTILS, PA_RESOURCE_UTILS, and PA_PLANNING_RESOURCE_UTILS. It standardises the rules for interpreting assignment status values, validating incoming assignment data, and returning derived information, ensuring consistent behaviour between the assignment forms, concurrent programs, and integration interfaces.

Key Procedures and Functions

The ETRM metadata documents thirty-three procedures and functions. The principal ones include:

• Status classification functions — IS_CONFIRMED_STATUS, IS_PROVISIONAL_STATUS, IS_ASGMT_IN_OPEN_STATUS, IS_OPEN_ASGMT_CANCELLED, IS_STAFFED_ASGMT_CANCELLED, and IS_ASGMT_FILLED evaluate an assignment's system status and return boolean or flag results indicating its lifecycle state (open, staffed, confirmed, provisional, cancelled). These centralise the status semantics used across staffing workflows.
• Validation procedures/functions — CHECK_STATUS_IS_IN_USE, CHECK_PROJ_ASSIGNMENTS_EXIST, CHECK_ASSIGNMENT_NUMBER_OR_ID, CHECK_STF_PRIORITYNAME_OR_CODE, CHECK_INPUT_SYSTEM_STATUS, VALIDATE_ASGMT_COMPETENCY, and IS_ASGMT_ALLOW_STUS_CTL_CHECK verify that input values are valid, that referenced assignments or statuses exist, and that the project's status controls permit the requested operation.
• Retrieval functions — GET_PROJECT_ID, GET_PERSON_ASGMT, GET_ASSIGNMENT_MEASURES, GET_DEF_ASGMT_STATUSES, GET_ROLE_ACTIVITY_TEXT, and GET_ROLE_ACTIVITY_DATE return project identifiers, person assignment records, measured values, default statuses, and role activity descriptions/dates.
• Messaging helpers — ADD_MESSAGE integrates with the FND message stack (FND_MSG_PUB, FND_NEW_MESSAGES) to register errors and warnings during validation.

Tables Accessed

The package reads and writes core Projects and HR tables through APPS synonyms. Assignment data resides in PA_PROJECT_ASSIGNMENTS and PA_RESOURCE_ASSIGNMENTS, with denormalised resource data in PA_RESOURCES_DENORM. Project context comes from PA_PROJECTS_ALL, PA_PROJECT_STATUSES, and PA_PROJECT_STATUS_CONTROLS (which determine whether a status change is permissible). Team and planning data are drawn from PA_TEAM_TEMPLATES, PA_PROJECT_PARTIES, PA_FIN_PLAN_TYPES_B, PA_FORECAST_ITEMS, and PA_PROJ_FP_OPTIONS. Resource transaction attributes come from PA_RESOURCE_TXN_ATTRIBUTES, and person-level details from PER_COMPETENCES. Implementation and operational settings are read from PA_IMPLEMENTATIONS. It also depends on FND_PROFILE for profile option values.

Usage Notes

PA_ASSIGNMENT_UTILS is not typically invoked directly by end users; rather, it is called by the Assignment, Staffing, and Team forms as their underlying validation and derivation engine, and by concurrent processes and public APIs (notably PA_ASSIGNMENT_APPROVAL_PUB and the resource and task assignment utilities). Custom extensions and interface programs that create or update project assignments should reuse these functions to obtain the same status interpretation and validation behaviour as the standard product, avoiding hard-coded status logic. Because the package is a dependent utility with no documented dependents of its own, its signatures are stable but considered internal; custom code should reference it cautiously and be retested during upgrades between 12.1.1 and 12.2.2.