Search Results rcv_shipment_lines

The RCV_SHIPMENT_LINES table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical repository for receiving transaction data, capturing detailed information about items received against purchase orders, requisitions, or other sourcing documents. As part of the Oracle Purchasing and Inventory modules, this table serves as a transactional backbone for receiving operations, interfacing with key supply chain processes such as procurement, inventory management, and accounts payable.

Table Structure and Key Columns

The RCV_SHIPMENT_LINES table contains columns that track receipt line details, including:

• SHIPMENT_LINE_ID: Primary key identifier for each receipt line.
• SHIPMENT_HEADER_ID: Foreign key linking to RCV_SHIPMENT_HEADERS, associating lines with their parent receipt document.
• PO_HEADER_ID and PO_LINE_ID: References to the purchase order and line being received.
• ITEM_ID: Links to MTL_SYSTEM_ITEMS_B for item master data.
• QUANTITY_SHIPPED, QUANTITY_RECEIVED, and QUANTITY_ACCEPTED: Tracks receipt progress against ordered quantities.
• UOM_CODE: Unit of measure for the received item.
• DESTINATION_TYPE_CODE: Determines whether items are received into inventory ('INVENTORY'), expense accounts ('EXPENSE'), or other destinations.
• TO_ORGANIZATION_ID: Target inventory organization for stock items.

Integration Points

The table integrates with multiple EBS modules:

• Purchasing: Validates receipts against purchase order terms via PO_DISTRIBUTIONS_ALL.
• Inventory: Generates material transactions through MTL_MATERIAL_TRANSACTIONS when items are delivered to stock.
• Accounts Payable: Provides matched receipt data for invoice validation via AP_INVOICE_LINES.
• General Ledger: Posts accounting entries through GL_INTERFACE for expense destinations.

Business Process Flow

1. Receipt Creation: Records are inserted into RCV_SHIPMENT_LINES when users initiate receipts in the "Receiving Transactions" form or via automated interfaces.
2. Quantity Updates: As goods move through inspection (accept/reject), the QUANTITY_ACCEPTED field is updated, triggering potential quality holds.
3. Delivery: For inventory destinations, delivery creates on-hand balances and cost distributions.
4. Interface to AP: The RCV_TRANSACTIONS table (child of RCV_SHIPMENT_LINES) provides three-way matching data.

Technical Considerations

• Indexing: Critical for performance on columns like SHIPMENT_HEADER_ID, PO_LINE_ID, and ITEM_ID.
• Purge Requirements: Data grows rapidly; Oracle provides the PURGE_RECEIVING_DATA API for archiving.
• Custom Extensions: Common extension points include custom validations via database triggers or workflow integrations.

Version-Specific Notes

In EBS 12.2.2, enhancements include:

• Improved LOB storage for attachment data.
• Integration with Oracle Fusion Procurement cloud services via SOAP APIs.
• Additional columns for landed cost management in advanced procurement deployments.

This table's comprehensive design ensures auditability, supports complex receiving scenarios (e.g., drop shipments, consignment), and maintains data integrity through foreign key constraints with over 15 related tables in the receiving ecosystem.