Search Results rcv_accounting_event_types




Overview
Explore in AI Chat

Overview

RCV_ACCOUNTING_EVENT_TYPES is a reference (lookup) table owned by the PO schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It defines the set of receiving accounting event types used by Oracle Purchasing and the Receiving module to categorize the accounting events generated during the receipt, delivery, return, and correction of goods. Each row represents a distinct event type — for example receipt, delivery, return to vendor, or correction — that drives the accounting entries created by the Receiving Accounting Engine and interfaced to Subledger Accounting and General Ledger.

In Data Vault terms, the primary key EVENT_TYPE_ID and the absence of any foreign key depending on this table make it a hub-leaning entity. It functions as a stable, slowly changing reference (code) table whose members are referenced by many transactional and interface tables. Modeling it as a hub (business key = EVENT_TYPE_NAME, surrogate = EVENT_TYPE_ID) with the descriptive attributes as a satellite is a reasonable suggestion, though in the EBS relational model it is simply a validation/reference table.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are:

The business-key candidate is EVENT_TYPE_ID plus ZD_EDITION_NAME (RCV_ACCOUNTING_EVENT_TYPES_U1); EVENT_TYPE_NAME is the natural descriptive identifier used in reporting joins.

Common Use Cases and Queries

The table is most often joined to the receiving accounting events to translate an internal event type ID into a meaningful name for reporting and reconciliation.

  • Listing all valid receiving event types: SELECT event_type_id, event_type_name, description FROM po.rcv_accounting_event_types ORDER BY event_type_name;
  • Resolving events to names: SELECT e.event_id, e.event_type_id, t.event_type_name, e.transaction_date FROM po.rcv_accounting_events e, po.rcv_accounting_event_types t WHERE e.event_type_id = t.event_type_id AND e.transaction_date >= :from_date;
  • Reconciliation and audit: counting accounting events by type to verify that receipt, delivery, and return volumes match expectations.
  • Subledger and SLA analysis: using the event type to classify accounting entries posted to XLA_AE_LINES and the general ledger.
  • Period-end validation: identifying any accounting events whose EVENT_TYPE_ID has no matching parent row (orphan detection).

Related Objects

RCV_ACCOUNTING_EVENT_TYPES is referenced by several transactional and interface tables through the EVENT_TYPE_ID column:

  • RCV_ACCOUNTING_EVENTS — the primary dependent table; RCV_ACCOUNTING_EVENTS.EVENT_TYPE_ID references RCV_ACCOUNTING_EVENT_TYPES.
  • PA_EVENT_TYPES — projects event type reference (PA_EVENT_TYPES.EVENT_TYPE_ID).
  • PA_RBS_ELEMENTS — project billing resource elements (PA_RBS_ELEMENTS.EVENT_TYPE_ID).
  • PJI_FM_AGGR_FIN6 — project financial aggregation (PJI_FM_AGGR_FIN6.EVENT_TYPE_ID).
  • CST_LC_RAE_EVENTS_GT — cost management receiving accounting events global temporary table (CST_LC_RAE_EVENTS_GT.EVENT_TYPE_ID).
  • PJI_FP_TXN_ACCUM_HEADER — project transaction accumulation header (PJI_FP_TXN_ACCUM_HEADER.EVENT_TYPE_ID).
  • CST_ACCT_LIB_PACKAGES — cost accounting library packages (CST_ACCT_LIB_PACKAGES.EVENT_TYPE_ID).

These relationships confirm the table's role as a centralized reference hub for receiving accounting events that feeds cost management, projects, and subledger accounting processes.