Results for “jtf_ih_wrap_ups”

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

Overview

JTF_IH_WRAP_UPS is a CRM Foundation (JTF) configuration and control table in Oracle E-Business Suite 12.1.1 and 12.2.2. It identifies the information that must be supplied by any application inserting Interaction History records into the JTF_IH_* schema family. In effect, the table defines wrap-up rules: for a given combination of object type, object identifier, source code, and wrap-up level, it declares whether an outcome, result, or reason is mandatory when an interaction is recorded. Downstream applications — TeleSales, Service, Marketing, and any custom module that logs customer interactions — consult these rows to enforce data-completeness policies at entry time.

Heuristic Data Vault classification mined from the foreign-key structure is link. In dimensional terms the table behaves as a rule/association entity: it joins attribute rows together rather than storing a descriptive profile of a single business key.

Key Information Stored

The table contains 23 documented columns. The most significant are:

• WRAP_ID — surrogate primary key, enforced by JTF_IH_WRAP_UPS_PK. Serves as the rule identifier.
• WRAP_UP_LEVEL — the granularity at which the rule applies (for example, activity-level versus interaction-level wrap-up).
• OBJECT_ID and OBJECT_TYPE — identify the entity the wrap-up rule governs; OBJECT_TYPE typically distinguishes activities, interactions, or campaigns.
• OUTCOME_REQUIRED, RESULT_REQUIRED, REASON_REQUIRED — boolean flags stating whether the corresponding code is mandatory for this rule combination.
• OUTCOME_ID, RESULT_ID, REASON_ID — default or permitted values validated against JTF_IH_OUTCOMES_B, JTF_IH_RESULTS_B, and JTF_IH_REASONS_B respectively.
• ACTION_ACTIVITY_ID — links the rule to an activity definition in JTF_IH_ACTIVITIES.
• SOURCE_CODE_ID and the legacy SOURCE_CODE column — both reference AMS_SOURCE_CODES, identifying the originating channel or application.
• SECURITY_GROUP_ID — multi-org style data isolation, referencing FND_SECURITY_GROUPS.
• START_DATE and END_DATE — effective-dating window for the rule.
• OBJECT_VERSION_NUMBER — optimistic locking, per the OAF/ADF convention introduced across EBS 12.1 and carried forward in 12.2.2.

The unique index JTF_IH_WRAP_UPS_U1 on (WRAP_ID, ZD_EDITION_NAME) supports the editioning mechanism used in 12.2 online patching; in 12.1 the ZD_EDITION_NAME column is not meaningful. The remaining audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are standard WHO columns.

Common Use Cases and Queries

Typical usage is validating that a rule exists for the interaction being logged and determining which fields must be collected from the user. A representative query resolves the required flags for a source and object type:

• SELECT w.WRAP_ID, w.OUTCOME_REQUIRED, w.RESULT_REQUIRED, w.REASON_REQUIRED, w.OUTCOME_ID, w.RESULT_ID, w.REASON_ID FROM JTF_IH_WRAP_UPS w WHERE w.SOURCE_CODE_ID = :source_id AND w.OBJECT_TYPE = :object_type AND TRUNC(SYSDATE) BETWEEN NVL(w.START_DATE, SYSDATE) AND NVL(w.END_DATE, SYSDATE);
• Reporting the effective rule set by joining AMS_SOURCE_CODES for channel names, or JTF_IH_OUTCOMES_B for outcome translations.
• Auditing gaps: rules flagged OUTCOME_REQUIRED = 'Y' whose OUTCOME_ID is null, indicating misconfiguration.
• Migrating rules between environments, filtered by SECURITY_GROUP_ID.

Because the table is metadata-like and low-volume, it is normally accessed by the CRM UI layer rather than directly by end users.

Related Objects

• AMS_SOURCE_CODES — referenced twice, via SOURCE_CODE_ID and SOURCE_CODE.
• JTF_IH_OUTCOMES_B — via OUTCOME_ID; supplies permitted outcome values.
• JTF_IH_RESULTS_B — via RESULT_ID.
• JTF_IH_REASONS_B — via REASON_ID.
• JTF_IH_ACTIVITIES — via ACTION_ACTIVITY_ID; the activity definitions the rules constrain.
• FND_SECURITY_GROUPS — via SECURITY_GROUP_ID; governs row-level access.
• The Interaction History fact tables in the same JTF_IH_* family, whose inserts these rules govern.