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:
- IGI_RPI_STANDING_CHARGES (documented synonym IGI_RPI_STANDING_CHARGES_ALL) — the driving table, aliased
SC, supplying theSTANDING_CHARGE_ID. - RA_CUSTOMER_TRX — the receivable transaction header, aliased
TX, providing invoice number, date, comments, currency, and audit columns. - RA_CUSTOMER_TRX_LINES (documented synonym RA_CUSTOMER_TRX_LINES_ALL) — the transaction lines, aliased
TL, whoseEXTENDED_AMOUNTis aggregated to produceAMOUNT. - IGI_AR_SYSTEM_OPTIONS_ALL — referenced in a scalar subquery that retrieves
RPI_HEADER_CONTEXT_CODE.
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
- STANDING_CHARGE_ID — identifier of the standing charge; the search key most users begin with.
- INVOICE_NUMBER — the transaction number from RA_CUSTOMER_TRX.
- INVOICE_DATE — transaction date of the generated invoice.
- AMOUNT — sum of
EXTENDED_AMOUNTacross the transaction lines, grouped per invoice. - INVOICE_CURRENCY_CODE — currency of the referenced transaction.
- COMMENTS and the audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — inherited from the transaction header for traceability.
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.
-
Contains invoice history informaion for a single standing charge
APPS.IGI_RPI_INVOICE_HISTORY_V·↳ IGI_AR_SYSTEM_OPTIONS_ALL·↳ IGI_RPI_STANDING_CHARGES_ALL·↳ RA_CUSTOMER_TRX·Explore IGI module →
-
Contains invoice history informaion for a single standing charge
APPS.IGI_RPI_INVOICE_HISTORY_V·↳ IGI_AR_SYSTEM_OPTIONS_ALL·↳ IGI_RPI_STANDING_CHARGES_ALL·↳ RA_CUSTOMER_TRX·Explore IGI module →
-
Records standing charge line price updates, each of which represents a price update to a specific standing charge line charge item
-
Records global update line information for charge items and standing charge line charge items
-
Records global update line information for charge items and standing charge line charge items
-
Records standing charge line price updates, each of which represents a price update to a specific standing charge line charge item
-
View used for line updates at detailed level
APPS.IGI_RPI_UPDATE_LINES_D_V·↳ IGI_RPI_STANDING_CHARGES_ALL·↳ IGI_RPI_UPDATE_LINES·Explore IGI module →
-
View used for line updates at detailed level
APPS.IGI_RPI_UPDATE_LINES_D_V·↳ IGI_RPI_STANDING_CHARGES_ALL·↳ IGI_RPI_UPDATE_LINES·Explore IGI module →
-
Records standing charge lines, each of which represents a charge for a specific item
-
Records standing charge lines, each of which represents a charge for a specific item
-
View: IGI_RPI_LINE_DETAILS_V 12.2.2
View for the standing charges line details form based on IGI_RPI_LINE_DETAILS view
APPS.IGI_RPI_LINE_DETAILS_V·↳ IGI_RPI_LINE_DETAILS·↳ RA_RULES·Explore IGI module →
-
View: IGI_RPI_LINE_DETAILS_V 12.1.1
View for the standing charges line details form based on IGI_RPI_LINE_DETAILS view
APPS.IGI_RPI_LINE_DETAILS_V·↳ IGI_RPI_LINE_DETAILS·↳ RA_RULES·Explore IGI module →
-
Records Standing Charges from which invoices can be generated
-
Records Standing Charges from which invoices can be generated
-
View for the standing charges forms based on IGI_RPI_STANDING_CHARGES view
APPS.IGI_RPI_STANDING_CHARGES_V·↳ AR_RECEIPT_METHODS·↳ HR_OPERATING_UNITS·↳ HZ_CUST_ACCOUNTS_ALL·Explore IGI module →
-
View for the standing charges forms based on IGI_RPI_STANDING_CHARGES view
APPS.IGI_RPI_STANDING_CHARGES_V·↳ AR_RECEIPT_METHODS·↳ HR_OPERATING_UNITS·↳ HZ_CUST_ACCOUNTS_ALL·Explore IGI module →
-
APPS.IGIRRGPP SQL Statements 12.2.2
-
APPS.IGIRRGPP SQL Statements 12.1.1
-
APPS.IGIRRPS SQL Statements 12.1.1