Results for “igs_da_spcl_prgms”

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

Overview

IGS_DA_REQ_STDNTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined in the Student Systems (IGS) product family. It presents data extracted from the student admissions and registration staging area, exposing records from the IGS_DA_REQ_STDNTS table joined to HZ_PARTIES so that each row combines a batch request line with the corresponding party identity. The view therefore serves as a denormalized, human-readable projection of requested student records, enriching coded values with descriptive text drawn from program versions and lookup values. It is used principally for diagnostic, reconciliation, and interface reporting rather than for transactional processing, and it is a natural target for administrators investigating failed or incomplete inbound records. Because the view resolves lookup meanings at query time, it is particularly convenient for ad hoc reporting where code values would otherwise be opaque.

Underlying Base Objects

The view is defined over two documented sources: IGS_DA_REQ_STDNTS (aliased DARS) and HZ_PARTIES (aliased PE), joined on the condition DARS.PERSON_ID = PE.PARTY_ID. No other base tables are documented as direct FROM-clause objects; all remaining tables appear only inside scalar subqueries that are evaluated per row. These include IGS_PS_VER, referenced twice to resolve program titles, IGS_LOOKUP_VALUES for special program meanings, and the function IGS_GE_GEN_004.GET_UNIT_SET_TITLE for major unit set titles. The DARS.ROWID pseudo-column is selected, allowing the view to be used in certain update contexts, although its read-oriented purpose is evident from the descriptive decoding performed in the select list. The left-hand driving table is IGS_DA_REQ_STDNTS, with HZ_PARTIES supplying party number and party name.

Key Columns

• BATCH_ID, IGS_DA_REQ_STDNTS_ID — the batch and line identifiers for the staged request record.
• PERSON_ID, PARTY_NUMBER, PARTY_NAME — the person identifier and the resolved party identity from HZ_PARTIES.
• PROGRAM_CODE — the intended program, with PROGRAM_CODE_DESC derived from IGS_PS_VER.TITLE.
• WIF_PROGRAM_CODE / WIF_PROGRAM_CODE_DESC — the program code associated with the withdrawal (WIF) context and its title.
• SPECIAL_PROGRAM_CODE / SPECIAL_PROGRAM_CODE_DESC — a code validated against lookup type IGS_DA_SPCL_PRGMS, with its MEANING exposed as the description. This is the column the user's search term, igs_da_spcl_prgms, refers to.
• MAJOR_UNIT_SET_CD / MAJOR_UNIT_SET_CODE_DESC — the major unit set, with its title returned by the IGS_GE_GEN_004 function.
• PROGRAM_MAJOR_CODE, WIF_ID — the major within the program and the withdrawal identifier.
• REPORT_TEXT, ERROR_CODE — diagnostic output and error status for the line.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

The view is typically queried to audit staged student requests, to trace errors in a batch, or to report the special programs associated with a population of applicants. Because the special program description is resolved from IGS_LOOKUP_VALUES during query execution, it provides a direct way to enumerate members of the IGS_DA_SPCL_PRGMS lookup without a separate join.

Example: list error lines within a batch, showing party and program descriptions.

• SELECT batch_id, igs_da_req_stdnts_id, party_number, party_name, program_code, program_code_desc, error_code, report_text FROM apps.igs_da_req_stdnts_v WHERE batch_id = :p_batch AND error_code IS NOT NULL ORDER BY igs_da_req_stdnts_id;

Example: report staged students by special program, which is the scenario implied by the search term igs_da_spcl_prgms.

• SELECT special_program_code, special_program_code_desc, batch_id, party_number, party_name, program_code_desc FROM apps.igs_da_req_stdnts_v WHERE special_program_code IS NOT NULL ORDER BY special_program_code, batch_id;

Example: locate all staged requests for a known party.

• SELECT igs_da_req_stdnts_id, batch_id, wif_program_code_desc, major_unit_set_code_desc, creation_date FROM apps.igs_da_req_stdnts_v WHERE party_number = :p_party_number;

Subquery-based description lookups make the view heavier than a plain join, so filters on BATCH_ID, PERSON_ID, or SPECIAL_PROGRAM_CODE should be applied wherever possible to constrain the driving rows before the scalar subqueries execute.