Search Results rh_impt_dtl




Overview
Explore in AI Chat

Overview

The RH_IMPT_DTL table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing (Process Planning) module. It functions as the detailed staging table for demand order import transactions. When demand data, such as sales orders or forecasts, is loaded into the Process Manufacturing system from external sources or other EBS modules, the transactional details are initially populated into this table. Its primary role is to hold the granular line-level information for each import batch, which is subsequently validated and processed by the system's import programs to create or update formal demand schedules within the GMP schema. The table's existence is critical for ensuring data integrity during the demand integration process.

Key Information Stored

The table stores detailed records that correspond to a parent import batch header. Based on its documented structure and purpose, key columns include the batch identifier and transaction specifics. The primary key, RH_IMPT_DTL_PK, is a composite key consisting of IMPORT_ID and IMPORT_TYPE, ensuring uniqueness of detail lines within a specific import context. The IMPORT_ID column is a foreign key that links each detail record to its corresponding control record in the master import table (RH_IMPT_MST). While the provided metadata does not list all columns, typical data stored would encompass item identifiers, demand quantities, required dates, sourcing information, and specific attributes relevant to process manufacturing demand, such as lot or grade requirements. Each row represents a single demand line awaiting processing.

Common Use Cases and Queries

The primary use case involves troubleshooting and monitoring the demand import process. Database administrators and functional consultants query this table to verify data loaded by interface programs, identify records that failed validation, and analyze import performance. Common SQL patterns include joining to the master table to get batch status and filtering for unprocessed records.

  • Identifying details for a specific import batch: SELECT * FROM GMP.RH_IMPT_DTL WHERE import_id = <batch_number>;
  • Reviewing pending import lines: SELECT d.* FROM gmp.rh_impt_dtl d, gmp.rh_impt_mst m WHERE d.import_id = m.import_id AND m.status = 'PENDING';
  • Investigating errors by correlating detail records with interface error tables, often via the IMPORT_ID.

Related Objects

RH_IMPT_DTL has a direct and documented foreign key relationship with the RH_IMPT_MST table, which serves as the import batch header. This relationship is fundamental to the import architecture.

  • RH_IMPT_MST (Master Import Table): This is the parent table. The foreign key is defined on the column RH_IMPT_DTL.IMPORT_ID, which references RH_IMPT_MST.IMPORT_ID. All detail records must belong to a valid master record. This table typically holds control information like batch creation date, status, and request ID.

While not listed in the provided excerpt, this table is also logically related to various GMP demand planning and scheduling base tables (e.g., GMD_DEMAND). Data is ultimately transferred from RH_IMPT_DTL into these permanent transactional tables upon successful import completion.