Results for “jtf_xml_invocations_b”

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

Overview

JTF_XML_INVOCATIONS_B is a base table in the JTF (CRM Foundation) product schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. Its documented description is "Table that stores XML Services Events." In practical terms, the table holds the definitions of XML service invocations that the CRM Foundation XML Services framework recognizes and executes. Each row describes one invocation — the application that owns it, the Java implementation type bound to it, and the naming attributes used by the invocation engine to resolve the service at runtime.

The table sits at the center of the XML Services configuration model. It is the parent of the translation table JTF_XML_INVOCATIONS_TL and is referenced by JTF_XML_EVENT_MAPPINGS, which associates invocation definitions with business events. It in turn references FND_APPLICATION and FND_SECURITY_GROUPS, tying each invocation to a registered Oracle EBS application and to a security group for multi-organization access control. The documentation does not publish the number of columns or the underlying tablespace, so sizing and column-count statements should be validated against the deployed instance.

Applying Data Vault modeling heuristics to the documented foreign-key topology, the table is hub-leaning: INV_ID is a single-column surrogate primary key with no composite business key mined from the constraint set, so it behaves like a durable hub of invocation identities. In practice, many implementations also treat descriptive attributes such as INV_NAME and INV_TYPE as type-2 tracked data, in which case the table functions as a combined hub and satellite. This classification is a modeling suggestion only; it is not an Oracle-documented property of the table.

Key Information Stored

The documented metadata identifies 14 columns on the table, with the physical definition recorded for the 12.2.2 release. The columns most relevant to functional and integration work are:

• INV_ID — the surrogate primary key, enforced by the JTF_XML_INVOCATIONS_B_PK constraint. It is the value propagated to all child tables.
• INV_NAME — the invocation name used to identify the XML service event in configuration and lookup screens.
• INV_TYPE — the invocation type, distinguishing the class of XML service being defined.
• JAVA_TYPE — the Java implementation type bound to the invocation, which drives how the framework dispatches the call at runtime.
• APPLICATION_ID — the owning Oracle EBS application; a foreign key to FND_APPLICATION.
• SECURITY_GROUP_ID — the security group associated with the row; a foreign key to FND_SECURITY_GROUPS.
• END_DATE — the effective end date of the invocation definition, supporting date-effective maintenance.
• ZD_EDITION_NAME — the editioning column introduced by the 12.2 online patching architecture; it forms part of the unique constraint JTF_XML_INVOCATIONS_B_U1 (INV_ID, ZD_EDITION_NAME).
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER — which support audit trail reporting and optimistic locking during concurrent maintenance.

Common Use Cases and Queries

The table is queried primarily to enumerate and diagnose XML service configuration — for example, listing all invocations belonging to a given application, or locating the invocation that a specific event mapping points to. Reporting commonly joins the base table to its translation table to present the invocation name in the session language:

SELECT b.inv_id, b.inv_name, b.inv_type, b.end_date, t.description
FROM jtf_xml_invocations_b b, jtf_xml_invocations_tl t
WHERE b.inv_id = t.inv_id AND t.language = USERENV('LANG')
AND SYSDATE BETWEEN NVL(b.start_date, SYSDATE) AND NVL(b.end_date, SYSDATE);

Note that START_DATE is not present in the documented 12.2.2 column list, so date-effective predicates should be adjusted to the columns actually present on the target release. A second common pattern resolves event bindings by walking from JTF_XML_EVENT_MAPPINGS back to the invocation definition:

SELECT m.event_name, b.inv_id, b.inv_name, b.java_type
FROM jtf_xml_invocations_b b, jtf_xml_event_mappings m
WHERE b.inv_id = m.inv_id;

Related Objects

• JTF_XML_INVOCATIONS_TL — the translation (child) table, joined on INV_ID.
• JTF_XML_EVENT_MAPPINGS — maps XML events to invocation definitions, joined on INV_ID.
• FND_APPLICATION — the registered application that owns the invocation, joined on APPLICATION_ID.
• FND_SECURITY_GROUPS — the security group assigned to the row, joined on SECURITY_GROUP_ID.
• EDW_IVTY_INV_LSTG and EDW_IVTY_INV_LTC — staging and current image tables that reference INV_ID for extraction and reporting purposes.
• IGI_AP_TRAN_TEMP — a temporary table that also carries an INV_ID reference to this object.