Search Results oe_ak_dep_plan_reqd_v




Overview
Explore in AI Chat

Overview

OE_AK_DEP_PLAN_REQD_V is a lightweight Oracle EBS view owned by the APPS schema and registered under the ONT (Order Management) product family. Despite its association with Order Management, the view is a generic lookup utility rather than a transactional order entity. Its sole purpose is to expose the seeded YES_NO lookup values from the FND_LOOKUPS foundation table, providing a controlled enumeration of valid "Yes"/"No" indicator codes for use throughout the E-Business Suite.

Within Oracle EBS 12.1.1 and 12.2.2, lookup-based validation is a core design pattern. Rather than hard-coding allowed values, Oracle stores configurable lists in FND_LOOKUPS and exposes them through narrowly scoped views such as this one. This abstraction means the set of returned rows is governed entirely by the lookup configuration in the application, not by any order-specific business logic. As a result, the view supports reporting, concurrent programs, Oracle Forms LOVs, OA Framework pages, and interface/API validation logic that must confirm a flag is either "Y" or "N" (or the enabled Yes/No codes defined for the instance). Its status is VALID in the documented metadata, confirming the object is compiled and queryable.

Underlying Base Objects

The ETRM metadata identifies two referenced base objects:

  • FND_LOOKUPS (VIEW) — the single data source named in the view's SELECT statement. FND_LOOKUPS is the runtime view over the lookup dictionary, and this development view selects from it with a fixed filter on LOOKUP_TYPE = 'YES_NO'.
  • FND_GLOBAL (PACKAGE) — referenced indirectly and typically invoked for session context functions such as FND_GLOBAL.USER_ID, FND_GLOBAL.RESP_ID, or FND_GLOBAL.LANG. Because lookups are language-sensitive, the effective language context supplied by FND_GLOBAL governs which translated description rows are returned.

The view defined in the documentation extracts the LOOKUP_CODE column from FND_LOOKUPS. The dependency on FND_LOOKUPS is therefore direct and read-only; no DML is performed through this object.

Key Columns

  • DEP_PLAN_REQUIRED_FLAG — the documented column exposed by the view. It returns the enabled LOOKUP_CODE values for the YES_NO lookup type, i.e., the codes representing Yes/No selections. In practice these resolve to values such as "Y" and "N".

Because the view text projects only LOOKUP_CODE, no descriptions, meanings, or tag columns are surfaced. Consumers requiring translated display text must join to FND_LOOKUPS or FND_LOOKUPS_TL themselves or query the lookup tables directly.

Common Use Cases and Queries

Typical scenarios include LOV population, Boolean-style flag validation in order interface programs, and report parameter domains. A representative query is:

  • SELECT DEP_PLAN_REQUIRED_FLAG FROM APPS.OE_AK_DEP_PLAN_REQD_V; — returns all enabled Yes/No codes.
  • SELECT DEP_PLAN_REQUIRED_FLAG FROM APPS.OE_AK_DEP_PLAN_REQD_V WHERE DEP_PLAN_REQUIRED_FLAG = 'Y'; — isolates the affirmative code.
  • Embedding the view inside a validation package to reject values outside the configured Yes/No set.

Because the view returns a small, static set of lookup codes, it carries negligible performance overhead. Its value lies in enforcing consistent, configuration-driven Yes/No handling across Order Management extensions and integrations in both 12.1.1 and 12.2.2 environments.