Results for “check_resourcename_or_id”

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

Overview

PA_PROJECT_SEARCH_UTILS is a utility package in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema. It exists to support the Project Lists search enhancement intrinsic to Oracle Projects, providing name-to-ID conversion routines that allow users to enter a human-readable value — a customer name, a person name, or a resource name — and have the system resolve that value to the corresponding surrogate primary key. In ETRM 12.2.2 the package is classified as an "OTHER" API, meaning it is a supporting utility rather than a public, externally supported interface, and it is referenced by zero other packages.

The header comment (PAPRSUTB.pls 120.2, dated 2006) identifies the lineage of the routines: the name-to-ID logic was copied from PA_CUSTOMERS_CONTACTS_UTILS and then modified so that, when more than one identifier matches a given name, the routine returns at least one ID rather than failing outright. This behavior is deliberate and is documented as a requirement of the Project Lists search enhancement. Only the code that uses a name to derive an ID was retained in the copy.

Key Procedures and Functions

The package body exposes five documented program units:

• CONVERT_NAMETOID — The generic name-to-identifier conversion routine underlying the search enhancement. It accepts a textual name and returns the resolved identifier, together with a standard FND_API return status and error message code.
• CHECK_CUSTOMER_NAME_OR_ID — Validates a customer by ID or resolves a customer name to a customer ID. Per the documented source, it only queries when the incoming customer ID is NULL or FND_API.G_MISS_NUM and a customer name is supplied. It opens a cursor against the customer view, keeps the last ID fetched so that at least one ID is returned when multiple matches exist, and raises NO_DATA_FOUND when no ID matches the name. On NO_DATA_FOUND it returns G_RET_STS_ERROR with error code PA_CUSTOMER_ID_INVALID; on OTHERS it returns G_RET_STS_UNEXP_ERROR, logs the exception via FND_MSG_PUB.add_exc_msg, and re-raises.
• CHECK_PERSONNAME_OR_ID — The person counterpart to the customer routine. This is the procedure that matches the search term provided by the user. It resolves a person name (for example, an employee name held in PER_ALL_PEOPLE_F) to a person identifier, applying the same "return at least one ID" convention used across the package.
• CHECK_RESOURCENAME_OR_ID — The resource counterpart, resolving a resource name to its identifier for use in project search and resource-related list criteria.
• GET_PERF_MEASURES — Returns performance measure information used in the project search context.

Tables Accessed

ETRM 12.2.2 documents three base tables reached through APPS synonyms: FND_USER, PER_ALL_PEOPLE_F, and PLITBLM. FND_USER supplies the application user identity used for the person and resource name lookups. PER_ALL_PEOPLE_F is the effective-dated HR people table against which person names are matched for CHECK_PERSONNAME_OR_ID. PLITBLM is an Oracle Projects temporary/interface table used in the project search infrastructure. The published source excerpt additionally shows a query against the view pa_customers_v (customer_id, customer_name, status = 'A') in CHECK_CUSTOMER_NAME_OR_ID, which is how customer names are matched to identifiers.

Usage Notes

The package is an internal utility. It is not intended to be called directly by customer extensions, and ETRM records no dependent packages. It is invoked in practice by the Oracle Projects search and list-of-values infrastructure — for example when a user enters a customer, person, or resource name into a Project Lists search field and the framework must translate that name into the ID used by the underlying query. Callers are expected to inspect x_return_status against FND_API.G_RET_STS_SUCCESS and, on error, to read x_error_msg_code (such as PA_CUSTOMER_ID_INVALID) rather than relying on SQL exceptions, since the routines trap NO_DATA_FOUND and OTHERS and convert them to API statuses. Because the routines may return one arbitrarily selected ID when a name is ambiguous, they are unsuitable as a strict uniqueness check in custom code; they should be treated as a search convenience layer over the Project Lists feature.