Results for “fte_batch_jobs”

16 results




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

Overview

FTE_BATCH_JOBS is a table within the Oracle E-Business Suite Transportation Execution (FTE) module. Its documented purpose is to store information about jobs being processed by the Transportation Execution batch infrastructure. In the FTE architecture, concurrent programs and background processes submit units of work — referred to as jobs — and FTE_BATCH_JOBS acts as the operational record of those jobs, capturing their identity and the trading partner context in which they execute.

The table is identified by the primary key constraint FTE_BATCH_JOBS_PK, defined on the JOB_ID column. JOB_ID is a surrogate identifier: it carries no intrinsic business meaning and exists solely to give each batch job a stable, system-generated handle. The documented foreign key to HZ_PARTIES via SUPPLIER_ID confirms that each job record is associated with a supplier or party registered in the Trading Community Architecture (TCA) model.

The metadata classifies this object as satellite-leaning under a heuristic Data Vault model. This is a modeling suggestion rather than a delivered construct: the table behaves like a satellite because it holds descriptive, job-specific attributes that change over time and depend on a parent entity, rather than serving as a pure hub of business keys or a link resolving many-to-many relationships. The HZ_PARTIES reference supplies the contextual key, while the job-oriented columns function as the descriptive payload.

Key Information Stored

  • JOB_ID — the surrogate primary key defined by FTE_BATCH_JOBS_PK. Every row is uniquely identified by this value, and it is the column referenced by dependent objects.
  • SUPPLIER_ID — the foreign key to HZ_PARTIES. It identifies the supplier or trading partner party associated with the job, supplying the business context for the batch run.

The documented metadata names only these columns explicitly. Because JOB_ID is the sole primary key column and no separate unique index on a business key is documented, no natural business-key candidate is formally established for this table; JOB_ID should be treated as the definitive identifier. Additional descriptive columns commonly present on FTE batch tables — control status, processing timestamps, and program identifiers — are not confirmed by the ETRM metadata and should be verified against the delivered dictionary before use in reporting.

Common Use Cases and Queries

The primary use of FTE_BATCH_JOBS is operational: monitoring which jobs have been submitted and processed, and resolving which supplier each job pertains to. A representative join to resolve the party context is:

  • SELECT j.job_id, j.supplier_id, p.party_name FROM fte_batch_jobs j, hz_parties p WHERE j.supplier_id = p.party_id;

A second common pattern is error analysis, correlating batch jobs against their recorded failures through the child table FTE_JOB_ERRORS:

  • SELECT j.job_id, e.job_id FROM fte_batch_jobs j, fte_job_errors e WHERE j.job_id = e.job_id;

Reporting scenarios include supplier-scoped batch performance summaries, reconciliation of jobs to the parties they serve, and exception reporting that isolates jobs having associated error rows. Administrators reviewing transportation execution concurrent program output typically begin from this table because it anchors the job-to-supplier-to-error chain.

Related Objects

  • FTE_JOB_ERRORS — the principal dependent table. Its JOB_ID column holds a foreign key to FTE_BATCH_JOBS.JOB_ID, making the relationship a one-to-many parent/child association in practice. Error records cannot exist without a corresponding job.
  • HZ_PARTIES — the TCA registry of parties. FTE_BATCH_JOBS.SUPPLIER_ID references this table, linking batch jobs to supplier records. Joins should target the HZ_PARTIES party identifier.
  • FTE_BATCH_JOBS_PK — the primary key constraint on JOB_ID, which enforces uniqueness and supports the join path with FTE_JOB_ERRORS.

No delivered views or APIs referencing this table are documented in the ETRM metadata. The object relationships above are therefore the authoritative integration points for developers and report writers working with FTE batch job data.