Search Results jfufrq_pk

Overview

JTF_FM_REQUESTS_AQ is a table owned by the JTF schema (CRM Foundation product family) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is internal: the Fulfillment Server uses it to store information about the queues into which fulfillment requests are placed. The table therefore acts as the persistence layer for the association between a fulfillment request and its Oracle Advanced Queuing (AQ) message, allowing the Fulfillment Server to correlate an outbound request record with the queue mechanism that carries or stages it.

The ETRM relationship data provides a heuristic Data Vault classification of standalone, meaning no foreign-key relationships to other tables were mined from the constraint structure. In Data Vault modeling terms this suggests the object is best treated as a standalone construct rather than a conventional hub, link, or satellite: it carries a composite identifier and descriptive attributes, but no documented FK paths connect it to parent hubs. That classification should be read as a modeling suggestion derived from constraint metadata, not as a statement about logical business dependency.

Key Information Stored

The documented physical schema contains eight columns in 12.2.2. The most significant are:

• REQUEST_ID — identifier of the fulfillment request placed in a queue. Part of the composite primary key and the principal business-key candidate for joining back to request records.
• AQ_MSG_ID — identifier of the associated Oracle Advanced Queuing message. Also part of the composite primary key.
• QUEUE_TYPE — the only documented non-key descriptive attribute; distinguishes the category of queue in which the request was placed.
• CREATED_BY, CREATION_DATE — standard audit columns recording who created the queue association and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the last modification and the login context of the updater.

The surrogate primary key is documented as JFUFRQ_PK, defined over the composite of REQUEST_ID and AQ_MSG_ID. Because the PK is composite and built from two business-meaningful identifiers rather than a generated sequence, the primary key itself functions as the uniqueness guarantee; no separate single-column unique index is documented. Columns such as QUEUE_TYPE plus REQUEST_ID form the natural business-key candidate for querying.

Common Use Cases and Queries

Because the table is maintained internally by the Fulfillment Server, direct DML is not supported and should be avoided. Typical use is diagnostic and reporting-oriented:

• Identifying which queue type carried a given fulfillment request, and whether multiple AQ messages were recorded for one request.
• Troubleshooting stuck or duplicate fulfillment processing by tracing REQUEST_ID to AQ_MSG_ID.
• Volume and throughput reporting by QUEUE_TYPE over CREATION_DATE ranges.
• Audit review of who last touched a queue association via LAST_UPDATED_BY and LAST_UPDATE_DATE.

A representative query joins the queue association to the request header:

• SELECT r.request_id, r.aq_msg_id, r.queue_type, r.creation_date FROM jtf.jtf_fm_requests_aq r WHERE r.queue_type = :p_queue_type AND r.creation_date >= :p_from_date ORDER BY r.creation_date DESC;
• SELECT r.request_id, COUNT(*) aq_msg_count FROM jtf.jtf_fm_requests_aq r GROUP BY r.request_id HAVING COUNT(*) > 1;

Related Objects

The documented relationship data classifies this object as standalone, so no FK-constrained parents or children are recorded. The most significant associated objects are therefore the fulfillment and queuing components that logically reference it:

• JTF_FM_REQUESTS or the equivalent Fulfillment Server request header table, joined on REQUEST_ID — the primary logical parent of this queue association.
• JTF_FM_REQUEST_ITEMS and related request-line tables, reachable through REQUEST_ID.
• Oracle Advanced Queuing dictionary views (for example AQ$ and USER_QUEUE_TABLES families), correlated via AQ_MSG_ID to resolve message metadata.
• Fulfillment Server concurrent programs and PL/SQL packages in the JTF schema that insert, update, and consume rows in this table.
• The composite key JFUFRQ_PK constraint, which defines the uniqueness semantics used by any external query.

Any integration or report should treat JTF_FM_REQUESTS_AQ as read-only internal state owned by the Fulfillment Server and join through REQUEST_ID to reach supported business entities.