Results for “op_alot_prm”

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

Overview

OP_ALOT_PRM is a GML (Process Manufacturing Logistics) table that stores allocation parameters by customer and item class. In Oracle EBS 12.1.1 and 12.2.2, it is the configuration backbone for the lot allocation and reservation logic used during sales order processing, picking, and shipment confirmation in process manufacturing environments. Each row defines how available lots should be selected, prioritized, and consumed for a given combination of customer, sold-to organization, ship-to organization, and allocation class.

The table is owned by the GML schema and is classified as VALID in the system data dictionary. It carries 25 documented columns in ETRM 12.2.2 and holds a primary key constraint, OP_ALOT_PRM_PK, defined on the ALLOCRULE_ID column. A secondary unique index, OP_ALOT_PRM_U1, spans ALLOC_CLASS, CUST_ID, SOLD_TO_ORG_ID, and SHIP_TO_ORG_ID, making this combination the principal business-key candidate for identifying a distinct allocation rule. Under a heuristic Data Vault classification, OP_ALOT_PRM is best modeled as a link, since its identity is largely derived from the foreign-key relationships it joins between customer master data, grade/QC reference data, text headers, and allocation rule definitions.

Key Information Stored

The surrogate primary key ALLOCRULE_ID uniquely identifies each allocation rule and is the column behind OP_ALOT_PRM_PK. The business-key candidates from OP_ALOT_PRM_U1 — ALLOC_CLASS, CUST_ID, SOLD_TO_ORG_ID, and SHIP_TO_ORG_ID — determine which rule applies to a given order. ALLOC_CLASS identifies the item class or grouping that the rule governs.

Allocation behavior is driven by ALLOC_METHOD, ALLOC_TYPE, ALLOC_HORIZON, SHELF_DAYS, LOT_QTY, and PARTIAL_IND. Collectively these control the selection algorithm, the time window over which lots are considered, minimum remaining shelf life, lot quantity constraints, and whether partial allocations are permitted. PREFQC_GRADE designates the preferred quality or grade, and GRADE_OR_QC_FLAG indicates whether grade or QC logic governs the rule.

Additional columns include ALLOC_CATEGORY_ID and CO_CODE for categorization and company context, ORG_ID for operating unit/warehouse scoping, and OPM_CUST_ID as the process manufacturing customer reference. TEXT_CODE links to descriptive text, while the standard audit columns (CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, TRANS_CNT, DELETE_MARK) support concurrency control and logical deletion.

Common Use Cases and Queries

Typical reporting and troubleshooting scenarios include determining which allocation rule applies to an order line, reviewing shelf-life and horizon parameters by customer, and auditing grade preferences. A representative query joining customer and grade reference data:

• SELECT p.ALLOCRULE_ID, p.ALLOC_CLASS, p.ALLOC_METHOD, p.ALLOC_TYPE, p.SHELF_DAYS, p.ALLOC_HORIZON, p.PREFQC_GRADE FROM GML.OP_ALOT_PRM p WHERE p.DELETE_MARK = 0 AND p.CUST_ID = :cust_id;
• Filtering by the business key: WHERE ALLOC_CLASS = :class AND SOLD_TO_ORG_ID = :sold_to AND SHIP_TO_ORG_ID = :ship_to.
• Auditing preferred grade assignments by joining to GMD_GRADES_B on PREFQC_GRADE.

These patterns support order-to-shipment analysis, allocation rule maintenance, and quality-driven lot selection reporting.

Related Objects

OP_ALOT_PRM participates in several documented foreign-key relationships:

• OP_CUST_MST — joined on CUST_ID, providing the customer master definition.
• GMD_GRADES_B — joined on PREFQC_GRADE, supplying grade definitions.
• QC_GRAD_MST — also joined on PREFQC_GRADE, providing QC grade master data.
• OP_TEXT_HDR — joined on TEXT_CODE, supplying descriptive text headers.

Through its primary key on ALLOCRULE_ID, the table is referenced by dependent allocation processing logic and reporting views in the GML module, making it a central configuration point for lot allocation in process manufacturing order fulfillment.