Search Results accounting_rule_name




Overview
Explore in AI Chat

Overview

IGI_RPI_LINE_DETAILS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the IGI product family — Public Sector Financials International — which extends standard Oracle Receivables and Payables functionality for government and public sector deployments. The view exposes standing charge line detail data used by the standing charges line details form, and is defined directly on top of the IGI_RPI_LINE_DETAILS storage object.

Standing charges represent recurring billing or revenue arrangements that a public sector organization applies to a customer, contract, or project over a defined duration. Because these arrangements must be billed periodically and posted to the correct accounting flexfield combinations, the view surfaces both the pricing attributes of each line and the two distribution code combinations associated with it. Its principal role in EBS reporting and integration is to provide a form-facing, denormalized projection that joins line-level pricing data to the Receivables accounting rule name, so that users and downstream reports can interpret how a standing charge is recognized and posted without querying the underlying tables separately.

Underlying Base Objects

The view is defined over two referenced base objects, both resolved through synonyms in the APPS schema:

  • IGI_RPI_LINE_DETAILS (SYNONYM) — the primary source, aliased as JURLD in the view text. It supplies every column except the accounting rule name.
  • RA_RULES (SYNONYM) — the Oracle Receivables accounting rules table, aliased as RR. It is joined with an outer join condition JURLD.ACCOUNTING_RULE_ID = RR.RULE_ID(+), so a standing charge line is returned even when no accounting rule is attached.

The outer join is significant: ACCOUNTING_RULE_ID is effectively optional, and ACCOUNTING_RULE_NAME will be null for lines whose accounting rule has not been assigned or whose rule identifier does not resolve in RA_RULES. The view performs no aggregation and no filtering; the row count and granularity match the qualifying rows in IGI_RPI_LINE_DETAILS one for one.

Key Columns

The view exposes twenty-seven columns. The following are the most operationally significant:

Common Use Cases and Queries

Typical uses include reconciling standing charge distributions to the general ledger, validating that a receivable code combination has been populated before billing, and driving form or report queries on accounting rule assignment. Because the view is not secured by an operating unit profile option at the view level, row-level access control is inherited from the underlying table and applied through the form or report layer.

To locate lines carrying a receivable code combination:

  • SELECT standing_charge_id, line_item_id, charge_item_number, receivable_code_combination_id, revenue_code_combination_id, price, period_name FROM apps.igi_rpi_line_details_v WHERE receivable_code_combination_id IS NOT NULL;

To identify lines missing an accounting rule name:

  • SELECT line_item_id, charge_item_number, accounting_rule_id, accounting_rule_name FROM apps.igi_rpi_line_details_v WHERE accounting_rule_name IS NULL;

To join back to the code combination table for accounting flexfield display, join RECEIVABLE_CODE_COMBINATION_ID to GL_CODE_COMBINATIONS.CODE_COMBINATION_ID in a separate query, since that table is not referenced by this view. Reporting queries should filter on STANDING_CHARGE_ID or PERIOD_NAME to constrain result sets, as the view itself applies no predicates.