Search Results ieu_lov_col4




Overview
Explore in AI Chat

Overview

The view APPS.AST_SOURCE_CODES_LOV_V is a reporting and integration object in Oracle E-Business Suite, defined in the APPS schema and owned by the Applications product family associated with Oracle Marketing (AMS) and TeleSales/CRM source tracking. Its role is to supply the values presented to users through a List of Values (LOV) that resolves campaign, event, offer, and source-code selections. In EBS 12.1.1 and 12.2.2 the view is consumed by form-based LOVs and by the Interaction/ETRM layer, where the column IEU_LOV_COL4 acts as the hidden identifier column expected by the LOV framework.

The distinctive feature of this view is that it is not a simple projection over a single source table. It joins source-code master data against the active offer and offer-usage context filtered by the current system date, so that the values surfaced to the LOV only include source codes that are currently valid and linked to active offers.

Underlying Base Objects

The documented ETRM metadata identifies three referenced base objects:

The Q + outer-join syntax throughout confirms that source codes remain visible even where no matching offer or lookup row exists; the offer and lookup predicates are therefore filters on optional context rather than mandatory driving conditions.

Key Columns

  • NAME — the descriptive name of the source code, displayed to the user in the LOV.
  • SOURCE_CODE — the code value assigned to the source record.
  • SOURCE_TYPE — the classification of the source, restricted by the view to 'EVEH', 'EVEO', 'CAMP', 'CSCH', and 'EONE', which broadly correspond to event headers, event offers, campaigns, campaign schedules, and one-to-one marketing entries.
  • IEU_LOV_COL4 — a derived identifier produced by TO_CHAR(SC.SOURCE_CODE_ID). It is the fourth LOV column referenced by the Interaction/ETRM search term and carries the numeric source-code ID as a character string for the LOV return value.

The DISTINCT keyword is required because the multiplication of source codes across offers and lookups would otherwise produce duplicate rows. Status filtering accepts 'ACTIVE', 'ONHOLD', and 'COMPLETED' source codes.

Common Use Cases and Queries

The view is chiefly used to populate LOV pickers in CRM and TeleSales forms, and in custom reports and interfaces that require the set of currently valid source codes with their offer context. A representative query restricting output to a single source type is:

  • SELECT name, source_code, source_type, ieu_lov_col4 FROM apps.ast_source_codes_lov_v WHERE source_type = 'CAMP' ORDER BY 1;

Because the view already enforces the date window through SYSDATE BETWEEN NVL(OFR.start_date, SYSDATE-1) AND NVL(OFR.end_date, SYSDATE+1), consumers obtain only source codes whose associated offer is temporally current. Query authors should avoid re-implementing that logic and should note that the outer joins mean rows can appear with no offer linkage. Exposing IEU_LOV_COL4 as the return item while presenting NAME as the display item is the standard pattern for any custom LOV defined over this object.