Results for “igf_ap_st_inst_appl”

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

Overview

IGF_AP_ST_INST_APPL is a secured, organization-enabled view in the Oracle E-Business Suite Financial Aid (IGF) product family. It presents applicant-level student data collected against configurable institutional application questions, exposing the institution application identifier, the base identifier, the question being answered, and the corresponding response value. In release 12.1.1 and 12.2.2 the object is deployed in the APPS schema with a status of VALID, and it is registered in ETRM as a VIEW.

The view exists primarily to enforce multi-org (organization) security at query time. Rather than exposing all rows held in the underlying table, it applies a WHERE clause that compares the row-level ORG_ID against the organization identifier derived from the session through USERENV('CLIENT_INFO'). Callers therefore see only the records belonging to their currently selected operating unit context, which is essential for reporting, concurrent programs, and integration extracts that must respect organizational boundaries.

Underlying Base Objects

The view is defined over a single documented base object, IGF_AP_ST_INST_APPL_ALL. The suffix "_ALL" on the base table indicates that it is the multi-org table holding data across all operating units, while the view name without the suffix is the org-secured presentation layer. The view text selects from IGF_AP_ST_INST_APPL_ALL, aliased SIA, and projects the ROWID as ROW_ID alongside the explicit columns.

Because the predicate is a correlated expression on ORG_ID, the view returns exactly the subset of base rows whose ORG_ID matches the organization resolved from CLIENT_INFO. Rows where ORG_ID is null are evaluated against the fallback value of -99 through the nested NVL and DECODE logic, so unsecured or global rows can be surfaced consistently. No other base objects are documented as contributing to this view definition.

Key Columns

• ROW_ID — the physical ROWID of the underlying base row, useful for direct row identification and update paths.
• INST_APP_ID — the institution application identifier, the primary linkage to the applicant's institutional application record.
• BASE_ID — the base identifier associated with the record, typically tying the answer to a base applicant or application entity.
• QUESTION_ID — the identifier of the configured application question whose response is stored.
• QUESTION_VALUE — the applicant's response to the associated question.
• ORG_ID — the operating unit that owns the row; this is the column evaluated by the view's security predicate.
• APPLICATION_CODE — the application/product code context for the record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS Who columns providing audit and concurrency information.

Common Use Cases and Queries

The view is typically used to retrieve an applicant's question-and-answer set within the caller's operating unit, to join responses back to the application header, or to feed downstream reporting and integration processes that must remain org-secure.

• Retrieve all answers for a given institutional application:
  SELECT inst_app_id, question_id, question_value FROM igf_ap_st_inst_appl WHERE inst_app_id = :p_inst_app_id;
• List answers for a specific question:
  SELECT inst_app_id, question_value FROM igf_ap_st_inst_appl WHERE question_id = :p_question_id;
• Audit recently changed responses:
  SELECT inst_app_id, question_id, last_updated_by, last_update_date FROM igf_ap_st_inst_appl WHERE last_update_date >= :p_since;
• Confirm the operative operating unit for a session before reporting:
  SELECT DISTINCT org_id FROM igf_ap_st_inst_appl;

Because organization security is applied inside the view, callers inherit the correct filter automatically and do not need to add an ORG_ID predicate, although doing so explicitly is harmless and can aid readability in custom reports.