Results for “date_last_updated”

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

Overview

IGS_DA_PRSMD is a table within the Oracle E-Business Suite IGS – Student System product family. In the ETRM 12.1.1 and 12.2.2 documentation sets, the module is flagged as Obsolete, and the table itself is explicitly recorded as Not implemented in this database. Its documented purpose is the storage of information on requests made for Person modifications, specifically to assist third-party consumers during OSS (Oracle Student System) update processing. In practical terms, IGS_DA_PRSMD functioned as a staging or request-tracking structure: rows represented pending or historical change requests against person records, captured in a denormalized form so that external or downstream processes could apply the changes without directly touching the core person tables.

The ETRM metadata records a heuristic Data Vault classification of standalone, meaning no foreign-key relationships were mined from the physical structure. Under Data Vault modeling conventions, this suggests treating the table as a self-contained artifact rather than a hub, link, or satellite participating in a broader integration bus. Where a modeling exercise requires it, the surrogate request identifier can be treated as a degenerate hub key, but the documented evidence does not support dependencies on other key structures.

Key Information Stored

The documented physical schema for release 12.1.1 defines the owner IGS and 26 columns. The primary key, IGS_DA_PRSMD_PK, is defined on PERS_MOD_REQ_ID, the surrogate request identifier. A unique index, IGS_DA_PRSMD_U1, is also documented on PERS_MOD_REQ_ID, confirming it as the sole business-key candidate; no alternate unique business key exists.

The most significant columns fall into three groups:

• Identity and targeting: PERS_MOD_REQ_ID (surrogate PK), PERSON_ID (the person record being modified), ALT_PERSON_ID_TYPE, and PERSON_TYPE.
• Person attributes carried on the request: SURNAME, GIVENNAME, MIDDLE_NAME, NAME_SUFFIX, DATE_OF_BIRTH, EMAIL_ADDR, and PERSON_CREATE_DATE.
• Address attributes carried on the request: MAILING_ADDRESS1 through MAILING_ADDRESS4, CITY, STATE, PROVINCE, COUNTRY, and POSTAL_CODE.

Standard EBS audit and concurrency columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and DATE_LAST_UPDATED — complete the structure and support traceability of request processing.

Common Use Cases and Queries

Because the table is documented as unimplemented, queries are primarily relevant to historical migrations, legacy integrations, and audits of the obsolete Student System. A typical diagnostic retrieves all modification requests for a given person, ordered by creation sequence:

• SELECT PERS_MOD_REQ_ID, PERSON_ID, PERSON_TYPE, SURNAME, GIVENNAME, EMAIL_ADDR, CREATION_DATE FROM IGS_DA_PRSMD WHERE PERSON_ID = :p_person_id ORDER BY CREATION_DATE;
• Reconciliation of request volume per person type: SELECT PERSON_TYPE, COUNT(*) FROM IGS_DA_PRSMD GROUP BY PERSON_TYPE;
• Stale request detection: comparing CREATION_DATE with LAST_UPDATE_DATE to identify rows never advanced beyond initial submission.

Reporting use cases center on 3rd-party OSS update feeds, where the denormalized person and address columns allow the feed to be serialized without additional joins. In upgrade or decommissioning projects, extracts from this table are used to confirm that no outstanding change requests remain before the obsolete objects are dropped.

Related Objects

The documented relationship classification is standalone, and no foreign keys are recorded. Consequently, the significant related objects are inferred from the columns rather than from FK constraints:

• IGS_DA_PRSM — the person modification master, conceptually linked via PERS_MOD_REQ_ID.
• HZ_PARTIES and HZ_PERSON_PROFILES — the Trading Community Architecture person entities referenced by PERSON_ID.
• HZ_LOCATIONS — target of the address fragments (MAILING_ADDRESS1-4, CITY, STATE, PROVINCE, COUNTRY, POSTAL_CODE).
• IGS_DA_* processing tables in the same DA family, which consume staged requests during OSS update runs.
• FND_USER and FND_LOGINS — resolvable from CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for audit reporting.

Any integration or query built against IGS_DA_PRSMD should first verify object existence, as the ETRM 12.1.1 and 12.2.2 reference explicitly states it is not implemented in the database.