Results for “enabled_flag”

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

Overview

PA_RESOURCE_CLASS_RES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the Projects (PA) product family. It exposes a denormalized, join-based representation of resource classes together with their associated planning resource defaults, allowing reporting and integration logic to retrieve descriptive resource class attributes (code, name, description) and the enablement status maintained at the planning default level in a single query.

The view is validated and present in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a base table, it carries no independent storage and always reflects the current committed state of the underlying source objects. This makes it suitable for concurrent program extracts, BI Publisher reports, Oracle Reports, OAF-based inquiry pages, and external integrations that need a lightweight, join-free source for resource class information.

Underlying Base Objects

The view text joins two documented base objects:

• PA_RESOURCE_CLASSES_VL (view) — a translatable (_VL) view over resource class definitions. It supplies the descriptive attributes: RESOURCE_CLASS_ID, RESOURCE_CLASS_CODE, NAME, and DESCRIPTION.
• PA_PLAN_RES_DEFAULTS (synonym) — the planning resource defaults entity, which provides the ENABLED_FLAG driving whether the resource class is active in planning contexts.

The join is an equijoin on RESOURCE_CLASS_ID, correlating each resource class to its planning default row. Because PA_RESOURCE_CLASSES_VL is a translated view, the values of NAME and DESCRIPTION returned depend on the current session language, following standard EBS MLS behavior. APPS.PA_RESOURCE_CLASS_RES_V therefore inherits both the language sensitivity and the security context of the underlying objects.

Key Columns

• RESOURCE_CLASS_ID — the unique surrogate key of the resource class. This is the join column and the most reliable identifier for programmatic use; it is stable across descriptive changes.
• RESOURCE_CLASS_CODE — the user-defined or seeded short code for the resource class, used in business rules, costing and planning logic, and cross-reference validation.
• NAME — the translatable display name of the resource class, appropriate for report headings and lookup lists.
• DESCRIPTION — the translatable long description providing business context.
• ENABLED_FLAG — the planning default enablement indicator (Y/N). Rows with a value other than 'Y' are not active defaults and are typically filtered out of operational queries.

Common Use Cases and Queries

Typical scenarios include populating LOVs and report parameters for resource-class selections, validating that a resource class is enabled before it is used in a planning or costing transaction, and feeding resource class dimensions into a warehouse or external planning system.

The simplest listed view query returns all enabled resource classes:

• SELECT resource_class_id, resource_class_code, name FROM pa_resource_class_res_v WHERE enabled_flag = 'Y' ORDER BY resource_class_code;

A lookup-by-code query resolves a single resource class in a validation routine:

• SELECT resource_class_id, name, enabled_flag FROM pa_resource_class_res_v WHERE resource_class_code = :p_code;

For integration extracts, restrict the columns needed and filter on enablement to reduce the result set; for audit-style reporting, include DESCRIPTION and ENABLED_FLAG to show the full descriptive and status picture. Because the view performs an inner join, resource classes with no corresponding row in PA_PLAN_RES_DEFAULTS will not appear in the result — a behavior worth noting when reconciling counts against PA_RESOURCE_CLASSES_VL directly.