Results for “deposit_levels”

7 results




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

Overview

IGS_AD_SS_APPL_TYP_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Student System (formerly Oracle Student Administration) product family, as indicated by the IGS prefix, and is registered in FND Design Data as IGS.IGS_AD_SS_APPL_TYP_V with a status of VALID. The view is classified in the ETRM documentation as a supplementary view used to simplify Oracle Forms coding, and Oracle explicitly warns that the view should not be queried or altered directly because its definition may change dramatically in subsequent minor or major releases.

Functionally, the view exposes configuration and control attributes for admission application types as they pertain to applicant self-service. It consolidates descriptive, financial, and instructional attributes into a single read-friendly structure so that Forms blocks, especially those driving the self-service admission application flow, can retrieve application type metadata without joining the underlying admission and accounts setup tables themselves. The presence of the USE_IN_APPL_SELF_SRVC column makes the view particularly relevant when determining which application types are surfaced to applicants through self-service channels.

Underlying Base Objects

The ETRM metadata for the 12.2.2 release does not document any referenced base objects for this view, and the object definition is described only through its exposed column list and query text. In practice, a supplementary Forms view of this nature is defined over the admission application type entity and its associated lookup and account derivation sources, projecting columns such as ADMISSION_APPLICATION_TYPE, DESCRIPTION, ADMISSION_CAT, and the account code identifiers GL_REV_ACCOUNT_CCID and GL_CASH_ACCOUNT_CCID. Because no base tables are formally documented, dependency analysis should be performed against the live data dictionary (for example, via ALL_DEPENDENCIES and ALL_VIEWS) before relying on any assumed join path.

Key Columns

Common Use Cases and Queries

Typical usage centers on configuration validation and self-service enablement checks. Because the view is an unsupported Forms support object, production queries should generally target the underlying admission application type table directly; however, the view remains useful for diagnostics and for confirming which types are published to applicants.

Example query listing self-service enabled application types:

SELECT admission_application_type, description, admission_cat, application_fee_amount, enroll_deposit_amount FROM apps.igs_ad_ss_appl_typ_v WHERE use_in_appl_self_srvc = 'Y' AND NVL(closed_ind,'N') = 'N';

A second common scenario audits account derivation, selecting admission_application_type, rev_account_code, cash_account_code, gl_rev_account_ccid, and gl_cash_account_ccid to verify that each self-service application type has valid revenue and cash account assignments. A third scenario retrieves instructional text (crt_rev_instr, submit_instr, submit_err_instr) to review or troubleshoot the guidance displayed to applicants. In all cases, treat the view as a convenience projection whose shape may change between releases.