Results for “pa_resource_formats”

50+ results




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

Overview

PA_RESOURCE_FORMATS is a system-defined reference table in the Oracle E-Business Suite Projects (PA) module. It stores the valid combinations of resource transaction attributes that Oracle Projects recognizes when processing expenditure, event, and resource transactions. Each row defines a distinct "format" — a permitted attribute pattern — that constrains how resources may be described on a project transaction. The table is therefore foundational to resource validation, cost collection, and cross-charging logic across the Projects suite.

Following the heuristic Data Vault classification derived from its foreign-key structure, PA_RESOURCE_FORMATS is hub-leaning. The majority of the related tables (PA_RESOURCE_FORMAT_RANKS, PA_RESOURCE_LIST_MEMBERS, PA_RESOURCE_TXN_ATTRIBUTES) reference this table through RESOURCE_FORMAT_ID, indicating that PA_RESOURCE_FORMATS acts as a central entity from which dependent detail and association records radiate. This classification should be treated as a modeling suggestion rather than a formal declaration.

Key Information Stored

The table is defined in the PA schema and contains 21 documented columns in release 12.2.2. The surrogate primary key is RESOURCE_FORMAT_ID, enforced by the PA_RESOURCE_FORMATS_PK constraint. A documented unique index, PA_RESOURCE_FORMATS_U1, covers RESOURCE_FORMAT_ID and ZD_EDITION_NAME, the latter supporting the editioning mechanism used in 12.2 online patching. This composite index represents the closest candidate for a business key.

The most significant attribute columns are a set of flags that declare which resource attributes are permitted within a given format:

Standard Oracle who-columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide auditability, and DESCRIPTION supplies the user-facing name of the format.

Common Use Cases and Queries

Typical usage centers on resolving and validating the format assigned to a transaction, and on reporting which attribute combinations are enabled. A common query retrieves the descriptive name and flags for a known identifier:

  • SELECT resource_format_id, description, person_id_flag, job_id_flag, vendor_id_flag FROM pa_resource_formats WHERE resource_format_id = :p_id;

Administrators frequently list all formats that permit a given attribute, for example all formats that allow vendor references:

  • SELECT resource_format_id, description FROM pa_resource_formats WHERE vendor_id_flag = 'Y';

Because transaction attribute records in PA_RESOURCE_TXN_ATTRIBUTES and rank definitions in PA_RESOURCE_FORMAT_RANKS share the RESOURCE_FORMAT_ID key, join queries typically combine these tables to validate a transaction or to drive cost collection and cross-charge processing. Reports may also join PA_RESOURCE_LIST_MEMBERS to determine which resource lists use a given format.

Related Objects

The following objects depend on PA_RESOURCE_FORMATS through the documented foreign keys:

  • PA_RESOURCE_FORMAT_RANKS — references RESOURCE_FORMAT_ID; stores the ranking of attributes within a format.
  • PA_RESOURCE_LIST_MEMBERS — references RESOURCE_FORMAT_ID; associates formats with resource list definitions.
  • PA_RESOURCE_TXN_ATTRIBUTES — references RESOURCE_FORMAT_ID; holds the transaction attribute values governed by the format.

These three tables constitute the immediate dependent family and are the principal objects joined to PA_RESOURCE_FORMATS in both application logic and custom reporting.