Search Results name_suffix

Overview

IGS_DA_XML_PERSON_V is a read-only view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It is classified in the ETRM metadata as the XML element PersonType for the IGS data access (IGS_DA) integration layer, meaning it is a staging and transformation surface that feeds person-level XML payloads rather than an end-user transactional entity. Its status is VALID across 12.1.1 and 12.2.2, and the definition is identical in both releases because the view text is delivered with the IGS product fileset and does not depend on the multi-tenant Online Patching tables introduced in 12.2.

The view projects a denormalized person record: identifiers, name components (including the name suffix), address elements, and the batch context under which the person was selected for extraction. For users who search on "name_suffix," the relevant fact is that PERSON_NAME_SUFFIX is exposed directly from HZ_PARTIES, so XML consumers receive the raw suffix value with no decoding or lookup applied.

Underlying Base Objects

Although the ETRM extract lists no referenced base objects, the view text is explicit. It joins HZ_PARTIES, HZ_LOCATIONS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, IGS_PE_HZ_PTY_SITES, IGS_DA_SETUP, IGS_DA_RQST, IGS_DA_REQ_STDNTS and IGS_DA_REQ_FTRS, with scalar subqueries against IGS_PE_ALT_PERS_ID. The driving keys are DS.S_CONTROL_NUM = 1 for IGS_DA_SETUP, DRS.PERSON_ID = HP.PARTY_ID, DRS.BATCH_ID = DR.BATCH_ID, and the party-site chain HP.PARTY_ID → HPS.PARTY_ID, HPS.LOCATION_ID → HPL.LOCATION_ID, HPS.PARTY_SITE_ID → HPSU.PARTY_SITE_ID, and HZPTYS.PARTY_SITE_ID = HPS.PARTY_SITE_ID. Two predicates narrow the address: the SITE_USE_TYPE must equal the batch feature 'PAO' from IGS_DA_REQ_FTRS when present, otherwise DS.DEFAULT_ADDRESS_TYPE, and HPS.IDENTIFYING_ADDRESS_FLAG must resolve to 'Y'. A UNION ALL combines a first branch with a second branch that is truncated in the documentation; in practice the second branch repeats the same projection with different selection criteria, so callers should assume duplicate person rows are possible and use DISTINCT or an explicit batch filter.

Key Columns

• PERSON_ID_TYPE / API_PERSON_ID — derived from IGS_PE_ALT_PERS_ID for the identifier type held in DS.DEFAULT_STUDENT_ID_TYPE, defaulting to 'OSS' and the HZ party number when no active alternate identifier exists.
• PARTY_TYPE, PARTY_ID, PARTY_NUMBER — person classification and party keys from HZ_PARTIES.
• PERSON_PRE_NAME_ADJUNCT, PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_LAST_NAME, PERSON_NAME_SUFFIX — the name block emitted to the XML PersonType element. PERSON_NAME_SUFFIX carries values such as JR, SR, III, or a localized equivalent exactly as stored.
• SITE_USE_TYPE, ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTRY — the selected identifying address; note that STATE and PROVINCE are concatenated into one column.
• BATCH_ID — the IGS_DA_RQST batch that selected this person, used to scope extraction runs.

Common Use Cases and Queries

Typical usage is validating an outbound person extract for a specific batch, or confirming how a suffix will render before XML generation.

SELECT party_id, person_last_name, person_name_suffix, site_use_type
FROM   apps.igs_da_xml_person_v
WHERE  batch_id = :p_batch_id
AND    person_name_suffix IS NOT NULL
ORDER BY person_last_name;

To confirm which address was chosen for a person, select the batch, party, and site-use columns together, since the SITE_USE_TYPE predicate depends on IGS_DA_REQ_FTRS feature 'PAO' and falls back to the setup default. Analysts auditing extract completeness should join the result back to IGS_DA_REQ_STDNTS to detect expected students that produced no view row, which usually indicates a missing identifying-address flag or an expired IGS_PE_HZ_PTY_SITES date range.