Search Results op_prce_cds




Overview
Explore in AI Chat

Overview

OP_PRCE_CDS is a reference (setup) table owned by the GML schema within Oracle Process Manufacturing Logistics (GML). Its documented description is "Order Entry Price Reason Codes," identifying it as the master list of reason codes that qualify or explain price adjustments captured during order entry in Process Manufacturing. In Oracle EBS 12.1.1 and 12.2.2, such code tables drive list-of-values validation, defaulting logic, and pricing auditability across the order-to-cash flow.

From a dimensional modeling perspective, the mined Data Vault classification for OP_PRCE_CDS is hub-leaning. This is consistent with its role: the table holds a stable business concept (a price reason code) with a single-column primary key and no upstream dependencies of its own, while downstream transactional tables reference it. A modeler would therefore treat OP_PRCE_CDS as a candidate hub, with OP_ORDR_DTL acting as the linking/satellite-bearing transaction that captures the actual price-reason assignments over time.

Key Information Stored

The table comprises 12 documented columns. The most significant are:

  • PRICEREAS_CODE — the primary key column and the sole unique-index business-key candidate (index OP_PRCE_CDS_PK). It is the code consumed by order-entry screens and stored on order lines.
  • PRICE_REASON — the descriptive text associated with the code, used in list-of-values and reporting labels.
  • TOLERANCE_HI and TOLERANCE_LO — upper and lower tolerance thresholds tied to the reason code, supporting validation of acceptable price variance.
  • TEXT_CODE — a secondary code providing additional classification or reference text for the reason.
  • DELETE_MARK — the soft-delete/active indicator; codes are typically end-dated rather than physically removed.
  • TRANS_CNT — the transaction counter used for optimistic locking and concurrency control.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns providing audit lineage.

Note that PRICEREAS_CODE serves as both the surrogate primary key and the natural business key, since OP_PRCE_CDS_PK is the only documented unique index and is defined on that single column.

Common Use Cases and Queries

Typical scenarios include validating price reason assignments on order lines, building pricing-variance reports, and auditing tolerance breaches. A list of active codes can be retrieved as follows:

  • SELECT PRICEREAS_CODE, PRICE_REASON, TOLERANCE_HI, TOLERANCE_LO FROM GML.OP_PRCE_CDS WHERE NVL(DELETE_MARK,0) = 0;
  • Joining order detail to its reason description:
    SELECT d.ORDER_ID, d.LINE_ID, d.PRICEREAS_CODE, c.PRICE_REASON, c.TOLERANCE_HI, c.TOLERANCE_LO FROM GML.OP_ORDR_DTL d, GML.OP_PRCE_CDS c WHERE d.PRICEREAS_CODE = c.PRICEREAS_CODE;
  • Identifying unassigned or orphaned reason codes on order lines using an outer join where c.PRICEREAS_CODE IS NULL.

These queries support pricing exception reporting, order-entry validation audits, and setup cleanliness checks before period close.

Related Objects

The dominant documented relationship is inbound from the order detail table, meaning OP_PRCE_CDS is a parent reference table rather than a child:

  • OP_ORDR_DTL — references OP_PRCE_CDS via OP_ORDR_DTL.PRICEREAS_CODE → OP_PRCE_CDS.PRICEREAS_CODE; this is the primary consuming transaction table for order-entry price reasons.
  • Setup and validation logic in the Order Entry and pricing modules that present price reason codes as list-of-values for the PRICEREAS_CODE field.
  • Reporting and concurrency frameworks that rely on the WHO audit columns and TRANS_CNT for change tracking.

No additional FK relationships are documented in the supplied ETRM metadata, indicating OP_PRCE_CDS is a terminal reference table with no upstream parent dependencies of its own.