Results for “wrap_id”

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

Overview

JTF_IH_ACTIVE_WRAP_UPS_VL is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the JTF — CRM Foundation product family. It exposes the currently effective subset of wrap-up records maintained by the Interaction History (IH) framework, filtering the base table so that only rows whose date range includes the current business day are visible. In practice the view presents the active "wrap-up" configurations that agents and telephony integrations apply when finalizing an interaction or activity — that is, the combination of outcome, result, and reason prompts that a business process may require.

The trailing "VL" suffix follows the standard EBS convention denoting a "validated" or date-effective view. Its defining predicate applies a one-day forward horizon on START_DATE and normalizes the open-ended END_DATE sentinel ('01/01/4721') to a perpetual value. The view therefore plays a well-defined role in reporting and integration: external consumers, custom forms, and workflow objects can join against it without re-implementing the effective-date logic, and any row returned is guaranteed to be currently active.

Underlying Base Objects

The view is defined over a single documented base object, JTF_IH_WRAP_UPS, which is referenced through a synonym in the APPS schema. There are no joins to other tables in the view text; the projected columns are drawn directly from the base table, with ROWID included to support update-through-view behavior where applicable. The relationship between the two objects is therefore one of filtered projection rather than aggregation or denormalization.

The effective-date filter operates as follows: START_DATE must be less than or equal to SYSDATE+1, and the decoded END_DATE — where the sentinel date 01/01/4721 and NULL are both treated as unbounded — must be greater than or equal to SYSDATE+1. Rows that have not yet begun, or that have already expired, are excluded. Because the view has no INSTEAD OF trigger, it is intended for query access; writes should be directed to the base table.

Key Columns

• WRAP_ID — Primary identifier of the wrap-up configuration.
• OUTCOME_REQUIRED, RESULT_REQUIRED, REASON_REQUIRED — Flags indicating whether an outcome, result, or reason must be captured for the wrap-up. These are the columns most directly relevant to the "reason_required" search term.
• OUTCOME_ID, RESULT_ID, REASON_ID — Foreign keys to the corresponding outcome, result, and reason setup entities, populated when a specific value is predefined.
• ACTION_ACTIVITY_ID, OBJECT_ID, OBJECT_TYPE — Contextual linkage of the wrap-up to an activity or business object.
• SOURCE_CODE_ID, SOURCE_CODE — Identifies the source or channel from which the wrap-up originates.
• START_DATE, END_DATE — Effective-dating columns driving the view's active-record filter.
• SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER, ROW_ID — Standard EBS multi-tenant, concurrency-control, and row-identity attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns.

Common Use Cases and Queries

Typical consumers include CRM agent-facing forms, interaction history reporting, and integration interfaces that must determine which wrap-up prompts are mandatory. The following query lists active wrap-ups where a reason is mandatory:

• SELECT wrap_id, object_type, outcome_required, result_required, reason_required, reason_id FROM apps.jtf_ih_active_wrap_ups_vl WHERE reason_required = 'Y';
• SELECT wrap_id, source_code, start_date, end_date FROM apps.jtf_ih_active_wrap_ups_vl WHERE object_type = :p_object_type;
• SELECT w.wrap_id, w.reason_required, r.reason_code, r.reason_text FROM apps.jtf_ih_active_wrap_ups_vl w, apps.jtf_ih_reasons_vl r WHERE w.reason_id = r.reason_id;

Because the effective-date predicate is evaluated at runtime, reports built on this view automatically reflect configuration changes without further filtering. Queries intended for extraction should account for the ROWID column and apply NLS-safe date handling when combining with other modules.