Results for “rh_mord_imp”

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

Overview

The RH_MORD_IMP table resides in the GMP schema and belongs to the Oracle Process Manufacturing (OPM) Process Planning module. Its documented purpose is manufacturing order import processing within the OPM application suite. The table is classified as VALID in the data dictionary, but Oracle's own documentation explicitly annotates the object with the remark "Manufacturing order import. - Currently Not Used," indicating that while the physical structure and constraints remain in place, the object no longer participates in active application logic in Oracle EBS 12.1.1 or 12.2.2.

From a Data Vault modeling perspective, the heuristic classification of RH_MORD_IMP is a link. This classification is derived from the foreign key structure, which connects the table to three distinct parent entities: PM_BTCH_HDR (batch header), RH_IMPT_MST (import master), and SY_ORGN_MST (organization master). A link classification suggests the table functions as an associative entity recording relationships between manufacturing orders, batch records, import sessions, and organizations, rather than acting as a standalone hub of a core business concept or a satellite capturing descriptive attributes over time.

Key Information Stored

RH_MORD_IMP contains 27 documented columns. The most significant of these include:

• IMPORT_ID — Identifier linking the record to an import session header in RH_IMPT_MST; part of the composite primary key.
• BATCH_ID — Foreign key to PM_BTCH_HDR, associating the imported row with a batch record; part of the primary key.
• LINE_NO — Sequence number for rows within an import batch; part of the primary key.
• NEW_DOC_TYPE and NEW_DOC_ID — The type and identifier of the new document affected by the import action; both are components of the composite primary key.
• ACTION_TYPE — The operation being performed (such as create, update, or delete); a primary key column.
• ORGN_CODE — Organization code, referencing SY_ORGN_MST for multi-organization filtering.
• PROCESS_ID — Identifier for the process associated with the manufacturing order.
• DOC_TYPE and BATCH_NO — Document type and batch number context for the import row.
• OLD_ROUTING_NO, OLD_ROUTING_VERS, ROUTING_NO, ROUTING_VERS — Routing number and version before and after the import action.
• OLD_PLAN_QTY and PLAN_QTY — Planned quantities before and after the change.
• EFF_ID and OLD_EFF_ID — Effectiveness identifiers pre- and post-import.
• OLD_PST, PST, OLD_PET, PET — Planned start and planned end timestamps before and after the action.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns.

The primary key RH_MORD_IMP_PK is a composite surrogate over IMPORT_ID, BATCH_ID, LINE_NO, NEW_DOC_TYPE, NEW_DOC_ID, and ACTION_TYPE. No separate unique business key index is documented in the ETRM metadata; the composite primary key effectively serves as the natural identifier for an import row.

Common Use Cases and Queries

Because the table is marked "Currently Not Used," most practical value in a live 12.1.1 or 12.2.2 environment derives from data archaeology and retrofit analysis rather than operational reporting. Typical uses include:

• Auditing legacy import activity to determine whether manufacturing order imports were ever processed through this path.
• Investigating orphaned or partially applied import rows when reconciling batch headers against routing changes.
• Supporting upgrade and data migration assessments, verifying that no residual rows exist prior to decommissioning.

A representative query enumerating imports by organization and batch looks as follows:

• SELECT m.IMPORT_ID, m.BATCH_ID, m.LINE_NO FROM RH_MORD_IMP m WHERE m.ORGN_CODE = :orgn_code;
• SELECT COUNT(*) FROM RH_MORD_IMP WHERE ACTION_TYPE = 'CREATE';
• SELECT i.IMPORT_ID, i.CREATION_DATE FROM RH_MORD_IMP m JOIN RH_IMPT_MST i ON m.IMPORT_ID = i.IMPORT_ID;

Related Objects

The table's referential relationships define its context within OPM Process Planning:

• PM_BTCH_HDR — Parent batch header; RH_MORD_IMP.BATCH_ID → PM_BTCH_HDR (documented FK).
• RH_IMPT_MST — Import master header; RH_MORD_IMP.IMPORT_ID → RH_IMPT_MST (documented FK).
• SY_ORGN_MST — Organization master; RH_MORD_IMP.ORGN_CODE → SY_ORGN_MST (documented FK).
• RH_MORD_IMP_PK — The primary key constraint enforcing uniqueness across the six key columns.
• Related OPM objects such as RH_IMPT_MST, PM_BTCH_HDR, and SY_ORGN_MST drive any dependent reporting or interface logic that historically consumed import rows.

Given its deprecated status, RH_MORD_IMP should be treated as a read-only historical artifact in current EBS deployments, with any remaining business logic directed toward active OPM manufacturing order interfaces.