Results for “supply_source_header_id”

50+ results




Overview
Explore in AI Chat

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

Overview

MTH_OPEN_SALES_ORDERS_F is a table owned by the MTH schema, which supports Oracle Manufacturing Operations Center (MOC) in Oracle E-Business Suite 12.1.1 and 12.2.2. As its name indicates, the object stores sales order demand that has not yet been fully consumed, typically staged for use by MOC scheduling, dispatching, and execution engines. These "open" sales order lines represent demand signals that MOC uses to align production and fulfillment activity against outstanding customer commitments. The F suffix denotes a fact-style table, consistent with its role as a collection point for transactional records rather than configuration or setup data.

From a Data Vault modeling perspective, the heuristic classification for this table is standalone. It does not participate in a network of foreign-key relationships that would justify classification as a hub, link, or satellite. Instead, it operates as an independent staging or summary object that MOC reads and refreshes on its own schedule. This standalone posture suggests the row-level granularity is the sales order supply record itself, qualified by its EBS header reference and associated reservation.

The table contains five documented columns, making it a narrow, purpose-built structure rather than a general-purpose order detail table. It appears to coexist with other MTH fact tables populated by concurrent programs that pull snapshots of upstream EBS supply and demand data.

Key Information Stored

The five documented columns are:

  • EBS_HEADER_ID — The EBS-side header identifier, linking the record back to its originating sales order header. This is the primary business-key candidate, since it ties MOC data to the transactional EBS record.
  • RESERVATION_ID — A foreign key referencing MTL_RESERVATIONS, tying the open sales order row to an inventory reservation. This is the only documented foreign-key relationship in the schema.
  • SUPPLY_SOURCE_HEADER_ID — Identifies the supply-side header record associated with the open demand. This supports MOC in matching supply to the referenced sales order.
  • SOURCE — Indicates the originating source system or process that created the record, useful for provenance and deduplication.
  • PROCESSING_FLAG — A status indicator used by MOC concurrent processing logic to track which rows have been consumed, processed, or retained.

No surrogate primary key is documented in the ETRM metadata. Practically, the combination of EBS_HEADER_ID and RESERVATION_ID serves as the natural business key, given the FK documented on RESERVATION_ID to MTL_RESERVATIONS.

Common Use Cases and Queries

Typical use cases center on MOC reporting and reconciliation between outstanding fulfillment demand and inventory reservations:

  • Reports listing open sales order demand pending reservation or processing, filtered by PROCESSING_FLAG.
  • Reconciliation queries joining MTH_OPEN_SALES_ORDERS_F to MTL_RESERVATIONS to verify reservation coverage.
  • Detection of stale or unprocessed rows, where PROCESSING_FLAG remains unset after a refresh cycle.
  • Feeds into MOC dashboards showing open demand by supply source.

A representative query:

  • SELECT o.EBS_HEADER_ID, o.RESERVATION_ID, o.SUPPLY_SOURCE_HEADER_ID, o.SOURCE, o.PROCESSING_FLAG FROM MTH.MTH_OPEN_SALES_ORDERS_F o WHERE o.PROCESSING_FLAG = 'N';

This pattern is frequently used to identify rows awaiting MOC processing after a data refresh.

Related Objects

The most significant related object is MTL_RESERVATIONS, referenced through MTL_RESERVATIONS.RESERVATION_ID = MTH_OPEN_SALES_ORDERS_F.RESERVATION_ID. Beyond this documented FK, other relevant objects include the MOC concurrent programs and fact tables that populate and consume this table (such as sibling MTH_OPEN_* objects), the EBS sales order header (OE_ORDER_HEADERS_ALL) commonly used to resolve EBS_HEADER_ID contextually, and MTL supply objects that resolve SUPPLY_SOURCE_HEADER_ID. When reporting, joining to OE_ORDER_HEADERS_ALL on ORDER_HEADER_ID = EBS_HEADER_ID is a common practice to retrieve order number and customer information, even though this join is not formally enforced as a database constraint in the documented metadata.