Search Results fte_batch_jobs_v

Overview

FTE_BATCH_JOBS_V is a reporting and integration view within the Oracle E-Business Suite Transportation Execution (FTE) module. It exposes batch job activity associated with transportation execution processing, presenting a denormalized and partially decoded representation of the underlying batch job records. In Oracle EBS 12.1.1 and 12.2.2, FTE provides the infrastructure for rating, routing, carrier selection, and freight tendering, and batch jobs are the mechanism by which large volumes of shipment, delivery, and freight transactions are processed asynchronously. This view is the primary read interface through which those batch job records are surfaced for inquiry, monitoring, and downstream integration.

The view is not implemented as a physical database object in all environments; the ETRM metadata explicitly notes "Not implemented in this database" for the source documentation. Where it is deployed, it is most commonly consumed by custom reports, concurrent program logic, and interface programs that need to monitor job status or reconcile processed transactions against their originating business documents.

Underlying Base Objects

The view is defined over a single base table, FTE_BATCH_JOBS. No other referenced base objects are documented in the ETRM metadata for this view. The projection applies two transformations to the base table: the CREATED_BY column is passed through FTE_XML_TRANS_UTIL.GETMESSAGE to yield a readable description (aliased to JOB_STATUS_CODE), and COMPLETION_DATE is formatted as a string using the TO_CHAR(..., 'YYYY-MM-DD HH24:MI:SS') mask. Because the definition is a thin projection over one table, performance characteristics are essentially those of FTE_BATCH_JOBS, subject to the cost of the GETMESSAGE function call per row.

Key Columns

• JOB_ID — The unique identifier of the batch job record in FTE_BATCH_JOBS. This is the primary correlation key for tracing a job through its lifecycle.
• JOB_STATUS_CODE — A message/description derived at runtime by FTE_XML_TRANS_UTIL.GETMESSAGE applied to the CREATED_BY value. This provides a human-readable status rendering rather than the raw internal code.
• SUPPLIER_ID — Identifier of the supplier (carrier or service provider) associated with the batch job, linking the job to the trading partner for whom tendering or freight processing is performed.
• JOB_PROCESSED_DATE — The completion timestamp of the job, formatted as 'YYYY-MM-DD HH24:MI:SS'. Note the column name in the view differs from the base COMPLETION_DATE column it is derived from.
• SHIPPER_REFERENCE_NUMBER — The shipper's own reference for the transaction or shipment, used to reconcile the batch job against the originating order, delivery, or shipment document.
• SOURCE_CODE — Identifies the source system or originating process that generated the batch job.
• TRANSACTION_SEQUENCE — A sequence value ordering transactions within the batch, useful for deterministic processing and auditing.

Common Use Cases and Queries

The most frequent use of this view is status monitoring and reconciliation. Users searching on shipper_reference_number typically need to locate the batch job associated with a specific shipper reference and examine its status and processing date. A representative query follows:

SELECT job_id, shipper_reference_number, supplier_id, source_code, transaction_sequence, job_processed_date, job_status_code FROM fte_batch_jobs_v WHERE shipper_reference_number = :p_shipper_ref ORDER BY transaction_sequence;

For operational monitoring of recent job activity, filter on the formatted processing date:

SELECT job_id, shipper_reference_number, job_status_code, job_processed_date FROM fte_batch_jobs_v WHERE job_processed_date >= TO_CHAR(SYSDATE-1, 'YYYY-MM-DD HH24:MI:SS') ORDER BY job_processed_date DESC;

Integration programs frequently extract all jobs for a given supplier and source to feed downstream freight payment or visibility systems:

SELECT job_id, shipper_reference_number, transaction_sequence, job_status_code FROM fte_batch_jobs_v WHERE supplier_id = :p_supplier_id AND source_code = :p_source_code;

Because JOB_STATUS_CODE and JOB_PROCESSED_DATE are computed values, queries filtering on these columns may not benefit from base-table indexes; filtering on JOB_ID, SUPPLIER_ID, or SHIPPER_REFERENCE_NUMBER generally yields better performance.