Results for “charge_reference”

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

Overview

IGI_RPI_STANDING_CHARGES_ALL is a transaction table in the IGI (Public Sector Financials International) product family of Oracle E-Business Suite, documented as VALID in releases 12.1.1 and 12.2.2. The table records standing charges — recurring billing arrangements from which invoices are generated automatically. In public sector and utility-style implementations, a standing charge represents a periodic amount owed by a customer regardless of usage, such as a fixed service fee, rental charge, or maintenance retainer. Each row captures the full billing context for one such arrangement, including the customer, the receivables transaction type, the invoicing schedule, and the payment method.

The ETRM metadata classifies this object heuristically as hub-leaning within a Data Vault model. That classification reflects its role as a durable, business-keyed entity whose identity is defined by CHARGE_REFERENCE within an operating unit, and from which dependent transactional records (line details, update lines, and audit details) radiate outward.

Key Information Stored

The physical schema is documented with 42 columns. The surrogate primary key is STANDING_CHARGE_ID, enforced by the IGI_RPI_STANDING_CHARGE_PK constraint. The business-key candidate is the unique index IGI_RPI_STANDING_CHARGES_U1 on CHARGE_REFERENCE combined with ORG_ID, meaning a charge reference is unique only within an operating unit, not across the enterprise.

• CHARGE_REFERENCE — the user-facing identifier for the standing charge arrangement.
• STANDING_CHARGE_DATE — the date the arrangement was established.
• STATUS — controls whether the charge is active and eligible for invoice generation.
• BILL_TO_CUSTOMER_ID, BILL_TO_SITE_USE_ID, BILL_TO_CONTACT_ID — define the invoicing party and destination.
• CUST_TRX_TYPE_ID — links to the receivables transaction type used when invoices are created.
• RECEIPT_METHOD_ID and BANK_ACCOUNT_ID — govern how payment is expected or collected.
• ADVANCE_ARREARS_IND — indicates whether billing occurs in advance or in arrears.
• PERIOD_NAME, START_DATE, END_DATE, NEXT_DUE_DATE, PREVIOUS_DUE_DATE, REVIEW_DATE — the scheduling and lifecycle dates that drive recurring invoicing.
• CURRENCY_CODE, TERM_ID, DEFAULT_INVOICING_RULE — currency, payment terms, and the rule that governs invoice timing.
• SET_OF_BOOKS_ID, ORG_ID, LEGAL_ENTITY_ID — the accounting and organizational context.

Common Use Cases and Queries

The most common operational need is identifying active standing charges that are due or overdue for invoicing. A representative query is:

• SELECT standing_charge_id, charge_reference, next_due_date, bill_to_customer_id FROM igi_rpi_standing_charges_all WHERE status = :active_status AND next_due_date <= SYSDATE AND org_id = :org_id;

Other frequent patterns include retrieving all charges for a given customer or legal entity, reconciling scheduled amounts against generated invoices, reviewing arrangement details before renewal or termination, and extracting full column detail for audit purposes. Reporting use cases typically involve aging of pending standing charges, period-based billing volume, and exception analysis where NEXT_DUE_DATE lags the current period. Because NEXT_DUE_DATE, PREVIOUS_DUE_DATE, and PERIOD_NAME are maintained on each row, trend reporting on billing cycles is straightforward without joining to invoice tables.

Related Objects

IGI_RPI_STANDING_CHARGES_ALL participates in a well-defined dependency network. Downstream child tables reference it through STANDING_CHARGE_ID, while it references master data in the Receivables and Legal Entity schemas. The most significant related objects are:

• IGI_RPI_LINE_DETAILS_ALL — child table joined on STANDING_CHARGE_ID; holds the individual billing line details.
• IGI_RPI_UPDATE_LINES_ALL — child table joined on STANDING_CHARGE_ID; records updates applied to charges.
• IGI_RPI_LINE_AUDIT_DET_ALL — audit detail table referencing STANDING_CHARGE_ID.
• RA_CUST_TRX_TYPES_ALL — joined via CUST_TRX_TYPE_ID to resolve invoice transaction type.
• AR_RECEIPT_METHODS — joined via RECEIPT_METHOD_ID to resolve the payment method.
• FV_LEGAL_ENTITIES — joined via LEGAL_ENTITY_ID to establish the owning legal entity.