Search Results po_drafts




Overview
Explore in AI Chat

Overview

The PO_DRAFTS table is a core control table within the Oracle E-Business Suite Purchasing (PO) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master repository for managing draft changes to purchasing documents, such as purchase orders and requisitions, before those changes are finalized and applied to the live transaction tables. This table is fundamental to the draft functionality, enabling users to create, save, and later submit modifications in a controlled, non-destructive manner. Each record in PO_DRAFTS represents a unique draft session or instance, acting as a parent entity that links to all related draft changes across subsidiary tables for headers, lines, distributions, and other document components.

Key Information Stored

The primary column in the PO_DRAFTS table is DRAFT_ID, which serves as the unique identifier (Primary Key: PO_DRAFTS_PK) for a draft session. While the provided ETRM metadata does not list additional columns, based on its role as a control table, it typically stores metadata about the draft itself. This commonly includes columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY to track the draft's lifecycle, and potentially a STATUS column to indicate if the draft is in progress, submitted, or canceled. The DRAFT_ID is the critical piece of data that propagates to all related draft detail tables to maintain referential integrity and allow for the reconstruction of a complete draft document set.

Common Use Cases and Queries

The primary use case for the PO_DRAFTS table is troubleshooting and administering the draft change process. Database administrators and functional consultants query this table to identify orphaned drafts, analyze draft volume, or clean up stale data. A common reporting query involves joining PO_DRAFTS with its related detail tables to get a comprehensive view of all pending changes for a specific document or user. For instance, to find all draft distributions linked to a specific draft ID, one would use the foreign key relationship:

Another typical query is to identify drafts that have been created but not submitted within a certain timeframe, which may require purging:

  • SELECT DRAFT_ID, CREATION_DATE, CREATED_BY FROM PO.PO_DRAFTS WHERE CREATION_DATE < SYSDATE - 7;

Related Objects

The PO_DRAFTS table has a central relationship with numerous draft detail tables, as indicated by its foreign key constraints. These dependent tables store the actual proposed changes to specific aspects of a purchasing document, all linked back to a master record in PO_DRAFTS. Key related objects include:

These relationships form a cohesive draft ecosystem where PO_DRAFTS acts as the controlling entity, ensuring data consistency and enabling the atomic application or rollback of all changes associated with a single draft session.