Search Results po_requisition_headers_all




The PO_REQUISITION_HEADERS_ALL table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical repository for purchase requisition header-level data, serving as the foundation for procurement processes. This table stores metadata and control information for requisitions, which are internal requests for goods or services before they are converted into purchase orders. Below is a detailed analysis of its structure, purpose, key columns, and integration within Oracle EBS.

Table Overview

PO_REQUISITION_HEADERS_ALL is a multi-organization table, denoted by the "_ALL" suffix, meaning it stores data across operating units. Each record represents a requisition header, which includes attributes like requisition number, creation date, status, and requester details. The table links to subsidiary tables such as PO_REQUISITION_LINES_ALL (for line items) and integrates with modules like Purchasing, Inventory, and General Ledger.

Key Columns and Descriptions

  • REQUISITION_HEADER_ID: Primary key, uniquely identifying each requisition.
  • SEGMENT1: The human-readable requisition number (e.g., "REQ12345").
  • PREPARER_ID: Foreign key to PER_ALL_PEOPLE_F, identifying the employee who created the requisition.
  • DESCRIPTION: Optional text describing the requisition's purpose.
  • AUTHORIZATION_STATUS: Tracks workflow approval states (e.g., "APPROVED," "PENDING").
  • CREATION_DATE and LAST_UPDATE_DATE: Audit columns for tracking record lifecycle.
  • ORG_ID: Operating unit identifier, enabling multi-org functionality.
  • TYPE_LOOKUP_CODE: Classifies requisitions (e.g., "PURCHASE," "INTERNAL").

Functional Significance

The table supports core procurement workflows:
  1. Requisition Creation: Users initiate requests via Oracle Self-Service Procurement or Purchasing forms, inserting records into this table.
  2. Approval Routing: The AUTHORIZATION_STATUS column interacts with Oracle Workflow to manage approvals.
  3. Conversion to POs: Approved requisitions are sourced by buyers to generate purchase orders, linking to PO_HEADERS_ALL.
  4. Reporting & Analytics: The table feeds OTBI (Oracle Transactional Business Intelligence) for spend analysis.

Integration Points

  • Inventory: Requisitions for stock items reference MTL_SYSTEM_ITEMS_B.
  • General Ledger: Charge accounts are validated against GL_CODE_COMBINATIONS.
  • HRMS: Employee data ties to PER_ALL_PEOPLE_F for requester details.

Technical Considerations

  • Indexes: Key indexes include PO_REQUISITION_HEADERS_U1 (on REQUISITION_HEADER_ID) and PO_REQUISITION_HEADERS_N1 (on SEGMENT1).
  • Partitioning: In large implementations, partitioning by CREATION_DATE improves performance.
  • Purge Strategies: Archiving old requisitions via PO_PURGE_REQUISITIONS prevents table bloating.

Customization Scenarios

Extensions might include:
  • Adding descriptive flexfields (DFFs) for industry-specific attributes.
  • Creating triggers to enforce custom validation rules.
  • Developing APIs to integrate with third-party systems.

Conclusion

The PO_REQUISITION_HEADERS_ALL table is a linchpin in Oracle EBS Procurement, enabling end-to-end requisition management. Its design supports scalability, auditability, and integration with financial and supply chain modules. Understanding its structure is essential for troubleshooting, customization, and optimizing procurement operations.