Search Results oe_discount_lines




Overview
Explore in AI Chat

Overview

APPS.OE_DISCOUNT_LINES_115_V is a compatibility view in the Oracle E-Business Suite Order Management (ONT) schema. It exposes discount line data stored in the base table OE_DISCOUNT_LINES, but restricts its result set to rows in which CUSTOMER_ITEM_ID is NULL. The view derives its name from the historical 11.5.x (11i) data model, in which customer-item-specific discount lines were not yet supported at the row level. By filtering out customer-item-scoped records, the view preserves the column and semantic shape that 11i-era reports, forms, concurrent programs, and integrations expect. Because it is a view and not a table, it holds no data of its own and reflects the current contents of its underlying synonym in real time.

In EBS 12.1.1 and 12.2.2, this object is typically retained for backward compatibility. Standard functionality has moved to the richer OE_DISCOUNT_LINES table and its surrounding pricing and discount APIs. Customizations, legacy reports, and third-party integrations that still reference the 115 view continue to function, but they only ever see the discount lines that are not tied to a specific customer item.

Underlying Base Objects

According to the ETRM metadata, the view is owned by APPS and is defined over one referenced base object, OE_DISCOUNT_LINES, which is exposed in the APPS schema as a synonym, along with the QP_VIEW_UTIL package. The view text is a straightforward SELECT with a WHERE clause restricting output to rows where CUSTOMER_ITEM_ID IS NULL.

The relationship to OE_DISCOUNT_LINES is therefore one-to-one for qualifying rows. Notably, the view does not project the CUSTOMER_ITEM_ID column from the base table. Instead it substitutes the literal NULL in that column position (annotated in the source as NULL, /* CUSTOMER_ITEM_ID */), followed by ENTITY_ID and ENTITY_VALUE. This means consumers cannot distinguish a genuinely absent customer item from a filtered one through the view — consistent with the legacy contract. QP_VIEW_UTIL is the Oracle Advanced Pricing view utility package commonly used to construct pricing-related compatibility views, though the documented view text itself is a static SELECT rather than a runtime-generated statement.

Key Columns

  • DISCOUNT_LINE_ID — Primary identifier of the discount line, inherited from OE_DISCOUNT_LINES and used to join to related discount records.
  • DISCOUNT_ID — Foreign key identifying the parent discount definition to which the line belongs.
  • CUSTOMER_ITEM_ID — Present in the projection but always NULL in this view, because the WHERE clause excludes any row where this column is populated.
  • ENTITY_ID / ENTITY_VALUE — The discount qualification entity and its value, defining which pricing or customer entity the line applies to.
  • PERCENT, AMOUNT, PRICE — The discount value, expressed as a percentage, a fixed amount, or a price, depending on how the discount line is configured.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date window governing when the discount line is active.
  • CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield (DFF) context and attribute columns for customer-defined data.
  • Audit and concurrency columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and the PROGRAM_* / REQUEST_ID columns that identify the concurrent program and request that last modified the row.

Common Use Cases and Queries

The view is most often used by legacy 11i reports and integrations that were authored before customer-item-level discount lines were introduced, and by support teams troubleshooting pricing discrepancies between historical and current data. A basic query lists all non-customer-item discount lines for a given discount:

  • SELECT discount_line_id, discount_id, entity_id, entity_value, percent, amount, price, start_date_active, end_date_active FROM apps.oe_discount_lines_115_v WHERE discount_id = :p_discount_id;
  • SELECT discount_line_id, discount_id, amount, percent FROM apps.oe_discount_lines_115_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));
  • SELECT l.discount_line_id, l.discount_id, l.entity_value, l.attribute1 FROM apps.oe_discount_lines_115_v l WHERE l.context = :p_context AND l.entity_id = :p_entity_id;

Because results exclude customer-item rows, comparisons against the full OE_DISCOUNT_LINES table are useful for quantifying how many discount lines fall outside the legacy scope. When migrating or re-implementing, teams should confirm whether downstream code genuinely requires the 11i projection, or whether the base table should be queried directly to capture customer-item-specific discount data.