Search Results profile_category

Overview

IGS.IGS_AD_ACT_PROFILES is a transactional table within the Oracle E-Business Suite 12.1.1 and 12.2.2 IGS (Student Systems / Admissions and Recruitment) schema. It stores ACT assessment profile components, capturing the profile type alongside the corresponding category details returned by a candidate's ACT test results. The table is registered as a VALID FND Design Data object (IGS.IGS_AD_ACT_PROFILES) and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, aligning it with the standard configuration for transactional data in the EBS Applications tablespace model.

The physical shape of the table—a composite primary key of reportable identifiers plus a wide set of generic CODE1 through CODE21 attributes and personal-background fields such as EDUC_MAJOR and VOC_CHOICE1/2—places it in a descriptive, attribute-bearing role. The data vault classification sourced from the foreign key structure is satellite-leaning, meaning the table should be modeled as a satellite attached to an assessment hub or link (anchored through REPORTING_YEAR and ACT_IDENTIFIER), rather than as an independent hub or relationship table. This is a modeling suggestion; the operational profile remains a standard EBS transactional detail table.

Key Information Stored

The composite primary key, enforced by the unique index IGS_AD_ACT_PRFL_PK, spans six business-key columns: REPORTING_YEAR, ACT_IDENTIFIER, TEST_TYPE, TEST_DATE_TXT, PROFILE_TYPE, and PROFILE_CATEGORY. These same columns constitute the business-key candidate exposed by the unique index; there is no separate surrogate sequence key documented. Their meanings are:

• REPORTING_YEAR — the reporting or cycle year of the assessment data; also the FK column that ties the row to an assessment record.
• ACT_IDENTIFIER — the ACT identification number for the candidate or assessment.
• TEST_TYPE — the specific ACT test type for which the profile is recorded.
• TEST_DATE_TXT — the test date held as text.
• PROFILE_TYPE — the profile type component of the ACT profile.
• PROFILE_CATEGORY — the profile category associated with the type; this is the column most relevant to profile-category filtering and is a core element of the primary key.

The substantive payload of the row is carried by CODE1 through CODE21, a generic set of standard code slots whose meaning is context-dependent and resolved through EBS lookups for the given profile type and category. Supplementary descriptive values are held in EDUC_MAJOR (education major), VOC_CHOICE1 and VOC_CHOICE2 (vocational choices), and CHOICE1 through CHOICE5 (additional selections). The four standard Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) plus LAST_UPDATE_LOGIN provide the standard audit trail maintained by EBS.

Common Use Cases and Queries

Typical usage involves joining this table to its parent assessment record and pivoting the CODE columns for a reporting year or ACT identifier. A pattern for retrieving all profile categories for a candidate season:

• SELECT reporting_year, act_identifier, test_type, test_date_txt, profile_type, profile_category, code1, code2 FROM igs.igs_ad_act_profiles WHERE reporting_year = :p_year AND profile_category = :p_category;
• Joining to the assessment table via a.reporting_year = p.reporting_year AND a.act_identifier = p.act_identifier for assessment-level reporting.
• Aggregate reporting by PROFILE_TYPE and PROFILE_CATEGORY to quantify distribution of assessed profiles.
• Extracting EDUC_MAJOR, VOC_CHOICE1/2, and CHOICE1–5 for candidate interest and academic-intent analysis.

Because the generic CODE columns are not self-describing, effective reporting resolves them through the relevant profile-type/category lookups rather than treating them literally.

Related Objects

The documented foreign key relationship is:

• IGS.IGS_AD_ACT_ASSESSMENTS — referenced through REPORTING_YEAR, the parent assessment record for each ACT profile row.

The natural additional relationships are driven by the composite key rather than a single column: ACT_IDENTIFIER and TEST_TYPE/TEST_DATE_TXT pair with the assessment context, while PROFILE_TYPE and PROFILE_CATEGORY drive lookup resolution for the CODE1–CODE21, VOC_CHOICE1/2, and CHOICE1–5 values. Design-data and FND lookup surfaces (lookup types and lookup values) are the usual companions when decoding the generic code slots. In EBS terms, the object is best consumed alongside the assessment header, the value-set/lookup definitions for profile types and categories, and any institution-specific ACT interface or staging tables that load the profile components before they are committed to this table.