Results for “po_price_diff_draft”

50+ results




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

Overview

PO_PRICE_DIFF_DRAFT is a purchasing-module draft table owned by the PO schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores draft definitions of price differentials applied to rate-based purchasing lines, so that changes to pricing schedules can be staged, reviewed, and only subsequently approved or rejected before they take effect on transactional documents. The table is therefore part of the Oracle Purchasing "draft" framework, in which supplier pricing, sourcing rules, and price differentials are held as pending versions rather than being edited in place. This staging discipline allows multi-user review, comparison, and audit before publication, and it preserves the relationship between a draft and the differential records that belong to it.

Under a heuristic Data Vault classification, mined from its foreign-key structure, PO_PRICE_DIFF_DRAFT is modeled as satellite-leaning. Practically, this means the table behaves as a descriptive, change-tracking set of attributes attached to a higher-level draft entity via the DRAFT_ID foreign key, rather than serving as an independent business hub or a pure associative link. The classification is a modeling suggestion, not a statement of the physical design, which remains a conventional relational table with a surrogate primary key.

Key Information Stored

The table contains 18 documented columns. The primary key PO_PRICE_DIFF_DRAFT_PK1 is a composite surrogate key over PRICE_DIFFERENTIAL_ID and DRAFT_ID, uniquely identifying each draft differential row. Two unique indexes supply business-key candidates: PO_PRICE_DIFF_DRAFT_U1 (PRICE_DIFFERENTIAL_ID, DRAFT_ID), which mirrors the primary key, and PO_PRICE_DIFF_DRAFT_U2 (ENTITY_ID, ENTITY_TYPE, PRICE_TYPE, DRAFT_ID), which defines uniqueness of a differential for a given entity, entity type, price type, and draft.

Common Use Cases and Queries

The principal use case is inspecting pending price differentials before they are published to the transactional pricing tables. A typical query returns all differentials for a draft, with their multiplier ranges and status:

  • SELECT price_differential_id, price_differential_num, entity_id, entity_type, price_type, multiplier, min_multiplier, max_multiplier, enabled_flag, change_status FROM po.po_price_diff_draft WHERE draft_id = :draft_id;
  • Reviewing rows pending deletion or acceptance: ... WHERE delete_flag = 'Y' or ... WHERE change_accepted_flag = 'N'.
  • Reconciling drafts by joining to PO_DRAFTS on DRAFT_ID to show the draft name and status alongside each differential.
  • Reporting on price-type coverage and multiplier ranges for a given entity to validate pricing schedules before approval.

Because the business key combines entity, entity type, price type, and draft, concurrency and duplicate-detection queries should filter on those four columns. Reporting extracts frequently join this table to published counterparts to highlight differences between the draft and current values.

Related Objects

  • PO_DRAFTS — the parent draft table; joined on PO_PRICE_DIFF_DRAFT.DRAFT_ID = PO_DRAFTS.DRAFT_ID.
  • PO_PRICE_DIFF_DRAFT_PK1 / _U1 / _U2 — primary-key and unique indexes enforcing row identity and business-key uniqueness.
  • Price differential transactional tables in the PO schema — the published counterparts against which draft rows are compared and merged upon approval.
  • Purchasing draft APIs and concurrent programs — create, submit, and publish draft records, consuming and updating this table.
  • Entity and price-type reference tables — resolved through ENTITY_ID, ENTITY_TYPE, and PRICE_TYPE for reporting lookups.