Search Results header_offer_flag

Overview

APPS.BIM_FCTV_ORDER_OFFERS is a read-only Oracle EBS view that correlates order lines captured in Oracle Order Management with the promotional offers or price-list adjustments that were applied to them through Oracle Advanced Pricing and Oracle Marketing (AMS). The view exposes a normalized relationship between an order header, its lines, the activity offer that generated a price adjustment, and a flag indicating whether that offer was applied at the header level rather than to a specific line. The HEADER_OFFER_FLAG column, which is what most users search for, returns 'Y' when the cited price adjustment record carries no line identifier — meaning the offer applied to the entire order — and 'N' otherwise. The view is defined with the WITH READ ONLY clause, so it can be queried but never used as a DML target. It serves reporting, diagnostic, and integration purposes in both 12.1.1 and 12.2.2, particularly where the business needs to reconcile which offers were honored against which order lines and whether those offers were header-level or line-level.

Underlying Base Objects

The view is constructed from three primary sources joined together, and its metadata references several supporting objects.

• ASO_I_ORDER_LINES_V — the order-lines view providing HEADER_ID and LINE_ID; aliased as ODL.
• ASO_I_ORDER_PRICE_ADJS_V — the price-adjustment view supplying HEADER_ID, LINE_ID, LIST_HEADER_ID, and APPLIED_FLAG; aliased as ADJ.
• AMS_ACT_OFFERS (a synonym) — the Oracle Marketing activity-offers table, providing QP_LIST_HEADER_ID and ACTIVITY_OFFER_ID; aliased as OFFR.

The documented metadata additionally lists OE_PROFILE and QP_PRICE_LIST_PVT as referenced base objects, reflecting the pricing and order-entry profile packages that support the underlying ASO views. The join condition ties order lines to price adjustments on HEADER_ID, ties offers to adjustments on LIST_HEADER_ID = QP_LIST_HEADER_ID, restricts to applied adjustments (APPLIED_FLAG = 'Y'), and matches line identity with the NVL(ADJ.LINE_ID, ODL.LINE_ID) construct so that header-level adjustments still align to every line on the order.

Key Columns

• ORDER_HEADER_ID — the order header identifier, defaulted to -999 via NVL when no source value exists.
• ORDER_LINE_ID — the order line identifier, likewise defaulted to -999.
• OFFER_ID — the activity offer identifier from AMS_ACT_OFFERS, defaulted to -999.
• HEADER_OFFER_FLAG — a DECODE over ADJ.LINE_ID yielding 'Y' when the adjustment has no line identifier (header-applied) and 'N' when it does (line-applied).

Common Use Cases and Queries

Typical uses include auditing which offers were honored, identifying header-level versus line-level promotions, and feeding downstream integration or reconciliation reports.

SELECT ORDER_HEADER_ID, ORDER_LINE_ID, OFFER_ID, HEADER_OFFER_FLAG
FROM   APPS.BIM_FCTV_ORDER_OFFERS
WHERE  ORDER_HEADER_ID = :p_header_id;

SELECT HEADER_OFFER_FLAG, COUNT(*)
FROM   APPS.BIM_FCTV_ORDER_OFFERS
GROUP  BY HEADER_OFFER_FLAG;

Because the view is read-only, it is safe for concurrent reporting and extracts. Queries returning -999 sentinel values should be treated as unmatched rows rather than valid low identifiers.