Results for “credit_points”

50+ results




Overview
Explore in AI Chat

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

Overview

The view APPS.IGS_SS_EN_RULE_CART_MAX_V is a reporting object within the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to return the sum of credit points for all units currently held in a student's enrollment cart. In the IGS self-service enrollment model, students place prospective unit attempts into a "cart" before final confirmation; rows in this state carry a unit attempt status of UNCONFIRM. This view therefore presents the aggregate credit-point position of unconfirmed enrollments, which is essential for enforcing enrollment rules such as maximum credit-point thresholds per teaching period.

From an integration and reporting standpoint, the view consolidates credit-point information from unit attempts, unit versions, unit offering options, and usec (unit set / course program) records, while simultaneously deriving the load calendar context from a teaching-to-load mapping view. The result is a single denormalized rowset keyed on person, course, unit offering option, and teaching calendar instance, which downstream rule engines and self-service pages consult to validate whether a proposed cart exceeds permissible limits.

Underlying Base Objects

The view text references five objects owned by the APPS schema. The primary driving table is IGS_EN_SU_ATTEMPT (aliased SUA), which stores the individual student unit attempt records in UNCONFIRM status. It is joined to IGS_PS_UNIT_VER (UV) on unit code and version number to obtain version-level enrolled credit points, and to IGS_PS_UNIT_OFR_OPT (UOO) on UOO_ID to resolve the unit offering option. A further join to IGS_PS_USEC_CPS (CPS) on UOO_ID retrieves usec-level credit points, and this join is outer (CPS.UOO_ID (+)). The fifth object, IGS_CA_TEACH_TO_LOAD_V (LTL), is a supporting view that maps a teaching calendar type and teaching calendar instance sequence number to the corresponding load calendar type and load calendar instance sequence number.

Although the ETRM 12.2.2 metadata records no referenced base objects for this view, the embedded view text establishes the join topology unambiguously. Note that IGS_CA_TEACH_TO_LOAD_V is itself a view, so the true base tables lie one layer deeper in the calendar schema.

Key Columns

  • CREDIT_POINTS — The resolved credit-point value, computed as NVL(SUA.OVERRIDE_ENROLLED_CP, NVL(CPS.ENROLLED_CREDIT_POINTS, UV.ENROLLED_CREDIT_POINTS)). The attempt-level override takes precedence, then the usec-level value, then the unit-version value.
  • LOAD_CAL_TYPE / LOAD_CI_SEQUENCE_NUMBER — The load calendar type and its calendar instance sequence number, obtained from IGS_CA_TEACH_TO_LOAD_V.
  • TEACH_CAL_TYPE / TEACH_CI_SEQUENCE_NUMBER — The teaching calendar type and calendar instance sequence number carried from the unit attempt. The sequence number is the field frequently sought by users searching for teach_ci_sequence_number.
  • PERSON_ID — The identifier of the student whose cart is being evaluated.
  • COURSE_CD — The course code associated with the attempt.
  • UOO_ID — The unit offering option identifier linking the attempt to its offering.

Common Use Cases and Queries

A typical use is to aggregate the maximum credit points a student has staged in the cart for a given teaching period, then compare that total against a rule-defined cap. The following query sums cart credit points per person and teaching calendar instance:

  • SELECT person_id, teach_cal_type, teach_ci_sequence_number, SUM(credit_points) cart_cp FROM igs_ss_en_rule_cart_max_v GROUP BY person_id, teach_cal_type, teach_ci_sequence_number;

Because the view exposes the load calendar mapping, it also supports cross-calendar validation, for example listing cart rows where the load calendar differs from the teaching calendar. Diagnostic queries joining back to IGS_EN_SU_ATTEMPT on PERSON_ID and UOO_ID allow administrators to reconcile cart totals against individual attempt records. The view is best treated as a read-only rule evaluation source rather than a transactional interface.