Search Results rh_mord_imp




Overview

The RH_MORD_IMP table is a data object within the Oracle E-Business Suite (EBS) Process Manufacturing (GMP) module, specifically under Process Planning. As its name and description indicate, it is designed as a staging table for importing manufacturing order data. Its primary role is to serve as an intermediate repository where external or legacy manufacturing order data can be loaded and validated before being processed and transferred into the core transactional tables of the system. A critical piece of information from the official documentation is the note "Currently Not Used." This status suggests that while the table structure exists within the GMP schema, the associated import functionality may be deprecated, unimplemented, or reserved for future use in the referenced EBS versions (12.1.1 and 12.2.2).

Key Information Stored

The table's structure is centered around managing discrete import records. The primary key is a composite of IMPORT_ID, BATCH_ID, and LINE_NO, which uniquely identifies each row in the import interface. Key columns include IMPORT_ID, which links to the master import control table; BATCH_ID, which references the target production batch; and LINE_NO, which sequences the records within an import request. The ACTION_TYPE column dictates the operation to be performed (e.g., CREATE, UPDATE), while NEW_DOC_TYPE and NEW_DOC_ID are likely intended to hold identifiers for the manufacturing order document being created or modified. The presence of an ORGN_CODE column, tied to the organization master (SY_ORGN_MST), indicates the table stores data scoped to a specific manufacturing organization.

Common Use Cases and Queries

Given its "Currently Not Used" status, direct operational use cases are limited. Its intended purpose would have been for bulk data migration or integration scenarios, such as initial system implementation or receiving orders from an external planning system. If data were present, common queries would focus on monitoring the import queue. For instance, a query to review pending import records for a specific batch would be: SELECT * FROM GMP.RH_MORD_IMP WHERE BATCH_ID = :batch_id ORDER BY LINE_NO;. Another pattern would involve joining with the import master table to check the status of import requests: SELECT imp.*, mst.IMPORT_STATUS FROM GMP.RH_MORD_IMP imp, GMP.RH_IMPT_MST mst WHERE imp.IMPORT_ID = mst.IMPORT_ID;. Reporting would typically be diagnostic, analyzing failed records or import volumes.

Related Objects

The table's foreign key constraints explicitly define its key relationships within the GMP schema. It is directly linked to:

  • RH_IMPT_MST: The master import control table, via IMPORT_ID. This manages the overall import job.
  • PM_BTCH_HDR: The primary Process Manufacturing batch header table, via BATCH_ID. This is the ultimate target for the imported order data.
  • SY_ORGN_MST: The standard organization master table, via ORGN_CODE, providing validation for the organization context.
These relationships confirm its role as an interface table sitting between import control (RH_IMPT_MST) and the core production batch entity (PM_BTCH_HDR).