Search Results jtf_xml_inv_params_n1

Overview

JTF.JTF_XML_INV_PARAMS is a VALID table owned by the JTF schema and registered in FND Design Data as JTF.JTF_XML_INV_PARAMS. It stores input parameter information for an invocation; each parameter that an invocation provides maps to a single row in this table. The table therefore acts as the configuration layer through which XML-based invocations declare the inputs they accept and how those inputs are typed and encoded before the invocation is executed.

All data resides in the APPS_TS_SEED tablespace with PCTFREE 10, consistent with reference and setup data rather than high-volume transactional data. The table participates in the EBS Data Vault model as a satellite-leaning entity: it carries descriptive attributes (parameter name, encoding, class, type) attached to an invocation service, but it does not sit on the primary transaction path. Its direct parent is JTF_XML_INV_SERVICES_B, referenced through INV_SERVICE_ID, and its row-level security is anchored through SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Key Information Stored

The surrogate primary key is PARAM_ID, implemented by the index JTF_XML_INV_PARAMS_PK. The documented unique index JTF_XML_INV_PARAMS_U1 covers (PARAM_ID, ZD_EDITION_NAME), which is the business-key candidate and reflects the Editioning View / online patching edition column introduced in 12.2. The most significant columns are:

• PARAM_ID — surrogate identifier and primary key for each parameter row.
• INV_SERVICE_ID — foreign key to JTF_XML_INV_SERVICES_B, tying the parameter to its owning invocation.
• PARAM_NAME (VARCHAR2 30) — the parameter's name as exposed to the invocation.
• PARAM_ENCODING (VARCHAR2 100) — encoding applied to the parameter value.
• PARAM_CLASS (VARCHAR2 256) — fully qualified Java class name used to bind the parameter.
• PARAM_TYPE (VARCHAR2 10) — the parameter type classification.
• END_DATE — effective end date; also indexed by JTF_XML_INV_PARAMS_N2.
• ZD_EDITION_NAME (VARCHAR2 30) — edition identifier used by 12.2 online patching.
• Standard Who columns — SECURITY_GROUP_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — provide auditing and row-level security.

The nonunique index JTF_XML_INV_PARAMS_N1 on INV_SERVICE_ID supports joining parameters back to their invocation.

Common Use Cases and Queries

Typical use cases include listing all parameters for a given invocation service, identifying parameters that have expired, and inspecting the Java class and encoding used to bind a parameter. A common retrieval pattern follows the documented query:

• SELECT PARAM_ID, INV_SERVICE_ID, PARAM_NAME, PARAM_ENCODING, PARAM_CLASS, PARAM_TYPE, END_DATE FROM JTF.JTF_XML_INV_PARAMS WHERE INV_SERVICE_ID = :service_id;
• SELECT p.PARAM_ID, p.PARAM_NAME, s.SERVICE_NAME FROM JTF.JTF_XML_INV_PARAMS p, JTF.JTF_XML_INV_SERVICES_B s WHERE p.INV_SERVICE_ID = s.INV_SERVICE_ID AND p.END_DATE IS NULL;
• SELECT INV_SERVICE_ID, COUNT(*) FROM JTF.JTF_XML_INV_PARAMS GROUP BY INV_SERVICE_ID; for inventory and exception reporting.

Because the table is a seed/setup data object, queries are typically read-only and used during integration diagnostics rather than in high-frequency transactional processing.

Related Objects

• JTF.JTF_XML_INV_SERVICES_B — parent invocation service table joined on INV_SERVICE_ID.
• JTF.JTF_XML — the broader XML invocation infrastructure associated with this object's dependency chain.
• FND_SECURITY_GROUPS — row-level security reference joined on SECURITY_GROUP_ID.
• FND_USER — referenced by LAST_UPDATED_BY and CREATED_BY.
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN.

These relationships establish the table as a satellite of the invocation service, providing per-parameter configuration and audit context within the EBS JTF XML integration framework.