Results for “source_code_for”

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

Overview

AST_TARGET_CAMPAIGNS_V is an Oracle Applications (APPS) view belonging to the AST – TeleSales product module. Its purpose is to surface the set of active TeleSales campaigns, schedules, events, offers, and related outreach sources that are valid targets for list and assignment processing. The view consolidates source-code definitions, list-entry membership, and lookup metadata into a single denormalized result set keyed at the party level.

The object is owned by the APPS schema and carries a VALID status in the ETRM where it is documented. It is a reporting-friendly projection rather than a transactional entity: it exposes a curated, filtered subset of records rather than the complete underlying data. By joining source-code, list-entry, and lookup tables, the view removes the need for consumers to replicate the multi-table qualification logic, making it suitable for reporting, integration, and downstream TeleSales processing.

Because the view is read-only and built from joins, no direct DML should be issued against it; changes to campaign targeting must be performed in the base entities.

Underlying Base Objects

The view is defined over three documented referenced objects: AMS_LIST_ENTRIES (a synonym), AMS_LOOKUPS (a view), and AMS_P_SOURCE_CODES_V (a view). These are joined on source code, source type, and lookup attributes.

• AMS_P_SOURCE_CODES_V (SC) — Provides source-code identifiers, source type, and status. It is the anchor for the campaign/offer classification used by the view.
• AMS_LIST_ENTRIES (LE) — Supplies the party-to-source-code association and the enabled flag that determines whether a given list entry participates in targeting.
• AMS_LOOKUPS (AL) — Provides the lookup meaning and enabled flag; the view restricts this lookup type to AMS_SYS_ARC_QUALIFIER, which is the specific lookup context that validates which source qualifiers are permissible targets.

The join structure links SC.SOURCE_CODE = LE.SOURCE_CODE, SC.SOURCE_TYPE = AL.LOOKUP_CODE, and constrains the lookup to enabled values of type AMS_SYS_ARC_QUALIFIER.

Key Columns

• PARTY_ID — The party (contact or organization) associated with the list entry; the view enforces LE.PARTY_ID IS NOT NULL.
• SOURCE_CODE_ID — Identifier of the source code record, used to trace back to the campaign/offer definition.
• SOURCE_CODE — The source code value linking list entries to their originating campaign source.
• OBJECT_ID — Identifier of the underlying object referenced by the source code.
• SOURCE_TYPE — Classifies the source; matched against lookup codes.
• MEANING — The descriptive lookup meaning for the source type, drawn from AMS_LOOKUPS.
• ACTIVE_FLAG — A constant 'Y' projected by the view to indicate that all returned rows are active targets.

The documentation lists additional columns, including SOURCE_CODE_FOR_ID, SOURCE_CODE_FOR, and SOURCE_CODE_TYPE, which further characterize the source relationship.

Common Use Cases and Queries

The view is typically used to identify valid TeleSales campaign targets for a party, to drive outbound calling lists, or to feed integration extracts. The AMS_SYS_ARC_QUALIFIER lookup is the controlling qualifier, and the view only returns records whose source type falls in the set ('CAMP', 'CSCH', 'EVEH', 'EVEO', 'OFFR', 'EONE') and whose source status is ACTIVE, ONHOLD, or COMPLETED.

• List all active targets for a specific party.
• Count targets grouped by campaign source code for workload planning.
• Join to party or campaign master data for enriched reporting.

A representative query:

SELECT party_id, source_code, source_code_id, source_type, meaning FROM apps.ast_target_campaigns_v WHERE source_code = :source_code;

All queries should treat the view as read-only and rely on the enabled-and-status filters already embedded in its definition.