Results for “jtf_ih_wrap_ups_vl”

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

Overview

The view APPS.JTF_IH_WRAP_UPS_VL is a CRM Foundation (JTF) reporting object delivered as part of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the wrap-up configuration records stored in the Interaction History (IH) subsystem, presenting wrap-up definitions alongside the descriptive and behavioral attributes of the outcome, result, and reason codes that they reference. In the ETRM repository the object carries a status of VALID, is owned by the APPS schema, and is classified as a VIEW.

The view functions as a denormalized, language-enabled presentation layer. Rather than requiring callers to join three separate "_VL" views manually, it returns outcome, result, and reason descriptions together with each wrap-up row, together with callback generation flags, versatility codes, positive-response indicators, and active flags inherited from the referenced lookup entities. This makes it suitable for direct use in concurrent programs, OAF/Forms list-of-values queries, BI Publisher data templates, and inbound/outbound integration extracts where a single flat row per wrap-up definition is preferred.

Underlying Base Objects

The view is defined over four documented referenced objects:

• JTF_IH_WRAP_UPS (SYNONYM) — the primary wrap-up definition store, aliased WRP. It supplies the identifying, audit, and versioning columns (WRAP_ID, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) as well as the foreign keys OUTCOME_ID, RESULT_ID, REASON_ID, and the descriptive columns OBJECT_ID, OBJECT_TYPE, SOURCE_CODE_ID, SOURCE_CODE, SECURITY_GROUP_ID, START_DATE, END_DATE, and WRAP_UP_LEVEL.
• JTF_IH_OUTCOMES_VL (VIEW) — aliased OUTC, joined on OUTCOME_ID. This is an inner join, so a wrap-up row is only returned when its outcome is resolvable.
• JTF_IH_RESULTS_VL (VIEW) — aliased RES, joined on RESULT_ID using an outer join (+) in the documented view text.
• JTF_IH_REASONS_VL (VIEW) — aliased REA, joined on REASON_ID, also using an outer join (+).

Because RESULT_ID and REASON_ID are optionally populated, the outer joins preserve wrap-up definitions that specify an outcome only, returning nulls for the result and reason attribute columns. The "_VL" suffix on the three lookup views confirms they are MLS-enabled, so their short description columns are translated according to the session language.

Key Columns

The view exposes the WRP.ROWID as ROW_ID, which permits the view to be treated as an updateable entity in Forms or ADF-based personalizations. The principal columns are:

• WRAP_ID — primary identifier of the wrap-up definition; the join key for downstream references.
• OUTCOME_ID, RESULT_ID, REASON_ID — the three lookup identifiers that constitute a wrap-up selection. OUTCOME_ID is mandatory; RESULT_ID and REASON_ID are optional.
• OUTCOME_SHORT_DESC, RESULT_SHORT_DESC, REASON_SHORT_DESC — language-sensitive descriptions of each referenced lookup value.
• REASON_GEN_PUB_CALLBACK / REASON_GEN_PVT_CALLBACK, RESULT_GEN_PUB_CALLBACK / RESULT_GEN_PVT_CALLBACK, OUTCOME_GEN_PUB_CALLBACK / OUTCOME_GEN_PVT_CALLBACK — flags indicating whether public and private callbacks should be generated for the respective outcome, result, and reason.
• REASON_VERS_CODE, RESULT_VERS_CODE, OUTCOME_VERS_CODE — versatility codes controlling the applicability of each lookup value.
• RESULT_POSITIVE_RESP_FLAG, OUTCOME_POSITIVE_OUTCOME_FLAG — indicators of whether a result or outcome represents a positive customer response.
• REASON_ACTIVE, RESULT_ACTIVE, OUTCOME_ACTIVE — active status of each referenced lookup value.
• START_DATE, END_DATE, WRAP_UP_LEVEL — effective dating and hierarchical level of the wrap-up definition.
• OBJECT_ID, OBJECT_TYPE, SOURCE_CODE_ID, SOURCE_CODE, SECURITY_GROUP_ID — extensibility, source attribution, and multi-tenancy (security group) context.

The documentation lists both RESULT_REQUIRED and REASON_REQUIRED, although the view text selects OUTC.RESULT_REQUIRED and RES.RESULT_REQUIRED against the same column alias — a documented quirk worth noting when reading the source.

Common Use Cases and Queries

Typical consumers use the view to drive wrap-up selection in interaction logging screens, to audit which lookup combinations are configured, and to extract CRM Foundation setup data for migration. Active, currently effective wrap-ups can be retrieved as follows:

• Active wrap-ups for a given outcome: SELECT WRAP_ID, OUTCOME_SHORT_DESC, RESULT_SHORT_DESC, REASON_SHORT_DESC, WRAP_UP_LEVEL FROM JTF_IH_WRAP_UPS_VL WHERE OUTCOME_ID = :p_outcome_id AND SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE) AND OUTCOME_ACTIVE = 'Y';
• Callback generation audit: SELECT WRAP_ID, OUTCOME_SHORT_DESC, OUTCOME_GEN_PUB_CALLBACK, RESULT_GEN_PVT_CALLBACK, REASON_GEN_PUB_CALLBACK FROM JTF_IH_WRAP_UPS_VL WHERE OUTCOME_GEN_PUB_CALLBACK = 'Y' OR RESULT_GEN_PUB_CALLBACK = 'Y';
• Positive-response analysis: SELECT WRAP_ID, OUTCOME_SHORT_DESC, RESULT_SHORT_DESC FROM JTF_IH_WRAP_UPS_VL WHERE OUTCOME_POSITIVE_OUTCOME_FLAG = 'Y' OR RESULT_POSITIVE_RESP_FLAG = 'Y';

Because the joins are outer for result and reason, queries must use NVL on the corresponding description columns when producing labels for wrap-ups defined at outcome level only. Seeded queries should also filter on SECURITY_GROUP_ID where multi-organization data separation is enforced.