Results for “igs_fi_f_cat_cal_rel”

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

Overview

The IGS_FI_F_CAT_CAL_REL table resides in the IGS schema, owned by the Oracle iGS (Student System) product family, and is delivered as part of Oracle E-Business Suite releases 12.1.1 and 12.2.2. Within the ETRM data model, the table is documented with the description "No longer used," which indicates that it is a legacy or deprecated object retained for backward compatibility rather than an active component of the current fee calendar processing architecture. Despite this status, the object remains VALID in the data dictionary and continues to be physically present with sixteen documented columns.

The name suggests that the table historically stored relationships between fee categories and fee calendar instances — a cross-reference mapping that tied a student's fee category to a specific fee calendar type and calendar instance sequence. Under Data Vault modeling heuristics derived from its foreign key structure, the object classifies as a standalone table. A standalone classification implies that, in a modern Data Vault design, this object would most naturally be modeled as an independent structure — effectively a hub or a self-contained satellite — rather than as a link bridging two strong hubs. This classification is a modeling suggestion only, and is inferred from the absence of documented foreign key relationships to other tables in the mined metadata.

Key Information Stored

Of the sixteen documented columns, the following carry the most analytical and operational significance:

• FEE_CAT_CAL_REL_ID — The surrogate primary key, enforced by IGS_FI_F_CAT_CAL_REL_PK and mirrored by the unique index IGS_FI_F_CAT_CAL_REL_U1. This is the system-generated identifier for each relationship row.
• PERSON_ID — Identifies the student or person associated with the fee category to calendar relationship.
• COURSE_CD and VERSION_NUMBER — Identify the course and its version to which the fee calendar mapping applies.
• FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER — Identify the fee calendar type and the specific calendar instance sequence, defining the temporal scope of the mapping.
• FEE_CAT — The fee category code assigned to the person/course combination.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE — Concurrency and traceability columns populated by the concurrent program that inserted or updated the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — Standard Oracle EBS WHO audit columns.

The business-key candidate is documented through the unique index IGS_FI_F_CAT_CAL_REL_U2, encompassing PERSON_ID, COURSE_CD, VERSION_NUMBER, FEE_CAL_TYPE, and FEE_CI_SEQUENCE_NUMBER. This composite uniquely identifies a relationship independently of the surrogate key.

Common Use Cases and Queries

Because the table is documented as no longer used, most current reporting scenarios involving fee categories and calendar instances reference successor fee calendar objects. Nevertheless, during upgrade validation from 12.1.1 to 12.2.2, or when auditing historical data, the following patterns remain relevant:

• Reconciling orphaned rows where FEE_CAT_CAL_REL_ID exists without a corresponding active calendar instance.
• Auditing WHO columns to determine the last concurrent program that touched a row, using REQUEST_ID joined to FND_CONCURRENT_REQUESTS.
• Verifying uniqueness of the business key, for example: SELECT PERSON_ID, COURSE_CD, VERSION_NUMBER, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, COUNT(*) FROM IGS.IGS_FI_F_CAT_CAL_REL GROUP BY ... HAVING COUNT(*) > 1;
• Historical extracts for students by FEE_CAT within a given FEE_CAL_TYPE for archival or migration reporting.

Related Objects

The mined FK metadata classifies the object as standalone, meaning no formal foreign keys to other tables are documented. Conceptually, the following objects are the most likely reference points when working with this table, joined on the columns indicated:

• HZ_PERSON / PER_ALL_PEOPLE_F — joined on PERSON_ID for student identification.
• IGS_FI_FEE_CAL / IGS_FI_FEE_CAL_TYPE — joined on FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER for calendar instance context.
• IGS_FI_FEE_CAT — joined on FEE_CAT for category definitions.
• IGS_PS_STUDENT / IGS_EN_STUDENT — student context joined through PERSON_ID.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID for concurrent program traceability.
• IGS_FI_F_CAT_CAL_REL_PK / _U2 — the constraints enforcing uniqueness on the surrogate and business keys.