Search Results ra_rules_u1

Overview

AR.RA_RULES is the Receivables master reference table for invoicing and accounting (revenue recognition) rules in Oracle E-Business Suite 12.1.1 and 12.2.2. Receivables creates one row for each rule defined by the user, and the table functions as the central definition point that determines both when a receivable is recognized on invoices spanning multiple accounting periods and how revenue is spread across periods for invoice lines. Two seeded invoicing rules are provided: Bill in Advance, which recognizes the receivable immediately, and Bill in Arrears, which recognizes it at the end of the revenue recognition schedule. Accounting rules drive the revenue recognition schedule rows stored in AR.RA_RULE_SCHEDULES. In the ETRM 12.2.2 physical schema the table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10 and 30 documented columns.

The supplied relationship metadata classifies AR.RA_RULES as hub-leaning, mined from the wide fan-out of foreign keys pointing at it. Treated as a modeling suggestion, this positions the table as a stable, code-like reference entity (a hub) whose rows are referenced by many transactional satellites and links, rather than as a transaction table itself.

Key Information Stored

The surrogate primary key is RULE_ID (NUMBER(15)), the revenue recognition rule identifier. The documented unique index RA_RULES_U1 — the object name the user searched — is defined on (RULE_ID, ZD_EDITION_NAME), reflecting the 12.2.x editioning column that supports online patching; in a non-editioned 12.1.1 environment the unique constraint is effectively carried by RULE_ID alone (RA_RULES_PK). RULE_ID and NAME together act as the practical business-key candidates for lookups and reporting joins.

• RULE_ID — surrogate primary key and the column referenced by every downstream foreign key.
• NAME — the user-visible rule name (VARCHAR2(30)); the natural lookup key for Bill in Advance and Bill in Arrears.
• TYPE — distinguishes invoicing rules from accounting rules.
• STATUS — active/inactive state controlling rule availability at entry time.
• FREQUENCY — the period frequency applied to the recognition schedule (for example, monthly).
• OCCURRENCES — the number of periods over which revenue is recognized.
• DESCRIPTION — free-text description of the rule's purpose.
• DEFERRED_REVENUE_FLAG — indicates whether recognition is deferred; relevant to multi-period revenue handling.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield (DFF) columns for customer-specific rule attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ZD_EDITION_NAME — 12.2.x editioning discriminator, part of the unique index.

Common Use Cases and Queries

Typical usage centers on resolving rule identifiers to meaningful names in reporting, validating rule configuration before AutoInvoice imports, and auditing where a rule is referenced. Querying active accounting rules is a common starting point:

SELECT rule_id, name, type, status, frequency, occurrences
FROM ar.ra_rules WHERE type = 'A' AND status = 'A';

To resolve invoicing rules applied on transaction lines, join RA_CUSTOMER_TRX_LINES_ALL to RA_RULES on ACCOUNTING_RULE_ID. Because many Order Management and Service tables carry INVOICING_RULE_ID and ACCOUNTING_RULE_ID, a frequent audit pattern counts references per rule across OE_ORDER_HEADERS_ALL and MTL_SYSTEM_ITEMS_B. Analysts also verify the revenue recognition schedule generated for a given rule by joining RA_RULES.RULE_ID to RA_RULE_SCHEDULES, typically reading from the RA_RULES_V or RA_RULE_SCHEDULES views rather than the base table.

Related Objects

The foreign-key fan-in is broad; the following are the most significant referencing objects with their join columns:

• AR.RA_RULE_SCHEDULES — stores the revenue recognition schedule rows for accounting rules (join on RULE_ID).
• AR.RA_CUSTOMER_TRX_LINES_ALL — invoice lines carry ACCOUNTING_RULE_ID → RA_RULES.RULE_ID.
• AR.AR_MEMO_LINES_ALL_B — credit/debit memo lines reference both INVOICING_RULE_ID and ACCOUNTING_RULE_ID.
• OE.OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL — order headers and lines default both rule identifiers.
• OE.OE_TRANSACTION_TYPES_ALL — transaction types default INVOICING_RULE_ID and ACCOUNTING_RULE_ID.
• INV.MTL_SYSTEM_ITEMS_B — item master defaults INVOICING_RULE_ID and ACCOUNTING_RULE_ID.
• OE.OE_AGREEMENTS_B / SO.SO_AGREEMENTS_B — agreements reference both rule columns.
• OE/SO interface tables — OE_HEADERS_IFACE_ALL, OE_LINES_IFACE_ALL, SO_HEADERS_INTERFACE_ALL, and SO_LINES_INTERFACE_ALL carry rule identifiers during import.

Together these references confirm RA_RULES as a shared reference hub consumed across Receivables, Order Management, Inventory, and Service.