Search Results recommendation_summary




Overview

APPS.IGS_RE_THS_PNL_MBR_V is a reporting view within the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 environment, belonging to the Oracle Student System / Records and Enrollment module. The view exposes thesis panel member data held in the base table IGS_RE_THS_PNL_MBR, enriched with party identification information from the Trading Community Architecture (TCA) table HZ_PARTIES. It presents, for each thesis panel member, the person's party number, panel member type, confirmation and decline status flags and dates, anonymity indicator, thesis result code, payment date, and audit columns. The view plays a supporting role in reporting and integration flows where downstream consumers require a denormalised, ready-to-query representation of panel membership rather than the raw base table. Because it joins to HZ_PARTIES, the view provides the PARTY_NUMBER attribute, which is the standard external identifier used across Oracle Applications for a person or organisation party.

Underlying Base Objects

The view is defined over two documented source objects: IGS_RE_THS_PNL_MBR (aliased TPM) and HZ_PARTIES (aliased PE). The join is an inner join on the person identifier: TPM.PERSON_ID = PE.PARTY_ID, meaning only thesis panel member rows whose PERSON_ID resolves to an existing HZ_PARTIES record are returned. The view selects TPM.ROWID as ROW_ID, which preserves a pseudo-column handle back to the driving table row for update or identification purposes. ETRM documentation for this object lists no further referenced base objects beyond these two tables. No analytic functions, aggregations, or GROUP BY clauses are present; the view is a straightforward projection with one DECODE-based derivation per status flag.

Key Columns

Common Use Cases and Queries

The view is typically queried to report confirmed versus outstanding panel members, or to reconcile panel invitations and payment status. Filtering on the derived CONFIRMED_IND is the most frequent access pattern, since that column is the one most often searched by name.

List all confirmed members for a thesis panel:

SELECT party_number, panel_member_type, confirmed_dt
FROM apps.igs_re_ths_pnl_mbr_v
WHERE the_sequence_number = :p_thesis_seq
AND confirmed_ind = 'Y';

Identify members who have neither confirmed nor declined, i.e. outstanding invitations:

SELECT party_number, panel_member_type, recommendation_summary
FROM apps.igs_re_ths_pnl_mbr_v
WHERE confirmed_ind = 'N' AND declined_ind = 'N';

Report members awaiting payment:

SELECT party_number, the_sequence_number, paid_dt
FROM apps.igs_re_ths_pnl_mbr_v
WHERE paid_dt IS NULL
ORDER BY the_sequence_number;

Because CONFIRMED_IND and DECLINED_IND are derived at runtime by DECODE rather than stored, queries cannot use an index on those columns, and the SYSDATE comparison means the value is evaluated at execution time. Users should therefore treat these flags as computed statuses and reference the underlying CONFIRMED_DT and DECLINED_DT columns when precise date predicates are required.