Search Results ra_rule_schedules




Overview
Explore in AI Chat

Overview

RA_RULE_SCHEDULES is an Oracle Receivables (AR) transactional table that stores the accounting schedules generated for invoices created with revenue recognition or invoicing rules. When a rule-driven invoice is generated in Oracle EBS 12.1.1 or 12.2.2, the Receivables engine derives one or more distribution rows with specific due dates and percentages; RA_RULE_SCHEDULES captures that derivation, giving each invoice a persisted set of period-by-period amounts that drive subsequent accounting entries. The table resides in the AR schema, is marked VALID, and is documented as containing 26 columns in the ETRM 12.2.2 physical schema.

From a Data Vault modeling perspective (heuristic classification mined from the FK structure), RA_RULE_SCHEDULES is assessed as standalone. This suggests it is best modeled as an independent satellite-like entity: its grain is defined by the composite primary key rather than by foreign-key linkage to a parent hub in the documented metadata. The absence of documented FK relationships reflects that linkage to the parent rule or invoice is carried through RULE_ID semantics rather than an enforced constraint.

Key Information Stored

The primary key of the table is RA_RULE_SCHEDULES_PK, defined on the composite columns (RULE_ID, RULE_DATE). A separate unique index, RA_RULE_SCHEDULES_U1, is defined on (RULE_ID, PERIOD_NUMBER, ZD_EDITION_NAME), which acts as a business-key candidate for the schedule rows. The most significant columns are:

  • RULE_ID — identifier of the parent rule instance; part of the primary key and the principal link to the source invoice/rule.
  • RULE_DATE — the schedule date for the row; the second component of the primary key.
  • PERIOD_NUMBER — the sequential period index within the schedule; part of the unique business key.
  • PERCENT — the percentage of the total amount allocated to this schedule period.
  • ZD_EDITION_NAME — edition/versioning column included in the unique index, supporting multi-edition (AD/Zd) installations.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — WHO columns providing standard audit tracking.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, exposing up to fifteen user-defined attribute values for extension and reporting.

Common Use Cases and Queries

Typical scenarios include reconciling scheduled revenue against invoice totals, verifying period allocation percentages, and feeding downstream revenue-recognition reporting. A simple schedule lookup by rule is:

  • SELECT rule_id, period_number, rule_date, percent FROM ra_rule_schedules WHERE rule_id = :p_rule_id ORDER BY period_number;
  • Validating that allocations sum correctly: SELECT rule_id, SUM(percent) FROM ra_rule_schedules GROUP BY rule_id HAVING SUM(percent) <> 100;
  • Auditing DFF usage: query ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for custom reporting when the flexfield is enabled for this table.

Because ZD_EDITION_NAME participates in the unique index, queries run in multi-edition environments should filter on the appropriate edition to avoid duplicate rows across editions.

Related Objects

The metadata classifies this object as standalone, so no enforced foreign keys are documented. Conceptually, the strongest relationships are:

  • RA_RULES — the parent rule definition referenced via RULE_ID.
  • RA_CUSTOMER_TRX_LINES — invoice lines whose rule-driven recognition is scheduled here.
  • RA_CUSTOMER_TRX — invoice header providing the transaction context.
  • RA_CUST_TRX_LINE_GL_DIST — accounting distributions generated from the schedule.
  • AR_RECEIVABLES_TRX_ALL — receivable activity definitions used in rule-driven generation.
  • RA_RULE_SCHEDULES_PK / RA_RULE_SCHEDULES_U1 — the constraint objects enforcing uniqueness.