Results for “standing_charge_id”

50+ results




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

Overview

The IGI_RPI_INVOICE_HISTORY_V view is a reporting object in the IGI – Public Sector Financials International product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It presents consolidated invoice history for a single standing charge, allowing users to retrieve every receivable transaction generated against a given standing charge identifier together with its billed amount and currency. The view exists primarily to support inquiry and reporting screens in the IGI/RPI (Recurring Payment Invoice) flow, where a standing charge definition drives periodic invoicing of a customer.

Because the view already joins the standing charge definition, the receivable transaction header, and the transaction lines, it removes the need for report authors to replicate the join logic. This makes it a natural source for both concurrent-program reports and ad hoc queries executed from the EBS responsibility. The view is owned by the APPS schema and is documented as VALID in the ETRM 12.2.2 metadata.

Underlying Base Objects

The view text is defined over three primary base objects with a correlated subquery against a fourth:

The critical join is a character-to-character match between TO_CHAR(SC.STANDING_CHARGE_ID) and the descriptive flexfield attribute TX.INTERFACE_HEADER_ATTRIBUTE1, filtered by the active RPI header context. This means invoice-to-standing-charge association depends on the DFF population made when the transaction was created via the RPI process.

Key Columns

Common Use Cases and Queries

Typical usage includes reviewing billing history for a standing charge, reconciling invoiced amounts against the standing charge setup, and troubleshooting missing or duplicated RPI invoices. A representative query filtering on the search term is:

SELECT standing_charge_id,
       invoice_number,
       invoice_date,
       amount,
       invoice_currency_code
FROM   apps.igi_rpi_invoice_history_v
WHERE  standing_charge_id = :p_standing_charge_id
ORDER  BY invoice_date DESC;

Because the join to RA_CUSTOMER_TRX relies on INTERFACE_HEADER_ATTRIBUTE1 and the RPI context code, any transaction whose DFF attribute does not store the standing charge identifier in the expected format will be excluded. Report authors should therefore treat the view as a filtered projection of RPI-driven invoices rather than a complete accounts-receivable history.