Results for “get_project_manager”

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

Overview

PA_PROJECTS_MAINT_UTILS is a utility package body in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema. It provides a centralized library of validation, lookup, and cross-field verification routines that are consumed by the Oracle Projects maintenance forms and by other PL/SQL packages during the creation and maintenance of project records. Rather than implementing a single transactional interface, the package serves as a shared service layer: it resolves organization names and identifiers, verifies project statuses, customers, calendars, probabilities, and class categories, and derives commonly needed values such as the project manager and primary customer for a given project.

The package is classified as OTHER in the ETRM documentation, indicating that it is not a public, callable business API in the same sense as the PA_PROJECT_PUB family, but rather an internal helper used within and behind the standard Oracle Projects user interface. Its ETRM status is VALID, confirming that the compiled body is present and free of compilation errors in the documented 12.1.1 / 12.2.2 environments.

Key Procedures and Functions

The documented package exposes 34 procedures and functions. The principal groups are summarized below; parameter lists are intentionally omitted.

• Name/ID resolution checks: CHECK_ORG_NAME_OR_ID, CHECK_PROJECT_STATUS_OR_ID, CHECK_CUSTOMER_NAME_OR_ID, CHECK_PROBABILITY_CODE_OR_ID, and CHECK_CALENDAR_NAME_OR_ID validate that a supplied name or primary key resolves to a single, valid reference entity, supporting flexfield-style entry in the maintenance forms.
• Project party lookups: GET_PROJECT_MANAGER and GET_PROJECT_MANAGER_NAME return the project manager identifier and display name respectively; GET_PRIMARY_CUSTOMER and GET_PRIMARY_CUSTOMER_NAME perform the equivalent role for the primary customer.
• Class category rules: CLASS_CHECK_TRANS, CHECK_CLASS_CATG_CAN_DELETE, CHECK_DUPLICATE_CLASS_CATG, CHECK_CLASS_CATG_ONE_ONLY_CODE, and CHECK_CLASS_CATG_CAN_OVERRIDE enforce the structural rules governing project class categories, including delete eligibility, duplication prevention, single-code constraints, and override permissions.
• Change-control validations: CHECK_PROBABILITY_CAN_CHANGE and CHECK_PROJECT_OPTION_EXISTS gate modifications to probability and project option data.
• Billing and cost configuration checks: CHECK_BILL_JOB_GRP_REQ, GET_COST_JOB_GROUP_ID, CHECK_BILL_RATE_SCHL_EXISTS, and CHECK_CATEGORY_TOTAL_VALID verify billing job group requirements, resolve cost job group identifiers, confirm bill rate schedule existence, and validate category totals.

Tables Accessed

The package reads and, in some cases, writes to a broad set of operational tables through APPS synonyms. Project master data is held in PA_PROJECTS_ALL, with status validation driven by PA_PROJECT_STATUSES. Class category configuration is validated against PA_CLASS_CATEGORIES and PA_CLASS_CODES.

Probability validation uses PA_PROBABILITY_LISTS and PA_PROBABILITY_MEMBERS. Customer and party resolution relies on HZ_CUST_ACCOUNTS and HZ_PARTIES. Currency and calendar lookups use FND_CURRENCIES and JTF_CALENDARS_B, while messaging uses FND_NEW_MESSAGES. Financial verification logic touches PA_COST_DISTRIBUTION_LINES, PA_COST_DISTRIBUTION_LINES_ALL, PA_DRAFT_INVOICES, and PA_DRAFT_REVENUES.

Usage Notes

PA_PROJECTS_MAINT_UTILS is referenced by 31 other database objects and depends on PA_PROJECT_PVT, PA_PROJECT_UTILS, PA_INTERFACE_UTILS_PUB, FND_API, FND_MSG_PUB, and related utility packages. It is typically invoked from Oracle Projects maintenance forms and from companion packages such as PA_PROJECTS_MAINT that manage project definition. Because it is an internal helper rather than a published interface, custom code should treat it as unsupported and subject to change across releases, and should prefer the documented public APIs where one exists.