Search Results rcv shipments




The PO_LINE_LOCATIONS_ARCHIVE_ALL table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 serves as a critical repository for historical purchase order shipment data, ensuring compliance, auditability, and reporting capabilities. This table archives shipment-level information from PO_LINE_LOCATIONS_ALL when purchase orders are modified, canceled, or closed, preserving a complete transactional history. Below is a detailed analysis of its structure, purpose, and integration within Oracle Procurement.

Purpose and Functional Overview

The PO_LINE_LOCATIONS_ARCHIVE_ALL table captures snapshots of shipment details (e.g., quantities, prices, delivery dates) associated with purchase order lines before changes are made. Key scenarios triggering archiving include:
  • Order Modifications: Changes to shipment terms, quantities, or pricing.
  • Order Cancellation/Closure: Retains pre-closure shipment data for reference.
  • Audit Requirements: Supports regulatory compliance (e.g., SOX, GDPR) by maintaining immutable records.

Key Columns and Relationships

The table mirrors the structure of PO_LINE_LOCATIONS_ALL with additional archival metadata. Notable columns include:
  • PO_LINE_LOCATION_ID: Foreign key to the original shipment record.
  • ARCHIVE_DATE: Timestamp of archival (critical for historical tracking).
  • SHIPMENT_TYPE: Distinguishes between standard, blanket, or planned shipments.
  • QUANTITY/PRICE: Archived values at the time of modification.
  • ORG_ID: Multi-org identifier for partitioned data access.
Relationships exist with PO_HEADERS_ARCHIVE_ALL and PO_LINES_ARCHIVE_ALL, forming a complete historical purchase order hierarchy.

Integration with Oracle EBS Modules

The table interacts with several EBS components:
  • Procurement: Tracks changes to shipments for supplier performance analysis.
  • Inventory/Receiving: Links archived shipments to receipt histories via RCV_SHIPMENT_LINES.
  • Financials: Provides audit trails for AP invoice matching (PO_DISTRIBUTIONS_ARCHIVE_ALL).

Technical Considerations

  • Partitioning: In EBS 12.2.2, partitioning by ARCHIVE_DATE improves query performance for large datasets.
  • Indexing: Key indexes on PO_LINE_LOCATION_ID, PO_HEADER_ID, and ORG_ID optimize joins.
  • Purge Policies: Controlled via concurrent programs (e.g., "Purge Document Archival Records") to manage storage.

Customization and Extensions

Common enhancements include:
  • Custom Reports: SQL queries leveraging archived data for trend analysis.
  • Triggers: Additional validation during archival (e.g., capturing user comments).
  • APIs: PO_ARCHIVE package for programmatic access to archived records.

Conclusion

The PO_LINE_LOCATIONS_ARCHIVE_ALL table is indispensable for maintaining data integrity in Oracle Procurement. Its design ensures traceability across the procure-to-pay lifecycle while supporting advanced reporting and compliance needs. Organizations should align archival retention policies with business requirements and leverage partitioning in EBS 12.2.2 for optimal performance.