Results for “fee_type_ci_status”

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

Overview

The IGS_FI_FEE_TYPE_CI_H view is a multi‑organization, date‑tracked reporting object within the Oracle E‑Business Suite Student System (IGS) product family. It exposes historical enrollment and configuration data for fee types as defined at the fee calendar instance level. In ETRM terminology, a "fee type CI" represents a fee calendar instance — a concrete, schedulable occurrence of a fee calendar type — and this view specifically surfaces the historical ("_H") versions of those instances so that changes to fee configuration over time remain queryable.

The view is created in the APPS schema and is marked VALID across the 12.1.1 and 12.2.2 releases. Its purpose is to provide a stable, secured read interface over the underlying history table, applying Oracle's standard multi‑org security predicate so that each operating unit sees only its own rows. Because it is a view rather than a base table, it is intended for reporting, integration extracts, and inquiry forms rather than for direct DML.

Underlying Base Objects

The view is defined as a single‑table SELECT over IGS_FI_FEE_TYPE_CI_H_ALL, the "all organizations" history table that stores dated versions of fee type calendar instance definitions. The view does not join additional tables; every column it exposes is a direct projection of a column on the base history table, with ROWID aliased to ROW_ID.

The critical behavioural difference between the view and its base table is the row‑level security clause. The view appends a predicate comparing the value of USERENV('CLIENT_INFO') — parsed from the first ten characters, with a leading space treated as NULL — against ORG_ID using NVL(..., -99) on both sides. This means callers see records for the operating unit set in their session context, plus rows whose ORG_ID is null or unset, which are effectively treated as globally visible. Because the view is read‑only in practice, updates to fee history must be performed against the base table by the application's own concurrent programs and forms.

Key Columns

• FEE_TYPE, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER — the composite identifier of the fee calendar instance whose history is being reported.
• HIST_START_DT, HIST_END_DT, HIST_WHO — the effective date range and responsible user for each historical version, forming the basis of point‑in‑time queries.
• FEE_TYPE_CI_STATUS — lifecycle status of the fee type instance at that version.
• START_DT_ALIAS / START_DAI_SEQUENCE_NUMBER, END_DT_ALIAS / END_DAI_SEQUENCE_NUMBER, RETRO_DT_ALIAS / RETRO_DAI_SEQUENCE_NUMBER — aliases and sequence numbers binding the instance to its start, end, and retroactive date definitions.
• S_CHG_METHOD_TYPE, RUL_SEQUENCE_NUMBER, SCOPE_RUL_SEQUENCE_NUM — the charge method and the pricing/scope rule that drive fee calculation.
• FIN_CAL_TYPE, FIN_CI_SEQUENCE_NUMBER — the financial calendar instance used for accounting and due‑date derivation.
• ACCOUNT_CD, PAYMENT_HIERARCHY_RANK, INITIAL_DEFAULT_AMOUNT — accounting distribution code, priority of payment, and the default charge amount.
• NONZERO_BILLABLE_CP_FLAG, ELM_RNG_ORDER_NAME, MAX_CHG_ELEMENTS — billing behaviour controls and charge element limits.
• ORG_ID — operating unit owning the row; drives the view's security predicate. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also exposed.

Common Use Cases and Queries

Typical uses include auditing configuration changes to a fee type over an academic period, populating data warehouse extracts, and driving inquiry reports that must show the fee setup as it stood on a given date.

To list the current and historical versions of a fee type:

• SELECT fee_type, fee_cal_type, fee_ci_sequence_number, hist_start_dt, hist_end_dt, fee_type_ci_status FROM igs_fi_fee_type_ci_h WHERE fee_type = :p_fee_type ORDER BY hist_start_dt;

To retrieve the version in force on a specific date:

• SELECT * FROM igs_fi_fee_type_ci_h WHERE TRUNC(:p_effective_date) BETWEEN hist_start_dt AND NVL(hist_end_dt, TO_DATE('31-DEC-4712','DD-MON-YYYY'));

To report billing configuration by operating unit:

• SELECT org_id, account_cd, payment_hierarchy_rank, initial_default_amount FROM igs_fi_fee_type_ci_h WHERE nonzero_billable_cp_flag = 'Y';

Because the view enforces the multi‑org predicate automatically, no additional ORG_ID filter is normally required, although explicit filtering is valid for extract programs that set client information themselves.