Search Results process_dt_tm

Overview

APPS.JTF_FM_REQUEST_HISTORY is an Oracle E-Business Suite view that exposes the historical record of fulfillment or job submission requests processed by the JTF (Java Technology Foundation) foundation layer. In the context of Release 12.1.1 and 12.2.2, this view is primarily consumed by reporting, diagnostics, and integration components that need to audit the lifecycle of a submitted request — including its submission time, processing outcome, priority, associated media type, and the eventual completion timestamp.

The view is a thin, non-modifying projection over the underlying storage table and performs a small but meaningful data transformation on the processing timestamp. It is owned by the APPS schema and is intended as a read-only reporting surface. Because it does not carry its own storage, its behavior is entirely determined by the definition text and the base object it selects from.

Underlying Base Objects

The view is defined over a single documented base object, exposed within the APPS schema as a synonym:

• JTF_FM_REQUEST_HISTORY_ALL (SYNONYM) — the actual storage object holding the full request history, including multi-org (ORG_ID) and deletion-flag (F_DELETEDFLAG) semantics implied by the _ALL suffix.

No joins, unions, or aggregations are present. The view's sole business transformation is a DECODE applied to the processing timestamp column, which is examined below. Because it references a synonym, the view inherits whatever object is currently resolved for that synonym in the APPS schema, which is the conventional EBS pattern.

Key Columns

The view exposes the full column list of the base object, including several identifiers and audit columns. Notable columns include:

• HIST_REQ_ID — primary identifier for the history row.
• REQUEST, REQUEST_TYPE, PARENT_REQ_ID — the request payload and its hierarchical relationship for grouped or child requests.
• SUBMIT_DT_TM — the timestamp the request was originally submitted.
• PROCESS_DT_TM — the raw processing timestamp on the base object.
• PROCESSED_DT_TM — a derived character column produced by DECODE(PROCESS_DT_TM, NULL, PROCESSED_DT_TM, TO_CHAR(PROCESS_DT_TM,'YYYY-MM-DD HH24:MI:SS')). When PROCESS_DT_TM is null, the pre-existing PROCESSED_DT_TM value is returned; otherwise the processing timestamp is converted to a formatted string.
• OUTCOME_CODE, OUTCOME_DESC — the result of the processing attempt.
• SERVER_ID, TEMPLATE_ID, GROUP_ID, MESSAGE_ID — routing and identification attributes.
• RESUBMIT_COUNT, PRIORITY, TOTAL_JOBS, MEDIA_TYPE — operational attributes describing the request.
• ORG_ID, F_DELETEDFLAG, OBJECT_VERSION_NUMBER — multi-org, soft-delete, and optimistic-locking columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• USER_ID, ORDER_ID, OBJECT_TYPE, OBJECT_ID, SOURCE_CODE, SOURCE_CODE_ID, APP_INFO — contextual and source-reference columns.

The PROCESSED_DT_TM column is the primary point of interest for the searched term, and it is important to note that it is returned as a character string, not a native date. Queries that filter or order on it must account for this conversion.

Common Use Cases and Queries

Typical scenarios include auditing failed or outstanding requests, tracking processing latency between submission and outcome, and locating requests by source, server, or grouping.

• Identifying requests that have not yet been processed (null processing timestamp).
• Listing recent outcomes for a given SERVER_ID or GROUP_ID.
• Measuring latency between SUBMIT_DT_TM and PROCESS_DT_TM.
• Reporting on requests flagged as deleted or scoped to a specific ORG_ID.

Sample queries:

SELECT HIST_REQ_ID, REQUEST, OUTCOME_CODE, OUTCOME_DESC,
       SUBMIT_DT_TM, PROCESSED_DT_TM
  FROM APPS.JTF_FM_REQUEST_HISTORY
 WHERE PROCESS_DT_TM IS NULL
   AND F_DELETEDFLAG = 'N';

SELECT HIST_REQ_ID, SERVER_ID, PRIORITY, PROCESSED_DT_TM
  FROM APPS.JTF_FM_REQUEST_HISTORY
 WHERE SERVER_ID = :p_server_id
   AND PROCESS_DT_TM >= TO_DATE(:p_from,'YYYY-MM-DD HH24:MI:SS')
 ORDER BY PROCESS_DT_TM DESC;

Note that because PROCESSED_DT_TM is a character value, range filtering and sorting are best performed against the underlying PROCESS_DT_TM date column rather than the derived string.