Results for “igi_rpi_component_periods”

50+ results




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

Overview

The IGI.IGI_RPI_COMPONENT_PERIODS table belongs to the IGI – Public Sector Financials International product within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the periods associated with individual recurring payment or recurring invoice components maintained by the IGI schema. Each row represents the intersection of a component and an accounting period, providing the periodic values, schedule references, and enablement controls used when IGI-generated recurring transactions are processed and reported.

From a Data Vault modeling perspective, the metadata suggests this object is satellite-leaning. The composite primary key, IGI_RPI_COMPONENT_PERIODS_PK, defined over COMPONENT and PERIOD_NAME, behaves as a natural business key rather than a generated surrogate identifier. The table therefore functions as a detail or satellite structure that attaches descriptive and quantitative attributes—factor, unit of measure, schedule, enablement status—to the broader component definition held in its parent table.

Key Information Stored

The 13 documented columns capture the identifying, descriptive, and controlling attributes of each component-period record:

  • COMPONENT – Part of the primary key; a foreign key to IGI_RPI_COMPONENTS that identifies the parent recurring payment component.
  • PERIOD_NAME – Part of the primary key; the accounting period to which the row's values apply.
  • DESCRIPTION – Free-text description of the component-period record.
  • FACTOR – The numeric factor applied to the component for the specified period, commonly used in proration or periodic calculation logic.
  • USE_SCHEDULES_FLAG – Indicates whether schedule-based processing is used for this component-period.
  • UNIT_OF_MEASURE – The unit of measure associated with the periodic factor or amount.
  • SCHEDULE_ID – Reference to the schedule definition associated with the component-period.
  • ENABLED_FLAG – Controls whether the component-period is active for processing.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard Oracle EBS audit columns recording who created and last modified the row and when.

The primary key is composite and business-facing, combining COMPONENT and PERIOD_NAME; no separate generated surrogate key is documented. The COMPONENT column also serves as the sole documented foreign key column, linking each period row to its owning component.

Common Use Cases and Queries

The table is typically queried to retrieve the periodic values that drive recurring payment and recurring invoice calculations. A common reporting pattern joins the periods to their parent component and then resolves the associated schedule:

  • Retrieve all active periods for a given component: filter on COMPONENT and ENABLED_FLAG to return only current rows.
  • Period-based reporting: group by PERIOD_NAME to summarize FACTOR values across components for a given accounting period.
  • Schedule validation: select rows where USE_SCHEDULES_FLAG is enabled and inspect SCHEDULE_ID to confirm schedule linkage.
  • Audit and reconciliation: compare LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recently changed component-period values.

A representative SQL pattern takes the form:

SELECT p.COMPONENT, p.PERIOD_NAME, p.FACTOR, p.UNIT_OF_MEASURE, p.ENABLED_FLAG FROM IGI.IGI_RPI_COMPONENT_PERIODS p WHERE p.COMPONENT = :component AND p.ENABLED_FLAG = 'Y' ORDER BY p.PERIOD_NAME;

Related Objects

The most significant relationship is to the parent component table, joined on the COMPONENT column. Additional IGI objects that reference or depend on this table include schedule and recurring payment processing entities. The principal related objects are:

  • IGI_RPI_COMPONENTS – Parent table; joined via IGI_RPI_COMPONENT_PERIODS.COMPONENT = IGI_RPI_COMPONENTS.COMPONENT.
  • IGI_RPI_COMPONENT_PERIODS_PK – The primary key constraint enforcing uniqueness of COMPONENT and PERIOD_NAME.
  • IGI recurring payment and recurring invoice schedule definitions referenced by SCHEDULE_ID.
  • IGI product period and calendar objects consulted to validate PERIOD_NAME.
  • IGI concurrent programs and reports that generate periodic recurring transactions from component-period factors.

Together these objects form the processing chain through which IGI derives recurring payment amounts period by period.