Results for “queue_no”

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

Overview

The RH_IMPT_MST table is the import master table within the Oracle EBS Process Manufacturing Process Planning (GMP) module. In Oracle EBS 12.1.1 and 12.2.2, it serves as the controlling header record for batch import activities, tracking the scheduling, execution, and status of import processes that load external data into the Process Planning environment. Each row represents a single import run, identified by a surrogate primary key and qualified by control attributes such as run status, scheduling identifiers, and audit stamping.

From a Data Vault modeling perspective, the metadata indicates a hub-leaning classification. This suggests RH_IMPT_MST functions as a business-key-bearing hub, capturing the durable identity of an import event, with descriptive and state-related attributes that could be separated into a satellite structure if a formal Data Vault model were constructed. The primary key RH_IMPT_MST_PK on IMPORT_ID provides the stable unique identifier that anchors downstream dependent tables.

Key Information Stored

RH_IMPT_MST contains 13 documented columns, of which the following are most significant for operational and reporting purposes:

• IMPORT_ID — The surrogate primary key (RH_IMPT_MST_PK) uniquely identifying each import master record. It is the join key referenced by all dependent tables.
• SCHEDULE_ID — Identifies the schedule under which the import run is executed, linking the import to planning or batch scheduling logic.
• RUN_STATUS — Indicates the current state of the import run (for example, pending, running, completed, or errored), which drives monitoring and retry logic.
• RUN_BY — The user or process that initiated the import run.
• QUEUE_NO — The queue assignment for the import job, supporting concurrency and sequencing control.
• BATCH_DATE — The business date associated with the batch being imported.
• ACTUAL_START_DATE — The timestamp when the import run actually began execution.
• ACTUAL_END_DATE — The timestamp when the import run completed or terminated.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing record creation and modification history.

The surrogate key is IMPORT_ID. No explicit unique business-key index is documented in the metadata, so IMPORT_ID remains the sole documented uniqueness constraint.

Common Use Cases and Queries

Typical usage centers on monitoring import execution and reconciling imported records. A common query retrieves the status and timing of recent import runs:

• SELECT import_id, run_status, run_by, batch_date, actual_start_date, actual_end_date FROM gmp.rh_impt_mst WHERE batch_date >= :p_from_date ORDER BY actual_start_date DESC;

• Joining RH_IMPT_MST to RH_IMPT_DTL on IMPORT_ID to audit the detail lines produced by a run.
• Filtering by RUN_STATUS to detect stalled or failed imports requiring reprocessing.
• Aggregating by BATCH_DATE to report import volumes and success rates over time.

Reporting use cases include operational dashboards tracking import throughput, reconciliation of imported work orders and detailed routing imports, and audit trails of who ran which import and when.

Related Objects

The FK metadata identifies the following dependent tables, all referencing RH_IMPT_MST via IMPORT_ID:

• RH_IMPT_DTL — The import detail table holding the granular records loaded by each master import run (RH_IMPT_DTL.IMPORT_ID → RH_IMPT_MST.IMPORT_ID).
• RH_DORD_IMP — Import staging for discrete order data (RH_DORD_IMP.IMPORT_ID → RH_IMPT_MST.IMPORT_ID).
• RH_MORD_IMP — Import staging for process/production order data (RH_MORD_IMP.IMPORT_ID → RH_IMPT_MST.IMPORT_ID).

These child tables depend on the hub row to provide the parent identity and control context, making RH_IMPT_MST the anchor for import-related transactional staging within the GMP module.