Results for “pro_sequence_number”

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

Overview

The IGS_PR_OU_PS_ALL table is a core table within the IGS — Student System product of Oracle E-Business Suite, available in both the 12.1.1 and 12.2.2 releases. It belongs to the IGS schema and stores the course codes that are used in encumbrances resulting from a progression outcome. A practical example is a course exclusion, where a specific course code is associated with a progression rule so that the encumbrance logic can recognise and apply it during outcome evaluation. The table thus acts as the bridge between progression rule definitions and the individual courses that those rules must target.

From a data-modelling perspective, the mined Data Vault classification is satellite-leaning. This suggests that the table functions primarily as a descriptive satellite attached to the surrogate/business key formed by its progression rule and sequence columns, carrying the attribute detail (COURSE_CD) about encumbrances rather than defining a new hub or a pure relationship link.

Key Information Stored

The documented physical schema records ten columns. The most important are the four that constitute the business key and the primary key:

• PROGRESSION_RULE_CAT — the progression rule category code, identifying the type of rule under which the encumbrance applies.
• PRA_SEQUENCE_NUMBER — the sequence number within the progression rule category, used to order or disambiguate rules of the same category.
• PRO_SEQUENCE_NUMBER — the progression outcome sequence number, linking the encumbrance detail to a specific outcome.
• COURSE_CD — the course code that is excluded or otherwise encumbered, for example a course exclusion.

The surrogate primary key is documented as IGS_PR_OU_PS_PK, defined over (PROGRESSION_RULE_CAT, PRA_SEQUENCE_NUMBER, PRO_SEQUENCE_NUMBER, COURSE_CD). A unique index, IGS_PR_OU_PS_ALL_U1, carries the identical column list and therefore serves as the business-key candidate. The remaining documented columns are the standard Oracle EBS audit and multi-org attributes: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and ORG_ID. The presence of ORG_ID indicates multi-organisation partitioning, so queries should be filtered by operating unit where appropriate.

Common Use Cases and Queries

Typical scenarios include auditing which courses are excluded under a progression rule, verifying encumbrance setup before an outcome run, and generating student-facing reports explaining why a course could not be counted. A frequently used query pattern retrieves all course codes for a given rule category and outcome:

• SELECT COURSE_CD FROM IGS_PR_OU_PS_ALL WHERE PROGRESSION_RULE_CAT = :cat AND PRA_SEQUENCE_NUMBER = :pra AND PRO_SEQUENCE_NUMBER = :pro;
• Joining to IGS_PR_RU_OU_ALL on the same three key columns to resolve rule descriptions alongside the course exclusions.
• Restricting results by ORG_ID to honour multi-org security when reporting per operating unit.

Reporting use cases include encumbrance validation reports, progression-rule configuration listings, and data-quality checks confirming that every configured outcome has an associated course list.

Related Objects

The principal referenced object is documented through a foreign key:

• IGS_PR_RU_OU_ALL — joined via PROGRESSION_RULE_CAT, PRA_SEQUENCE_NUMBER, and PRO_SEQUENCE_NUMBER, providing the progression rule/outcome context.

Additional dependent or related objects include the primary key constraint IGS_PR_OU_PS_PK and the unique index IGS_PR_OU_PS_ALL_U1 on the same object. In practice, reporting and integration commonly also reference the progression outcome and rule definition tables within the IGS Student System that share the progression rule category and sequence columns, since those are the attributes through which this satellite is reachable.