Search Results mtl_interface_proc_ctrl_u1

Overview

INV.MTL_INTERFACE_PROC_CONTROLS is a seeded control table in the Oracle EBS Inventory (INV) schema that governs the behavior of the background transaction managers responsible for processing the open interface tables used by Oracle Manufacturing. Rather than representing transactional data itself, the table acts as a configuration and scheduling registry: each row corresponds to one supported background process, capturing whether it is active, how frequently it polls its interface tables, and how work is distributed across parallel workers.

The table resides in the APPS_TS_SEED tablespace with PCT FREE 10, consistent with its role as reference seed data that is populated during installation rather than by end users. Its contents are largely static, but administrators may tune PROCESS_INTERVAL, PROCESS_STATUS, and WORKER_ROWS to align throughput with operational load.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. Under that lens, MTL_INTERFACE_PROC_CONTROLS is best treated as a small reference hub keyed on PROCESS_CODE, with its descriptive attributes (status, interval, worker allocation) behaving as satellite-style descriptive data. Because the FK graph shows no dependent relationships, no link tables are implied.

Key Information Stored

The table has a documented physical schema of 19 columns. The primary key is MTL_INTERFACE_PROC_CONTROLS_PK on PROCESS_CODE, which is the surrogate identifier for each background process. A second unique index, MTL_INTERFACE_PROC_CTRL_U1, is defined over (PROCESS_CODE, ZD_EDITION_NAME); this composite is the business-key candidate that supports Edition-based Redefinition in 12.2.

• PROCESS_CODE — Numeric code identifying the background process; primary key.
• PROCESS_NAME — Short name of the background process (VARCHAR2(10)).
• PROCESS_APP_SHORT_NAME — Application short name associated with the process.
• PROCESS_STATUS — Flag indicating whether the corresponding background process is active or inactive.
• PROCESS_INTERVAL — Polling interval at which the process reads its interface table.
• WORKER_ROWS — Maximum number of transaction rows assigned to a single worker.
• PROCESSING_TIMEOUT — Interval after which errored rows are reprocessed; used only by WIP managers.
• MANAGER_PRIORITY — Concurrent priority for the manager (documented as not currently used).
• WORKER_PRIORITY — Concurrent priority for workers (documented as not currently used).
• ZD_EDITION_NAME — Edition name supporting EBR.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage centers on validating that the correct managers are enabled and tuned. A common diagnostic query lists active processes and their interval and worker settings:

SELECT process_code, process_name, process_status,
       process_interval, worker_rows, processing_timeout
FROM   inv.mtl_interface_proc_controls
WHERE  process_status = 1
ORDER  BY process_name;

Administrators may update intervals or worker allocations to reduce contention when interface volumes spike, and auditors may inspect WHO columns to trace who adjusted a setting and when. Reporting use cases include dashboards that track which managers are disabled, since a disabled manager causes interface rows to accumulate unconsumed.

Related Objects

• MTL_TRANSACTIONS_INTERFACE — primary staging table whose rows are processed by the managers governed here.
• MTL_MATERIAL_TRANSACTIONS_TEMP — working table for pending transaction processing.
• MTL_TRANSACTION_LOTS_INTERFACE — lot and serial detail rows processed alongside transactions.
• MTL_SERIAL_NUMBERS_INTERFACE — serial number interface consumed by the same background managers.
• WIP_MOVE_TXN_INTERFACE — move transaction interface specifically referenced by PROCESSING_TIMEOUT.
• FND_CONCURRENT_PROGRAMS — defines the concurrent programs referenced by PROGRAM_ID and PROGRAM_APPLICATION_ID.
• FND_CONCURRENT_REQUESTS — runtime instances linked through REQUEST_ID.