Search Results igi_exp_num_schemes_pk

Overview

IGI.IGI_EXP_NUM_SCHEMES_ALL is a table within the IGI - Public Sector Financials International product family. It stores the configuration details of numbering schemes used for exchange protocol numbering — the rules that govern how sequential identifiers are assigned to exchange protocol documents. Because the table is multi-org enabled (it carries an ORG_ID column and uses the _ALL suffix), numbering scheme definitions can be maintained independently per operating unit, allowing organizations with distinct statutory or procedural requirements to assign document numbers according to their own conventions.

From a Data Vault modeling perspective, the mined metadata classifies this object as standalone. It carries no foreign keys to other tables, so it is best treated as a hub-like reference entity — the anchor that holds the numbering scheme identity — rather than as a link or satellite. The absence of FK relationships suggests the table functions as a configurable control record consumed by application logic rather than as a transaction detail.

Key Information Stored

The table contains 14 documented columns. The most significant are:

• NUM_SCHEME_ID — The surrogate primary key, enforced by IGI_EXP_NUM_SCHEMES_PK and also covered by unique index IGI_EXP_NUM_SCHEMES_U1. Every reference to a numbering scheme resolves through this identifier.
• NUMBERING_TYPE, NUMBERING_CLASS, DU_TU_TYPE_ID, FISCAL_YEAR, ORG_ID — Together these form the composite business key, enforced by unique index IGI_EXP_NUM_SCHEMES_U2. This combination defines the uniqueness boundaries of a scheme: the type and class of numbering, the document unit/transaction unit type, the fiscal year, and the owning operating unit.
• PREFIX and SUFFIX — Literal text applied before and after the generated sequence value, used to embed scheme-specific or fiscal identifiers in the final document number.
• NEXT_SEQ_VAL — The next sequential value to be assigned, acting as the runtime counter that advances as documents are numbered.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS auditing columns recording who created and last maintained each scheme definition.

Common Use Cases and Queries

The primary operational use is identifying which numbering scheme applies to a given exchange protocol document at generation time. A typical lookup joins on the business-key components:

• Resolving an active scheme: SELECT num_scheme_id, prefix, suffix, next_seq_val FROM igi.igi_exp_num_schemes_all WHERE numbering_type = :type AND numbering_class = :class AND du_tu_type_id = :du_tu AND fiscal_year = :year AND org_id = :org;
• Auditing sequence position: Reporting on NEXT_SEQ_VAL per fiscal year and operating unit to detect gaps or approaching overflow limits.
• Multi-org comparison: Listing all schemes for an organization to confirm that no duplicate or conflicting configurations exist across operating units.
• Configuration review: Extracting PREFIX/SUFFIX patterns to verify numbering conventions meet statutory formatting requirements.

Because the table is standalone, reporting queries do not require joins to resolve scheme identity; the unique index on (NUMBERING_TYPE, NUMBERING_CLASS, DU_TU_TYPE_ID, FISCAL_YEAR, ORG_ID) supports efficient filtered access.

Related Objects

The mined metadata identifies no foreign-key relationships for this table, so it is referenced by application logic rather than by enforced database constraints. Objects that logically depend on or consume the numbering schemes include:

• IGI_EXP_NUM_SCHEMES_PK — The primary key constraint on NUM_SCHEME_ID.
• IGI_EXP_NUM_SCHEMES_U1 — Unique index on NUM_SCHEME_ID.
• IGI_EXP_NUM_SCHEMES_U2 — Composite unique index on NUMBERING_TYPE, NUMBERING_CLASS, DU_TU_TYPE_ID, FISCAL_YEAR, ORG_ID, defining the business key.
• Exchange protocol document tables within the IGI module, which reference NUM_SCHEME_ID to determine the applicable numbering rule.
• IGI setup and concurrent programs that initialize or advance NEXT_SEQ_VAL during document generation.

Administrators should treat this table as reference configuration data, protected through standard EBS schema and multi-org security rather than through relational integrity to transaction tables.