Search Results jtf_fm_request_history




Overview
Explore in AI Chat

Overview

The JTF_FM_REQUEST_HISTORY view is a CRM Foundation (JTF) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes request history information generated by the JTF Foundation Management request-processing framework. This framework handles asynchronous and concurrent requests such as concurrent-program submissions, business-event-driven jobs, and workflow-triggered processing. Each row in the view represents the outcome of a single submitted request, together with the source, template, server, priority, and audit context associated with it.

The view is primarily used for monitoring and troubleshooting CRM Foundation request processing. Because it presents a denormalized, timestamps-mostly-ready projection of the underlying history table, it is well suited to operational dashboards, exception reporting, and integration extracts. The PROCESSED_DT_TM column is of particular interest to users searching for processing timestamps, as it reports when a request reached a terminal or intermediate processed state.

Underlying Base Objects

The view is defined over a single documented base object: the synonym JTF_FM_REQUEST_HISTORY_ALL. This is the multi-organization (ORG_ID-enabled) history table maintained by the JTF FM request subsystem. The _ALL suffix indicates that rows are partitioned by operating unit through ORG_ID, so any query that is not scoped to a single organization must either filter on ORG_ID or account for the multiple organizations present. The view applies a small transformation before exposing the data, most notably a DECODE on PROCESSED_DT_TM.

Key Columns

Common Use Cases and Queries

Typical uses include reviewing request outcomes by source, identifying unprocessed requests (where PROCESSED_DT_TM is NULL), measuring turnaround time between SUBMIT_DT_TM and PROCESSED_DT_TM, and auditing resubmissions through RESUBMIT_COUNT and PARENT_REQ_ID.

Because the view exposes PROCESSED_DT_TM as a formatted character string when populated, string and NULL comparisons behave differently from date comparisons. The following examples reflect that behavior:

  • Find requests not yet processed:
    SELECT HIST_REQ_ID, REQUEST, SUBMIT_DT_TM FROM APPS.JTF_FM_REQUEST_HISTORY WHERE PROCESSED_DT_TM IS NULL;
  • Find requests processed on a given day:
    SELECT HIST_REQ_ID, REQUEST, PROCESSED_DT_TM FROM APPS.JTF_FM_REQUEST_HISTORY WHERE PROCESSED_DT_TM LIKE '2024-01-15%';
  • Count outcomes by code:
    SELECT OUTCOME_CODE, COUNT(*) FROM APPS.JTF_FM_REQUEST_HISTORY GROUP BY OUTCOME_CODE;
  • Scope to an organization:
    SELECT * FROM APPS.JTF_FM_REQUEST_HISTORY WHERE ORG_ID = :org_id;

Repeated resubmissions should always be reconciled through PARENT_REQ_ID to avoid double-counting related history rows, and soft-deleted rows should be excluded with F_DELETEDFLAG where appropriate.