Results for “oefv_discount_lines”

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

Overview

OEFV_DISCOUNT_LINES is a reporting view in the Oracle Order Entry (OE) module of Oracle E-Business Suite. It presents the discount line records associated with order discounts, exposing the qualifying entity against which a discount is applied — an inventory item or a customer purchase order — together with the discount percentage, amount, and price. The view is described in ETRM metadata as a "retrofitted" object, meaning it originated in an earlier release and has been carried forward for compatibility rather than reengineered for current data models.

ETRM documentation explicitly records the implementation status as "Not implemented in this database." In ETRM 12.2.2 the view metadata records no owner and no referenced base objects. These facts indicate that OEFV_DISCOUNT_LINES is not a shipped, supported database object in a standard 12.1.1 or 12.2.2 installation. Its primary value is therefore as a reference pattern for how discount lines are denormalized for reporting, not as a directly queryable seeded view.

Underlying Base Objects

Although ETRM lists no referenced base objects, the documented view text establishes the underlying tables unambiguously:

• SO_DISCOUNT_LINES (aliased DISCOUNTLN) — the driving table holding percent, amount, price, active dates, discount line identifier, discount identifier, entity identifier, and entity value.
• SO_DISCOUNTS (aliased DISCOUNT) — the discount header supplying the discount name.
• SO_ENTITIES (aliased ENTITY) — the entity type definition supplying the entity name.
• MTL_SYSTEM_ITEMS_KFV (aliased ITEM) — the concatenated inventory item segments, joined only in the item branch of the union.

The view is a UNION of two branches. The first branch (TYPE = ITEM) filters on ENTITY.ENTITY_ID = '1001' and joins to MTL_SYSTEM_ITEMS_KFV, restricting items to the operating unit returned by FND_PROFILE.VALUE_SPECIFIC('SO_ORGANIZATION_ID'). The second branch (TYPE = CUSTOMER_PO) populates a different positional column with ENTITY_VALUE, interpreted as a purchase order number.

Key Columns

• PERCENT, AMOUNT, PRICE — discount rate, fixed amount, and price basis from SO_DISCOUNT_LINES.
• START_DATE_ACTIVE, END_DATE_ACTIVE — validity window of the discount line.
• A literal token — shown as '_DF:OE:SO_DISCOUNT_LINES:DISCOUNTLN', identifying the descriptor-flexfield source.
• DISCOUNT.NAME — the discount name.
• ENTITY.NAME — the entity type name (for example, item or customer PO).
• DISCOUNT_LINE_ID, DISCOUNT_ID — primary and foreign keys linking to the discount header.
• ENTITY_ID — the entity type's identifier; ENTITY_VALUE — the discounted entity's value, reused as INVENTORY_ITEM_ID in the item branch.
• CONCATENATED_SEGMENTS — the inventory item's concatenated key flexfield segments.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY.

Common Use Cases and Queries

Because the view is not implemented, teams generally reconstruct equivalent logic directly against the base tables. The metadata nonetheless documents the reporting intent: presenting item and customer purchase order qualifiers side by side for a discount. The relevant search term agreement_type maps loosely to this behavior — the view distinguishes discount qualifier types (item versus customer PO) in a single, positionally aligned result set.

A representative query against the underlying tables is:

• SELECT d.discount_id, d.name, l.discount_line_id, l.percent, l.amount, l.price, l.start_date_active, l.end_date_active, e.name entity_type, l.entity_id, l.entity_value FROM so_discount_lines l, so_discounts d, so_entities e WHERE l.discount_id = d.discount_id AND l.entity_id = e.entity_id;

To reproduce the item branch, add AND l.entity_id = 1001 and join MTL_SYSTEM_ITEMS_KFV on l.entity_value = item.inventory_item_id. For the customer PO branch, read ENTITY_VALUE as the purchase order number. Analysts should confirm entity type identifiers in SO_ENTITIES before relying on the literal '1001' shown in the documented view text, as values may differ by environment.