Search Results receipts




Deep Dive into PO_HISTORY_RECEIPTS Table in Oracle EBS 12.1.1/12.2.2

The PO_HISTORY_RECEIPTS table is a critical repository within Oracle E-Business Suite (EBS) Procurement modules (versions 12.1.1 and 12.2.2), storing historical receipt transactions linked to purchase orders. It serves as an audit trail for received items, capturing granular details about quantity, date, location, and acceptance status. This table is integral to inventory reconciliation, financial accruals, and compliance reporting.

Key Attributes and Structure

  • RECEIPT_NUM: Unique identifier for each receipt transaction.
  • PO_HEADER_ID/PO_LINE_ID: Foreign keys linking to PO_HEADERS_ALL and PO_LINES_ALL.
  • ITEM_ID: References MTL_SYSTEM_ITEMS_B for item details.
  • QUANTITY: Received quantity with UOM (Unit of Measure).
  • RECEIPT_DATE: Timestamp of receipt creation.
  • SHIPMENT_HEADER_ID: Links to RCV_SHIPMENT_HEADERS for shipment context.
  • DESTINATION_TYPE_CODE: Indicates if receipt is for inventory, expense, or shop floor.
  • ACCOUNTING_DATE: Used for GL period reconciliation.

Functional Integration

The table interacts with multiple Oracle EBS modules:

  1. Inventory Management: Updates MTL_MATERIAL_TRANSACTIONS upon receipt.
  2. Payables: Provides matched receipt data for invoice validation via AP_INVOICE_LINES.
  3. General Ledger: Feeds accrual entries through GL_INTERFACE.
  4. Cost Management: Captures item costs in CST_ITEM_COSTS.

Technical Considerations

Data flows into PO_HISTORY_RECEIPTS through:

  • Receiving Transactions form (Oracle Forms).
  • Auto-receipts via EDI/XML integrations.
  • APIs like RCV_TRANSACTION_API.

Indexes on PO_HEADER_ID, PO_LINE_ID, and RECEIPT_NUM optimize query performance for PO matching and reporting.

Customization and Extensions

Common enhancements include:

  • Adding custom columns for project tracking (e.g., PROJECT_ID).
  • Creating triggers to sync with external WMS systems.
  • Developing BI Publisher reports leveraging PO_HISTORY_RECEIPTS_V view.

Data Retention and Archiving

Oracle recommends:

  • Purging via RCV_PURGE_ARCHIVE concurrent program.
  • Partitioning by RECEIPT_DATE for large-volume implementations.

In summary, PO_HISTORY_RECEIPTS is a foundational table for procure-to-pay processes, ensuring traceability from purchase orders to financial postings. Its design supports complex multi-org, multi-currency implementations while maintaining data integrity through foreign key constraints.