Search Results g_org_role
Overview
PA_PROJECT_PUB is the public PL/SQL API package within the Oracle Projects (PA) module of Oracle E-Business Suite. Its primary business function is to provide a controlled, programmatic interface for the creation and maintenance of project structures, including the definition of project headers, organizational assignments, key members, classifications, and tasks. The package formulates and enforces business rules governing project setup, thereby shielding external callers from the underlying data model complexity in tables such as PA_PROJECTS and PA_TASKS.
The package body carries a source header identifying version 120.75.12010000.20, reflecting its maintenance lineage across the 12.1.1 and 12.2.2 releases. It is the executable counterpart to the PA_PROJECT_PUB specification and is catalogued in the ETRM as a public (PUB) API, meaning it is intended for invocation by other Oracle EBS components and by customer extensions.
Key Procedures and Functions
The package exposes 78 documented procedures and functions. Thematically, these fall into several functional groups:
- Project lifecycle: INIT_PROJECT, LOAD_PROJECT, EXECUTE_CREATE_PROJECT, CREATE_PROJECT, CLEAR_PROJECT, and CHECK_DELETE_PROJECT_OK collectively support initialization, population, validation, creation, and deletion of project records.
- Task management: ADD_TASK, LOAD_TASK, FETCH_TASK, DELETE_TASK, CHECK_ADD_SUBTASK_OK, CHECK_DELETE_TASK_OK, CHECK_UNIQUE_TASK_REFERENCE, and CHECK_UNIQUE_TASK_NUMBER govern task hierarchy operations and reference integrity.
- Assignment loading: LOAD_KEY_MEMBER, LOAD_ORG_ROLE, and LOAD_CLASS_CATEGORY load key member assignments, organization role assignments, and classification categories respectively. LOAD_ORG_ROLE is the routine most relevant to the user's search term, being the designated entry point for populating organizational role data associated with a project.
- Validation utilities: CHECK_UNIQUE_PROJECT_REFERENCE, CHECK_CHANGE_PARENT_OK, and CHECK_CHANGE_PROJECT_ORG_OK enforce uniqueness and structural re-parenting rules prior to committing changes.
The body defines package-level constants for error messaging, including G_ORG_ROLE, G_PROJECT_CODE, G_CUSTOMER_CODE, G_KEY_MEMBER, G_CLASS_CATEGORY_CODE, and G_TASK_CODE, which are used to construct consistent error text returned to callers.
Tables Accessed
The package reads and writes through APPS synonyms over the following documented tables:
- PA_PROJECTS, PA_IMPLEMENTATIONS, PA_OBJECT_RELATIONSHIPS, PA_OBJ_STATUS_CHANGES_S: core project definition, setup, and status-tracking data.
- PA_ALTERNATE_TASKS and related task structures: task definition and alternate numbering.
- PA_CLASS_CODES: classification categories applied to projects.
- PA_DRAFT_INVOICES, PA_DRAFT_REVENUES, AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL: financial reference data consulted during validation and project setup.
- HZ_CUST_ACCOUNTS and HZ_PARTIES: customer and party information used to resolve customer references.
- FND_NEW_MESSAGES: message retrieval for standardized error reporting.
- PA_PJI_PROJ_EVENTS_LOG: project events logging for integration with the projects event framework, plus PA_PROBABILITY_MEMBERS for probability and forecasting data.
Usage Notes
Because PA_PROJECT_PUB is classified as a public API, it is typically invoked from Oracle Projects forms, from concurrent programs that perform bulk project maintenance, and from custom PL/SQL extensions or interfaces that need to create or update project structures. Callers must observe the package's sequencing convention: INIT_PROJECT is called first to initialize the in-memory record, followed by LOAD_* calls to populate attributes such as key members, organization roles, classifications, and tasks, and finally EXECUTE_CREATE_PROJECT or CREATE_PROJECT to persist. LOAD_ORG_ROLE in particular is used during this loading phase to populate organizational role assignments, and it should only be called after INIT_PROJECT has established the session context. The package is referenced by 20 other packages, underscoring its role as a foundational interface within Oracle Projects. All callers must supply valid project IDs and rely on the package's validation routines to detect duplicate references or invalid hierarchy changes. Standard EBS error handling conventions apply, with messages sourced via FND_NEW_MESSAGES.