Results for “activity_type_description”

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

Overview

The view IGS_PS_USEC_ACT_TYPE_V belongs to the IGS – Student System product family within Oracle E-Business Suite, a module now classified as obsolete in the ETRM documentation. The view exposes descriptive and administrative attributes of activity type reference data used historically by the Student System for prospect and recruitment processing. Its defining role is to present a single, denormalised row per activity type, including the human-readable ACTIVITY_TYPE_DESCRIPTION, which is the attribute users most frequently search for when building reports or integration payloads keyed on activity_type_description.

Although the object is labelled "Not implemented in this database" in the captured ETRM metadata, the documented view text remains the authoritative definition and is reproduced here for reference purposes. In environments where the IGS schema is still present, the view behaves as a thin projection over its single base table, exposing no derived logic beyond a passthrough of stored columns plus the ROWID. This makes it suitable for read-only reporting, validation of reference data, and as a lookup source in interfaces that consume activity type codes and descriptions.

Underlying Base Objects

The view is defined entirely over one object:

• IGS_PS_USEC_ACT_TYPE (aliased USAT) – the activity type reference table holding the authoritative rows.

No other tables, joins, or subqueries are documented as referenced base objects. The view text is a straight SELECT from IGS_PS_USEC_ACT_TYPE USAT, projecting every significant column of the underlying entity. Consequently the view inherits the table's cardinality one-for-one: one view row corresponds to one row in IGS_PS_USEC_ACT_TYPE, with no aggregation, filtering, or DISTINCT applied. Because no joins or relational constraints are documented, the view presents the flat reference structure of the base table without resolving lookups to other Student System entities.

Key Columns

• ROW_ID – the base table's physical ROWID, carried forward via USAT.ROWID ROW_ID. Useful for direct row addressing in maintenance scripts.
• ACTIVITY_TYPE_ID – the surrogate primary key of the activity type.
• ACTIVITY_TYPE_CODE – the short business key, typically used in transactional records and interfaces.
• ACTIVITY_TYPE_DESCRIPTION – the descriptive text value most commonly retrieved; it is the column behind the frequent search term "activity_type_description".
• CLOSED_IND – a flag indicating whether the activity type is still active or has been end-dated for new use.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard Oracle EBS who-columns supporting audit and change tracking.

Common Use Cases and Queries

The view is typically queried to resolve an activity type ID or code into its description, or to enumerate valid activity types for a pick list. Because it is a simple projection, query performance mirrors that of the base table.

Listing all open activity types:

• SELECT activity_type_code, activity_type_description FROM igs_ps_usec_act_type_v WHERE closed_ind = 'N';

Resolving a description by code:

• SELECT activity_type_description FROM igs_ps_usec_act_type_v WHERE activity_type_code = :p_code;

Searching on the description text:

• SELECT activity_type_id, activity_type_code FROM igs_ps_usec_act_type_v WHERE UPPER(activity_type_description) LIKE UPPER('%'||:search||'%');

Auditing recent changes for integration reconciliation:

• SELECT activity_type_code, last_updated_by, last_update_date FROM igs_ps_usec_act_type_v WHERE last_update_date >= :since;

Where the object is not implemented, reports referencing it must be retired or redirected to its successor reference table; otherwise queries will fail at parse time with an object-not-found error.