Search Results jtf_xml_inv_auths_u1

Overview

JTF.JTF_XML_INV_AUTHS is a seed-data table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the JTF (Java Technology Foundation) schema and registered under FND Design Data as JTF.JTF_XML_INV_AUTHS. It stores authentication profiles used by the XML Invoice and related XML integration infrastructure. Each row defines how an outbound or inbound XML transaction should authenticate against an external endpoint — capturing the target URL, the authentication mechanism, a profile name, and a free-form authentication payload such as a credential token, username/password pair, or certificate reference. Because these records are seeded as administrative configuration rather than transactional data, the table resides in the APPS_TS_SEED tablespace with a PCT Free of 10.

Functionally, the table acts as a small configuration hub from which multiple invoicing and payment programs resolve authentication credentials at runtime. Under the heuristic Data Vault classification supplied in the metadata, JTF_XML_INV_AUTHS is described as hub-leaning. This is consistent with its role: it holds a stable business key surrounded by descriptive attributes, and is referenced by several dependent tables. In strict Data Vault terms it behaves as a hub with an embedded satellite, since descriptive columns such as URL, AUTH_TYPE, and AUTH_NAME are carried directly on the same physical row.

Key Information Stored

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

• AUTH_ID — the surrogate primary key (JTF_XML_INV_AUTHS_PK) and the column exposed by the unique index JTF_XML_INV_AUTHS_U1. It is also the business-key candidate that downstream tables use as a foreign key.
• URL — the endpoint against which authentication is performed; indexed by JTF_XML_INV_AUTHS_N1.
• AUTH_TYPE — the authentication profile type, distinguishing the credential scheme in use.
• AUTH_NAME — the human-readable profile name used when administrators select a profile.
• AUTH_INFO — the largest column (VARCHAR2 2048), holding the credential payload.
• END_DATE — the expiration date of the profile; indexed by JTF_XML_INV_AUTHS_N2 and typically used to filter active records.
• SECURITY_GROUP_ID — standard multi-org/security grouping column with a foreign key to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking control for concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard Who columns capturing audit trail information, with LAST_UPDATED_BY and CREATED_BY referencing FND_USER.USER_ID and LAST_UPDATE_LOGIN referencing FND_LOGINS.LOGIN_ID.

The separation of the surrogate key (AUTH_ID) from the business identifiers (URL, AUTH_NAME) supports stable foreign-key relationships while allowing profile definitions to change over time.

Common Use Cases and Queries

The primary use case is resolving the correct credentials for an XML invoicing transaction. ETL and support teams frequently query the table to audit which URLs are configured and whether any profiles have expired:

• Listing all active profiles by joining AUTH_ID to dependent invoice tables and filtering records where END_DATE is null or greater than SYSDATE.
• Identifying duplicate or overlapping URL entries using the JTF_XML_INV_AUTHS_N1 index column.
• Auditing credential changes by ordering on LAST_UPDATE_DATE and joining LAST_UPDATED_BY to FND_USER.USER_ID.
• Confirming profile usage by counting references from IGF and JTF_XML_INV_SERVICES_B.

A representative query pattern selects from JTF.JTF_XML_INV_AUTHS with a predicate on AUTH_ID when a specific profile is required, or on URL and END_DATE when searching by endpoint. Because AUTH_INFO can contain sensitive data, reporting extracts should exclude that column unless explicitly required.

Related Objects

JTF_XML_INV_AUTHS does not reference any table other than through its SECURITY_GROUP_ID foreign key to FND_SECURITY_GROUPS. Conversely, it is referenced by several dependent tables via the AUTH_ID column:

• JTF.JTF_XML_INV_SERVICES_B — joins on AUTH_ID; ties authentication profiles to XML invoice services.
• IGF.IGF_SE_AUTH — joins on AUTH_ID; student-systems authorization records.
• IGF.IGF_AW_AWD_DISB_ALL — joins on AUTH_ID; award disbursement records.
• IGF.IGF_SE_PAYMENT_INT — joins on AUTH_ID; payment interface rows.
• IGF.IGF_SE_PAYMENT — joins on AUTH_ID; student payment records.
• FND.FND_USER and FND.FND_LOGINS — referenced indirectly through the Who columns LAST_UPDATED_BY, CREATED_BY, and LAST_UPDATE_LOGIN.
• FND_SECURITY_GROUPS — the parent of the SECURITY_GROUP_ID foreign key.

The APPS schema grants the JTF_XML_INV_AUTH synonym, which is the object name most commonly referenced by application code and ad-hoc queries.