Results for “run_status”

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

Overview

RH_IMPT_DTL is a table owned by the GMP schema in Oracle E-Business Suite, associated with the Process Manufacturing Process Planning module. It stores demand order import details, functioning as the line-level detail table for demand import operations executed through the Oracle Demand Planning and Process Planning integration flows. The table captures the outcome of each import run at a granular level, recording status and processing volume for demand orders submitted to the planning engine.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. RH_IMPT_DTL hangs off the parent import header table RH_IMPT_MST via IMPORT_ID, which suggests it is best modeled as a satellite of the import master hub, carrying descriptive and status attributes about each import execution. It is not a pure hub, since it carries no independent business key beyond its composite identifier, and it is not a link, since it does not resolve a many-to-many relationship between distinct business entities.

Key Information Stored

The table contains nine documented columns. The primary key is defined by the constraint RH_IMPT_DTL_PK, which is composed of IMPORT_ID and IMPORT_TYPE, making these two columns the composite surrogate identifier for each detail row.

• IMPORT_ID — Identifier of the parent import run; foreign key to RH_IMPT_MST. Serves as the primary correlation column across the import subsystem.
• IMPORT_TYPE — Discriminator that distinguishes the category of import being processed; combined with IMPORT_ID it forms the composite primary key.
• RUN_STATUS — Status of the import execution, indicating whether the demand order import completed, failed, or is in progress.
• ROWS_PROCESSED — Count of records successfully processed during the import run, used for reconciliation and monitoring.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking the most recent modification of the row.
• CREATION_DATE, CREATED_BY — Who and when the detail row was originally created.

Common Use Cases and Queries

The primary use case is monitoring and troubleshooting demand import runs. Planners and technical support staff query this table to determine whether a demand import completed successfully and how many rows were processed. A typical diagnostic query joins RH_IMPT_DTL to RH_IMPT_MST:

• SELECT d.import_id, d.import_type, d.run_status, d.rows_processed FROM gmp.rh_impt_dtl d WHERE d.import_id = :import_id;
• SELECT m.*, d.run_status, d.rows_processed FROM gmp.rh_impt_mst m, gmp.rh_impt_dtl d WHERE m.import_id = d.import_id AND d.run_status <> 'SUCCESS';

Reporting use cases include auditing import throughput over time, identifying recurring failures by IMPORT_TYPE, and reconciling processed row counts against expected demand order volumes. Because audit columns are present, the table also supports change-tracking queries that identify recent import activity by CREATED_BY or LAST_UPDATE_DATE.

Related Objects

The most significant related object is the parent header table, referenced through the documented foreign key. The following relationships are most relevant:

• RH_IMPT_MST — Parent import master table. Joined on RH_IMPT_DTL.IMPORT_ID = RH_IMPT_MST.IMPORT_ID. This foreign key is the authoritative link between detail and header import records.
• RH_IMPT_DTL_PK — Primary key constraint spanning IMPORT_ID and IMPORT_TYPE, enforcing uniqueness of each detail row.
• Demand planning and Process Planning concurrent programs that populate these tables consume RH_IMPT_DTL for status reporting and exception handling.
• Related GMP planning tables that store imported demand orders reference the same IMPORT_ID context, enabling end-to-end traceability from import run to resulting demand records.