Results for “igs_av_stnd_conf_all”

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

Overview

IGS_AV_STND_CONF_ALL is a configuration table within the Oracle E-Business Suite IGS — Student System product, a module marked obsolete in the ETRM reference set. The table describes the values used as the basis for default values applied to advanced standing tables. In functional terms, it stores the control parameters that govern how advanced standing (credit transfer, exemption, and articulation) records are defaulted during entry, rather than holding the advanced standing records themselves. It therefore behaves as a reference and setup object rather than a transactional one.

The documented physical schema for ETRM 12.1.1 records the owner as IGS, with twelve columns and a single unique index, IGS_AV_STND_CONF_ALL_U1, on S_CONTROL_NUM. The primary key constraint is IGS_AV_STND_CONF_ALL_PK, also defined on S_CONTROL_NUM. The Data Vault classification heuristic mined from the foreign key structure returns standalone, meaning no inbound or outbound FK relationships were detected. From a modeling perspective this suggests the object is best treated as a standalone reference or lookup structure rather than as a hub, link, or satellite in a Data Vault model. The ETRM implementation note states the table is not implemented in the reference database, so it may be absent from some 12.1.1 and 12.2.2 environments depending on the installed IGS feature set.

Key Information Stored

The table is keyed by a single surrogate identifier, with the following columns carrying the substantive business meaning:

• S_CONTROL_NUM — the primary key and the sole documented business-key candidate via IGS_AV_STND_CONF_ALL_U1; identifies each configuration control record.
• ADV_STND_CUTOFF_DT_ALIAS — alias used to resolve the advanced standing cutoff date when defaulting records.
• ADV_STND_EXPIRY_DT_ALIAS — alias for the advanced standing expiry date default.
• ADV_STND_BASIS_INST — the basis institution applied by default to advanced standing entries.
• ADV_STND_MAJOR_EXEMPT_INST — the institution used by default when a major-level exemption is granted.
• EXPIRY_DT_INCREMENT — the increment applied to derive an expiry date from a cutoff date.
• ORG_ID — the operating unit or organization context, making the configuration multi-org aware.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.

The S_CONTROL_NUM column is the surrogate primary key; it is also the only documented unique index, so it serves as both the technical and the business identifier for the row. The remaining columns are attribute-bearing configuration values, not alternate keys.

Common Use Cases and Queries

Typical usage centres on retrieving default values for the advanced standing entry forms, and on auditing how those defaults are configured per operating unit. A representative query joins the configuration key to the organisation context:

• Look up the control row for an operating unit: SELECT * FROM igs_av_stnd_conf_all WHERE org_id = :p_org_id;
• Resolve specific defaults by key: SELECT adv_stnd_basis_inst, adv_stnd_major_exempt_inst, expiry_dt_increment FROM igs_av_stnd_conf_all WHERE s_control_num = :p_control_num;
• Audit changes over time using the WHO columns: SELECT s_control_num, last_updated_by, last_update_date FROM igs_av_stnd_conf_all WHERE last_update_date >= :p_since;

Because the object is standalone, reporting joins are driven by application logic rather than enforced foreign keys, so extracts should filter on ORG_ID to respect multi-org security.

Related Objects

The ETRM relationship data classifies this table as standalone, with no documented FK dependencies. The most significant objects that reference or depend on it conceptually are the advanced standing tables it seeds defaults for, including the advanced standing header and detail tables in the IGS module, the institution and organisation definition tables that supply ADV_STND_BASIS_INST, and the API or forms layer that reads these configuration values during entry. Practically, joins are performed on S_CONTROL_NUM and ORG_ID rather than on foreign key columns, and administrators should verify existence, since the table is documented as not implemented in the reference database.