Search Results export_id

Overview

The RH_EXPT_DTL table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing Process Planning (GMP) module. It functions as the detail or line-level table for recording and managing export operations. Its primary role is to store granular information for each individual export transaction, complementing the master-level header information stored in its parent table, RH_EXPT_MST. This table is essential for tracking the specifics of data exports, which are critical for process planning, recipe management, and interfacing with external systems in a manufacturing environment. The presence of the EXPORT_TYPE column indicates it supports categorizing exports by their specific business purpose or data target.

Key Information Stored

The table's structure is designed to capture the identity, type, and specific details of an export record. Based on the provided metadata, the critical columns include the composite primary key and other descriptive fields. The primary key consists of EXPORT_ID, which links to the master record, and EXPORT_TYPE, which classifies the nature of the export. While the full column list is not detailed in the excerpt, typical detail tables in this context would store information such as the specific entity being exported (e.g., a recipe, routing, or ingredient), its identifier, status of the export line, timestamps, error messages for failed lines, and processing flags. The EXPORT_TYPE is a pivotal column for filtering and reporting on different categories of export activities.

Common Use Cases and Queries

This table is central to auditing, troubleshooting, and reporting on data export processes from GMP. A common use case involves reconciling exported data or investigating failures for specific export batches. For instance, users may query for all detail lines of a particular export run or for all exports of a specific type that encountered errors. Sample SQL patterns include retrieving details for a given export header or analyzing export activity by type.

• To list all detail lines for a specific export ID: SELECT * FROM GMP.RH_EXPT_DTL WHERE EXPORT_ID = <id> ORDER BY EXPORT_TYPE;
• To summarize the count of export lines by type: SELECT EXPORT_TYPE, COUNT(*) FROM GMP.RH_EXPT_DTL GROUP BY EXPORT_TYPE;
• To join with the master table for a comprehensive view: SELECT mst.*, dtl.* FROM GMP.RH_EXPT_MST mst, GMP.RH_EXPT_DTL dtl WHERE mst.EXPORT_ID = dtl.EXPORT_ID AND mst.CREATION_DATE > SYSDATE - 7;

Related Objects

The RH_EXPT_DTL table has a defined, documented foreign key relationship with the RH_EXPT_MST table, establishing a strict master-detail hierarchy. This relationship is fundamental to the data model.

• RH_EXPT_MST: This is the primary parent table. The foreign key constraint links RH_EXPT_DTL.EXPORT_ID to the corresponding primary key column(s) in RH_EXPT_MST. All detail records must have a valid corresponding master record. This table likely stores header information such as overall export request date, requester, batch name, and total status.

While not listed in the provided metadata, it is plausible that this table is referenced by various GMP process planning APIs or views responsible for executing and monitoring export processes. Direct joins should typically be performed via the EXPORT_ID column to the RH_EXPT_MST table.