Search Results purchase




The PO_LINES_ALL_EXT_B_ARCHIVE table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 serves as an archival repository for extended attributes of purchase order lines that have been purged or archived from the primary transactional table PO_LINES_ALL. This table is part of the Purchasing module's data retention strategy, ensuring historical purchase order line details remain accessible for compliance, reporting, or audit purposes while maintaining optimal performance in active transactional tables.

Table Structure and Key Columns

The table inherits core columns from PO_LINES_ALL while focusing on extended attributes. Key columns include:
  • PO_LINE_ID: Primary key reference to the original purchase order line
  • PO_HEADER_ID: Links to the parent purchase order
  • LINE_TYPE_ID: Classification of the line item
  • ITEM_ID: Reference to inventory items
  • UNIT_PRICE: Historical pricing information
  • QUANTITY: Archived order quantities
  • NEED_BY_DATE: Original delivery requirements
  • EXT_ATTRIBUTE_[1-15]: Flexible fields for custom attributes
  • ARCHIVE_DATE: Timestamp when the record was archived

Functional Context

This table supports critical business processes:
  1. Compliance Reporting: Maintains legally required purchase records beyond active system retention periods
  2. Audit Trails: Preserves complete procurement history for internal/external audits
  3. Historical Analysis: Enables trend analysis on purchasing patterns and supplier performance
  4. Dispute Resolution: Provides immutable records for contract or delivery disagreements

Technical Implementation

The archiving process typically occurs:
  • Through scheduled purge processes in Purchasing module
  • Via custom archiving scripts for specific retention policies
  • During system upgrades or data migration projects
Integration points exist with:
  • Oracle Purchasing purge concurrent programs
  • Oracle Data Archive Manager
  • Custom archive/reporting solutions

Data Volume Considerations

In production environments:
  • Table growth correlates with purchase order volume and retention policies
  • Indexing strategy should focus on PO_HEADER_ID, PO_LINE_ID, and ARCHIVE_DATE
  • Partitioning may be implemented for large installations

Customization Potential

Organizations often extend functionality by:
  • Adding custom columns through extension tables
  • Developing archive-specific reports
  • Creating data extraction routines for external systems

Upgrade Implications

Between 12.1.1 and 12.2.2:
  • Table structure remains largely consistent
  • New extended attributes may be introduced
  • Online Patching (ADOP) in 12.2.2 affects maintenance procedures
The PO_LINES_ALL_EXT_B_ARCHIVE table represents a critical component of Oracle EBS's data lifecycle management for procurement operations, balancing system performance with regulatory and business intelligence requirements.