Results for “igs_as_untas_pattern”

38 results




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

Overview

IGS_AS_UNTAS_PATTERN is a secured (organization‑filtered) view owned by the APPS schema in the Oracle E‑Business Suite Student System (IGS) product family. As documented in the ETRM 12.1.1 / 12.2.2 reference material, the view describes the assessment patterns that make up the assessment requirement for a unit. In practical terms, it exposes the catalogue of alternative assessment structures — for example, "examination only", "continuous assessment plus examination", or "portfolio‑based" — that may satisfy the assessment requirement defined against a specific unit version.

For reporting and integration purposes the view acts as the read‑only presentation layer over the underlying ALL table. Its most significant behavioural characteristic is that it is multi‑org enabled: rather than returning every row regardless of operating unit, it restricts output through a row‑level security predicate embedded in its defining query. Consumption of the view therefore depends on the session’s CLIENT_INFO setting, which Oracle forms and concurrent programs populate with the logged‑in operating unit; when called from a PL/SQL context, the caller must set this value explicitly or the predicate resolves to the sentinel value ‑99 and no valid operating‑unit rows are returned.

Underlying Base Objects

The view is defined over a single object: IGS_AS_UNTAS_PATTERN_ALL, which is the intersection (multi‑org) entity holding assessment pattern definitions for all operating units. The defining query selects the base table’s ROWID as ROW_ID and projects each functional column directly, applying an INLINE secure predicate of the form:

Because the view is a thin projection over a single intersection table, no joins, unions, or aggregations are performed. It does not itself enforce referential constraints; those are defined on the base table. The "ALL" designation confirms that the physical data is partitioned by ORG_ID at the table level, and the view narrows this to the current operating unit.

Key Columns

  • ROW_ID — the base table ROWID; useful as a unique row identifier in reporting extracts.
  • ORG_ID — the operating unit owning the assessment pattern record; drives the security predicate.
  • UNIT_CD, VERSION_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER — the composite context identifying the unit version and calendar/teaching period to which the pattern belongs.
  • ASS_PATTERN_ID, ASS_PATTERN_CD, DESCRIPTION — the assessment pattern identity, its short code, and its descriptive text.
  • LOCATION_CD, UNIT_CLASS, UNIT_MODE — the delivery location and the unit’s class/mode, allowing patterns to vary by delivery context.
  • DFLT_PATTERN_IND — flags the default assessment pattern, a key discriminator in enquiry and enrolment‑related logic.
  • LOGICAL_DELETE_DT, ACTION_DT — logical deletion and effective action dates supporting history retention.
  • Standard WHO and concurrent‑program columns (CREATED_BY … PROGRAM_UPDATE_DATE) for audit and interface traceability.

Common Use Cases and Queries

Typical reporting scenarios include validating which patterns exist for a unit version, identifying default patterns prior to student assessment selection, and extracting reference data for integration into a VLE or assessment management system. A sample query for the current operating unit is:

  • SELECT ass_pattern_cd, description, dflt_pattern_ind
  • FROM   igs_as_untas_pattern
  • WHERE  unit_cd = :unit_cd
  • AND    version_number = :version_number
  • AND    cal_type = :cal_type
  • AND    logical_delete_dt IS NULL;

In PL/SQL or OAF contexts where CLIENT_INFO is not set, applications should either call the multi‑org API to initialise the org context, or query IGS_AS_UNTAS_PATTERN_ALL with an explicit ORG_ID filter. This avoids the ‑99 fallback and guarantees correct organisation‑scoped results.