Search Results jtf_xml_inv_auths




Overview
Explore in AI Chat

Overview

JTF_XML_INV_AUTHS is a table owned by the JTF schema within the CRM Foundation product module of Oracle E-Business Suite (validated against 12.1.1 and 12.2.2). As documented in the ETRM repository, it stores authentication profiles. These profiles define the credential and authorization metadata required when EBS components invoke external XML-based services — for example, outbound web service calls, integration endpoints, or online-invocation (XML INV) service registrations. Each row represents a discrete authentication profile that can be bound to one or more service registrations, making the table a reusable credential catalog rather than a transactional or audit table.

From a dimensional modeling perspective, the heuristic Data Vault classification is hub-leaning. This is consistent with the structure: a single surrogate primary key (AUTH_ID), a small set of descriptive attributes, and a wide fan-out of foreign-key references from dependent tables. Analysts designing a Data Vault or star-schema layer should therefore consider treating JTF_XML_INV_AUTHS as a hub (or dimension) keyed on AUTH_ID, with the descriptive columns carried as hub attributes or split into a satellite if historical tracking of credential changes is required.

Key Information Stored

The table contains 13 documented columns. The most significant are:

  • AUTH_ID — Surrogate primary key, enforced by JTF_XML_INV_AUTHS_PK and reinforced by the unique index JTF_XML_INV_AUTHS_U1. This is the business-key candidate and the join column for every dependent table.
  • AUTH_NAME — Human-readable name of the authentication profile, used to identify the credential in setup and administration screens.
  • AUTH_TYPE — Classifies the authentication mechanism (for example basic, token, or certificate-based schemes).
  • AUTH_INFO — Holds the authentication payload or configuration details associated with the profile.
  • URL — The endpoint or resource location to which the authentication profile applies.
  • END_DATE — Effective end date of the profile, supporting expiry handling and deactivation.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, providing multi-tenant or security-group isolation of the profile.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework to detect concurrent updates.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY record who created and last modified each profile, supporting audit reporting and data lineage.

The distinction between AUTH_ID (surrogate primary key and unique business key) and the descriptive attributes is important when building integration or extraction logic: joins should always be driven via AUTH_ID, while filtering and reporting typically use AUTH_NAME, AUTH_TYPE, or END_DATE.

Common Use Cases and Queries

Typical scenarios include identifying which authentication profile backs a given XML invocation service, auditing expired profiles, and reconciling security-group ownership of credentials.

  • Joining authentication profiles to their service registrations: 
    SELECT a.auth_id, a.auth_name, a.auth_type, s.service_name
FROM   jtf.jtf_xml_inv_auths a,
       jtf.jtf_xml_inv_services_b s
WHERE  a.auth_id = s.auth_id;
  • Locating profiles by endpoint or credential type: 
    SELECT auth_id, auth_name, url, end_date
FROM   jtf.jtf_xml_inv_auths
WHERE  auth_type = :p_type
AND    (end_date IS NULL OR end_date > SYSDATE);
  • Auditing recently changed profiles using the audit columns: 
    SELECT auth_id, auth_name, last_updated_by, last_update_date
FROM   jtf.jtf_xml_inv_auths
WHERE  last_update_date >= :p_from_date
ORDER  BY last_update_date DESC;
  • Reporting profiles by security group, joining to FND_SECURITY_GROUPS via SECURITY_GROUP_ID for multi-org or tenant-level reporting.

These patterns are commonly used in integration inventories, credential-expiry dashboards, and CRM Foundation administration reports.

Related Objects

  • JTF_XML_INV_SERVICES_B — References JTF_XML_INV_AUTHS via AUTH_ID, linking each service registration to its authentication profile.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID, providing the security-group context for each profile.
  • IGF_SE_AUTH — References AUTH_ID; part of the student-systems (IGF) integration, indicating shared credential usage across modules.
  • IGF_AW_AWD_DISB_ALL — References AUTH_ID for award-disbursement processing.
  • IGF_SE_PAYMENT — References AUTH_ID for payment integration.
  • IGF_SE_PAYMENT_INT — References AUTH_ID for payment interface processing.

Because JTF_XML_INV_AUTHS behaves as a hub, its dependent objects are primarily foreign-key satellites and transactional consumers. When extending or reporting on credentials, always resolve joins through AUTH_ID and honor SECURITY_GROUP_ID filtering to respect EBS data-security rules.