Search Results igs_fi_f_typ_ca_inst




Overview
Explore in AI Chat

Overview

The view IGS_FI_F_TYP_CA_INST belongs to the IGS — Student System product family within Oracle E-Business Suite, a module that Oracle has classified as obsolete in current 12.1.1 and 12.2.2 environments. Despite its obsolete designation, the object remains documented in the ETRM reference repository and describes configuration data that links fee types to calendar instances within the Student System fee engine.

Functionally, the view presents the intersection of a fee type definition with a specific calendar instance, carrying the retention and accounting attributes that govern how charges, receivables, and revenue are posted to General Ledger. Because the underlying entity is a multi-org (partitioned) object, the view is filtered through the ORG_ID value derived from the CLIENT_INFO session context, ensuring that only rows belonging to the currently selected operating unit are returned. The view is therefore best understood as a reporting and integration surface over the fee-type calendar-instance setup, rather than as a transactional ledger object.

Underlying Base Objects

The view is defined over a single base object, IGS_FI_F_TYP_CA_INST_ALL, which is a partitioned/multi-org table. No additional joins to reference tables or lookup views are present in the view text; all descriptive columns are drawn directly from the base table by projection. The multi-org filter is applied via a DECODE and SUBSTRB expression on USERENV('CLIENT_INFO'), compared against the row-level ORG_ID. When the client information is unset, the default sentinel value of -99 is substituted, which yields no rows for a normal session.

The ETRM metadata lists no other referenced base objects, and the object is flagged as Not implemented in this database in the supplied excerpt, which indicates that the view text is documented for reference but the object may not be present or usable in the corresponding environment.

Key Columns

Common Use Cases and Queries

Typical queries retrieve the GL code combination used for retention on a given fee type and calendar instance, or join the view to GL_CODE_COMBINATIONS to resolve the chart-of-accounts segments behind RET_GL_CCID. Because the view is org-striped, callers must initialise CLIENT_INFO before querying.

SELECT fee_type, fee_cal_type, fee_ci_sequence_number,
       ret_gl_ccid, ret_account_cd, rec_gl_ccid
  FROM igs_fi_f_typ_ca_inst
 WHERE fee_type = :p_fee_type;

SELECT g.segment1, g.segment2, g.segment3
  FROM igs_fi_f_typ_ca_inst v, gl_code_combinations g
 WHERE v.ret_gl_ccid = g.code_combination_id;

Because the object is obsolete and may not be implemented, integration code should treat its absence as an expected condition.