Results for “revised_price”

50+ results




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

Overview

The IGI_RPI_LINE_AUDIT_DETAILS_V view is an APPS-owned, valid database view delivered within the IGI – Public Sector Financials International product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in ETRM as the "View for the standing charges audit form based on IGI_RPI_LINE_AUDIT_DET view." Its principal role is to present a flat, presentation-ready result set for the standing charges audit form, denormalizing standing charge line audit records so that price revisions, effective dates, and run identifiers can be reviewed without joins by the calling form or report.

Because it is a view rather than a table, it stores no data of its own and imposes no additional storage or indexing overhead. It exists purely to expose a governed, named interface over the underlying audit detail data. This makes it suitable for reporting, form-block queries, and controlled integrations that need audit visibility into revised price information for standing charges without querying base tables directly.

Underlying Base Objects

Per the documented view text, IGI_RPI_LINE_AUDIT_DETAILS_V is a simple inner-join view defined over two synonyms:

The join predicate is A.STANDING_CHARGE_ID = C.STANDING_CHARGE_ID. The selection also projects A.ROWID as ROW_ID, which is a significant design choice: the audit form can use this pseudocolumn as a unique row handle even though the view is non-updatable in the conventional sense. Deletion or manipulation performed by the form against ROW_ID resolves to the physical row in IGI_RPI_LINE_AUDIT_DET.

Key Columns

  • ROW_ID — the ROWID of the audit detail row; used by the audit form as the unique identifier for the displayed record.
  • CHARGE_REFERENCE — the standing charge reference from IGI_RPI_STANDING_CHARGES, providing business context for the audit line.
  • ITEM_ID — the inventory or line item identifier to which the standing charge applies.
  • PRICE and EFFECTIVE_DATE — the original (pre-revision) price and the date from which it was effective.
  • REVISED_PRICE and REVISED_EFFECTIVE_DATE — the updated price and the effective date of the revision. This is the pair most commonly sought by users searching on revised_price.
  • PREVIOUS_PRICE and PREVIOUS_EFFECTIVE_DATE — the immediately preceding price and date, enabling before/after comparison across revision cycles.
  • RUN_ID — identifies the concurrent program or price revision run that produced the audit line.
  • LAST_UPDATE_DATE — standard audit timestamp for the detail row.

Common Use Cases and Queries

Typical usage centers on auditing standing charge price changes and reconciling revisions to the run that produced them.

  • Review all revisions for a given charge reference.
  • Compare previous, original, and revised prices side by side.
  • Trace audit lines back to a specific RUN_ID.
  • Feed downstream reporting that requires the standing charge reference without joining base tables.

The following query lists revised price activity for a single run:

SELECT charge_reference, item_id, price, effective_date, revised_price, revised_effective_date, previous_price FROM igi_rpi_line_audit_details_v WHERE run_id = :p_run_id ORDER BY charge_reference, item_id;

A comparison query highlights variance between original and revised prices:

SELECT charge_reference, item_id, price, revised_price, (revised_price - price) variance FROM igi_rpi_line_audit_details_v WHERE revised_price IS NOT NULL ORDER BY ABS(revised_price - price) DESC;

As with any view projecting ROWID, consumers should restrict queries with selective predicates on CHARGE_REFERENCE, ITEM_ID, or RUN_ID to avoid full scans of the audit detail and standing charge tables.