Results for “igi_rpi_update_lines_c_v”

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

Overview

The view APPS.IGI_RPI_UPDATE_LINES_C_V belongs to the IGI – Public Sector Financials International product family within Oracle E-Business Suite, and remains valid in both 12.1.1 and 12.2.2 releases. It is documented as a view used for line updates at the standing charge level, meaning it exposes the working set of price revision lines that a user or batch process is reviewing before committing revised pricing back to the underlying standing charge records. In practice, the view functions as a reporting and integration surface over the Retail Price Index (RPI) update process, allowing concurrent programs, Oracle Forms, and external interfaces to query candidate line updates without directly touching transactional base tables. Because the view applies a filter that excludes standing charge level rows, it presents only item-level update lines that participate in the RPI uplift workflow.

Underlying Base Objects

The view is defined over two documented base objects, exposed to the APPS schema through synonyms:

• IGI_RPI_UPDATE_LINES_ALL — the transactional table holding the individual update lines, aliased as A in the view definition. The _ALL suffix indicates it is partitioned by operating unit through the ORG_ID column, which the view carries forward.
• IGI_RPI_ITEMS_ALL — the item master reference table, aliased as B, supplying the item code used for display and lookup.

The join is an equi-join on ITEM_ID, combined with the predicate A.STANDING_CHARGE_ID IS NULL. This predicate is the defining characteristic of the view: it deliberately restricts the result set to lines that are not associated with a standing charge, so callers receive only the item-level update candidates. The view exposes ROW_ID via A.ROWID, which allows Forms-based and programmatic updates to address individual rows through the ROWID pseudocolumn rather than a primary key.

Key Columns

The view projects the following columns, each carrying specific meaning within the RPI update process:

• ROW_ID — the physical row identifier from the update lines table, used for row-level updates.
• RUN_ID — identifies the RPI update run that generated the line.
• ITEM_ID and ITEM_CODE — the item identifier and its human-readable code from the item master.
• PRICE, PREVIOUS_PRICE, UPDATED_PRICE, REVISED_PRICE — the price values captured at different stages of the revision cycle, allowing comparison between the original and proposed prices.
• PREVIOUS_EFFECTIVE_DATE, EFFECTIVE_DATE, REVISED_EFFECTIVE_DATE — the date the current price became effective, the initially proposed effective date, and the revised effective date applied by the user. The REVISED_EFFECTIVE_DATE column is the field most commonly searched for, as it records the user-adjusted date that supersedes the system-generated effective date.
• SELECT_FLAG — a selection indicator allowing users to include or exclude individual lines from processing.
• ORG_ID — the operating unit, enabling multi-org filtering.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centres on reviewing proposed RPI revisions before they are applied. A common query retrieves all item-level lines for a given run, including any revised effective dates:

• SELECT item_code, price, previous_price, effective_date, revised_effective_date, select_flag FROM igi_rpi_update_lines_c_v WHERE run_id = :run_id AND org_id = :org_id;
• To find lines whose revised effective date has been manually overridden: SELECT item_code, revised_effective_date, effective_date FROM igi_rpi_update_lines_c_v WHERE revised_effective_date <> effective_date AND run_id = :run_id ORDER BY revised_effective_date;
• To list only lines flagged for update: SELECT item_code, revised_price FROM igi_rpi_update_lines_c_v WHERE select_flag = 'Y' AND run_id = :run_id;

Because the view filters out standing charge rows, it is unsuitable for queries requiring standing charge context; those must target IGI_RPI_UPDATE_LINES_ALL directly.