Results for “load_type”

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

Overview

FTE_BULKLOAD_DATA is a transactional staging and control table within the Oracle E-Business Suite Transportation Execution (FTE) module. It stores the payload and metadata associated with bulk download and upload operations executed during bulkload processing in Oracle Transportation Management integration scenarios. In EBS 12.1.1 and 12.2.2, the FTE schema houses objects that bridge order, shipment, and carrier data with external transportation systems, and FTE_BULKLOAD_DATA functions as the persistence layer for the file-based exchange mechanism underpinning that bridge.

The table is owned by the FTE schema with status VALID and comprises 12 documented columns in the ETRM 12.2.2 physical schema. Its primary key is FTE_BULKLOAD_DATA_PK, defined on the LOAD_ID column, which uniquely identifies each bulkload record.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This suggests the table can be modeled as an independent hub-like or transaction entity, since no explicit parent-child foreign-key relationships were detected in the documented metadata. Practitioners designing a Data Vault or dimensional layer over FTE should treat LOAD_ID as the natural business key anchor for this entity.

Key Information Stored

The 12 documented columns capture both the control attributes and the actual data payload for each bulkload operation. The most significant columns are:

• LOAD_ID — Surrogate primary key (FTE_BULKLOAD_DATA_PK) that uniquely identifies each bulkload record.
• LOAD_TYPE — Indicates the direction or category of the bulkload operation, typically distinguishing download versus upload processing.
• FILE_TYPE — Classifies the format of the associated file (for example, CSV, XML, or delimited text) used in the exchange.
• FILE_NAME — The name of the file involved in the download or upload.
• FILE_SIZE — The size of the referenced file, useful for validation and monitoring.
• REQUEST_ID — The concurrent request identifier that links the bulkload record to its originating or dependent concurrent program run.
• CONTENT — The stored payload of the bulkload file, held as a large object capable of containing the full file body.
• CREATED_BY / CREATION_DATE — Audit columns recording the user and timestamp of record creation.
• LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard EBS audit columns tracking the most recent modification and the login session responsible for it.

A secondary unique index, SYS_IL0000194331C00007$$, exists on the CONTENT column; this is an internal LOB index created automatically to support the large-object storage rather than a business-key candidate. The true business-key candidate remains LOAD_ID.

Common Use Cases and Queries

Typical use cases center on monitoring, troubleshooting, and reconciliation of bulkload processing. Administrators and developers use this table to inspect the status and content of files exchanged between EBS and external transportation systems, to link bulkload activity back to concurrent requests, and to audit who created or modified records.

A common monitoring query joins the table to concurrent request information via REQUEST_ID:

• SELECT load_id, load_type, file_name, file_size, request_id FROM fte.fte_bulkload_data WHERE request_id = :request_id;
• SELECT load_id, load_type, file_type, creation_date FROM fte.fte_bulkload_data WHERE TRUNC(creation_date) = TRUNC(SYSDATE);
• SELECT load_id, file_name, DBMS_LOB.GETLENGTH(content) payload_size FROM fte.fte_bulkload_data WHERE load_type = 'DOWNLOAD';

Reporting use cases include tracking file volumes by type and date, auditing upload/download activity per user, and diagnosing failed or oversized bulkloads by reviewing FILE_SIZE and CONTENT length.

Related Objects

Because the documented heuristic classifies FTE_BULKLOAD_DATA as standalone, no explicit foreign-key dependencies were mined. The most significant logical associations are:

• FND_CONCURRENT_REQUESTS — joined through REQUEST_ID to correlate bulkload records with concurrent program executions.
• FND_CONCURRENT_PROGRAMS — identifies the bulkload concurrent program responsible for the data.
• FND_USER — joined via CREATED_BY and LAST_UPDATED_BY for audit attribution.
• FTE_BULKLOAD_DATA_PK — the primary key constraint enforcing LOAD_ID uniqueness.
• Additional FTE schema objects handling shipment, order, and carrier interfaces that consume the bulkload payload during processing.