Search Results birth_cntry_resn_code




Overview
Explore in AI Chat

Overview

APPS.IGS_SV_EV_ADD_DPD_BLK_V is a valid Oracle E-Business Suite view owned by the APPS schema, registered in FND Design Data as IGS.IGS_SV_EV_ADD_DPD_BLK_V. It is classified as a Web view, meaning it was designed to simplify access from Oracle Self-Service Web Applications by presenting a flattened, denormalized projection of data that would otherwise require multi-table joins. The object is part of the Student Systems (IGS) product family, and its functional purpose is described as "Add dependent block for the Exchange Visitor."

In the context of Oracle EBS 12.1.1 and 12.2.2, the view supplies the row set backing the dependent-block region of the Self-Service Exchange Visitor registration flow. Each row represents one dependent of an exchange visitor within a batch request, carrying the personal, demographic and relationship attributes required to create or validate a dependent person record. The view therefore functions as an integration and reporting surface as much as a UI construct: external interfaces and concurrent programs can query it to extract exchange visitor dependent batches without needing to navigate the underlying IGS staging and person tables.

Underlying Base Objects

The ETRM documentation excerpt for this view does not enumerate any referenced base objects; the "Referenced base objects" field is recorded as none documented. The column set nonetheless indicates the view is defined over exchange visitor batch staging data and person/dependent records maintained by the IGS Student Systems schema and the Oracle HR/TCA person model. The BATCH_ID and PERSON_ID columns anchor the row to a batch request and to the sponsoring exchange visitor, while DEPDNT_ID and PERSON_ID_LONG carry the dependent's own person identifiers. The presence of columns such as PERSON_NUMBER and PERSON_ID_LONG, which mirror the standard person identifiers used throughout EBS, confirms that the view resolves dependent person records rather than storing them independently. Because the view is a Web view, it is expected to be a simple projection with minimal transformation logic, and it should be treated as read-only.

Key Columns

  • BATCH_ID (NUMBER 14) — Batch request identifier; groups all dependents belonging to a single submission.
  • PERSON_ID (NUMBER 15) — Person identifier of the exchange visitor within the request block.
  • DEPDNT_ID (NUMBER 15) — Person identifier of the dependent.
  • PERSON_ID_LONG (VARCHAR2 15) and PERSON_NUMBER (VARCHAR2 11) — Character representations of the dependent person identifier and the user-visible person number.
  • LAST_NAME, FIRST_NAME, MIDDLE_NAME, SUFFIX — Dependent name components.
  • BIRTH_DATE (VARCHAR2 10), GENDER, BIRTH_CITY (VARCHAR2 60) — Birth and demographic attributes.
  • BIRTH_CNTRY_CODE (VARCHAR2 30) — Birth country code of the dependent.
  • BIRTH_CNTRY_RESN_CODE (VARCHAR2 30) — The column the user searched for; it captures the birth country reason code associated with the dependent's recorded country of birth.
  • CITIZENSHIP_CNTRY_CODE and PERM_RESIDENCY_CODE — Citizenship and permanent residency country codes.
  • RELATIONSHIP — Relationship of the dependent to the exchange visitor.
  • REMARKS (VARCHAR2 500) — Free-text remarks recorded when the dependent was added.

Common Use Cases and Queries

Typical usage includes batch validation reporting, dependent demographic extracts for regulatory filings, and reconciliation of submitted dependents against the final person records. A batch-level extract would be written as follows:

SELECT BATCH_ID, PERSON_ID, LAST_NAME, FIRST_NAME, BIRTH_DATE, RELATIONSHIP, BIRTH_CNTRY_CODE, BIRTH_CNTRY_RESN_CODE FROM APPS.IGS_SV_EV_ADD_DPD_BLK_V WHERE BATCH_ID = :p_batch_id;

To isolate dependents whose birth country reason code has been populated, filter on BIRTH_CNTRY_RESN_CODE IS NOT NULL, optionally joining to the country code table on BIRTH_CNTRY_CODE for descriptive reporting. Because the view exposes no documented base objects, joins should be made through the exposed identifier columns (PERSON_ID, DEPDNT_ID, PERSON_NUMBER) rather than by predicting internal table names.