Search Results approval_notes

Overview

IGS_AD_APPL_PGMAPPRV_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered as part of the IGS (Student System) product family. Its documented purpose is to show the program approval status and associated details for a particular person. In practice, the view denormalizes the program-approval assignment records held against an admission application, resolving the raw approval status code to its descriptive lookup meaning and joining to the person base view to expose the approver's name and person number. This makes the view suitable for both operational enquiry screens and downstream reporting or integration extracts where program approvals must be presented in a human-readable form.

The object is documented as VALID in ETRM 12.2.2 and behaves identically in the 12.1.1 code line, as the underlying IGS table structures and this view definition were not materially changed between the two releases. It is a read-only presentation object: no DML should be issued against it.

Underlying Base Objects

The view text is defined over three sources:

• IGS_AD_APPL_PGMAPPRV — the driving table of program-approval assignments for an admission application. All ID, status, assign type, assign date, and audit columns are sourced from this table, aliased AP.
• IGS_LOOKUP_VALUES — aliased L, joined on AP.PROGRAM_APPROVAL_STATUS = L.LOOKUP_CODE restricted to L.LOOKUP_TYPE = 'PROGRAM_APPROVAL_STATUS', supplying the decoded MEANING column.
• IGS_PE_PERSON_BASE_V — aliased P, joined on AP.PGM_APPROVER_ID = P.PERSON_ID, supplying PERSON_NUMBER and FULL_NAME for the nominated approver.

The relationships are inner joins in all cases, so a row is returned only where a valid lookup meaning and a matching person record exist. Because the approver join uses PGM_APPROVER_ID and IGS_PE_PERSON_BASE_V, the person attributes exposed describe the approver, not the applicant.

Key Columns

• ROW_ID — the ROWID of the base IGS_AD_APPL_PGMAPPRV row; the unique handle for the approval record.
• APPL_PGMAPPRV_ID — primary key of the program-approval assignment.
• PERSON_ID, PERSON_NUMBER — applicant identifiers carried from the assignment record.
• ADMISSION_APPL_NUMBER, NOMINATED_COURSE_CD, SEQUENCE_NUMBER — the admission application reference and the course nominated within it.
• PGM_APPROVER_ID, FULL_NAME — the approver's person ID and resolved full name.
• ASSIGN_TYPE, ASSIGN_DATE — how and when the approval was assigned. ASSIGN_DATE is the timestamp most commonly filtered on when auditing approval workload or turnaround by approver.
• PROGRAM_APPROVAL_DATE, PROGRAM_APPROVAL_STATUS, MEANING — the date the approval decision was recorded, the status code, and its decoded description.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — linkage back to the program application and program definition.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, APPROVAL_NOTES).

Common Use Cases and Queries

Typical uses include approval workload reporting, applicant tracking, and integration extracts feeding external student systems. A frequent requirement is locating approvals assigned on or after a given date, which is exactly the assign_date search pattern.

SELECT person_id, person_number, admission_appl_number,
       full_name, assign_type, assign_date,
       program_approval_status, meaning
FROM   apps.igs_ad_appl_pgmapprv_v
WHERE  assign_date >= :p_from_date
ORDER  BY assign_date;

To review all approvals for one approver, filter on full_name or pgm_approver_id. Because the view is defined in APPS, it is normally queried from a reporting or read-only responsibility rather than exposed directly for data entry.