Results for “media_data”

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

Overview

JTF_IH_MEDIA_ITEMS_V is a reporting view owned by the APPS schema within the JTF – CRM Foundation product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support report generation over records held in the JTF_IH_MEDIA_ITEMS base table. The view is a direct projection of the columns from that table, joined by no other objects, and it adds no filtering or transformation logic beyond renaming the physical ROWID to ROW_ID for reporting convenience. Because media items record the individual content elements (phone calls, e-mails, faxes, web interactions, and similar) attached to an interaction, this view is the primary read-only interface used by customer-facing reports, extract programs, and integrations that need media-level detail without querying the transactional table directly. The object is documented as VALID in the ETRM repository, which confirms that it compiles successfully against the 12.2.2 data dictionary and is safe for use in ad hoc and application SQL.

Underlying Base Objects

The view is defined over a single referenced base object: the synonym JTF_IH_MEDIA_ITEMS. The view text is a straightforward SELECT ... FROM JTF_IH_MEDIA_ITEMS MED, exposing every business column of the underlying table. There are no joins to lookup tables, no unions, and no WHERE predicates. Because the synonym resolves to the APPS-owned table, the view inherits the table's partitioning, indexes, and security posture; row-level security is therefore applied only through whatever grants and policies exist on the base table, not through the view itself. Any data inserted or updated in JTF_IH_MEDIA_ITEMS is immediately visible through the view, since no materialization or snapshot is involved.

Key Columns

• ROW_ID – the physical ROWID of the base row, aliased for reporting use.
• MEDIA_ID – primary identifier of the media item record.
• BULK_BATCH_ID – identifies the bulk processing batch to which the media item was assigned when created through bulk interaction processing. This is the column users most frequently search for when tracing outbound bulk campaigns.
• BULK_WRITER_CODE and BULK_BATCH_TYPE – describe the bulk writer implementation and the category of batch used during bulk media creation.
• BULK_INTERACTION_ID – links the bulk-created media item back to its generated interaction.
• SOURCE_ID and SOURCE_ITEM_ID – reference the originating interaction and source item.
• MEDIA_ITEM_TYPE, MEDIA_ITEM_REF, and MEDIA_DATA – classify the media and carry its payload reference.
• DIRECTION, DURATION, START_DATE_TIME, END_DATE_TIME – interaction timing and flow attributes.
• ACTIVE – soft-delete/status flag.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER – standard audit and concurrency columns.
• ADDRESS – contact address associated with the media item.

Common Use Cases and Queries

Typical scenarios include tracing bulk campaign output, auditing media volumes per interaction, and validating that outbound records were generated correctly. A common query resolves all media items belonging to a given bulk batch:

SELECT media_id, bulk_batch_id, bulk_batch_type, bulk_interaction_id, source_id, media_item_type, creation_date FROM apps.jtf_ih_media_items_v WHERE bulk_batch_id = :p_batch_id;

Reports reconciling bulk writers filter on BULK_WRITER_CODE, while interaction-level audits join MEDIA_ID to JTF_IH_INTERACTIONS or filter by SOURCE_ID. Because the view exposes ROW_ID and OBJECT_VERSION_NUMBER, it can also be used cautiously in Forms-based update logic, although its documented role remains report generation. All queries should be schema-qualified as APPS and executed with the privileges granted to the reporting user.