Search Results ra_rules_pk

Overview

RA_RULES is the Oracle Receivables reference table that stores the invoicing and accounting rules used throughout the E-Business Suite. Invoicing rules control how revenue or billing amounts are distributed across invoice lines (for example, periodic, milestone, or advance-based billing), while accounting rules define the recognition schedule — the number of periods and the percentage allocated to each period — for deferred revenue and receivable recognition. The table resides in the AR schema and is validated under both EBS 12.1.1 and 12.2.2.

Because RA_RULES acts as a central definition repository referenced by order management, inventory, and receivables entities, a Data Vault modeling heuristic classifies it as hub-leaning: the RULE_ID is a stable business key reused as a foreign key across many dependent tables. Under this interpretation, RA_RULES functions as the hub from which invoicing and accounting rule assignments radiate into link and satellite structures.

Key Information Stored

The table is defined with 30 columns. The most significant are:

• RULE_ID — the surrogate primary key (RA_RULES_PK), uniquely identifying each rule. It is also the column referenced by all foreign keys pointing to this table.
• NAME — the user-facing rule name displayed in Receivables and Order Management.
• TYPE — distinguishes whether the row is an invoicing rule or an accounting rule.
• STATUS — active/inactive indicator controlling availability in pick lists and validation.
• FREQUENCY — the interval (for example, monthly, quarterly) governing the recognition or billing cycle.
• OCCURRENCES — the number of periods over which the rule is applied.
• DESCRIPTION — free-text explanation of the rule's purpose.
• DEFERRED_REVENUE_FLAG — indicates whether the rule defers revenue recognition.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns for customer-specific extensions.
• ZD_EDITION_NAME — the edition column used by the 12.2.2 online patching (editioning) architecture; the unique index RA_RULES_U1 is defined on (RULE_ID, ZD_EDITION_NAME), making this the effective business-key candidate in 12.2.2.
• Standard audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting and validation scenarios include listing active rules by type, tracing which orders or items reference a given rule, and verifying rule assignments before revenue recognition runs.

• Look up active rules of a given type: SELECT rule_id, name, type, frequency, occurrences FROM ra_rules WHERE status = 'A' AND type = 'A';
• Join to order lines to see assigned invoicing rules: SELECT l.order_number, r.name FROM oe_order_lines_all l, ra_rules r WHERE l.invoicing_rule_id = r.rule_id;
• Find items bound to an accounting rule: SELECT i.segment1, r.name FROM mtl_system_items_b i, ra_rules r WHERE i.accounting_rule_id = r.rule_id;
• Identify invoice lines using a specific accounting rule: SELECT t.trx_number, r.name FROM ra_customer_trx_lines_all t, ra_rules r WHERE t.accounting_rule_id = r.rule_id;

These patterns support revenue recognition audits, setup validation, and impact analysis before changing or end-dating a rule.

Related Objects

RA_RULES is referenced through two principal foreign key columns — INVOICING_RULE_ID and ACCOUNTING_RULE_ID. The most significant dependent objects are:

• RA_CUSTOMER_TRX_LINES_ALL — references via ACCOUNTING_RULE_ID.
• AR_MEMO_LINES_ALL_B — references via INVOICING_RULE_ID and ACCOUNTING_RULE_ID.
• OE_ORDER_HEADERS_ALL — references via both rule columns.
• OE_ORDER_LINES_ALL — references via both rule columns.
• OE_TRANSACTION_TYPES_ALL — defaults rules at the transaction-type level.
• MTL_SYSTEM_ITEMS_B — item-level rule defaults.
• OE_AGREEMENTS_B and SO_AGREEMENTS_B — agreement-level rule assignments.
• OE_HEADERS_IFACE_ALL, OE_LINES_IFACE_ALL, SO_HEADERS_INTERFACE_ALL, and SO_LINES_INTERFACE_ALL — interface tables used during order import.

These relationships confirm RA_RULES as a foundational setup table whose values propagate into ordering, agreements, and receivables transaction processing.