Results for “milcs_code”

4 results




Overview
Explore in AI Chat

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

Overview

JTF_IH_MEDIA_ITM_LC_SEG_TYS is a CRM Foundation (JTF) reference table that stores the descriptors of Media Lifecycle Segments. Each row identifies a distinct segment type that denotes the system or activity to which an interval of time is attributed within the media interaction history model. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the JTF schema and is designated VALID. It functions as a lookup and classification parent against which transactional media lifecycle segment records are qualified.

Applying the heuristic Data Vault classification supplied in the metadata, this object is described as hub-leaning. Under that modeling suggestion, MILCS_TYPE_ID behaves as the hub business key: a stable, non-volatile identifier for each segment type, with descriptive and audit attributes acting in a satellite capacity. The table is not a transactional fact object; it is a controlled vocabulary of segment types referenced by higher-volume child records.

Key Information Stored

The documented physical schema for release 12.2.2 contains eleven columns. The most significant are:

The unique index JTF_IH_MEDIA_ITM_LC_SET_TYS_U1 covers (MILCS_TYPE_ID, ZD_EDITION_NAME), confirming that the surrogate key is unique within each edition while remaining the principal business-key candidate. Note the index name uses "SET_TYS" while the table name uses "SEG_TYS"; this discrepancy is documented and should be accounted for in DDL scripts.

Common Use Cases and Queries

Typical usage resolves the segment-type code or description for reporting, or validates that a child segment record references a defined type.

  • Joining types to child segments: SELECT s.MILCS_TYPE_ID, t.MILCS_CODE, t.SHORT_DESCRIPTION FROM JTF_IH_MEDIA_ITEM_LC_SEGS s, JTF_IH_MEDIA_ITM_LC_SEG_TYS t WHERE s.MILCS_TYPE_ID = t.MILCS_TYPE_ID;
  • Security-filtered lookup for a session: filter by SECURITY_GROUP_ID to honor data partitioning.
  • Resolving codes to labels in CRM media analytics: select MILCS_CODE and SHORT_DESCRIPTION for all segment types to build report parameter lists.
  • Referential integrity auditing: identify child segments whose MILCS_TYPE_ID has no matching parent row.

Because the table is low-volume reference data, queries are inexpensive and typically executed as inline joins rather than pre-aggregated extracts.

Related Objects

The following objects are the most significant dependencies:

  • JTF_IH_MEDIA_ITEM_LC_SEGS — the principal child table; its MILCS_TYPE_ID column is a foreign key to JTF_IH_MEDIA_ITM_LC_SEG_TYS.MILCS_TYPE_ID. This is the dominant relationship and defines the hub-to-child join.
  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID, supplying the multi-tenant security partition metadata.
  • FND_APPLICATION / FND_LOOKUP_TYPES — typically consulted alongside this table for valid-value validation in user interfaces and concurrent programs.
  • JTF_IH_MEDIA_ITEMS and related JTF_IH media history objects — the broader interaction-history model in which lifecycle segments participate.
  • JTF_IH_MEDIA_ITM_LC_SEG_TYS_PK and JTF_IH_MEDIA_ITM_LC_SET_TYS_U1 — the primary key constraint and unique business-key index governing uniqueness and access paths.

Together, these objects position the table as a compact but structurally central hub in the CRM Foundation media lifecycle hierarchy.