Search Results project accounting




The RCV_SUB_LEDGER_DETAILS table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical repository for capturing detailed transactional data related to the Receiving (RCV) subledger. This table plays a pivotal role in the Procure-to-Pay (P2P) cycle, particularly in tracking receipt and inspection details before they are accounted for in the General Ledger (GL). Below is a detailed breakdown of its structure, purpose, and integration within Oracle EBS.

1. Purpose and Functional Context

The RCV_SUB_LEDGER_DETAILS table stores granular information about receiving transactions, acting as a bridge between the Receiving module and the Subledger Accounting (SLA) framework. It captures data necessary for generating accounting entries, including:
  • Receipt Details: Quantities, item descriptions, and unit of measure (UOM) for received goods.
  • Cost Distribution: Allocation of costs across accounts (e.g., inventory, expense, or asset accounts).
  • Inspection Results: Quality inspection outcomes (accepted, rejected, or returned quantities).
  • PO and Shipment References: Links to purchase orders (PO_HEADER_ID, PO_LINE_ID) and shipments (SHIPMENT_HEADER_ID).

2. Key Columns and Relationships

The table's schema includes columns that facilitate integration with other EBS modules:
  • Primary Keys: RCV_TRANSACTION_ID (links to RCV_TRANSACTIONS) and ACCOUNTING_LINE_NUMBER.
  • Accounting Attributes: CODE_COMBINATION_ID (GL accounts), AMOUNT, CURRENCY_CODE.
  • Subledger References: APPLICATION_ID (set to 707 for Receiving), EVENT_ID, SOURCE_ID (tied to SLA events).
  • Audit Columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE.
Relationships with other tables:
  • RCV_TRANSACTIONS: Provides transactional metadata (e.g., receipt dates).
  • PO_DISTRIBUTIONS_ALL: Maps PO distributions to accounting lines.
  • XLA_AE_LINES: Final accounting entries in SLA.

3. Integration with Subledger Accounting (SLA)

The table feeds data into SLA for accrual and liability accounting:
  • Event Processing: Records in RCV_SUB_LEDGER_DETAILS trigger SLA events (e.g., RCV_RECEIVING_SUB_LEDGER).
  • Accounting Rules: SLA uses this data to apply rules defined in XLA_EVENT_TYPES and generate journal entries.
  • GL Reconciliation: Ensures receipt costs align with PO distributions before GL posting.

4. Data Flow Example

A typical workflow involves:
  1. A receipt is created in RCV_TRANSACTIONS for a PO line.
  2. RCV_SUB_LEDGER_DETAILS stores cost distributions (e.g., $1,000 to Inventory Account).
  3. SLA processes the event, creating a journal entry debiting Inventory and crediting Accrued Liabilities.
  4. Journals are transferred to GL via GL_INTERFACE.

5. Customization and Reporting

The table is often leveraged for:
  • Custom Reports: SQL queries to analyze receipt-to-accounting discrepancies.
  • Audit Trails: Tracking changes to received item costs.
  • Extensions: Triggers or APIs may update it for third-party integrations.

6. Common Issues and Troubleshooting

  • Missing Accounting Entries: Verify SLA event completeness and RCV_SUB_LEDGER_DETAILS data.
  • Data Corruption: Use XLA_EVENTS to trace unprocessed transactions.
  • Performance: Indexes on RCV_TRANSACTION_ID and SHIPMENT_HEADER_ID are critical.
In summary, RCV_SUB_LEDGER_DETAILS is a foundational table for Receiving accounting in Oracle EBS, ensuring accurate cost capture and GL integration. Its design supports auditability, compliance, and seamless interoperability with SLA, making it indispensable for financial controls in procurement operations.