Search Results check_task_contract_asso

Overview

PA_PROJ_STRUCTURE_PUB is a public PL/SQL package in the APPS schema that governs the creation, maintenance, and publishing of the hierarchical project structure within Oracle Projects. In Oracle EBS 12.1.1 and 12.2.2, project structures define the relationships between projects, subprojects, tasks, and control items, and determine how work breakdown and reporting hierarchies are organized. This package encapsulates the business logic required to establish and modify those relationships, validate association rules between subprojects, tasks, and contracts, and stage structure records for mass processing. Its classification as a public (PUB) API indicates it is intended to be callable from other Oracle Projects modules and, where appropriate, from customer extensions. The package depends on FND_API for the standard EBS API error handling and message framework, and on PA_INTERFACE_UTILS_PUB for shared project interface utilities. It is itself referenced extensively by PA_PROJECT_CORE, PA_PROJECT_UTILS, PA_PROJ_ELEMENTS_UTILS, PA_TASK_UTILS, and recursively within its own package body, confirming its central role in the project structure domain.

Key Procedures and Functions

The package exposes thirteen documented procedures and functions:

• CREATE_RELATIONSHIP and DELETE_RELATIONSHIP — create and remove structural relationships between project entities, writing to the PA_OBJECT_RELATIONSHIPS repository that stores the project hierarchy.
• CHECK_SUBPROJ_CONTRACT_ASSO and CHECK_TASK_CONTRACT_ASSO — validation routines that verify whether a subproject or task is properly associated with a contract before structural changes are permitted.
• POPULATE_STRUCTURES_TMP_TAB — loads structure data into a temporary table in preparation for set-based processing.
• INSERT_PUBLISHED_RECORDS and INSERT_WORKING_RECORDS — bulk insert the published and working (unpublished) versions of structure records respectively.
• INSERT_PUBLISHED_RECORD and INSERT_WORKING_RECORD — single-record counterparts for incremental insertion.
• INSERT_UPD_WORKING_RECORDS and INSERT_UPD_PUBLISHED_RECORDS — combined insert-and-update processing for working and published records across the structure element versions.
• INSERT_SUBPROJECTS — creates subproject records within the structure hierarchy.
• POPULATE_PJI_TAB_FOR_PLAN_PRJ — populates the project interface staging structures used for planning project data.

Tables Accessed

The package operates primarily against the project structure and element tables. PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, and PA_PROJ_ELEM_VER_SCHEDULE hold the definitional and versioned/scheduled data for project elements. PA_PROJECTS_ALL and PA_PROJECT_STATUSES provide the project master and lifecycle status context. PA_OBJECT_RELATIONSHIPS stores the actual hierarchy relationships created and deleted by the package. PA_CONTROL_ITEMS and PA_CI_TYPES_B support control item structure definitions. PA_PERCENT_COMPLETES and PA_PROGRESS_ROLLUP are touched for progress measurement and rollup, while PA_PAGE_LAYOUTS supports structure presentation. Organization and party data — HR_ALL_ORGANIZATION_UNITS_TL, HZ_CUST_ACCT_SITES_ALL, HZ_LOCATIONS, and HZ_PARTY_SITES — are referenced for organizational and customer-site context on structure records.

Usage Notes

PA_PROJ_STRUCTURE_PUB is typically invoked indirectly through Oracle Projects forms and concurrent programs that manage project templates, work breakdown structures, and subproject hierarchies, rather than being called directly by end users. Because PA_PROJECT_CORE, PA_PROJECT_UTILS, PA_TASK_UTILS, and PA_PROJ_ELEMENTS_UTILS all reference it, most structure maintenance performed in the Projects window or via Project Templates flows through these APIs. Concurrent programs that publish project structures or roll up progress also rely on its insert and populate routines. Custom code should treat this as a PUB API and invoke it only after first calling the CHECK_* validation routines, observing the standard FND_API return status and message conventions. Direct DML against the underlying structure tables is discouraged, as the package maintains the versioning, working-versus-published state, and relationship integrity that those tables require.