Results for “jtf_fm_status_all_u1”

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

Overview

JTF_FM_STATUS_ALL is a CRM Foundation (JTF) table in Oracle E-Business Suite that stores fulfillment status information for asynchronous requests processed by the fulfillment manager. It records the operational state of each submitted request — such as its request identifier, submission time, processing mode, and outcome — providing the persistence layer that the fulfillment engine relies on to track, requeue, and report on background processing activity. In Release 12.1.1 and 12.2.2 the table is owned by the JTF schema and is marked VALID in the ETRM repository, with 41 documented columns.

From a dimensional modeling perspective, the mined foreign-key structure classifies this object heuristically as standalone, meaning it does not participate in a conformed hub-and-link web within the Data Vault sense. It behaves more like a self-contained transaction/status satellite: each row is an event keyed to a request, and the only documented outbound relationship is to the security group table. Modelers should treat it as a factless-style status journal rather than a traditional dimension.

Key Information Stored

The documented primary key is JTF_FM_STATUS_ALL_PK, composed of REQUEST_ID and SUBMIT_DT_TM. A parallel unique index, JTF_FM_STATUS_ALL_U1, covers the same two columns and serves as the documented business-key candidate. The composite key implies that a single request may appear multiple times, distinguished by submission timestamp — for example, on requeue.

• REQUEST_ID, SUBMIT_DT_TM — composite identifier of the fulfillment request and the moment it was submitted.
• REQUEST_STATUS, REQUEST_MODE — the current processing state and the execution mode under which the request was launched.
• ORDER_ID, OBJECT_ID, OBJECT_TYPE, SOURCE_CODE, SOURCE_CODE_ID — the business object the request acts upon and the source system designation from which it originated.
• REQUEUE_COUNT, JOBS_PROCESSED — retry telemetry and the count of jobs handled, useful for diagnosing stalled or looping requests.
• SERVER_ID, TEMPLATE_ID, GROUP_ID, PRIORITY — routing and scheduling attributes controlling which server and processing template handle the work.
• USER_ID, MESSAGE_ID — the submitting user and any associated message reference.
• ORG_ID, SECURITY_GROUP_ID — multi-org and security-group partitioning; SECURITY_GROUP_ID is the only documented foreign key, referencing FND_SECURITY_GROUPS.
• F_DELETEDFLAG, OBJECT_VERSION_NUMBER — soft-delete indicator and optimistic locking column used by the OAF/BC4J layer.
• ATTRIBUTE1 through ATTRIBUTE15, WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — the standard descriptive flexfield and audit columns present on most EBS transactional tables.

Common Use Cases and Queries

Typical usage centers on monitoring asynchronous fulfillment activity, troubleshooting failures, and feeding operational reports. A common pattern retrieves the most recent status per request:

• Identify failures: SELECT REQUEST_ID, REQUEST_STATUS, REQUEUE_COUNT FROM JTF.JTF_FM_STATUS_ALL WHERE REQUEST_STATUS = 'ERROR';
• Trace activity for a business object: SELECT REQUEST_ID, SUBMIT_DT_TM, REQUEST_MODE FROM JTF.JTF_FM_STATUS_ALL WHERE OBJECT_ID = :p_object_id AND OBJECT_TYPE = :p_type ORDER BY SUBMIT_DT_TM DESC;
• Throughput reporting by day: aggregate counts grouped by TRUNC(SUBMIT_DT_TM) and REQUEST_MODE.
• Detect requeue hot spots: SELECT REQUEST_ID, MAX(REQUEUE_COUNT) FROM JTF.JTF_FM_STATUS_ALL GROUP BY REQUEST_ID HAVING MAX(REQUEUE_COUNT) > 3;

Reporting queries should respect ORG_ID and SECURITY_GROUP_ID to honor multi-org and data-security enforcement, and should filter F_DELETEDFLAG when active records are required.

Related Objects

• FND_SECURITY_GROUPS — referenced by JTF_FM_STATUS_ALL.SECURITY_GROUP_ID; the sole documented foreign-key relationship.
• JTF_FM_STATUS_ALL_PK / JTF_FM_STATUS_ALL_U1 — the primary key constraint and unique index enforcing uniqueness on REQUEST_ID and SUBMIT_DT_TM.
• FND_CONCURRENT_REQUESTS — commonly joined via REQUEST_ID where fulfillment requests correspond to concurrent program submissions.
• JTF_FM_* fulfillment manager tables — the surrounding fulfillment framework objects that share REQUEST_ID as the correlation key.
• FND_USER — joined through USER_ID and the WHO columns to resolve submitting and updating users.
• HR_ALL_ORGANIZATION_UNITS — joined via ORG_ID for multi-org reporting context.