Results for “ra_line_ordering_rules”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RA_LINE_ORDERING_RULES is a Receivables (AR) reference table that stores the AutoInvoice line ordering rules used by Oracle E-Business Suite during the import of transaction data from external sources. AutoInvoice is the inbound interface engine that validates and converts staged records in the RA_INTERFACE_LINES_ALL and related interface tables into live Receivables transactions. When a transaction line is built from multiple interface distributions or line attributes, the ordering rule determines the sequence in which those lines are presented and processed, which in turn affects tax calculation, line-level defaults, and the final invoice layout.

The table resides in the AR schema and is classified as VALID in Oracle EBS 12.1.1 and 12.2.2. Its documented physical schema contains 27 columns. Based on the mined foreign key structure — where RA_GROUPING_RULES and RA_LINE_ORDER_BYS each hold an ORDERING_RULE_ID foreign key pointing back to this table — the Data Vault classification heuristic suggests a hub-leaning object. In other words, RA_LINE_ORDERING_RULES functions as the central business entity around which dependent detail tables are attached, rather than as a link or satellite. Practitioners modeling AutoInvoice configuration in a warehouse context may reasonably treat it as a hub keyed by ORDERING_RULE_ID.

Key Information Stored

The table is defined by a small set of descriptive columns plus a standard Oracle WHO-audit and descriptive-flexfield footprint. The most significant columns are:

• ORDERING_RULE_ID — the surrogate primary key, enforced by RA_LINE_ORDERING_RULES_PK. This is the value referenced by dependent tables.
• NAME — the user-visible ordering rule name. It is a business-key candidate, enforced by unique index RA_LINE_ORDERING_RULES_U2 (NAME, ZD_EDITION_NAME).
• DESCRIPTION — free-text explanation of the rule's purpose.
• START_DATE and END_DATE — the effective date range during which the rule is active, supporting date-effective configuration.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) columns, allowing site-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard audit (WHO) columns recording who created and last modified each rule.
• ZD_EDITION_NAME — the editioning column used with the unique indexes U1 and U2 to support Oracle's edition-based redefinition (EBR) in 12.2.x.

The unique index RA_LINE_ORDERING_RULES_U1 (ORDERING_RULE_ID, ZD_EDITION_NAME) reinforces the surrogate key within the editioning framework, while U2 confirms NAME as the logical business key. No ordering direction or sequence-number columns are documented in this table; the actual ordering behavior is held in the dependent RA_LINE_ORDER_BYS table.

Common Use Cases and Queries

Typical use cases include diagnosing AutoInvoice line sequence problems, auditing configuration, and migrating setups between environments. A common query lists active rules for a given effective date:

• SELECT ordering_rule_id, name, start_date, end_date FROM ra_line_ordering_rules WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));
• Joining to the detail table to expose the ordered columns: SELECT lr.name, lob.column_name FROM ra_line_ordering_rules lr, ra_line_order_bys lob WHERE lr.ordering_rule_id = lob.ordering_rule_id ORDER BY lr.name.
• Identifying which grouping rules reference an ordering rule: SELECT gr.grouping_rule_id, gr.name FROM ra_grouping_rules gr WHERE gr.ordering_rule_id = :rule_id.

These patterns are useful when investigating why transaction lines imported through AutoInvoice appear in an unexpected order, or when validating that a seeded rule such as the default line-ordering configuration has not been altered.

Related Objects

The following objects are the most significant dependencies, based on documented foreign key and key relationships:

• RA_GROUPING_RULES — references this table via RA_GROUPING_RULES.ORDERING_RULE_ID, linking a grouping rule to its line ordering rule.
• RA_LINE_ORDER_BYS — references this table via RA_LINE_ORDER_BYS.ORDERING_RULE_ID, storing the individual columns and their order sequence that constitute the rule.
• RA_INTERFACE_LINES_ALL and the AutoInvoice interface tables — consume ordering behavior indirectly during import.
• AutoInvoice setup forms and the Receivables system options — the application UI and configuration layer through which ordering rules are maintained.

Together these objects form the AutoInvoice sorting configuration chain: the ordering rule heads the definition, RA_LINE_ORDER_BYS provides the sort detail, and RA_GROUPING_RULES binds the ordering rule into the broader grouping and transaction-building logic.