Results for “oe_ak_default_line_set_v”

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

Overview

OE_AK_DEFAULT_LINE_SET_V is a lightweight Oracle EBS database view owned by the APPS schema and registered under the Order Management (ONT) product. Its purpose is narrow and highly specific: it exposes the set of valid values for the Request Date Type attribute used within Oracle Order Management's ordering and defaulting framework. The view returns a single column of lookup codes drawn from the OE_LOOKUPS view, filtered to the lookup type REQUEST_DATE_TYPE.

Because it is a view rather than a base table, it carries no independent data storage and introduces no maintenance overhead. In Oracle EBS 12.1.1 and 12.2.2 the object is reported as VALID, meaning it compiles cleanly against its underlying dependency. It functions as a semantic abstraction layer: rather than requiring developers or integrators to hard-code the lookup type string repeatedly, the view encapsulates that filter and presents a clean, purpose-built result set. This is a common design pattern in EBS, where seeded lookups are wrapped in convenience views so that reports, concurrent programs, and integration layers can query a stable interface.

Underlying Base Objects

The view is defined entirely over one referenced base object: OE_LOOKUPS, which is itself a view in the APPS schema. The documented view text is:

• SELECT LOOKUP_CODE FROM OE_LOOKUPS WHERE LOOKUP_TYPE = 'REQUEST_DATE_TYPE'

OE_LOOKUPS is the Order Management lookup repository and ultimately resolves to the FND_LOOKUP_VALUES / FND_LOOKUPS foundation tables, translated and filtered for the ONT application context. Consequently, OE_AK_DEFAULT_LINE_SET_V inherits all behavior of that chain: it is language-aware, respects the enabled/start-date/end-date semantics of the seeded lookup values, and reflects any customer-defined extensions added to the REQUEST_DATE_TYPE lookup type.

The relationship is therefore strictly one-to-many projection: OE_LOOKUPS is the parent, and this view selects a single projected attribute from the subset matching one lookup type. No joins, aggregations, or outer references are present in the documented definition.

Key Columns

• LOOKUP_CODE — The only column exposed. It contains the abbreviated code values that Oracle Order Management recognizes for the Request Date Type attribute. Typical seeded values correspond to scheduling behaviors such as request date, requested ship date, or arrival date semantics, depending on how the ordering flow consumes the value. Because the column is not aliased in the view text, it retains the native name LOOKUP_CODE.
• DEFAULT_LINE_SET — The ETRM metadata lists this name in the columns section of the object record. It denotes the defaulting line set context associated with the view's usage in the Order Management defaulting engine.

Notably absent are columns such as MEANING, DESCRIPTION, or ENABLED_FLAG. Consumers needing the translated display value must join back to OE_LOOKUPS or FND_LOOKUP_VALUES on LOOKUP_CODE.

Common Use Cases and Queries

The view is typically used to populate LOVs, validate user-entered or interface-loaded values, and drive conditional defaulting logic on order lines.

• Enumerating permissible request date types for a custom form or OAF region.
• Validating inbound order data before calling the Order Management APIs.
• Building reconciliation reports that classify order lines by request date type.

Sample queries:

SELECT LOOKUP_CODE FROM APPS.OE_AK_DEFAULT_LINE_SET_V;

SELECT v.LOOKUP_CODE, l.MEANING FROM APPS.OE_AK_DEFAULT_LINE_SET_V v, APPS.OE_LOOKUPS l WHERE l.LOOKUP_TYPE = 'REQUEST_DATE_TYPE' AND l.LOOKUP_CODE = v.LOOKUP_CODE;

Because the object is a simple projection, it is inexpensive to query and suitable for inclusion in high-frequency validation paths.