Search Results lead_instructor_flag
Overview
IGS_PS_USEC_TCH_RESP_V is a reporting view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It exposes teaching-responsibility assignments for unit sections — that is, the record of which instructors are attached to a given offering of a unit and in what capacity. The view joins the base teaching-responsibility table to the Trading Community Architecture parties table so that each assignment row is presented together with the instructor's formatted name and party number, eliminating the need for downstream consumers to perform the party lookup themselves.
Because it is a view rather than a table, IGS_PS_USEC_TCH_RESP_V carries no independent storage and reflects the current state of its base objects at query time. It is commonly used in institutional reporting, staff workload analysis, and integration extracts where a denormalised, human-readable instructor identity is required alongside the allocation attributes. The leading underscore-free naming and APPS ownership are typical of seed views shipped with the product, and the object is documented as VALID in ETRM for both 12.1.1 and 12.2.2.
Underlying Base Objects
The view is defined over two documented base objects:
- IGS_PS_USEC_TCH_RESP (aliased USTR) — the primary source table holding the unit section teaching-responsibility rows, including the surrogate key, allocation percentages, load figures, and audit columns.
- HZ_PARTIES (aliased PE) — the TCA party master, joined on
USTR.INSTRUCTOR_ID = PE.PARTY_IDto supply surname components and party number.
ETRM documentation lists no additional referenced base objects. The join is an inner equi-join on the party identifier, so any teaching-responsibility row whose instructor identifier does not resolve to a valid HZ_PARTIES record will be excluded from the result set. The view selects USTR.ROWID as ROW_ID, which exposes the physical row locator of the underlying teaching-responsibility record rather than a column value.
Key Columns
- ROW_ID — the ROWID of the base IGS_PS_USEC_TCH_RESP row; useful for locating the physical record.
- UNIT_SECTION_TEACH_RESP_ID — primary identifier of the teaching-responsibility assignment.
- UOO_ID — the unit offering option identifier linking the assignment to a specific teaching period and offering.
- INSTRUCTOR_ID — the party identifier of the assigned instructor.
- SURNAME — concatenation of last name, first name, and middle name from HZ_PARTIES, formatted as "LAST, FIRST MIDDLE".
- CONFIRMED_FLAG — indicates whether the teaching-responsibility assignment has been confirmed; this is the column most frequently used to filter the view to firm rather than provisional assignments.
- PERCENTAGE_ALLOCATION — the share of the teaching commitment assigned to the instructor.
- INSTRUCTIONAL_LOAD, INSTRUCTIONAL_LOAD_LAB, INSTRUCTIONAL_LOAD_LECTURE — total, laboratory, and lecture instructional load values.
- LEAD_INSTRUCTOR_FLAG — identifies the instructor who holds lead responsibility for the unit section.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
- PARTY_NUMBER, PERSON_NUMBER — the party number from HZ_PARTIES (PERSON_NUMBER is listed in the column registry).
Common Use Cases and Queries
Typical uses include confirming staffing of unit sections, reporting instructional load by instructor, and identifying lead instructors for a teaching period. Filtering on CONFIRMED_FLAG is central to most of these scenarios.
- List confirmed instructor assignments for a unit offering option:
SELECT u.unit_section_teach_resp_id, u.surname, u.percentage_allocation
FROM apps.igs_ps_usec_tch_resp_v u
WHERE u.confirmed_flag = 'Y' AND u.uoo_id = :uoo_id; - Totalled instructional load per confirmed instructor:
SELECT u.instructor_id, u.surname, SUM(u.instructional_load) load_total
FROM apps.igs_ps_usec_tch_resp_v u
WHERE u.confirmed_flag = 'Y'
GROUP BY u.instructor_id, u.surname; - Identify lead instructors:
SELECT u.surname, u.party_number
FROM apps.igs_ps_usec_tch_resp_v u
WHERE u.lead_instructor_flag = 'Y' AND u.confirmed_flag = 'Y';
When querying, always qualify the view with the APPS schema, expect only rows with a valid HZ_PARTIES match, and apply the confirmed_flag predicate where only firm assignments are relevant.
-
View: IGS_PS_USEC_TCH_RESP_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_PS_USEC_TCH_RESP_V, object_name:IGS_PS_USEC_TCH_RESP_V, status:VALID, product: IGS - Student System , implementation_dba_data: APPS.IGS_PS_USEC_TCH_RESP_V ,
-
View: IGS_PS_USEC_TCH_RESP_V
12.2.2
product: IGS - Student System (Obsolete) , implementation_dba_data: Not implemented in this database ,
-
VIEW: APPS.IGS_PS_USEC_TCH_RESP_V
12.1.1
-
VIEW: APPS.IGS_PS_USEC_TCH_RESP_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_PS_USEC_TCH_RESP_V, object_name:IGS_PS_USEC_TCH_RESP_V, status:VALID,
-
TABLE: IGS.IGS_PS_USEC_TCH_RESP
12.1.1
owner:IGS, object_type:TABLE, fnd_design_data:IGS.IGS_PS_USEC_TCH_RESP, object_name:IGS_PS_USEC_TCH_RESP, status:VALID,
-
APPS.IGS_AS_ATT_WF_PKG SQL Statements
12.1.1
-
APPS.IGS_PS_USEC_TCH_RESP_PKG SQL Statements
12.1.1
-
APPS.IGS_AS_CGR_WF_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.IGS_PS_USEC_TCH_RESP_PKG
12.1.1
-
PACKAGE BODY: APPS.IGS_AS_ATT_WF_PKG
12.1.1
-
TABLE: IGS.IGS_PS_LGCY_INS_INT
12.1.1
owner:IGS, object_type:TABLE, fnd_design_data:IGS.IGS_PS_LGCY_INS_INT, object_name:IGS_PS_LGCY_INS_INT, status:VALID,
-
APPS.IGS_PS_VALIDATE_LGCY_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.IGS_AS_CGR_WF_PKG
12.1.1
-
APPS.IGS_PS_CREATE_GENERIC_PKG SQL Statements
12.1.1
-
APPS.IGS_PS_GEN_001 SQL Statements
12.1.1
-
Lookup Type: LEGACY_TOKENS
12.2.2
product: IGS - Student System (Obsolete) , meaning: Legacy Message Tokens , description: Legacy Message Tokens ,
-
Lookup Type: LEGACY_TOKENS
12.1.1
product: IGS - Student System , meaning: Legacy Message Tokens , description: Legacy Message Tokens ,
-
APPS.IGS_PS_GENERIC_PUB dependencies on IGS_PS_USEC_TCH_RESP
12.1.1
-
PACKAGE: APPS.IGS_PS_GENERIC_PUB
12.1.1
-
APPS.IGS_PS_CREATE_GENERIC_PKG dependencies on IGS_PS_USEC_TCH_RESP
12.1.1
-
APPS.IGS_AS_ATT_WF_PKG dependencies on IGS_PS_USEC_TCH_RESP
12.1.1
-
APPS.IGS_AS_CGR_WF_PKG dependencies on FND_USER
12.1.1
-
APPS.IGS_PS_GEN_001 dependencies on IGS_PS_USEC_TCH_RESP
12.1.1
-
APPS.IGS_PS_CREATE_GENERIC_PKG dependencies on IGS_PS_USEC_TCH_RESP_PKG
12.1.1
-
APPS.IGS_PS_VALIDATE_LGCY_PKG dependencies on IGS_PS_USEC_TCH_RESP
12.1.1
-
APPS.IGS_AS_ATT_WF_PKG dependencies on IGS_PS_UNIT_OFR_OPT
12.1.1
-
APPS.IGS_PS_VALIDATE_LGCY_PKG dependencies on IGS_PS_USEC_TCH_RESP_PKG
12.1.1
-
APPS.IGS_AS_CGR_WF_PKG dependencies on IGS_PS_UNIT_OFR_OPT
12.1.1
-
APPS.IGS_AS_CGR_WF_PKG dependencies on IGS_PS_USEC_TCH_RESP
12.1.1
-
APPS.IGS_PS_USEC_SCHEDULE dependencies on IGS_PS_USEC_TCH_RESP
12.1.1
-
APPS.IGS_PS_USEC_TCH_RESP_PKG dependencies on APP_EXCEPTION
12.1.1
-
APPS.IGS_PS_USEC_SCHEDULE SQL Statements
12.1.1
-
PACKAGE BODY: APPS.IGS_PS_VALIDATE_LGCY_PKG
12.1.1
-
APPS.IGS_PS_USEC_TCH_RESP_PKG dependencies on IGS_GE_MSG_STACK
12.1.1
-
APPS.IGS_PS_USEC_TCH_RESP_PKG dependencies on IGS_PS_USEC_TCH_RESP
12.1.1
-
APPS.IGS_PS_USEC_TCH_RESP_PKG dependencies on FND_MESSAGE
12.1.1
-
APPS.IGS_PS_CREATE_GENERIC_PKG dependencies on IGS_PS_UNIT_OFR_OPT_ALL
12.1.1
-
APPS.IGS_PS_VALIDATE_LGCY_PKG dependencies on IGS_PS_UNIT_OFR_OPT_ALL
12.1.1
-
APPS.IGS_PS_VALIDATE_LGCY_PKG dependencies on IGS_PS_UNIT_OFR_OPT
12.1.1
-
PACKAGE BODY: APPS.IGS_PS_LGCY_CONC_PKG
12.1.1
-
PACKAGE BODY: APPS.IGS_PS_CREATE_GENERIC_PKG
12.1.1
-
PACKAGE BODY: APPS.IGS_PS_GEN_001
12.1.1
-
APPS.IGS_PS_CREATE_GENERIC_PKG dependencies on FND_MESSAGE
12.1.1
-
APPS.IGS_PS_VALIDATE_LGCY_PKG dependencies on FND_MESSAGE
12.1.1
-
APPS.IGS_PS_VALIDATE_LGCY_PKG dependencies on IGS_PS_VALIDATE_LGCY_PKG
12.1.1
-
PACKAGE BODY: APPS.IGS_PS_USEC_SCHEDULE
12.1.1
-
APPS.IGS_PS_CREATE_GENERIC_PKG dependencies on IGS_PS_GENERIC_PUB
12.1.1
-
APPS.IGS_PS_CREATE_GENERIC_PKG dependencies on IGS_PS_VALIDATE_LGCY_PKG
12.1.1
-
eTRM - IGS Tables and Views
12.1.1
description: Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'. ,