Results for “number_of_records”

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

Overview

MTL_DEMAND_INTERFACE_VIEW is an APPS-owned database view in the Oracle E-Business Suite Inventory (INV) product module. Its documented status is VALID, and it is described in the ETRM metadata simply as "a view for demand interface table." It is therefore not a base transactional object, but a reporting and aggregation layer built on top of the demand interface staging table.

The view does not stage or hold demand data of its own. Instead, it summarizes the contents of MTL_DEMAND_INTERFACE by schedule group and transaction mode, returning one row per distinct combination of those two attributes together with a record count. This makes it a diagnostic and monitoring utility rather than a data-entry interface. Within the Oracle EBS integration landscape, the demand interface table is used to load demand and reservation data into the Inventory module for processing by the demand interface concurrent program. The view provides a quick, low-overhead way to inspect how much demand is pending and in what mode, without querying the full interface table.

Underlying Base Objects

The only referenced base object documented in the ETRM metadata is MTL_DEMAND_INTERFACE, referenced through the APPS synonym. The view is defined directly over that table; no joins to other tables, lookup views, or staging objects are recorded.

Because the view is a simple aggregation of a single table, it inherits the transactional lifecycle of MTL_DEMAND_INTERFACE. Rows become visible in the view as soon as they are inserted into the interface table, and they disappear from the view once the interface rows are processed and deleted by the demand interface program. The view performs no filtering, no joins, and no transformation of values; it exposes only the grouping keys and a count.

Key Columns

• SCHEDULE_GROUP_ID — The schedule group identifier being grouped on. This correlates to the scheduling group against which the pending demand records are staged, allowing the count to be reviewed per scheduling group.
• TRANSACTION_MODE — The transaction mode of the staged demand records. The count is reported separately for each mode, which lets the reviewer distinguish how demand is being introduced (for example, different processing modes) rather than seeing a single undifferentiated volume.
• NUMBER_OF_RECORDS — The count of rows in MTL_DEMAND_INTERFACE for the corresponding SCHEDULE_GROUP_ID and TRANSACTION_MODE combination, produced by COUNT(*).

The view returns exactly three columns. No timestamps, item identifiers, quantities, or status columns are exposed, so any detail-level investigation must be performed against MTL_DEMAND_INTERFACE itself.

Common Use Cases and Queries

The primary use case is operational monitoring: confirming whether demand interface records are accumulating, and if so, under which schedule group and transaction mode. A typical query is:

• SELECT schedule_group_id, transaction_mode, number_of_records FROM apps.mtl_demand_interface_view ORDER BY schedule_group_id, transaction_mode; — a full summary of pending demand by group and mode.
• SELECT transaction_mode, SUM(number_of_records) FROM apps.mtl_demand_interface_view GROUP BY transaction_mode; — aggregate pending volume by mode across all schedule groups.
• SELECT * FROM apps.mtl_demand_interface_view WHERE schedule_group_id = :group_id; — pending volume for a specific schedule group, useful when investigating a single interface run.
• SELECT * FROM apps.mtl_demand_interface_view WHERE number_of_records > 0; — a defensive predicate when only non-empty groups are of interest.

Because the view aggregates rather than filters, it is suitable for pre-run and post-run checks around the demand interface concurrent program. It is not suitable for reconciliation at the record level; for that, MTL_DEMAND_INTERFACE should be queried directly.