Results for “jtf_media_type”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.OKC_LAUNCH_COMMGRID_V is a reporting view in Oracle E-Business Suite that consolidates interaction and activity data associated with contract records, presenting it in a denormalized form suitable for communication grids, dashboards, and integration extracts. The view is part of the Oracle Knowledge and Contracts (OKC) and interaction history (JTF) family of objects. It joins interaction records to their underlying activities, media items, resources, parties, action items, outcomes, and notes, returning one row per activity-media combination. In EBS 12.1.1 and 12.2.2 the object is owned by APPS and is primarily intended for read-only query and reporting rather than transactional DML.
Underlying Base Objects
The view is defined over a set of interaction-history and contract-related objects. The core transactional sources are JTF_IH_ACTIVITIES and JTF_IH_INTERACTIONS, linked on INTERACTION_ID. JTF_IH_MEDIA_ITEMS supplies the media record, joined to FND_LOOKUPS on LOOKUP_TYPE = 'JTF_MEDIA_TYPE' to translate the media item type into a meaning. HZ_PARTIES provides the party name, while JTF_RS_RESOURCE_EXTNS_VL supplies the agent resource name. JTF_OBJECTS_VL resolves the customer/role object code. Supporting views include JTF_IH_ACTION_ITEMS_VL, JTF_IH_OUTCOMES_VL, JTF_NOTES_VL, and the JTF_COMMON_PVT, JTF_NOTES_PKG, and FND_GLOBAL packages, which supply security and utility logic. The view comprises a UNION ALL of two branches, the first restricting to TOUCHPOINT1_TYPE = 'PARTY' and joining HZ_PARTIES, the second using an alternative party source for other touchpoint configurations.
Key Columns
- INTERACTION_ID — identifier of the parent interaction record.
- CONTRACT_ID — DOC_ID from the activity, associated with OKC_K_HEADERS_V.
- ROLE / PARTY_NAME / PARTY_ID — party role, name, and identifier from HZ_PARTIES or the alternate source.
- AGENT_NAME / AGENT_ID — resource name and identifier of the agent handling the interaction.
- MEDIA_TYPE / MEDIA_MEANING — media item code and its FND_LOOKUPS meaning, with LOOKUP_TYPE = 'JTF_MEDIA_TYPE'.
- TOUCHPOINT1_TYPE / TOUCHPOINT2_TYPE — touchpoint classification columns.
- ACT_START_DATE / ACT_END_DATE / INT_START_DATE / INT_END_DATE — activity and interaction timestamps.
- ACTION_ITEM_ID / ACTION_ITEM_MEANING — associated action item and its description.
- OUTCOME_ID / OUTCOME_MEANING — outcome and its description.
- NOTES_HEADER / NOTES_DETAIL — note text attached to the activity.
- CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE — standard audit columns.
Common Use Cases and Queries
The view is typically queried to report on contract-related communications, agent activity, and media usage. Because the user search referenced jtf_media_type, a common pattern is filtering on MEDIA_MEANING or joining FND_LOOKUPS for that lookup type:
SELECT INTERACTION_ID, CONTRACT_ID, PARTY_NAME, AGENT_NAME, MEDIA_MEANING, ACT_START_DATE FROM APPS.OKC_LAUNCH_COMMGRID_V WHERE MEDIA_MEANING = 'Phone Call';
Other uses include extracting all communications for a specific contract (WHERE CONTRACT_ID = :p_contract_id), summarizing agent activity by date range, and feeding downstream integration or BI reports. Because it is a view, standard SELECT privileges granted through the APPS schema apply, and no direct DML should be attempted.
-
Lookup Type: JTF_MEDIA_TYPE 12.2.2
An instance of media that was processed by the system and/or its users. Media items can be generated by a customer or by a system or an application. Media items can be inbound (e.g., mail or call from a customer).
-
Lookup Type: JTF_MEDIA_TYPE 12.1.1
An instance of media that was processed by the system and/or its users. Media items can be generated by a customer or by a system or an application. Media items can be inbound (e.g., mail or call from a customer).
-
Not implemented in this database·Explore BIM module →
-
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 →
-
Not implemented in this database·Explore BIM module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2