Results for “sup_unit_cd”

50+ results




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

Overview

IGS_AD_PS_APLINSTUNT is an Oracle E-Business Suite (EBS) view owned by the APPS schema within the IGS – Student System product family. It exposes person-level and unit-level admission application instance data, specifically the association between an applicant's admission application, the nominated course, and the individual units (subjects) for which the applicant is being considered. The "UNT" suffix in the object name denotes the unit dimension of the record, while "APLINST" reflects the admission application instance context.

In EBS 12.1.1 and 12.2.2, this view functions as a multi-org secured reporting and integration layer. It is commonly consumed by concurrent programs, Oracle Reports, OBIEE/BIP extracts, and custom PL/SQL packages that need to surface admission application unit data. Because it applies an ORG_ID filter based on the USERENV('CLIENT_INFO') session setting, the view honors the operating unit (ORG_ID) security model, returning only rows belonging to the organization that the current session is set to.

Underlying Base Objects

Per the documented view text, IGS_AD_PS_APLINSTUNT is defined over a single base object: IGS_AD_PS_APLINSTUNT_ALL, aliased as TAB. The "_ALL" base table is the multi-org variant that stores rows for every operating unit, including an ORG_ID discriminator column. The view does not introduce new columns; it projects all columns from the base table and appends the ROWID as ROW_ID for row identification purposes.

The WHERE clause applies the standard multi-org security predicate, comparing the base table's ORG_ID against the value derived from USERENV('CLIENT_INFO') (the first ten bytes of the client info string), with a fallback of -99 when the session client info is blank or space-padded. This means the "_ALL" table holds the physical rows, and the view presents only those visible to the currently initialized organization.

Key Columns

Common Use Cases and Queries

The view is typically queried to report on unit-level admission decisions, to audit rule waivers, and to feed downstream student records once an applicant accepts an offer. A common query to list waivers within the current operating unit is:

SELECT PERSON_ID,
       ADMISSION_APPL_NUMBER,
       UNIT_CD,
       RULE_WAIVED_DT,
       RULE_WAIVED_PERSON_ID
FROM   APPS.IGS_AD_PS_APLINSTUNT
WHERE  RULE_WAIVED_DT IS NOT NULL
ORDER  BY RULE_WAIVED_DT;

Reporting on decision outcomes by unit is equally common:

SELECT UNIT_CD,
       ADM_UNIT_OUTCOME_STATUS,
       COUNT(*) AS APPLICANT_COUNT
FROM   APPS.IGS_AD_PS_APLINSTUNT
WHERE  ADMISSION_APPL_NUMBER = :p_appl_number
GROUP  BY UNIT_CD, ADM_UNIT_OUTCOME_STATUS;

Because multi-org security is applied within the view itself, callers do not need to add an ORG_ID predicate, provided the session client info is correctly initialized via the standard FND_GLOBAL.APPS_INITIALIZE call. When writing back or reconciling data, the ROW_ID column can be used to target the underlying base table row directly. All source records reside in IGS_AD_PS_APLINSTUNT_ALL, so any direct DML must account for the ORG_ID of the target organization.