Search Results jtf_xml_inv_params_pk

Overview

JTF_XML_INV_PARAMS is a CRM Foundation (JTF) transactional configuration table in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores the input parameter definitions associated with an XML invocation service. The table is owned by the JTF schema and is registered as VALID in the ETRM repository. Its structural role is to hold the parameter-level metadata that describes how an individual invocation service is invoked — the parameter's name, encoding, class, and type — so that the runtime XML invocation framework can construct, validate, and dispatch calls consistently.

Where JTF_XML_INV_SERVICES_B defines the service itself, JTF_XML_INV_PARAMS defines the contract for that service. Each row describes a single input parameter belonging to one service, linked back to the service through the INV_SERVICE_ID foreign key. This parent-child shape places the table firmly on the detail side of the JTF XML invocation model.

Under the heuristic Data Vault classification mined from the foreign key structure, the object is satellite-leaning. This is a modeling suggestion rather than a prescribed design: the table carries descriptive, versioned attributes (name, type, class, encoding, end date) keyed to a parent hub-like entity, which is characteristic of a satellite. Analysts building a dimensional or Data Vault representation should treat JTF_XML_INV_SERVICES_B as the parent and this table as the descriptive detail.

Key Information Stored

The table contains 15 documented columns. The most significant are summarized below.

• PARAM_ID — Surrogate primary key, enforced by JTF_XML_INV_PARAMS_PK. This is the unique identifier for each parameter definition row.
• INV_SERVICE_ID — Foreign key to JTF_XML_INV_SERVICES_B, identifying the invocation service to which the parameter belongs. This is the principal business relationship in the table.
• PARAM_NAME — The name of the input parameter as exposed to the invocation.
• PARAM_TYPE and PARAM_CLASS — Describe the data type and structural class of the parameter, governing how values are interpreted and serialized.
• PARAM_ENCODING — The encoding applied to the parameter value, relevant when the parameter is transmitted as part of an XML payload.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting Oracle's multi-tenant security-group data isolation model.
• END_DATE — Effective-dating column indicating when the parameter definition ceases to be active.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and modification history.
• ZD_EDITION_NAME — Editioning column supporting the Online Patching / Edition-Based Redefinition model introduced in Release 12.2.

The unique index JTF_XML_INV_PARAMS_U1 (PARAM_ID, ZD_EDITION_NAME) is documented as a business-key candidate and reflects the editioning-aware uniqueness required under ADOP in 12.2.2.

Common Use Cases and Queries

The table is most often queried to reverse-engineer the input contract for a given XML invocation service, or to audit which parameters are defined across the JTF integration layer. A typical pattern joins parameters to their parent service:

• Retrieve all parameters for a service: SELECT p.param_name, p.param_type, p.param_class FROM jtf.jtf_xml_inv_params p WHERE p.inv_service_id = :service_id AND (p.end_date IS NULL OR p.end_date > SYSDATE).
• Report parameter definitions with service context: join JTF_XML_INV_PARAMS to JTF_XML_INV_SERVICES_B on INV_SERVICE_ID to produce a service-to-parameter catalog.
• Validate security-group isolation by joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.
• Audit recently changed parameter definitions using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because the table is configuration rather than high-volume transactional data, reporting volumes are typically small, and lookups are normally driven by INV_SERVICE_ID or PARAM_NAME.

Related Objects

• JTF_XML_INV_SERVICES_B — Parent service definition; joined on JTF_XML_INV_PARAMS.INV_SERVICE_ID = JTF_XML_INV_SERVICES_B.INV_SERVICE_ID.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for security-group data partitioning.
• JTF_XML_INV_PARAMS_PK — Primary key constraint on PARAM_ID.
• JTF_XML_INV_PARAMS_U1 — Unique index on (PARAM_ID, ZD_EDITION_NAME), the editioning-aware business-key candidate.
• JTF_XML_INV_SERVICES_TL — The translatable sibling of the parent service table, commonly joined alongside this table to resolve service display names.

Together these objects form the JTF XML invocation service configuration layer, with JTF_XML_INV_PARAMS supplying the parameter-level detail consumed by the invocation runtime.