Search Results agent_person_id




Overview
Explore in AI Chat

Overview

APPS.IGSBV_VISAS is a Business Intelligence System (BIS) view registered in the APPS schema and shipped under FND Design Data IGS.IGSBV_VISAS. It exposes visa and immigration information held against a person record within the Oracle E-Business Suite student and scholar management footprint. The view is documented as containing information about a person's visa details, and it is intended for reporting and integration consumption rather than for transactional maintenance of visa data. Responsibility for maintaining the underlying records rests with the Oracle iLearning / Student Systems visa functionality, while IGSBV_VISAS provides a denormalised, read-oriented projection suitable for Business Intelligence queries, extracts and third-party interfaces.

The view carries a STATUS of VALID in the documented releases and is available in both Oracle EBS 12.1.1 and 12.2.2. Because the design data is registered as IGS.IGSBV_VISAS, the object participates in the standard FND dictionary and is therefore subject to standard patching and dictionary synchronisation. The presence of the “_LA:” prefixed columns indicates that several descriptive values are returned through flexfield or lookup translation logic rather than from stored columns, so consumers should not assume a one-to-one mapping between the view's columns and physical columns of the base table.

Underlying Base Objects

The documented dependency list records that APPS.IGSBV_VISAS references APPS.HZ_PARTIES, IGS_PE_VISA and AP. The principal transactional source is IGS_PE_VISA, which stores the person's visa records including visa type, category, issue and expiry dates, issuing post and country, and agent identifiers. HZ_PARTIES is referenced to reconcile the person and agent identities through the TCA party model, supplying the PERSON_NUMBER, PERSON_ID and AGENT_PERSON_ID values that anchor the visa records to a specific individual and to the international agent who represents the organisation. The reference to AP indicates that the international agent's organisational context is derived from Oracle Payables supplier or organisation information, which is how AGENT_ORG_UNIT_CD is resolved.

The view type is documented as a Business Intelligence System view, which means it forms part of a published reporting layer rather than an internal implementation detail. It inherits the standard Oracle “WHO” audit columns from its base tables: CREATION_DATE, CREATED_BY, LAST_UPDATED_BY and LAST_UPDATE_DATE. No documented view metadata (for example a maintained column synonym list) was recorded for the 12.2.2 ETRM entry beyond the referenced base objects, so changes to the underlying IGS_PE_VISA definition should be reviewed before relying on this view across an upgrade.

Key Columns

The PERSON_NUMBER column provides the unique identification number for a person and is the natural business key most frequently requested by report authors. VISA_TYPE, VISA_CATEGORY and VISA_NUMBER together describe the visa held, while VISA_ISSUE_DATE and VISA_EXPIRY_DATE bound its validity period. The translated columns _LA:VISA_TYPE_DESCRIPTION, _LA:VISA_ISSUING_POST and _LA:VISA_ISSUING_COUNTRY provide the human-readable descriptions for the coded visa type, the issuing post and the issuing country respectively.

The agent-related columns are of particular interest to users searching on AGENT_CONTACT_NAME. AGENT_ORG_UNIT_CD indicates the external agency's organisation unit code that the international agent represents, AGENT_CONTACT_NAME holds the international agent's contact name, and AGENT_PERSON_ID holds the unique person identifier of the agent. The surrogate keys VISA_ID and PASSPORT_ID uniquely identify the visa and the associated passport, and PERSON_ID identifies the subject of the visa. Standard WHO columns support audit and incremental extraction patterns.

Common Use Cases and Queries

  • Reporting all visa holders represented by a given international agent, filtered on AGENT_ORG_UNIT_CD, for agent performance or commission reviews.
  • Producing visa expiry tracking reports for immigration compliance, using VISA_EXPIRY_DATE and PERSON_NUMBER.
  • Extracting agent contact details into third-party CRM or recruitment systems, sourcing AGENT_CONTACT_NAME and AGENT_PERSON_ID.
  • Joining the view to TCA party queries to reconcile person identities and contact information.
SELECT person_number,
       visa_type,
       _LA:VISA_TYPE_DESCRIPTION   AS visa_type_description,
       visa_number,
       visa_issue_date,
       visa_expiry_date,
       agent_org_unit_cd,
       agent_contact_name
FROM   apps.igsbv_visas
WHERE  agent_contact_name IS NOT NULL
AND    visa_expiry_date >= SYSDATE
ORDER  BY visa_expiry_date;

Because the object is a BIS view registered in APPS, it should be queried with the APPS schema or through a synonym granted to the reporting user, and it should be treated as read-only in all integration scenarios.