Results for “igs_ca_da_offcnt”

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

Overview

IGS_CA_DA_OFFCNT is a configuration table within the Oracle E-Business Suite Student System (IGS) product family, a module designated as obsolete in Release 12.1.1 and 12.2.2. The table describes the set of constraints that must be applied when an offset is used to generate a date alias value from another date alias. In the IGS calendar and date-alias framework, date aliases represent symbolic calendar references, and offsets allow one alias to be derived from another by applying a shift. IGS_CA_DA_OFFCNT stores the constraint rules that bound or qualify those derived values, ensuring that generated dates honour institutional calendar policy.

The documented ETRM metadata does not include this table in the current database implementation ("Not implemented in this database"), which indicates it is a legacy or dormant object retained for upgrade, reference, or historical schema purposes. From a heuristic Data Vault modelling perspective, the FK structure suggests a satellite-leaning classification: the table hangs off IGS_CA_DA_OFST and carries descriptive constraint attributes rather than acting as a pure hub or link.

Key Information Stored

The table is owned by the IGS schema and contains ten documented columns. The primary key, IGS_CA_DA_OFFCNT_PK, is the composite business key formed by DT_ALIAS, OFFSET_DT_ALIAS, and S_DT_OFFSET_CONSTRAINT_TYPE. A unique index, IGS_CA_DA_OFFCNT_U1, mirrors this same three-column combination, confirming it as the business-key candidate that guarantees uniqueness of each constraint definition. No separate surrogate key column is documented, so the composite key itself serves as the identifier.

• DT_ALIAS — the source date alias to which the offset is applied; part of the composite primary key and a foreign key to IGS_CA_DA_OFST.
• OFFSET_DT_ALIAS — the target date alias produced by applying the offset; also part of the composite primary key and referenced by the foreign key relationship.
• S_DT_OFFSET_CONSTRAINT_TYPE — the constraint type applied to the offset operation, dependent on a system-defined lookup; completes the primary key.
• CONSTRAINT_CONDITION — the conditional expression or rule that determines when the constraint applies.
• CONSTRAINT_RESOLUTION — the action or resolution taken when the constraint condition is met.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns recording who created and last modified each constraint row, and when.

The combination of CONSTRAINT_CONDITION and CONSTRAINT_RESOLUTION effectively encodes the behavioural logic: the condition identifies an edge case, and the resolution defines how the offset derivation should be adjusted to remain valid.

Common Use Cases and Queries

The principal use case is validating and troubleshooting date alias offset derivation within the IGS calendar engine. Administrators and technical consultants query this table to determine which constraint rules govern a particular alias pair before or after a date-generation run.

A typical retrieval lists all constraints for a given source alias:

• SELECT dt_alias, offset_dt_alias, s_dt_offset_constraint_type, constraint_condition, constraint_resolution FROM igs_ca_da_offcnt WHERE dt_alias = :alias;

A joined query against the offset definition table provides the full picture of how an offset and its constraints combine:

• SELECT o.dt_alias, o.offset_dt_alias, c.s_dt_offset_constraint_type, c.constraint_resolution FROM igs_ca_da_ofst o, igs_ca_da_offcnt c WHERE o.dt_alias = c.dt_alias AND o.offset_dt_alias = c.offset_dt_alias;

Because the table is marked obsolete, such queries are most relevant during migration analysis, data-archaeology exercises, or when auditing historical date-alias configuration prior to an upgrade. Reporting use cases centre on constraint coverage: identifying alias pairs that carry conditions but no resolution, or enumerating all constraint types in use.

Related Objects

The most significant related object is the parent offset definition table, which supplies the alias pairs constrained here:

• IGS_CA_DA_OFST — referenced by IGS_CA_DA_OFFCNT through DT_ALIAS and OFFSET_DT_ALIAS (the documented foreign key). This is the primary join partner.
• IGS_CA_DA_OFFCNT_PK / IGS_CA_DA_OFFCNT_U1 — the primary key constraint and unique index enforcing uniqueness of the alias-and-constraint-type combination.
• IGS_CA_DATE_ALIAS — the underlying date alias definitions to which both DT_ALIAS and OFFSET_DT_ALIAS resolve.
• IGS_CA_DA_CONSTRAINT (or equivalent constraint-lookup structures) — the reference source validating S_DT_OFFSET_CONSTRAINT_TYPE.
• IGS_CA_CALENDAR and IGS_CA_INSTANCE — calendar and instance objects that consume derived date alias values, indirectly dependent on the constraint rules recorded here.

Together these objects form the date-alias derivation chain: alias definitions feed offset definitions, offset definitions are qualified by constraint rules in IGS_CA_DA_OFFCNT, and the resulting derived values populate the institutional calendar.