Results for “jtf_mon_data_attr”

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

Overview

JTF_MON_DATA_ATTR is a CRM Foundation (JTF) table that belongs to the Oracle E-Business Suite monitoring subsystem. It records attribute-level detail associated with monitored activity log entries, forming the intersection between a monitoring activity log record and a data lookup definition. Its purpose is to qualify or annotate monitoring activity records with named, referenceable attribute values rather than storing those values as unstructured text.

The table is documented as not implemented in this database in the Oracle ETRM reference for EBS 12.1.1 and 12.2.2. This is a significant operational fact: the table definition exists in the JTF schema and is referenced by the data model, but customer installations in scope do not populate it through standard application flows. Any query against it typically returns no rows unless custom or third-party code has inserted data.

Based on the mined foreign key structure, the ETRM metadata classifies this object heuristically as a link table in Data Vault terms. This is a modeling suggestion only. The classification reflects its structure: JTF_MON_DATA_ATTR does not own a natural business entity of its own, but resolves relationships between a monitoring activity log record and a monitoring data lookup record.

Key Information Stored

The documented metadata exposes two foreign key columns and references two parent tables. The following are the most important data elements.

• ACCESSKEY — Foreign key to JTF_MON_ACT_LOG. Identifies the parent monitoring activity log entry to which this attribute row belongs.
• DATA_ID — Foreign key to JTF_MON_DATA_LOOKUP. Identifies the lookup definition that gives the attribute its meaning or category.

Both columns are foreign keys and together form the effective composite business key of the intersection. No standalone surrogate primary key column is documented in the provided metadata. Where a surrogate key exists in the physical schema, it should be treated as a technical row identifier only, while ACCESSKEY and DATA_ID remain the meaningful key candidates for joins and de-duplication. Attributes such as the attribute value itself, creation date, created-by, last-update date, and last-updated-by are not documented in the supplied excerpt and should be confirmed against the live data dictionary before being referenced in SQL.

Common Use Cases and Queries

Because the table is not implemented in a standard database, its realistic use cases are diagnostic and structural rather than transactional. The most common scenario is determining whether a monitoring configuration has been extended to store attribute-level data.

• Existence and volume check. Run SELECT COUNT(*) FROM jtf_mon_data_attr; to confirm whether any rows exist. A zero result is consistent with the documented "not implemented" status.
• Attribute lookup resolution. Join to JTF_MON_DATA_LOOKUP to resolve the meaning of DATA_ID for any populated rows.
• Activity context. Join to JTF_MON_ACT_LOG on ACCESSKEY to associate attributes with their parent monitoring activity entries.
• Schema inventory and impact analysis. Identify dependent custom objects before upgrades or patches, since foreign keys mean child rows cannot exist without valid parents.

A representative query pattern is:

SELECT a.ACCESSKEY, d.DATA_ID, /* lookup columns */
FROM jtf_mon_data_attr a, jtf_mon_data_lookup d
WHERE a.DATA_ID = d.DATA_ID;

Reporting use cases are limited. In most implementations no monitoring report depends on this table, and any BI extract should treat it as optional.

Related Objects

The relationship data documented for JTF_MON_DATA_ATTR identifies two direct parents by foreign key.

• JTF_MON_ACT_LOG — referenced via JTF_MON_DATA_ATTR.ACCESSKEY. The parent monitoring activity log.
• JTF_MON_DATA_LOOKUP — referenced via JTF_MON_DATA_ATTR.DATA_ID. The parent lookup definition.

These two tables are the most significant dependencies and are the only documented join targets. When investigating the monitoring subsystem, they should be queried together with JTF_MON_DATA_ATTR to establish whether the intersection is in use. As the table is not implemented in the standard database, no further dependent views, packages, or concurrent programs are documented in the supplied metadata; additional relationships, if any, must be verified against the actual schema and dependencies in the target instance.