Results for “order_qty”

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

Overview

RH_DORD_IMP is a demand order import table owned by the GMP schema and associated with the Oracle Process Manufacturing Process Planning module (GMP). Its documented purpose is to store imported details of demand orders, serving as a staging structure into which external demand-order data can be loaded and subsequently processed by the planning engine. The ETRM metadata explicitly marks this table as "Currently Not Used," meaning that in Oracle EBS 12.1.1 and 12.2.2 the object is a valid, physically present, but largely dormant artifact. It exists in the schema for schema-consistency and historical reasons rather than as an actively populated operational table.

Because the table is a staging/import structure, its heuristic Data Vault classification, mined from its foreign-key structure, is satellite-leaning. A satellite in Data Vault terms stores descriptive attributes that change over time and hang off a hub or link. Here, RH_DORD_IMP carries the mutable descriptive payload of an import batch — quantities, schedule dates, priorities, and intended action types — keyed to a parent import master (RH_IMPT_MST). Practitioners modeling this area should treat it as a satellite attached to an import-master hub, not as an independent hub or a resolution link.

Key Information Stored

The table possesses a documented composite primary key, RH_DORD_IMP_PK, spanning IMPORT_ID, DOC_TYPE, LINE_ID, LINE_NO, NEW_DOC_TYPE, NEW_DOC_ID, and ACTION_TYPE. This composite key is the surrogate/technical identifier for each imported demand-order line and its planned action. The foreign-key column IMPORT_ID references RH_IMPT_MST, tying every imported line back to its controlling import master record.

• IMPORT_ID — Foreign key to RH_IMPT_MST; identifies the import batch or master run that owns the line.
• LINE_ID / LINE_NO — Surrogate and sequence identifiers distinguishing individual demand-order lines within the import.
• DOC_TYPE / NEW_DOC_TYPE — The original and target document classification for the imported demand.
• NEW_DOC_ID — Identifier of the target document that the import intends to create or update.
• ACTION_TYPE — The operation to perform on the demand line (for example add, change, or delete).
• ORDER_NO — Business identifier of the source demand order.
• ORDER_QTY / OLD_ORDER_QTY — New and prior demand quantities, supporting change comparison.
• ORDER_UOM — Unit of measure for the demand quantity.
• SCHED_DATE / OLD_SCHED_DATE — New and prior required schedule dates for the demand.
• PRIORITY / OLD_PRIORITY — New and prior demand priorities.
• PROCESS_ID / ORGN_CODE — Process-planning process identifier and organization context.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN track record provenance.

The composite primary key is the documented unique constraint; the pairings of ORDER_NO with DOC_TYPE and LINE_NO act as business-key candidates for source-to-target reconciliation.

Common Use Cases and Queries

Since the table is documented as not currently used, its principal value lies in migration analysis, schema auditing, and understanding legacy import architecture. A typical diagnostic query confirms whether any rows exist:

• SELECT COUNT(*) FROM gmp.rh_dord_imp; — validates whether historical import data was ever staged.
• Join to the import master for batch context: SELECT i.import_id, d.order_no, d.order_qty, d.sched_date FROM gmp.rh_dord_imp d JOIN gmp.rh_impt_mst i ON d.import_id = i.import_id.
• Reconcile changes by comparing OLD_ORDER_QTY to ORDER_QTY or OLD_SCHED_DATE to SCHED_DATE to detect quantity and date revisions.
• Filter by ACTION_TYPE to enumerate intended operations across a batch.
• Audit lineage using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

These patterns support data-migration validation when moving demand data into supported planning tables, and serve as reference during upgrades from 12.1.1 to 12.2.2.

Related Objects

The most significant documented relationship is the foreign key from RH_DORD_IMP.IMPORT_ID to RH_IMPT_MST, the import master table that governs the staging batch. This parent-child dependency defines RH_DORD_IMP as a subordinate satellite of the import master. Supporting objects in the same Process Planning import area include the demand-order target tables that would ultimately receive processed lines, the planning engine tables that consume demand, and the organization and process-definition tables referenced through ORGN_CODE and PROCESS_ID. Because the table is unused in current releases, the FK to RH_IMPT_MST remains the authoritative documented linkage; any additional consumers should be verified directly against the installed 12.2.2 schema before being relied upon.