Search Results ret_gl_ccid
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
- ROW_ID — the
ROWIDof the underlying base row, exposed for direct row addressing. - FEE_TYPE, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER — identify the fee type and the calendar instance to which it applies.
- FEE_TYPE_CI_STATUS — status flag for the fee type/calendar-instance combination.
- START_DT_ALIAS, END_DT_ALIAS, RETRO_DT_ALIAS (and their
DAI_SEQUENCE_NUMBERcounterparts) — date alias references that drive effective, termination, and retroactive dating. - S_CHG_METHOD_TYPE, RUL_SEQUENCE_NUMBER — charge method classification and the sequence number of the associated rule.
- FIN_CAL_TYPE, FIN_CI_SEQUENCE_NUMBER — financial calendar context for the fee instance.
- ACCOUNT_CD, REC_ACCOUNT_CD, REV_ACCOUNT_CD, RET_ACCOUNT_CD — account code identifiers for the receivable, revenue, and retention postings.
- REC_GL_CCID, RET_GL_CCID — General Ledger code combination identifiers for the receivable and retention accounts. The
RET_GL_CCIDcolumn is the field most frequently referenced by users searching under the term ret_gl_ccid. - RETENTION_LEVEL_CODE, COMPLETE_RET_FLAG — retention level and completion indicators.
- ORG_ID — operating unit identifier used by the multi-org filter.
- Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent-program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).
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.
-
View: IGS_FI_F_TYP_CA_INST
12.2.2
product: IGS - Student System (Obsolete) , implementation_dba_data: Not implemented in this database ,
-
View: IGS_FI_F_TYP_CA_INST
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_FI_F_TYP_CA_INST, object_name:IGS_FI_F_TYP_CA_INST, status:VALID, product: IGS - Student System , implementation_dba_data: APPS.IGS_FI_F_TYP_CA_INST ,
-
VIEW: APPS.IGS_FI_F_TYP_CA_INST
12.1.1
-
View: IGS_FI_F_TYP_CA_INST_LKP_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_FI_F_TYP_CA_INST_LKP_V, object_name:IGS_FI_F_TYP_CA_INST_LKP_V, status:VALID, product: IGS - Student System , implementation_dba_data: APPS.IGS_FI_F_TYP_CA_INST_LKP_V ,
-
View: IGS_FI_F_TYP_CA_INST_LKP_V
12.2.2
product: IGS - Student System (Obsolete) , implementation_dba_data: Not implemented in this database ,
-
VIEW: APPS.IGS_FI_F_TYP_CA_INST
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_FI_F_TYP_CA_INST, object_name:IGS_FI_F_TYP_CA_INST, status:VALID,
-
VIEW: APPS.IGS_FI_F_TYP_CA_INST_LKP_V
12.1.1
-
VIEW: APPS.IGS_FI_F_TYP_CA_INST_LKP_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_FI_F_TYP_CA_INST_LKP_V, object_name:IGS_FI_F_TYP_CA_INST_LKP_V, status:VALID,
-
APPS.IGS_FI_PRC_ACCT_PKG SQL Statements
12.1.1
-
TABLE: IGS.IGS_FI_F_TYP_CA_INST_ALL
12.1.1
owner:IGS, object_type:TABLE, fnd_design_data:IGS.IGS_FI_F_TYP_CA_INST_ALL, object_name:IGS_FI_F_TYP_CA_INST_ALL, status:VALID,
-
APPS.IGS_FI_F_TYP_CA_INST_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.IGS_FI_F_TYP_CA_INST_PKG
12.1.1
-
APPS.IGS_FI_PRC_ACCT_PKG dependencies on IGS_FI_F_TYP_CA_INST
12.1.1
-
APPS.IGS_FI_PRC_FEE_ROLLV dependencies on IGS_FI_F_TYP_CA_INST_PKG
12.1.1
-
APPS.IGS_FI_F_TYP_CA_INST_PKG dependencies on IGS_FI_VAL_FTCI
12.1.1
-
APPS.IGS_FI_PRC_FEE_ROLLV SQL Statements
12.1.1
-
PACKAGE BODY: APPS.IGS_FI_PRC_ACCT_PKG
12.1.1
-
APPS.IGS_FI_PRC_FEE_ROLLV dependencies on IGS_FI_F_TYP_CA_INST
12.1.1
-
PACKAGE BODY: APPS.IGS_FI_PRC_FEE_ROLLV
12.1.1
-
eTRM - IGS Tables and Views
12.1.1
description: Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'. ,