Results for “po_notification_ctrl_draft”

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

Overview

PO_NOTIFICATION_CTRL_DRAFT is a Purchasing (PO) module table owned by the PO schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores draft notification control records for blanket agreements and planned purchase orders. In the Oracle EBS sourcing and procurement flow, buyers can define notification controls on blanket agreements and planned purchase orders so that the system raises alerts or notifications when consumption against an agreement crosses a defined monetary amount, quantity percentage, or other condition. Because these controls are frequently edited during the negotiation and revision cycle, Oracle maintains a draft copy of the notification controls in this table before the changes are finally applied through the corresponding transactional path.

The table therefore functions as a staging and versioning area rather than as the definitive notification control store. Its relationship structure is heuristic and Data Vault oriented: the object behaves principally as a link, since it exists to associate two parent entities — a draft (PO_DRAFTS) and a purchasing document header (PO_HEADERS_ALL) — while carrying descriptive notification control attributes. The presence of the DRAFT_ID and PO_HEADER_ID foreign keys reinforces this associative role and, like a link table, it also carries a degree of versioning/status information (CHANGE_STATUS, CHANGE_ACCEPTED_FLAG, DELETE_FLAG) more typical of a satellite.

Key Information Stored

The table's documented schema contains 36 columns. The most significant are summarized below.

• NOTIFICATION_ID — Identifier of the notification control definition referenced by this draft row.
• DRAFT_ID — Foreign key to PO_DRAFTS; identifies the draft version to which the notification control belongs.
• PO_HEADER_ID — Foreign key to PO_HEADERS_ALL; links the control to the underlying blanket agreement or planned purchase order header.
• NOTIFICATION_AMOUNT — The monetary threshold at which a notification is triggered.
• NOTIFICATION_QTY_PERCENTAGE — The quantity percentage threshold for triggering notification.
• NOTIFICATION_CONDITION_CODE — Code indicating the condition under which the notification fires.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range during which the notification control is active.
• CHANGE_ACCEPTED_FLAG — Indicates whether the pending change has been accepted in the draft flow.
• CHANGE_STATUS — Tracks the workflow/status of the change within the draft process.
• DELETE_FLAG — Marks the control for logical deletion.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard auditing columns.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrency program audit columns.
• ATTRIBUTE1 … ATTRIBUTE15, ATTRIBUTE_CATEGORY — Descriptive flexfield (DFF) segments.

The surrogate primary key is PO_NOTIFICATION_CTRL_DRAFT_PK (NOTIFICATION_ID, DRAFT_ID). A unique index, PO_NOTIFICATION_CTRL_DRAFT_U1 (or UK1), exists on the same pair (NOTIFICATION_ID, DRAFT_ID), confirming this combination as the business-key candidate. The composite key guarantees that a given notification control appears only once per draft.

Common Use Cases and Queries

Because this table isolates pending notification control modifications, it is central to any reporting or reconciliation that must distinguish committed versus draft notification definitions. Typical scenarios include validating that draft controls have been accepted before a blanket agreement is activated, auditing the pending state of agreement changes, and reconciling draft controls against their finalized counterparts.

A representative query retrieves all draft notification controls for a given draft:

SELECT nctd.*
FROM po.po_notification_ctrl_draft nctd
WHERE nctd.draft_id = :draft_id;

Joining to the header and to the draft source confirms ownership and status:

SELECT d.draft_id, nctd.notification_id, nctd.notification_amount, nctd.change_status
FROM po.po_notification_ctrl_draft nctd,
po.po_drafts d,
po.po_headers_all h
WHERE nctd.draft_id = d.draft_id
AND nctd.po_header_id = h.po_header_id
AND h.segment1 = :agreement_number;

Reporting use cases include aging analyses of draft controls awaiting acceptance, tracking notification thresholds per agreement, and generating exception lists of draft rows marked with DELETE_FLAG or with CHANGE_ACCEPTED_FLAG not set.

Related Objects

The following objects are most significant to the referential and operational context of PO_NOTIFICATION_CTRL_DRAFT.

• PO_DRAFTS — referenced via DRAFT_ID; the governing draft record.
• PO_HEADERS_ALL — referenced via PO_HEADER_ID; the purchasing document header.
• PO_NOTIFICATION_CONTROLS — the transactional counterpart table storing committed notification controls, used for reconciliation.
• PO_LINES_ALL / PO_LINE_LOCATIONS_ALL — related purchasing document structures typically joined when analyzing agreement consumption against notification thresholds.
• PO_AGENTS / PO_VENDORS_SITES — sourcing counterparts often combined with this table to trace notification alerts back to agreement parties.
• PO_DRAFT_UTIL / PO_DRAFT_* APIs — the draft processing routines that populate, update, and clear rows in this staging table.