Search Results confirmed_dt

Overview

The view IGS_RE_THS_PNL_MR_HS is a Multi-Org secured (MOAC) reporting view owned by the APPS schema within the IGS — Student System product family in Oracle EBS 12.1.1 and 12.2.2. It exposes historical (dated) records of thesis panel members, capturing the confirmation, declining, payment and recommendation lifecycle associated with an individual serving on a thesis examination or review panel. The view presents a row-level history of panel member assignments, with effective dating columns (HIST_START_DT, HIST_END_DT) that allow consumers to reconstruct the state of a panel member record at any point in time.

Because it is a view rather than a table, it does not store data; it is a reporting and integration access point layered over the underlying _ALL table. The select list surfaces the ROWID (aliased ROW_ID), the operating unit (ORG_ID) and the full audit and business attribute set, making it suitable for BIPublisher reports, concurrent-program extracts, and inbound/outbound integration feeds that need a flattened, security-filtered projection of thesis panel member history.

Underlying Base Objects

Per the documented view text, the definition is a straightforward projection over a single base object:

• IGS_RE_THS_PNL_MR_HS_ALL — the physical, Multi-Org enabled table holding all rows for all operating units. The view joins to no child tables; the only predicate applied is the MOAC security filter.

The MOAC predicate is applied directly on ORG_ID:

WHERE NVL(TAB.ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))),-99)) = NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))),-99)

This standard EBS pattern reads the current operating unit from the CLIENT_INFO session context and restricts rows to that org (or to a sentinel of -99 when none is set). The corresponding non-secured view, IGS_RE_THS_PNL_MR_HS (the same name in the non-ALL namespace), would expose all orgs; consumers who need cross-org data must use a MOAC-aware access path or run with the appropriate security context.

Key Columns

• ROW_ID — the ROWID of the underlying base-table row; useful for direct row identification during DML or debugging.
• ORG_ID — operating unit; drives the MOAC filter and defines the security boundary.
• CA_PERSON_ID / CA_SEQUENCE_NUMBER — identifies the thesis/assessment entity and its sequence that the panel member is associated with.
• PERSON_ID — the person acting as panel member.
• THE_SEQUENCE_NUMBER — sequence within the thesis/panel context.
• PANEL_MEMBER_TYPE — the role the person plays on the panel (for example, supervisor, examiner, chair).
• CONFIRMED_DT — the date the panel member confirmed their participation. This is the column most relevant to the searched term confirmed_dt and is the timestamp used to measure response latency against invitation/creation dates.
• DECLINED_DT — the date the panel member declined; mutually informative with CONFIRMED_DT.
• PAID_DT — the date any associated honorarium or fee was paid to the panel member.
• ANONYMITY_IND — flag indicating whether the member's identity is withheld.
• THESIS_RESULT_CD — coded thesis outcome recorded for that member's assessment.
• RECOMMENDATION_SUMMARY — free-text summary of the member's recommendation.
• TRACKING_ID — integration/correlation identifier.
• HIST_START_DT / HIST_END_DT / HIST_WHO — history effective dating: when the row version became active, when it was superseded, and who made the change.
• CREATION_DT — the date the panel member record was created (distinct from the standard CREATION_DATE audit column).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

1. Confirmed panel members by operating unit within a date range. The confirmed_dt predicate the user searched for is the natural entry point for measuring confirmations.

SELECT ca_person_id, ca_sequence_number, person_id, panel_member_type, confirmed_dt
FROM apps.igs_re_ths_pnl_mr_hs
WHERE confirmed_dt BETWEEN :p_from AND :p_to;

2. Panel members who confirmed but have not yet been paid. This is a typical finance/administration reconciliation:

SELECT person_id, panel_member_type, confirmed_dt, paid_dt
FROM apps.igs_re_ths_pnl_mr_hs
WHERE paid_dt IS NULL
AND confirmed_dt IS NOT NULL;

3. Response history for a specific panel member. Using the history columns to track changes over time:

SELECT person_id, panel_member_type, hist_start_dt, hist_end_dt, hist_who, confirmed_dt, declined_dt
FROM apps.igs_re_ths_pnl_mr_hs
WHERE person_id = :p_person_id
ORDER BY hist_start_dt;

4. Integration extracts. TRACKING_ID and ROW_ID allow an external system to correlate and de-duplicate rows; the MOAC predicate guarantees the extract is scoped to the calling operating unit, so integrations that need cross-org data must explicitly run under an MOAC-capable context or union results across orgs.

Because the view performs no join and no aggregation, it is inexpensive and safe for high-volume reporting; however, since IGS_RE_THS_PNL_MR_HS_ALL is a history (_HS) table, consumers should filter on HIST_END_DT IS NULL when only the current version of a panel member record is required.