Results for “use_pending_req_flag”

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

Overview

JTF_UM_APPROVALS_B is a base table in the JTF schema, owned by the CRM Foundation product (often labeled "JTF - CRM Foundation"). It defines the header (base) records that describe approval configurations used by the Oracle User Management (UM) and workflow-driven sign‑off features in Oracle E‑Business Suite 12.1.1 and 12.2.2. Each row represents a discrete approval definition, keyed by APPROVAL_ID, that can be referenced by multiple dependent entities such as translations, approvers, user types, subscriptions, and fulfillment or service request transactions.

From a Data Vault modeling perspective, the metadata heuristically classifies this table as hub‑leaning. That is consistent with its structure: it holds a stable business key (APPROVAL_ID and APPROVAL_KEY) with descriptive attributes, and it is referenced by numerous child tables through APPROVAL_ID. In Data Vault terms this behaves like a hub for the approval concept, with dependent tables (for example JTF_UM_APPROVALS_TL and JTF_UM_APPROVERS) acting as satellites or links that carry the translated text and the participant relationships.

Key Information Stored

The table contains 15 documented columns. The most significant are:

• APPROVAL_ID — the surrogate primary key (JTF_UM_APPROVALS_B_PK) and the foreign key targeted by all child tables.
• APPROVAL_KEY — a business-key candidate that provides a human-recognizable identifier for the approval definition.
• ENABLED_FLAG — indicates whether the approval configuration is active and available for use.
• WF_ITEM_TYPE — the workflow item type associated with the approval; this is a foreign key to WF_ITEM_TYPES and ties the record to Oracle Workflow.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — the date range over which the approval is valid, supporting date‑effective querying.
• APPLICATION_ID — identifies the owning application, typically within the EBS application taxonomy.
• SECURITY_GROUP_ID — a reference to FND_SECURITY_GROUPS used for multi‑org or data‑security filtering.
• USE_PENDING_REQ_FLAG — controls whether a pending requisition or request must exist before the approval can be processed.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN provide standard EBS who‑did‑what tracking.
• ZD_EDITION_NAME — participates in the unique index JTF_UM_APPROVALS_B_U1 (APPROVAL_ID, ZD_EDITION_NAME), which is the documented business-key candidate and supports the editioning pattern used in later EBS releases.

Common Use Cases and Queries

Typical usage centers on listing active approvals, resolving the workflow item type behind an approval, and joining to translations or approvers for reporting. A simple lookup joins the base table to Workflow item types:

SELECT a.approval_id, a.approval_key, a.enabled_flag, w.name
FROM jtf.jtf_um_approvals_b a, wf_item_types w
WHERE a.wf_item_type = w.name AND a.enabled_flag = 'Y';

For instance-level reporting, filter on EFFECTIVE_START_DATE/EFFECTIVE_END_DATE and SECURITY_GROUP_ID, or join to JTF_UM_APPROVERS to count approvers per approval. A multilingual report joins to JTF_UM_APPROVALS_TL on APPROVAL_ID to retrieve translated names and descriptions. Because many other objects reference APPROVAL_ID (including FV_BE_RPR_TRANSACTIONS, FV_BE_TRX_HDRS, and JTF_UM_SUBSCRIPTIONS_B), the table is also useful for tracing which approvals are referenced by transactions, subscriptions, and user types, and for detecting orphaned or unused approval definitions.

Related Objects

The following are the most significant dependent and referenced objects, with the actual join columns:

• WF_ITEM_TYPES — referenced by JTF_UM_APPROVALS_B.WF_ITEM_TYPE.
• FND_SECURITY_GROUPS — referenced by JTF_UM_APPROVALS_B.SECURITY_GROUP_ID.
• JTF_UM_APPROVALS_TL — child translation table; joins on APPROVAL_ID.
• JTF_UM_APPROVERS — child table listing approvers; joins on APPROVAL_ID.
• JTF_UM_USERTYPES_B — references this table through APPROVAL_ID.
• JTF_UM_SUBSCRIPTIONS_B — references this table through APPROVAL_ID.
• FV_BE_TRX_HDRS — references this table through APPROVAL_ID.
• FV_BE_RPR_TRANSACTIONS — references this table through APPROVAL_ID.

These relationships confirm the hub role of JTF_UM_APPROVALS_B within the CRM Foundation approval model, with dependent satellites and linking tables extending the definition and usage of each approval.