Search Results mtl_interface_proc_controls




Overview
Explore in AI Chat

Overview

MTL_INTERFACE_PROC_CONTROLS is an Inventory (INV) module control table that stores configuration parameters governing the behavior of the concurrent interface processes that load data into Oracle E-Business Suite inventory tables. The table is owned by the INV schema and holds one row per registered interface process, keyed by PROCESS_CODE. Each row defines how the corresponding interface manager or worker program should schedule itself, how many records it should batch, how long it should wait before timing out, and which concurrent program actually performs the work.

Under the heuristic Data Vault classification mined from the foreign-key structure, MTL_INTERFACE_PROC_CONTROLS is reported as standalone. In practice, the table behaves as a reference or control hub: PROCESS_CODE is the natural business key, and the transactional detail associated with each interface run is recorded in separate staging and manager tables. The optional ZD_EDITION_NAME column places the object within the Oracle EBS 12.2 online patching (Editioning) model, allowing edition-specific control rows to coexist.

Key Information Stored

The primary key is enforced through MTL_INTERFACE_PROC_CONTROLS_PK on PROCESS_CODE, while the unique index MTL_INTERFACE_PROC_CTRL_U1 (PROCESS_CODE, ZD_EDITION_NAME) acts as the business-key candidate when editioning is enabled.

Common Use Cases and Queries

Administrators and technical consultants query this table to verify that an interface is enabled and correctly scheduled, to tune batch sizes and timeouts for large data loads, and to troubleshoot stalled or repeatedly failing interfaces. A typical query lists enabled processes and their scheduling characteristics:

  • SELECT process_code, process_name, process_status, process_interval, worker_rows, processing_timeout FROM mtl_interface_proc_controls ORDER BY process_code;
  • SELECT process_code, manager_priority, worker_priority, request_id FROM mtl_interface_proc_controls WHERE process_status = 'ENABLED';
  • Joining to concurrent program definitions via PROCESS_NAME and PROCESS_APP_SHORT_NAME to confirm the target executable and its enabled state.
  • Auditing recent configuration changes through LAST_UPDATED_BY, LAST_UPDATE_DATE, and REQUEST_ID.

Because the table is small and stable, it is frequently used as a driver in reporting queries that pivot interface status by process, and as a lookup when reconciling staging tables such as MTL_INTERFACE_ERRORS against their owning process.

Related Objects

The metadata documents no incoming foreign keys, so relationships are functionally rather than declaratively enforced. The most significant associated objects include: