Results for “numbering_scheme”

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

Overview

IGI_DOSSIER_NUMBERING is a table in the IGI schema (IGI – Public Sector Financials International) that stores dossier numbering schemes. In Oracle EBS 12.1.1 and 12.2.2, it is used by public sector organizations to define the rules by which dossier numbers are generated, including prefixes, year components, delimiters, and the last number issued. The table acts as a central configuration repository for numbering sequences applied to dossiers, ensuring consistent and auditable document identification across ledger and chart of accounts contexts.

Under the heuristic Data Vault classification derived from foreign key structure, this object is modeled as a standalone entity. That classification suggests it functions as an independent hub-like reference table rather than a dependent satellite or link, because the metadata does not identify inbound foreign key relationships to other tables. The primary key is IGI_DOSSIER_NUMBERING_PK, defined on the NUMBERING_SCHEME column, which uniquely identifies each numbering scheme record.

Key Information Stored

The table contains 16 documented columns. The most significant columns and their roles are:

• NUMBERING_SCHEME – Surrogate primary key; uniquely identifies each numbering scheme definition.
• SOB_ID – Set of Books identifier, associating the scheme with a ledger.
• COA_ID – Chart of Accounts identifier, scoping the scheme to an accounting structure.
• SEGMENT_NAME – The segment to which the numbering scheme applies.
• NUMBERING_TYPE – Classifies the numbering approach used by the scheme.
• SCHEME_TYPE – Distinguishes the type of scheme configuration.
• PREFIX – Prefix applied to generated dossier numbers.
• DELIMETER – Separator character inserted between number components.
• ENABLED_FLAG – Indicates whether the scheme is active.
• YEAR – Year component associated with the numbering scheme.
• LAST_NUMBER – The last number issued by the scheme, used to derive the next value.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard audit columns tracking record creation and modification.

A unique index, IGI_DOSSIER_NUMBERING_U1, is defined on (PREFIX, YEAR), making this pair a business-key candidate distinct from the surrogate primary key NUMBERING_SCHEME.

Common Use Cases and Queries

Typical scenarios include retrieving the active numbering scheme for a given ledger and year, validating prefix uniqueness, and auditing the last issued number. A representative query to list enabled schemes for a ledger is:

• SELECT numbering_scheme, prefix, year, last_number FROM igi.igi_dossier_numbering WHERE sob_id = :sob_id AND enabled_flag = 'Y';
• SELECT * FROM igi.igi_dossier_numbering WHERE prefix = :prefix AND year = :year; – leverages the unique index for business-key lookup.
• SELECT numbering_scheme, scheme_type, numbering_type, delimeter FROM igi.igi_dossier_numbering WHERE coa_id = :coa_id; – analyzes scheme configuration by chart of accounts.

Reporting use cases include reconciling dossier numbering sequences, monitoring LAST_NUMBER progression for audit, and verifying that no duplicate prefix/year combinations exist across ledgers.

Related Objects

Because the metadata classifies this table as standalone with no mined foreign key links, direct relational dependencies are limited. Related objects are inferred from the shared IGI dossier domain and the columns present:

• IGI_DOSSIERS – The primary dossier records that consume numbers generated by these schemes, joined on the dossier number and SOB_ID.
• IGI_DOSSIER_TYPES – Defines dossier types that may reference numbering schemes.
• GL_SETS_OF_BOOKS – Joined via SOB_ID to resolve ledger context.
• GL_CODE_COMBINATIONS – Joined via COA_ID to resolve chart of accounts context.
• FND_ID_FLEX_STRUCTURES – Provides the accounting flexfield structure referenced by COA_ID.
• FND_FLEX_VALUES – Supplies segment values referenced by SEGMENT_NAME.

These associations reflect logical joins rather than enforced foreign keys, consistent with the standalone Data Vault classification documented in the ETRM metadata.