Search Results jtf_xml_inv_services_b_n2

Overview

The JTF.JTF_XML_INV_SERVICES_B table is a base (non-translated) table within the Oracle E-Business Suite JTF schema that stores the definitions of XML web service invocations. It acts as the master registry for outbound and inbound XML service calls that the EBS integration layer can dispatch, recording the service name, target application, message encoding, authentication profile, and timeout behaviour associated with each invocation. The table is classified as seed data in the APPS_TS_SEED tablespace, indicating that its rows are typically delivered as part of the application's seeded configuration rather than being created by ordinary transactional activity.

Its dependency note lists JTF.JTF_XML among its associated objects, confirming its position within the JTF XML messaging framework used for BPEL and web services orchestration. Consistent with the heuristic Data Vault classification supplied in the metadata, the object leans toward a hub: it holds a stable, uniquely identified business entity (an invocation service) with descriptive attributes, and it is referenced by several surrounding tables that capture translations, parameters, event mappings, and transport mappings.

Key Information Stored

The table's surrogate primary key is JTF_XML_INV_SERVICES_B_PK (INV_SERVICE_ID), a NUMBER column described as the invocation ID. A unique index, JTF_XML_INV_SERVICES_B_U1, enforces uniqueness on INV_SERVICE_ID, and in the 12.2.2 documented schema the uniqueness key includes ZD_EDITION_NAME, reflecting the editioning column introduced in the online patching architecture. The remaining columns capture:

• INV_NAME (VARCHAR2 50) — the human-readable name of the invocation.
• APPLICATION_ID (NUMBER) — the owning application, foreign keyed to FND_APPLICATION.
• SERVICE_GROUP_NAME and SERVICE_NAME (VARCHAR2 50 each) — the logical grouping and the specific service being invoked.
• MESSAGE_ENCODING (VARCHAR2 100) — the encoding used for the message payload.
• TIMEOUT (NUMBER) — the timeout threshold applied to the invocation.
• AUTH_ID (NUMBER) — reference to the authentication profile, foreign keyed to JTF_XML_INV_AUTHS.
• END_DATE (DATE) — the date the invocation definition ceases to be effective; indexed non-uniquely.
• SECURITY_GROUP_ID (NUMBER) — the standard security group discriminator, foreign keyed to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — the standard optimistic locking column.
• The standard WHO columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY.

Common Use Cases and Queries

Typical usage centres on auditing and configuring the integration layer: identifying which XML service invocations are defined for a given application, reviewing authentication and timeout settings, and detecting definitions that have been end-dated. A representative query joining the base record to its owning application is:

• SELECT s.INV_SERVICE_ID, s.INV_NAME, a.APPLICATION_SHORT_NAME, s.SERVICE_NAME, s.TIMEOUT FROM JTF.JTF_XML_INV_SERVICES_B s, FND_APPLICATION a WHERE s.APPLICATION_ID = a.APPLICATION_ID AND (s.END_DATE IS NULL OR s.END_DATE > SYSDATE) ORDER BY a.APPLICATION_SHORT_NAME;
• Filter on AUTH_ID against JTF_XML_INV_AUTHS to report which authentication profiles are consumed by which services.
• Filter on END_DATE to surface expired invocations for cleanup.
• Join to JTF_XML_INV_PARAMS to inspect the parameter set passed to a given invocation.

Reporting usage frequently targets the non-unique indexes JTF_XML_INV_SERVICES_B_N1 (APPLICATION_ID) and JTF_XML_INV_SERVICES_B_N2 (END_DATE), which support application-scoped listing and active/expired filtering respectively.

Related Objects

The table participates in a well-defined cluster of integration objects:

• FND_APPLICATION via APPLICATION_ID — identifies the owning application.
• JTF_XML_INV_AUTHS via AUTH_ID — supplies the authentication profile for the invocation.
• FND_SECURITY_GROUPS via SECURITY_GROUP_ID — enforces security grouping.
• JTF_XML_INV_SERVICES_TL via INV_SERVICE_ID — stores translated name and description, making the base table the language-independent anchor.
• JTF_XML_INV_PARAMS via INV_SERVICE_ID — holds parameter definitions for each invocation.
• JTF_XML_EVENT_MAPPINGS via INV_SERVICE_ID — associates business events with invocation services.
• JTF_XML_INV_TMAPPINGS via INV_SERVICE_ID — maps invocations to transport configuration.

Collectively these relationships make JTF_XML_INV_SERVICES_B the central hub from which the JTF XML web service integration metadata is resolved.