Results for “jtf_hooks_data”

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

Overview

JTF_HOOKS_DATA is a CRM Foundation (JTF) repository table that stores the internal hook call-out registrations used by the Oracle E-Business Suite hook mechanism. In Oracle EBS 12.1.1 and 12.2.2, hooks provide a metadata-driven extension framework: instead of modifying seeded application code, developers register a public API that the framework invokes at a designated point in a business flow. The hook_package attribute, which is part of the composite primary key and the business identity of each row, names the PL/SQL package that defines the hook interface being extended; together with hook_api, product_code, package_name, and api_name, it uniquely identifies which customer extension is wired to which seeded hook point. The table therefore acts as the routing directory for both Oracle-seeded and customer-defined extensions across CRM Foundation and its dependent modules.

From a Data Vault modeling perspective, the metadata classifies this object as standalone, with no foreign-key dependencies to other documented tables. A heuristic suggestion, therefore, is to model JTF_HOOKS_DATA as a hub-like reference set keyed on the composite business key (HOOK_TYPE, HOOK_PACKAGE, HOOK_API, PRODUCT_CODE, PACKAGE_NAME, API_NAME), with the mutable control attributes treated as satellite-type descriptive data. This classification is a modeling heuristic derived from the FK structure, not a physical constraint declared by Oracle.

Key Information Stored

The documented physical schema contains fifteen columns. The most functionally significant are:

• HOOK_PACKAGE — the PL/SQL package implementing the hook interface; a principal business-key component and the primary lookup target for the hook_package search term.
• HOOK_API — the specific API within the hook package that the framework calls.
• HOOK_TYPE — categorizes the hook (for example, before/after processing or substitution semantics), governing when and how the call-out fires.
• PRODUCT_CODE, PACKAGE_NAME, API_NAME — identify the seeded product and the target package/API being extended, completing the composite business key.
• EXECUTE_FLAG — controls whether the registered hook is active; typically toggled to enable or disable a customization without deleting the row.
• PROCESSING_TYPE — defines how multiple matching hooks are handled, such as single execution versus chaining of all registered implementations.
• EXECUTION_ORDER — the numeric precedence used to sequence multiple hooks registered against the same hook point.
• HOOK_ID — the surrogate identifier for the row, distinct from the composite business key.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording insert and change history.

The primary key JTF_HOOKS_DATA_PK is composite, spanning HOOK_TYPE, HOOK_PACKAGE, HOOK_API, PRODUCT_CODE, PACKAGE_NAME, and API_NAME. This composite key, rather than HOOK_ID, constitutes the true business-key candidate; HOOK_ID serves as a surrogate reference.

Common Use Cases and Queries

The dominant use case is diagnosing extension behavior: identifying which customer package is invoked for a given seeded API, verifying that an extension is enabled, and confirming execution ordering when multiple hooks compete for the same point.

• Locate a hook by package: SELECT hook_type, hook_package, hook_api, execute_flag, execution_order FROM jtf.jtf_hooks_data WHERE hook_package = :pkg;
• List active extensions for a seeded API: SELECT hook_package, hook_api, processing_type FROM jtf.jtf_hooks_data WHERE product_code = :prod AND package_name = :pkg AND api_name = :api AND execute_flag = 'Y' ORDER BY execution_order;
• Audit recent changes: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace configuration drift.
• Duplicate or misconfigured registrations where the same hook point appears under multiple types.

Reporting typically profiles hook inventory by product code, counts active versus inactive registrations, and highlights custom (non-seeded) packages for upgrade-impact analysis.

Related Objects

Because JTF_HOOKS_DATA is classified as standalone in the documented FK structure, joins are logical rather than enforced:

• FND_HOOKS / FND_HOOKS_CALLS style hook framework and lookup tables — join on hook type or product code to resolve seeded hook points.
• FND_PRODUCT_INSTALLATIONS / FND_APPLICATION — join PRODUCT_CODE to APPLICATION_SHORT_NAME for readable product names.
• FND_FORM_FUNCTIONS and FND_API registries — correlate PACKAGE_NAME and API_NAME with registered extension APIs.
• JTF_HOOKS_DATA itself, via HOOK_ID, when referenced by auxiliary configurations.
• FND_LOG_MESSAGES — join on package and API names to correlate runtime errors with registered hooks during troubleshooting.