Search Results igs_gr_crmn




Overview

IGS_GR_CRMN is a secure, operational view owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) product family. In the context of Oracle EBS 12.1.1 and 12.2.2, this view exposes information concerning graduation ceremony records maintained by the institution. It provides a filtered presentation of the graduation ceremony entity, presenting venue assignments, ceremony scheduling attributes, date alias references, fee information, and guest allowances associated with each graduation ceremony instance.

The view serves as the primary read interface through which graduation ceremony data is accessed for reporting, inquiry forms, and integration touchpoints. Because it is defined with a Multi-Org filter predicate, it implements the standard Oracle EBS operating unit (ORG_ID) security model, ensuring that a session only sees ceremony rows belonging to the operating unit context stored in the user's client information. This makes it suitable for both online form-based access and concurrent-program reporting within a multi-org enabled installation.

Underlying Base Objects

IGS_GR_CRMN is defined over a single base table, IGS_GR_CRMN_ALL. The "_ALL" suffix follows the Oracle EBS Multi-Org convention, indicating that the table stores rows across multiple operating units and that the corresponding non-suffixed view applies row-level security to restrict visibility. The view projects the base table's columns and appends a ROWID-derived ROW_ID column, which supplies a stable row identifier for the underlying physical record.

The security predicate compares the ORG_ID column of IGS_GR_CRMN_ALL against the value derived from USERENV('CLIENT_INFO'). The client information string is parsed using SUBSTRB to extract the operating unit identifier from the first ten bytes, with a leading space treated as NULL and a fallback sentinel value of -99 applied via NVL on both sides of the comparison. This pattern is characteristic of the standard Oracle EBS Multi-Org views and reflects the 11i/12.x client-info mechanism used prior to the full multi-org session context.

Key Columns

Common Use Cases and Queries

Typical uses include listing ceremonies for a graduation instance, retrieving venue and scheduling details, and reporting fees and guest allowances. A representative query follows:

  • SELECT ceremony_number, venue_cd, ceremony_dt_alias, ceremony_start_time, ceremony_end_time, ceremony_fee, number_of_guests FROM igs_gr_crmn WHERE grd_cal_type = :p_cal_type AND grd_ci_sequence_number = :p_ci_seq;
  • SELECT venue_cd, count(*) FROM igs_gr_crmn GROUP BY venue_cd; — venue utilisation reporting.

Because the ORG_ID predicate is applied automatically, queries executed through the view respect the caller's operating unit context without additional filtering, aligning the view with standard EBS multi-org reporting practice.