Results for “igs_en_cat_prc_step”

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

Overview

The IGS_EN_CAT_PRC_STEP view is a secured, organization-aware reporting object within the Oracle E-Business Suite Student System (IGS) product family. Its purpose is to expose the category procedure step configuration that governs how an enrolment is processed. Specifically, the view incorporates the category procedure step derived from three controlling attributes: the enrolment category, the enrolment method type, and the student commencement type. In practical terms, it tells the Student System which procedural steps apply to a given enrolment scenario and in what sequence those steps must be executed.

Like many IGS views, IGS_EN_CAT_PRC_STEP is not a stored table but a query layer built over an underlying "_ALL" table. This design pattern is standard in Oracle EBS multi-org implementations: the physical data is held in a table carrying an ORG_ID discriminator, and the view applies a row-level security (RLS) predicate so that each operating unit sees only the rows for which it is responsible. The view is owned by the APPS schema and is reported as VALID, meaning its definition compiles successfully against the base objects in the supported release. Because it carries an ORG_ID column and a security predicate, it behaves as an operating-unit-secured view rather than a global lookup.

The presence of Application Context and Client Info logic in the view text is significant. The predicate uses USERENV('CLIENT_INFO') to retrieve the current organization identifier at runtime. This is the classic multi-org access mechanism: the CLIENT_INFO string is parsed to obtain the ORG_ID, and the view filters accordingly, defaulting to -99 when no organization is set. Consultants and developers writing custom reports against this view therefore inherit the same security behavior that standard IGS forms and concurrent programs observe.

Underlying Base Objects

The documented base object for this view is IGS_EN_CAT_PRC_STEP_ALL. No other referenced base objects are recorded in the ETRM metadata. The view selects directly from that single table and applies a WHERE clause that constrains ORG_ID to the organization currently established in the session.

Two operational implications follow. First, the view is a thin projection: it does not join additional tables, denormalize lookups, or aggregate data, so it should be expected to perform comparably to a direct query on the base table with an equivalent organization filter. Second, because the view reads from the "_ALL" variant, any change in the CLIENT_INFO context — for example, switching the active organization responsibility or setting the org via FND_GLOBAL — changes the rows returned without any change to the SQL text.

A subtlety worth noting is the MANDATORY_STEP_IND column. It appears in the column list but is commented out of the projection (rendered as TO_CHAR(NULL) in the view text). Consequently, querying MANDATORY_STEP_IND through the view returns a NULL value even though the corresponding column may exist in the underlying table. Reports requiring the mandatory-step indicator must read the base table directly or confirm whether the column is populated in the installed schema.

Key Columns

• ROW_ID — The ROWID of the underlying base-table row, exposed for row identification and locking purposes.
• ORG_ID — The operating unit identifier. Drives the multi-org security filter and indicates ownership of the configuration row.
• ENROLMENT_CAT — The enrolment category to which this procedure step applies; the primary business discriminator.
• S_STUDENT_COMM_TYPE — The student commencement type, further qualifying which procedure steps are relevant.
• ENR_METHOD_TYPE — The enrolment method type, completing the three-part key that determines the step configuration.
• S_ENROLMENT_STEP_TYPE — The enrolment step type code identifying the individual procedural step.
• STEP_ORDER_NUM — The sequence in which the step is executed relative to other steps.
• MANDATORY_STEP_IND — Documented but projected as NULL in this view definition; treat as unavailable through the view.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the configuration and when.

Common Use Cases and Queries

The principal use case is configuration validation and reporting: administrators and implementers need to confirm which steps apply to a combination of enrolment category, method type, and commencement type, and in what order. A second use case is integration support, where downstream processes must replicate the Student System's step sequence.

To list all configured steps for a category in the current organization:

SELECT enrolment_cat,
       s_student_comm_type,
       enr_method_type,
       s_enrolment_step_type,
       step_order_num
FROM   apps.igs_en_cat_prc_step
WHERE  enrolment_cat = :p_category
ORDER  BY s_student_comm_type, enr_method_type, step_order_num;

To audit recently changed configuration:

SELECT enrolment_cat,
       enr_method_type,
       s_enrolment_step_type,
       last_updated_by,
       last_update_date
FROM   apps.igs_en_cat_prc_step
WHERE  last_update_date >= TRUNC(SYSDATE) - 30
ORDER  BY last_update_date DESC;

Because the view enforces organization security, callers must ensure the correct organization context is set before executing these queries; otherwise the predicate resolves to the -99 default and returns no business rows. For cross-organization, administrative reporting, query IGS_EN_CAT_PRC_STEP_ALL directly under an appropriately privileged account, applying an explicit ORG_ID filter.