Results for “business_area_name”

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

Overview

OKE_BUSINESS_AREAS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE – Project Contracts product family. Its status is VALID in both the 12.1.1 and 12.2.2 releases, and it exposes the set of business areas available for use within Project Contracts and related Oracle Projects functionality. Business areas provide a classification mechanism that allows contract, project, and billing data to be segmented by line of business, operating unit grouping, or internal organizational responsibility.

The view is not a transactional entity. It presents a filtered, denormalized projection of Oracle Application Object Library (FND) lookup values, restricted to the lookup type BUSINESS_AREA and to the owning application identifier 777. This design means the view inherits the standard behavior of Oracle lookups: rows are language-aware (through the underlying _VL view), can be date-effectivity controlled, and can be enabled or disabled without being deleted.

Because it is a view rather than a table, OKE_BUSINESS_AREAS_V is read-only. It is intended for query, reporting, and integration consumption rather than maintenance. Customers administer the underlying records through the standard Oracle lookup maintenance forms or the corresponding FND APIs, not by inserting into this view.

Underlying Base Objects

The view is defined over a single documented base object: FND_LOOKUP_VALUES_VL, the language-sensitive view on FND_LOOKUP_VALUES. The view definition applies two constant predicates: LOOKUP_TYPE must equal 'BUSINESS_AREA', and VIEW_APPLICATION_ID must equal 777. The presence of VIEW_APPLICATION_ID in the predicate is significant; it restricts the returned rows to lookups visible to the OKE application context, preventing business area values defined for other applications from leaking into Project Contracts reporting.

FND_LOOKUP_VALUES_VL itself combines FND_LOOKUP_VALUES with the language-specific lookup meaning and description, so the MEANING and DESCRIPTION columns returned by OKE_BUSINESS_AREAS_V are translated according to the session language of the querying user. There are no joins to OKE contract tables in this view; it is a pure lookup extraction, which is why it remains stable across the 12.1.1 and 12.2.2 releases.

Key Columns

• BUSINESS_AREA_CODE — Maps to LOOKUP_CODE. The unique, untranslated identifier for the business area, used as the stored value on transactional records.
• BUSINESS_AREA_NAME — Maps to MEANING. The translatable display name shown to users.
• DESCRIPTION — Optional descriptive text for the lookup value.
• START_DATE_ACTIVE — Beginning of the date range during which the business area is effective.
• END_DATE_ACTIVE — End of the effective date range; null for open-ended values.
• ENABLED_FLAG — Indicates whether the business area is currently enabled and selectable.

Common Use Cases and Queries

Typical uses include validating business area values in contract interfaces, populating value lists in custom forms and BI Publisher reports, and reconciling contract records against the active lookup set. Because date and enablement are exposed, the view is well suited to reporting only currently valid values.

Active business areas with names:

SELECT business_area_code,
       business_area_name,
       description
FROM   apps.oke_business_areas_v
WHERE  enabled_flag = 'Y'
AND    (start_date_active IS NULL OR start_date_active <= SYSDATE)
AND    (end_date_active   IS NULL OR end_date_active   >= SYSDATE)
ORDER BY business_area_name;

Count of enabled business areas by code:

SELECT business_area_code, COUNT(*)
FROM   apps.oke_business_areas_v
WHERE  enabled_flag = 'Y'
GROUP BY business_area_code;

Referencing the view in joins against OKE contract headers provides translated business area names without requiring application-specific lookup maintenance in each report.