Results for “outcome_code”

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

Overview

AST_IH_OUTCOMES_CAMPAIGNS_VL is a TeleSales (AST) reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the association between interaction outcomes and campaign-related objects, resolving the outcome identifier to its descriptive attributes through a join against the interaction history outcomes view. In the ETRM repository the object is registered as a VALID VIEW under product AST — TeleSales, and it is commonly surfaced in outcome-driven reporting, campaign execution diagnostics, and integration extracts that must resolve outcome codes and descriptions without navigating the underlying interaction history tables directly.

The view is read-only in practical use. It inherits the multi-language behavior of the joined JTF_IH_OUTCOMES_VL view while exposing the transactional campaign association rows from JTF_IH_OUTCOMES_CAMPAIGNS. The name suffix "_VL" indicates that descriptive columns are sourced from a translated view, so SHORT_DESCRIPTION and related text respect the session language.

Underlying Base Objects

The view text is a two-table join:

• JTF_IH_OUTCOMES_CAMPAIGNS (documented as a SYNONYM in the ETRM metadata) — supplies the association rows, including OUTCOME_ID, OBJECT_ID, OBJECT_TYPE, SOURCE_CODE, and standard WHO/audit columns. This is the driving object, aliased OC.
• JTF_IH_OUTCOMES_VL (a VIEW) — supplies outcome-level descriptive data, including OUTCOME_CODE, SHORT_DESCRIPTION, and RESULT_REQUIRED. This is aliased O.

The join condition is OC.OUTCOME_ID = O.OUTCOME_ID, making the outcome the common key between the transactional campaign association and the outcome definition. O.ROWID is not selected; OC.ROWID is exposed as ROW_ID. Both underlying objects reside in the interaction history (JTF_IH) schema family, and the view therefore depends on the integrity of those objects in the APPS synonym layer.

Key Columns

• ROW_ID — the ROWID of the JTF_IH_OUTCOMES_CAMPAIGNS row, usable for direct row addressing.
• OUTCOME_ID — the outcome identifier linking the campaign association to the outcome definition.
• OBJECT_ID / OBJECT_TYPE — the referenced object (for example, a campaign) and its type, defining what the outcome is associated with.
• OBJECT_VERSION_NUMBER — the optimistic locking version of the association row.
• SOURCE_CODE_ID / SOURCE_CODE — the source of the outcome association, distinguishing origin channels or setups.
• OUTCOME_CODE — the system code of the outcome, resolved from JTF_IH_OUTCOMES_VL.
• SHORT_DESCRIPTION — the translated, user-facing description of the outcome.
• RESULT_REQUIRED — indicates whether a result value must be captured for the outcome; this is the column most often searched for under the term "result_required".
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns inherited from the base association row.

Common Use Cases and Queries

Typical use cases include reporting on which outcomes are configured for campaign objects, verifying whether an outcome mandates a captured result, and building integration extracts that resolve outcome codes and descriptions. A representative query filtering on the result requirement flag follows:

• SELECT outcome_id, outcome_code, short_description, result_required, source_code, object_id, object_type
• FROM apps.ast_ih_outcomes_campaigns_vl
• WHERE result_required = 'Y'
• ORDER BY outcome_code;

Another common pattern joins the view to campaign tables using OBJECT_ID and OBJECT_TYPE to obtain campaign names alongside outcome text, or filters by SOURCE_CODE to isolate outcomes originating from a specific channel. Because RESULT_REQUIRED is defined at the outcome level, distinct values appear once per outcome definition, while the association rows repeat per campaign object. Analysts should therefore use DISTINCT or aggregate functions when counting outcomes versus associations. Where language-dependent text is needed, the view already returns the session-language SHORT_DESCRIPTION, so no additional translation join is required.