Search Results po.po_headers_all




The PO.PO_HEADERS_ALL table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 serves as a fundamental repository for purchase order (PO) header information. It stores critical metadata and transactional data related to purchase orders, requisitions, and blanket agreements, forming the backbone of Oracle Purchasing and Procurement modules. This table is multi-org enabled, meaning it contains records for all operating units within an enterprise, distinguished by the ORG_ID column.

Key Columns and Their Significance

  • PO_HEADER_ID: Primary key identifier for each PO header record.
  • SEGMENT1: Stores the human-readable PO number (e.g., 'PO-12345').
  • TYPE_LOOKUP_CODE: Indicates PO type (STANDARD, BLANKET, CONTRACT, PLANNED).
  • AUTHORIZATION_STATUS: Tracks approval workflow state (APPROVED, IN PROCESS, REJECTED).
  • ORG_ID: Operating unit identifier for multi-org implementations.
  • VENDOR_ID: Foreign key to AP_SUPPLIERS for supplier information.
  • AGENT_ID: References PER_ALL_PEOPLE_F for the buyer/creator.
  • CURRENCY_CODE: Stores transaction currency from FND_CURRENCIES.
  • RATE_TYPE/RATE_DATE/RATE: Fields for currency conversion details.

Business Process Integration

The table integrates with numerous Oracle EBS processes:

  • Procurement Lifecycle: Tracks POs from creation through approval to closure.
  • Financial Integration: Links to AP_INVOICES_ALL for invoice matching.
  • Inventory Management: Connects to MTL_SYSTEM_ITEMS for item-based POs.
  • Project Accounting: Contains project references via PROJECT_ID column.

Technical Considerations

  • Indexes: Key indexes include PO_HEADERS_ALL_N1 (PO_HEADER_ID) and PO_HEADERS_ALL_N2 (TYPE_LOOKUP_CODE, SEGMENT1).
  • Partitioning: Often partitioned by CREATION_DATE in large implementations.
  • Views: Business users typically access data through PO_HEADERS_V view.
  • API Access: Modifications should use PO_PUBLISH_PKG APIs rather than direct DML.

Customization Points

Common extension scenarios include:

  • Adding custom attributes via Descriptive Flexfields (DFF)
  • Creating triggers for approval workflow enhancements
  • Developing custom reports using the ORG_ID filter
  • Integrating with third-party systems via the interface tables

Data Retention and Archiving

The table typically grows large in active implementations. Oracle provides the PO_PURGE_PROCESS package for archiving obsolete records while maintaining referential integrity with related tables like PO_LINES_ALL and PO_DISTRIBUTIONS_ALL.

In both 12.1.1 and 12.2.2 versions, the table structure remains largely consistent, with 12.2.2 adding minor enhancements for cloud readiness. Proper understanding of PO_HEADERS_ALL is essential for implementing, customizing, and troubleshooting Oracle Purchasing modules.