Search Results pa_plan_res_format

Overview

APPS.PA_RESOURCE_PREC_PUB is a public PL/SQL package body within the Oracle Projects (PA) module of Oracle E-Business Suite. Its purpose is to establish and expose the resource formatting precedence rules used throughout Oracle Projects planning and resource management functionality. The package encodes the ordered sequence in which resource name components — such as person name, job, organization, role, and assignment — are combined to build a display name for a project resource.

The central design element is the seeded collection of format definitions built from the pa_plan_res_format object type. Each entry pairs a numeric format identifier with a comma-delimited format string and a precedence rank. The package comment block explicitly records a design intent: format precedence should ultimately be seeded in a database table and bulk-loaded into a collection as the first step, rather than hard-coded in the package body. This indicates the current implementation is a transitional or legacy structure where the precedence data is compiled directly into PL/SQL.

The user search term "pa_plan_res_format" corresponds directly to the object constructor used to instantiate each format record within this package. Consumers searching for that identifier are typically tracing how resource display formats are defined and ordered.

Key Procedures and Functions

• FORMAT_PRECEDENCE_INIT — The single documented procedure in this package. Its role is to initialize the format precedence global variables. It populates the global format collection g_people_formats using a plan_res_formats nested-table constructor, supplying each element as a pa_plan_res_format instance. Each instance carries a format class or format code number, a literal format string, and a precedence sequence number. The procedure is declared with no parameters and returns no value; it simply seeds the package-level state.

The seeded format strings follow a recognizable grammar composed of tokens separated by commas. Tokens include PER (person), FN1 through FN4 (person name flex segments), ROL (role), ORG (organization), JOB, BML, and PTP. Precedence ranks run from 1 to at least 32 in the documented excerpt, with the highest priority assigned to person-based compound formats and lower priority to job- and role-oriented formats.

Tables Accessed

No database tables are referenced by this package through APPS synonyms according to the documented metadata. All format precedence data is defined as PL/SQL literals within the package body. This is consistent with the embedded comment acknowledging that the precedence rules have not yet been externalized into a seed table. Consequently, the package performs no SQL reads or writes and is purely an in-memory initialization routine.

Usage Notes

Because FORMAT_PRECEDENCE_INIT establishes global package variables, it is invoked during package initialization or as an explicit setup call before any dependent routine accesses the format collection. The metadata indicates the package is referenced by one other package, which presumably consumes the initialized precedence collection when formatting or resolving resource names.

Typical invocation paths include Oracle Projects planning pages, resource assignment and search forms where resource display names must be rendered deterministically, and any custom code that requires the same precedence ordering used by the standard application. When extending or troubleshooting resource name display behavior, developers should treat this package as the authoritative source of format precedence for release 12.1.1 and 12.2.2, noting that the hard-coded ordering differs from a table-driven model and must be patched at source level if precedence changes are required.