Search Results so_invoicing_rules_v

Overview

The view SO_INVOICING_RULES_V is an APPS-owned reporting and integration view within the Oracle E-Business Suite Order Entry (OE) product family. Its purpose is to expose a simplified, read-optimized projection of active invoicing rules defined in the Receivables module so that order management, order capture, and downstream integration components can reference invoicing rule identifiers and descriptive text without querying the underlying Receivables base table directly. The view is registered in the EBS 12.1.1 and 12.2.2 environments with a status of VALID, indicating that it compiles successfully against the referenced base object.

Because the object is a view rather than a table, it stores no data of its own. Instead, it derives its content at runtime from the Receivables rules table and restricts the result set to a specific subset of records. This design isolates callers from the physical column names and internal filtering logic of the Receivables schema while still providing stable, meaningful column aliases such as INVOICING_RULE, DESCRIPTION, and INVOICING_RULE_ID. For users searching on the term INVOICING_RULE_ID, this view is the primary OE-facing access path to the Receivables rule identifier used when attaching an invoicing rule to an order or transaction line.

Underlying Base Objects

The view is defined over a single documented base object: RA_RULES, referenced through a synonym in the APPS schema. The ETRM metadata records RA_RULES as the referenced base object and SO_INVOICING_RULES_V as a dependent view owned by APPS with a synonym relationship.

The defining SQL is a classic filtered projection:

SELECT NAME INVOICING_RULE, DESCRIPTION, RULE_ID INVOICING_RULE_ID FROM RA_RULES WHERE STATUS = 'A' AND TYPE = 'I'

Two predicates constrain the result. The STATUS = 'A' condition restricts the output to active rules only, filtering out any rules that have been end-dated or deactivated. The TYPE = 'I' condition restricts output to invoicing rules, excluding other rule classifications maintained in the same Receivables table, such as accounting rules. As a result, callers receive a clean list limited to currently active invoicing rules.

Key Columns

• INVOICING_RULE_ID — The alias for the base RA_RULES.RULE_ID column. This is the unique identifier for an invoicing rule and is the value most commonly joined or passed between OE and Receivables tables such as RA_RULES, order headers, and transaction records. It is the column most frequently searched when tracing how an invoicing rule is attached to a sales document.
• INVOICING_RULE — The alias for RA_RULES.NAME. This is the user-visible name of the invoicing rule and is used for display in concurrent program outputs, reports, and LOV-style queries.
• DESCRIPTION — A free-text description of the rule, taken directly from RA_RULES.DESCRIPTION. It provides user-maintained context explaining when the rule should be applied.

Only three columns are exposed, deliberately limiting the projection to the attributes relevant for identification and presentation. Additional Receivables rule attributes remain accessible only through the base table.

Common Use Cases and Queries

The primary use case is populating a values list or lookup for invoicing rule selection during order entry and order import, and resolving a stored INVOICING_RULE_ID back to its descriptive name for reporting. A typical query lists all active invoicing rules for a pick list:

SELECT INVOICING_RULE_ID, INVOICING_RULE, DESCRIPTION FROM APPS.SO_INVOICING_RULES_V ORDER BY INVOICING_RULE;

A second common pattern resolves a specific identifier, for example when validating a rule captured on an order or printed on a transaction report:

SELECT INVOICING_RULE, DESCRIPTION FROM APPS.SO_INVOICING_RULES_V WHERE INVOICING_RULE_ID = :p_rule_id;

Because the view already filters on active status and invoicing type, consumers do not need to repeat those predicates, though adding explicit conditions is harmless. The view may also be joined to order or transaction tables on INVOICING_RULE_ID to decorate transactional extracts with rule names. Query performance is driven entirely by RA_RULES; appropriate indexes on the rule identifier and status/type columns support efficient filtering. As with any APPS view, access should be granted through the standard APPS synonym and privileges rather than querying RA_RULES directly.