Results for “result_code”

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

Overview

The AST_IH_CAMPAIGNS_RESULTS_VL view is a TeleSales (AST) module database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents campaign result records joined with their iStore/Interaction History result definitions, providing a denormalized, reporting-friendly structure that combines transactional campaign-result data with the descriptive attributes of each result type. The "_VL" suffix reflects that the view supplies a validated list-style presentation of result metadata, combining the base result assignment with its user-facing short description and required-flag.

Within Oracle EBS, this view serves as an integration and reporting surface rather than a transactional entity. Functional users searching for "jtf_ih_results_vl" are usually attempting to locate the result-code definitions that back campaign outcomes; the AST_IH_CAMPAIGNS_RESULTS_VL view is the APPS-level object that exposes those definitions alongside the campaign-result associations. It is commonly consumed by concurrent programs, Discoverer reports, OBIEE extracts, and custom PL/SQL that need to resolve a numeric RESULT_ID into a human-readable result code without writing the join manually.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over two base objects:

• JTF_IH_CAMPAIGNS_RESULTS (SYNONYM) — the transactional base table that stores individual campaign result records, identified as alias CR in the view definition. This is the driving object supplying the row context, object association, and audit columns.
• JTF_IH_RESULTS_VL (VIEW) — the validated result-definition view, identified as alias R. It supplies the textual attributes: RESULT_CODE, SHORT_DESCRIPTION, and RESULT_REQUIRED.

The join condition is a simple equi-join on CR.RESULT_ID = R.RESULT_ID, meaning only campaign-result rows whose RESULT_ID resolves to a valid result definition are returned. Rows orphaned from a valid result definition are excluded by the inner join, which is typical for a "_VL" presentation view. Because it references JTF_IH_RESULTS_VL (itself a view), the object is a layered view and depends on the underlying iStore/Interaction History result tables for the descriptive side.

Key Columns

The view exposes the following documented columns:

• ROW_ID — the underlying CR.ROWID, uniquely addressing the physical base row; useful for direct row addressing but not portable across reorganizations.
• RESULT_ID — the foreign key linking the campaign result to its result definition; the join column between both base objects.
• OBJECT_TYPE, OBJECT_ID — polymorphic association identifying the entity (for example, a lead, contact, or opportunity) to which the campaign result applies.
• SOURCE_CODE_ID, SOURCE_CODE — the origin of the result assignment, allowing reports to distinguish result sources.
• OBJECT_VERSION_NUMBER — optimistic locking version, incremented on each update.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns available for date- and user-based analysis.
• RESULT_CODE, SHORT_DESCRIPTION, RESULT_REQUIRED — descriptive attributes sourced from JTF_IH_RESULTS_VL; the result code is the stable business identifier, the short description is the display label, and RESULT_REQUIRED indicates whether the result must be supplied.

Common Use Cases and Queries

Typical scenarios include campaign-outcome reporting, resolving result IDs to labels for extracts, and auditing result capture completeness. A representative query listing campaign results with their descriptive definitions is:

SELECT result_id, result_code, short_description,
       result_required, object_type, object_id,
       creation_date, created_by
FROM   apps.ast_ih_campaigns_results_vl
WHERE  creation_date >= :p_start_date;

A join to the underlying transactional table for a full result-per-campaign listing is:

SELECT cr.object_id, avl.result_code, avl.short_description
FROM   apps.jtf_ih_campaigns_results cr,
       apps.ast_ih_campaigns_results_vl avl
WHERE  cr.result_id = avl.result_id
AND    avl.result_required = 'Y';

Because the view applies the validated-list join, reports requiring only rows with a valid result definition can query it directly; reports needing orphaned or undefined results must query JTF_IH_CAMPAIGNS_RESULTS with an outer join to JTF_IH_RESULTS_VL instead.