Results for “jtf_xml_invocations_vl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_XML_INVOCATIONS_VL is a CRM Foundation (JTF) view that stores event information related to Java-based XML invocation registrations. It is a "_VL" (translated) view, meaning it exposes a language-specific slice of the underlying translatable entity, returning only rows whose translation matches the session language. The view's purpose is to present XML invocation definitions (business events registered for a Java class implementation) joined with their language-specific description text, giving applications and reports a single, denormalized source for invocation metadata.

Because it is a view rather than a table, JTF_XML_INVOCATIONS_VL is not a seat of primary data. It is used for querying, reporting, and lookup purposes so that consumers do not have to manually join the base and translation tables while also applying the language filter. In the supplied ETRM metadata, the object carries the note "Not implemented in this database," indicating the view may be present only in environments where the relevant JTF XML invocation setup has been deployed or seeded, and no base objects were documented as referenced in that metadata capture.

Underlying Base Objects

Although the documented metadata lists no referenced base objects, the view text itself defines the relationship. JTF_XML_INVOCATIONS_VL is defined over two base objects:

• JTF_XML_INVOCATIONS_B — the base ("_B") table holding non-translatable attributes such as INV_ID, APPLICATION_ID, INV_NAME, INV_TYPE, JAVA_TYPE, END_DATE, audit columns, ORIG_SYSTEM/SECURITY_GROUP_ID, and OBJECT_VERSION_NUMBER.
• JTF_XML_INVOCATIONS_TL — the translation ("_TL") table holding DESCRIPTION (and the LANGUAGE column) keyed by INV_ID.

The join is B.INV_ID = T.INV_ID combined with T.LANGUAGE = USERENV('LANG'). This pattern is standard Oracle multi-language support (MLS): the _B table holds one row per invocation, while the _TL table holds one row per installed language. The view's WHERE clause reduces the result to the single language of the current session, so each INV_ID appears once. The view also exposes B.ROWID as ROW_ID, allowing row identification.

Key Columns

• ROW_ID — ROWID of the base table row, useful for row addressing.
• INV_ID — primary identifier of the invocation; the join key between base and translation tables, and the value most often referenced by child objects.
• INV_NAME — the name of the invocation. This is the column most directly relevant to the user's search term "inv_name"; it is the human-readable identifier for the registered XML invocation/business event.
• APPLICATION_ID — the Oracle application (application_id from FND_APPLICATION) that owns the invocation.
• INV_TYPE — classification of the invocation (for example, the category or mechanism of the event).
• JAVA_TYPE — the Java class or type associated with the invocation; defines how the event is dispatched.
• END_DATE — the date on which the invocation ceases to be active, supporting date-effective lookups.
• SECURITY_GROUP_ID — security grouping, relevant in multi-org or restricted-access contexts.
• OBJECT_VERSION_NUMBER — optimistic locking version for concurrent updates.
• DESCRIPTION — language-specific description of the invocation, sourced from the _TL table.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically queried to look up invocation definitions by name, by application, or to display them with descriptions for configuration and diagnostic purposes. A straightforward lookup by invocation name follows the pattern below.

• Look up an invocation by name: SELECT inv_id, inv_name, inv_type, java_type FROM jtf_xml_invocations_vl WHERE inv_name = :inv_name;
• List active invocations for an application: SELECT inv_id, inv_name, java_type FROM jtf_xml_invocations_vl WHERE application_id = :app_id AND (end_date IS NULL OR end_date > SYSDATE) ORDER BY inv_name;
• Join to other setup objects using INV_ID as the foreign key to resolve descriptions or child registrations.

Because the view is language-filtered through USERENV('LANG'), query results return descriptions in the caller's session language, which makes it well suited for user-facing reports and concurrent-program output. When an invocation's name is known but its INV_ID is not, this view is the canonical place to resolve the identifier before joining to related invocation or event tables.