Search Results check_suppliername_or_id

Overview

PA_PLANNING_RESOURCE_UTILS is an internal PL/SQL utility package in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema. It provides reusable helper logic for project planning and resource management, principally the retrieval and validation of resource-related codes and attributes used across resource lists, resource assignments, and resource breakdown structures. The package is classified under ETRM as an OTHER API, meaning it is not a public, supported interface but rather a shared internal library consumed by other Project applications code. Its source header indicates a 2006 vintage (PARPRLUS.pls 120.2), and it remains present through EBS 12.1.1 and 12.2.2.

The package is referenced by 25 other packages, confirming its role as a foundation utility rather than a user-facing entry point. Functions such as GET_RES_MEMBER_CODE, GET_MEMBER_FIN_CAT_CODE, and GET_RESOURCE_CODE translate numeric identifiers held on planning rows into the descriptive codes planners and downstream processes require.

Key Procedures and Functions

The documented interface comprises 55 procedures and functions. The most prominent groups are:

• Code lookup functions — GET_RES_MEMBER_CODE, GET_MEMBER_FIN_CAT_CODE, GET_MEMBER_INCUR_BY_RES_CODE, GET_RES_TYPE_CODE, GET_RESOURCE_CODE, GET_INCUR_BY_RES_CODE, and GET_FIN_CATEGORY_CODE return descriptive codes for a supplied resource list member, resource format, resource assignment, or related identifier. The user search term "get_plan_res_combination" reflects this family of lookup routines used when resolving plan resource combinations.
• Validation procedures — VALIDATE_RESOURCE, VALIDATE_ORGANIZATION, VALIDATE_SUPPLIER, CHECK_SUPPLIERNAME_OR_ID, CHECK_PERSONNAME_OR_ID, CHECK_JOBNAME_OR_ID, CHECK_BOM_EQLABOR_OR_ID, CHECK_ITEMCAT_OR_ID, and CHECK_INVENTORYITEM_OR_ID confirm that a planning resource reference is valid for the given organization, supplier, person, job, or item context.
• Existence checks — CHK_SPREAD_CURVE_IN_USE and CHK_NLR_RESOURCE_EXISTS test whether a spread curve is referenced and whether a non-labor resource exists.
• Defaults — DEFAULT_EXPENDITURE_TYPE and DEFAULT_RATE_EXPENDITURE_TYPE derive the expenditure type (and rate expenditure type) applicable to a planning resource.

All standard "who" columns (created_by, creation_date, last_updated_by, last_update_date, last_update_login) are initialised from FND_GLOBAL.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

• Planning and project core — PA_PROJECTS_ALL, PA_BUDGET_VERSIONS, PA_ALL_ORGANIZATIONS, PA_EXPENDITURE_CATEGORIES, PA_EXPENDITURE_TYPES, PA_EVENT_TYPES: supply project, budget version, organization, and expenditure classification context.
• Resource definition — BOM_RESOURCES: source of non-labor resource definitions checked by CHK_NLR_RESOURCE_EXISTS.
• Inventory and item data — MTL_SYSTEM_ITEMS_B, MTL_CATEGORIES_B, MTL_CATEGORY_SET_VALID_CATS, MTL_UNITS_OF_MEASURE: validate inventory items, item categories, and units of measure for resource entries.
• HR and reference data — HR_ORGANIZATION_INFORMATION, FND_CURRENCIES, FND_LANGUAGES, FND_NEW_MESSAGES: organization attributes, currency and language lookups, and message retrieval.

Usage Notes

Because PA_PLANNING_RESOURCE_UTILS is an internal utility rather than a published API, it is normally invoked indirectly from Project Planning and Resource Management forms, concurrent programs, and other PA packages that need to resolve or validate a plan resource combination. Custom code should prefer documented public APIs; where PA_PLANNING_RESOURCE_UTILS must be called, the lookup functions are read-only and safe to invoke, while any routine performing inserts or updates inherits the calling transaction's commit semantics. The package relies on FND_GLOBAL session context, so it must be executed within an initialized EBS session.