Search Results roundoff_fact




Overview
Explore in AI Chat

Overview

APPS.IGF_AP_EFC_V is a supplementary view in the Oracle E-Business Suite Applications (APPS) schema, registered in FND Design Data as IGF.IGF_AP_EFC_V and reported with a status of VALID. The view supports the Oracle Student System / Financial Aid functionality delivered through the IGF module, specifically the effective financing cost (EFC) processing flow that maps awards generated by the awards generation engine to accounts payable batch processing. In this role the view simplifies forms coding by presenting a denormalised result set that combines EFC formula definitions, award-generation calendar context, and rounding behaviour into a single queryable structure. Oracle explicitly notes that this is a supplementary view used to simplify forms coding and warns that querying or altering data through it is not recommended, since its definition may change dramatically in subsequent minor or major releases. Consequently, the view should be treated as an internal implementation artefact of the IGF application rather than a stable public interface for downstream reporting or integration.

Underlying Base Objects

The documented dependency list identifies three base objects referenced by APPS.IGF_AP_EFC_V: IGS_CA_INST, IGF_AP_BATCH_AW_MAP, and IGF_AW_GEN. IGS_CA_INST supplies the calendar instance context, which is projected through the CI_ prefixes (CI_CAL_TYPE, CI_SEQUENCE_NUMBER, CI_ALTERNATE_CODE, CI_START_DT, CI_END_DT). IGF_AP_BATCH_AW_MAP provides the award-to-batch mapping used when awards are passed into Oracle Payables, and IGF_AW_GEN is the awards generation entity from which the formula and rounding attributes are drawn. The ETRM 12.2.2 metadata records no additional documented base objects beyond these, and the view carries no documented owner-level extensions. The view is itself referenced by several dependent components, including IGF_AP_EFC_CALC, IGF_AP_EFC_MULT_FCT_V, IGF_AW_COA_GEN, and IGF_AW_GEN_004, indicating that it participates in EFC calculation, multiple-factor derivation, and chart-of-accounts generation for awards.

Key Columns

The column list exposes both calendar and formula dimensions. ROW_ID is the ROWID pseudo-column, used for row identification in forms. The CI_* columns describe the award-generation calendar instance: CI_CAL_TYPE and CI_SEQUENCE_NUMBER identify the calendar and instance, CI_ALTERNATE_CODE provides a short user-facing reference, and CI_START_DT and CI_END_DT bound the instance in time. EFC_FRML and EFC_FRML_DESC hold the effective financing cost formula code and its description. NUM_DAYS_DIVISOR stores the divisor used when prorating amounts across the period. ROUNDOFF_FACT and ROUNDOFF_FACT_DESC are the rounding factor code and description — the columns most relevant to users searching on "roundoff_fact" — and govern how calculated EFC amounts are rounded before being passed to Payables. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also exposed. All descriptive fields are VARCHAR2, with descriptions sized at 4000 characters.

Common Use Cases and Queries

Typical use is diagnostic: confirming which rounding factor, divisor, and formula are associated with a given award-generation calendar instance before an EFC run, or reconciling amounts produced by IGF_AP_EFC_CALC and IGF_AW_COA_GEN. Because the view is unsupported for direct querying, any use should be read-only and version-aware. A representative query is:

  • SELECT ci_cal_type, ci_sequence_number, efc_frml, efc_frml_desc, num_days_divisor, roundoff_fact, roundoff_fact_desc FROM apps.igf_ap_efc_v WHERE ci_cal_type = :cal_type AND ci_sequence_number = :seq;
  • SELECT roundoff_fact, roundoff_fact_desc, COUNT(*) FROM apps.igf_ap_efc_v GROUP BY roundoff_fact, roundoff_fact_desc ORDER BY roundoff_fact;
  • SELECT v.ci_cal_type, v.ci_start_dt, v.ci_end_dt, v.efc_frml, v.roundoff_fact FROM apps.igf_ap_efc_v v WHERE v.ci_start_dt >= :start_date AND v.ci_end_dt <= :end_date;

These queries support validation and troubleshooting only; persistent logic should be built against the underlying base tables rather than this view.