Results for “oe_ak_order_date_type_v”

32 results




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

Overview

OE_AK_ORDER_DATE_TYPE_V is a lightweight Oracle EBS database view owned by the APPS schema and registered as a VALID object within the Order Management (ONT) product family. Its design purpose is narrow and specific: it exposes the set of valid order date type codes that can be assigned to an order request in Oracle Order Management. These codes function as a controlled lookup list that governs selection of the "request date type" — the date basis used when an order header or line is scheduled, priced, or committed during order capture and fulfillment.

In the EBS reporting and integration layers, this view serves as a decoupled interface point. Rather than requiring external reports, concurrent programs, or third-party integrations to query OE_LOOKUPS directly, the view provides a stable, purpose-built projection that returns only the relevant lookup codes. This is consistent with the general Oracle EBS design pattern in which "AK" (attribute/known-set) style views bridge the Attribute framework and the underlying lookup tables, allowing LOV (List of Values) queries, flexfield validation, and descriptive flexfield contexts to resolve against the same controlled vocabulary used by forms.

Underlying Base Objects

Per the documented ETRM metadata for EBS 12.2.2 (which is also applicable to 12.1.1), OE_AK_ORDER_DATE_TYPE_V is defined over a single referenced base object:

  • OE_LOOKUPS (VIEW) — the Order Management lookup view that in turn resolves to the FND_LOOKUPS / lookup_types foundation table. OE_LOOKUPS exposes lookup_type and lookup_code combinations maintained via the Application Lookups form.

The view filter is highly selective, restricting rows to LOOKUP_TYPE = 'REQUEST_DATE_TYPE'. Consequently, it is tightly coupled to the seeded lookup type 'REQUEST_DATE_TYPE' and returns only those lookup codes active under that type. If the lookup type itself is renamed or disabled at the application level, this view inherits that behavior, since it is a pure pass-through definition with no stored data of its own.

Key Columns

The view exposes a single documented column:

  • ORDER_DATE_TYPE_CODE — the lookup code value that identifies a permissible request date type. Typical seeded values correspond to date bases such as the order's requested date, the promise date, or the scheduling date used by Order Management during fulfillment. This column is the value that a user selects on the order entry form and that is subsequently stored on order headers and lines.

Although only one column is documented, the mapping to OE_LOOKUPS means the underlying lookup record also carries associated meaning (description, enabled flag, tag) in the parent lookup definition. Any enrichment beyond the code itself must therefore be retrieved by joining back to OE_LOOKUPS or FND_LOOKUPS.

Common Use Cases and Queries

Typical uses include populating value sets and LOVs for custom forms, validating order date type values in inbound order APIs and interface tables, and generating reference reports that list available request date types for a given implementation.

Sample query to list all valid order date type codes:

SELECT ORDER_DATE_TYPE_CODE
  FROM APPS.OE_AK_ORDER_DATE_TYPE_V
 ORDER BY ORDER_DATE_TYPE_CODE;

To include the lookup description, join to the parent lookup view (note that OE_AK_ORDER_DATE_TYPE_V carries only the code):

SELECT d.ORDER_DATE_TYPE_CODE,
       l.MEANING
  FROM APPS.OE_AK_ORDER_DATE_TYPE_V d,
       APPS.OE_LOOKUPS l
 WHERE l.LOOKUP_TYPE = 'REQUEST_DATE_TYPE'
   AND l.LOOKUP_CODE = d.ORDER_DATE_TYPE_CODE;

Because the view returns a small, volatile lookup set, it is best used as a validation source rather than a reporting fact. For high-volume reporting, query the underlying FND_LOOKUPS table directly and cache results, since lookup values are maintained centrally and versioned by the lookup type lifecycle.