Results for “int_end_date”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKC_LAUNCH_COMMGRID_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the OKC – Contracts Core product. The view presents a consolidated, denormalized projection of Oracle Contracts interaction and communication activity, joining contract header records to their associated interaction (communication) history, media, agents, parties, action items, and outcomes. Its principal role is to back the "Communications Grid" or launch-page summary that surfaces, for a given contract, the communications exchanged with customers, the responsible agents, and the results recorded against each interaction.
The view is read-only and exists purely for reporting and integration consumption rather than transactional processing. It is typically surfaced through Oracle Forms, OAF pages, or custom concurrent programs, and is commonly queried by developers extending the Contracts module. The presence of OUTCOME_MEANING in the projection makes the view particularly relevant to outcome-based communication reporting.
Underlying Base Objects
The view is defined over a UNION ALL of two similar SELECT statements, each joining the same eleven to twelve core objects. The documented base objects are:
- JTF_IH_ACTIVITIES (synonym) — the activity instances linked to each interaction.
- JTF_IH_INTERACTIONS (synonym) — the interaction header, supplying party and resource context.
- JTF_IH_MEDIA_ITEMS (synonym) — media items used in the interaction.
- JTF_IH_ACTION_ITEMS_VL (view) — action items raised during the interaction.
- JTF_IH_OUTCOMES_VL (view) — the outcome recorded for the activity.
- JTF_NOTES_VL (view), with JTF_NOTES_PKG (package) — notes attached to the activity.
- JTF_OBJECTS_VL (view) — object/role registration keyed to the touchpoint.
- JTF_RS_RESOURCE_EXTNS_VL (view) — the resource (agent) record.
- FND_LOOKUPS (view) — lookup meanings, notably for media type.
- HZ_PARTIES (synonym) — trading party name.
- Additionally, FND_GLOBAL and JTF_COMMON_PVT packages supply session context and utility logic referenced internally.
The initial SELECT drives party-based touchpoints (TOUCHPOINT1_TYPE = 'PARTY') joined to HZ_PARTIES; the UNION ALL branch handles the alternate party source (ROL.SOURCE_NAME) for non-standard touchpoint configurations.
Key Columns
- INTERACTION_ID — identifier of the parent interaction.
- CONTRACT_ID — identifier of the linked OKC contract (DOC_REF = 'OKC_K_HEADERS_V').
- ROLE / PARTY_NAME / PARTY_ID — the customer role, name, and party identifier.
- AGENT_NAME / AGENT_ID — the resource responsible for the interaction.
- MEDIA_TYPE / MEDIA_MEANING — media code and its decoded meaning via FND_LOOKUPS.
- ACT_START_DATE / ACT_END_DATE / INT_START_DATE / INT_END_DATE — date ranges for the activity and interaction.
- ACTION_ITEM_ID / ACTION_ITEM_MEANING — action item identifiers and descriptions.
- OUTCOME_ID / OUTCOME_MEANING — the recorded outcome identifier and its descriptive meaning, sourced from JTF_IH_OUTCOMES_VL.
- NOTES_HEADER / NOTES_DETAIL — attached note text.
- CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE — WHO-column audit attributes.
The OUTCOME_MEANING column, resolved from the short description of JTF_IH_OUTCOMES_VL, allows reports to display human-readable results without an additional lookup join.
Common Use Cases and Queries
Typical uses include building a communications dashboard for a contract, analysing outcome distributions, and auditing agent activity. A representative query filtering by contract and surfacing outcome detail:
SELECT contract_id, party_name, agent_name, media_meaning, outcome_meaning, act_start_date FROM okc_launch_commgrid_v WHERE contract_id = :p_contract_id ORDER BY act_start_date DESC;- Outcome-based reporting, e.g. grouping interactions by OUTCOME_MEANING to measure communication effectiveness across a period.
- Agent activity summaries joining AGENT_ID to JTF_RS resources for workload analysis.
- Media-channel breakdowns using MEDIA_MEANING joined through FND_LOOKUPS values under lookup type JTF_MEDIA_TYPE.
Because the view is read-only, it should never be used for DML. When performance is a concern, restrict queries by CONTRACT_ID, PARTY_ID, or date ranges to limit the UNION ALL scan, as the object joins multiple VL and synonym objects that can be expensive without selective predicates.
-
View: OKC_LAUNCH_COMMGRID_V 12.2.2
APPS.OKC_LAUNCH_COMMGRID_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ HZ_PARTIES·Explore OKC module →
-
View: OKC_LAUNCH_COMMGRID_V 12.1.1
APPS.OKC_LAUNCH_COMMGRID_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ HZ_PARTIES·Explore OKC module →
-
eTRM - OKC Tables and Views 12.1.1
Intersection entity between templates and rules.
-
eTRM - OKC Tables and Views 12.2.2
Intersection entity between rules and templates