Search Results ast_source_codes_lov_v

Overview

The AST_SOURCE_CODES_LOV_V view is a TeleSales (AST) object owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It functions as a list-of-values (LOV) source for the TeleSales and Advanced Marketing (AMS) source code selection interface, presenting the set of source codes that a user may associate with a TeleSales activity. Because the view filters on status, source type, and the active date window of an associated offer, it exposes only currently valid source codes at query time rather than the full population of source code records.

The object is a database view rather than a table, so it holds no data of its own. All values are derived from the underlying AMS source code and activity offer objects, joined and filtered at runtime. The view is frequently surfaced in the Source Codes LOV window and is reachable through the AMS generic LOV framework, which supplies the IEU_LOV_COL column naming convention visible in its projection. Users searching for ams_p_source_codes_v typically arrive here because that underlying view is one of the base objects referenced by this LOV definition.

Underlying Base Objects

The view text references four underlying objects:

• AMS_P_SOURCE_CODES_V — the primary source of source code records. It is joined twice: once as the driving source (alias SC) and once to resolve the associated active offer (alias OFR). The synonym AMS_ACT_OFFERS provides the activity offer linkage.
• AMS_ACT_OFFERS — a synonym supplying the relationship between a source code and the offers that use it, through ACT_OFFER_USED_BY_ID and QP_LIST_HEADER_ID.
• AMS_LOOKUPS — a view providing lookup validation for the source type through the AMS_SYS_ARC_QUALIFIER lookup type. This join is outer ((+)), so a missing lookup does not suppress the record.

The joins to AMS_ACT_OFFERS and to the offer projection of the source codes view are also outer joins, ensuring that source codes without an associated active offer are not automatically excluded by the join itself; the date window predicate operates on the NVL-guarded offer dates.

Key Columns

The documented projection exposes four columns, all using the LOV column naming convention:

• IEU_LOV_COL1 — corresponds to SC.NAME, the descriptive name of the source code shown to the user in the LOV.
• IEU_LOV_COL2 — corresponds to SC.SOURCE_CODE, the source code identifier.
• IEU_LOV_COL3 — corresponds to SC.SOURCE_TYPE, the classification of the source. Eligible values are EVEH, EVEO, CAMP, CSCH, and EONE.
• IEU_LOV_COL4 — a character conversion of SC.SOURCE_CODE_ID, providing the internal identifier used to populate the calling field.

Source code status is restricted to ACTIVE, ONHOLD, or COMPLETED. Where an offer is present, the offer status must be ACTIVE and its source type OFFR, and the current system date must fall between the offer start and end dates. Absent offer dates, the NVL defaults widen the window to one day either side of the current date.

Common Use Cases and Queries

The principal use case is populating the source code LOV during TeleSales activity or campaign setup, where only eligible and currently valid codes should appear. A representative query mirrors the view definition:

• SELECT ieu_lov_col1, ieu_lov_col2, ieu_lov_col3, ieu_lov_col4 FROM apps.ast_source_codes_lov_v WHERE ieu_lov_col2 LIKE :search ORDER BY 1;

An additional scenario is diagnostic reporting on which source codes are currently eligible, for instance filtering by IEU_LOV_COL3 to isolate all active CAMP codes. Because the DISTINCT keyword is applied in the definition, duplicate offer associations collapse to a single row per code, making the view safe for direct LOV consumption. For integration or validation logic, querying IEU_LOV_COL4 against the source code ID is the recommended method for confirming that a submitted code remains within the active source type and status envelope.