Results for “fte_job_errors”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FTE_JOB_ERRORS is a Transportation Execution (FTE) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store detail error messages produced for each bulk load job executed within the FTE bulk processing framework. In practice, this makes it the diagnostic companion to the job header table, capturing row-level or message-level failures returned by Oracle Transportation Management (OTM) or by the EBS-side loader when processing transportation data through concurrent bulk load jobs.
The ETRM metadata records the table as "Not implemented in this database," meaning it exists in the application object library but was not physically instantiated in the source environment from which the documentation was derived. Implementers should verify physical presence against their own FTE schema before relying on direct SQL access, since features such as bulk load error persistence may or may not be enabled depending on patch level and configuration.
Mined foreign-key structure suggests a satellite-leaning Data Vault classification. In this modeling suggestion, FTE_JOB_ERRORS behaves as a satellite hanging off the FTE_BATCH_JOBS hub (or a link, depending on the surrounding model), because each row is a descriptive, non-key attribute set keyed to a parent job record. The parent is identified by JOB_ID referencing FTE_BATCH_JOBS, and error rows carry no independent business identity beyond their association with a job.
Key Information Stored
The documented metadata enumerates only the relationship structure and the table purpose, not the full column list. The following reflect the columns evidenced by the ETRM records:
- JOB_ID — Documented foreign key to FTE_BATCH_JOBS. This is the principal join column tying each error message to the bulk load job that generated it, and is the strongest business-key candidate for filtering errors by job.
- Error message detail — Per the table description, rows hold the individual error text produced per job. In standard FTE implementations this is typically a message or description column holding the OTM or loader exception text, often accompanied by a sequence column, severity, and error-code fields.
- Surrogate primary key — The metadata does not document a named surrogate key column. Where a surrogate exists, it is distinct from JOB_ID, which is a foreign key rather than a unique key; multiple error rows share the same JOB_ID.
Because the metadata is limited on column detail, exact column names other than JOB_ID should be confirmed from the deployed data dictionary (ALL_TAB_COLUMNS) rather than assumed.
Common Use Cases and Queries
Typical usage centers on troubleshooting failed or partially failed bulk loads. A DBA or transportation analyst retrieves all errors for a given job by joining to the parent header:
- Job-level error retrieval:
SELECT e.* FROM fte_job_errors e WHERE e.job_id = :job_id; - Error inventory by job: join FTE_JOB_ERRORS to FTE_BATCH_JOBS on JOB_ID to list job names, run dates, and error counts — useful for a bulk load monitoring report.
- Trend analysis: aggregate error occurrences by message text over a date range to identify recurring OTM integration defects.
- Corrective load re-run: extract offending records referenced in error rows, correct the source data, and resubmit the bulk load job.
Reporting use cases include operational dashboards of failed transportation bulk loads and root-cause analysis for periodic interfaces feeding OTM.
Related Objects
The documented relationship set is narrow, but the following objects are significant in the surrounding FTE bulk load model:
- FTE_BATCH_JOBS — Parent table; join on
FTE_JOB_ERRORS.JOB_ID = FTE_BATCH_JOBS.JOB_ID. This is the sole documented foreign key and the primary dependency. - FTE_BATCH_JOB_PARAMETERS (where present) — Holds the run-time parameters supplied to the same job.
- FTE_BULK_LOAD / OTM integration interfaces — The concurrent programs and APIs that generate error rows during load processing.
- FTE_LOADER_HISTORY and related FTE staging tables — Source records that failed and were routed to the error table.
- FND_CONCURRENT_REQUESTS — Links the originating concurrent request to the bulk load job for end-to-end traceability.
The FK structure confirms FTE_JOB_ERRORS is a dependent, satellite-style child of the FTE batch job framework rather than an independent hub entity.
-
Table: FTE_JOB_ERRORS 12.2.2
Stores detail Error Messages for each Bulk Load Job.
Not implemented in this database·Explore FTE module →
-
Table: FTE_JOB_ERRORS 12.1.1
Stores detail Error Messages for each Bulk Load Job.
Not implemented in this database·Explore FTE module →
-
Table: FTE_BATCH_JOBS 12.1.1
Store informations about jobs being processed
Not implemented in this database·Explore FTE module →
-
Table: FTE_BATCH_JOBS 12.2.2
Store informations about jobs being processed
Not implemented in this database·Explore FTE module →
-
View: FTE_JOB_ERRORS_V 12.2.2
Not implemented in this database·Explore FTE module →
-
View: FTE_JOB_ERRORS_V 12.1.1
Not implemented in this database·Explore FTE module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2