Results for “igi_exp_numbering”

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

Overview

IGI_EXP_NUMBERING is a multi-organization view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGI – Public Sector Financials International product. Its stated purpose is to display all code combinations and numbering information used for Exchange Protocol (EP) numbering. In practice, the view exposes the numbering configuration that governs how Exchange Protocol documents are sequenced and formatted, including prefixes, suffixes, and the next sequence value to be consumed.

The view is defined as a filtering layer over the underlying table IGI_EXP_NUMBERING_ALL. The predicate restricts rows to those matching the operating unit context of the current session, resolved from the USERENV('CLIENT_INFO') value. Where ORG_ID is null, the literal sentinel value -99 is substituted via NVL, allowing global or non-organization-specific numbering definitions to be visible alongside org-specific ones. Because it presents the same column set as its base table, IGI_EXP_NUMBERING is primarily intended for reporting and integration reads rather than for direct maintenance, which should be performed against the base table under the appropriate multi-org responsibilities.

Underlying Base Objects

The view is defined over a single documented base object: IGI_EXP_NUMBERING_ALL, referenced through a synonym. IGI_EXP_NUMBERING_ALL is the multi-org table that holds Exchange Protocol numbering definitions for all operating units. The view applies the standard EBS multi-org filtering pattern, comparing the session's organization context to the ORG_ID column.

Because IGI_EXP_NUMBERING_ALL carries the full unfiltered data set, IGI_EXP_NUMBERING acts as the security and context-sensitive projection of that data. Queries against the view return only the rows relevant to the current operating unit, plus any rows whose ORG_ID resolves to the -99 sentinel. Positions where the view text references or is expected to join to related IGI Exchange Protocol setup tables should be validated against the specific environment, as the excerpt documents only the base object relationship.

Key Columns

• NUMBER_ID – Primary identifier for the numbering configuration record.
• EP_NUMBERING_TYPE – Classification of the numbering scheme applied to Exchange Protocol documents.
• EP_DOCUMENT_CLASS and DOCUMENT_CLASS_CODE – Document class in descriptive and coded form.
• EP_DOCUMENT_TYPE and DOCUMENT_TYPE_CODE – Document type in descriptive and coded form. The latter is the column most frequently sought when mapping configuration to document types.
• EP_NUMBERING_CODE – The numbering code assigned to the configuration.
• APPLICATION – Application context owning the numbering definition.
• FISCAL_YEAR – Fiscal year associated with the numbering record.
• TRX_TYPE_CODE and EP_TRX_TYPE – Transaction type in coded and descriptive forms.
• ORG_ID – Operating unit identifier driving the multi-org filter.
• PREFIX and SUFFIX – Text components applied to generated numbers.
• NEXT_SEQ_VAL – The next sequence value to be issued.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include auditing numbering setup, verifying the next sequence value per operating unit, and integrating Exchange Protocol document generation with external systems. To locate configuration for a particular document type, query the DOCUMENT_TYPE_CODE column:

SELECT number_id, ep_document_type, document_type_code, ep_numbering_code, prefix, suffix, next_seq_val FROM igi_exp_numbering WHERE document_type_code = :p_document_type_code;

To review all numbering definitions visible in the current operating unit context, including the global sentinel rows, use:

SELECT org_id, ep_document_class, ep_document_type, fiscal_year, next_seq_val FROM igi_exp_numbering ORDER BY org_id, ep_document_type;

For reconciliation against the unfiltered data set, join or compare against IGI_EXP_NUMBERING_ALL using NUMBER_ID. Because the view relies on USERENV('CLIENT_INFO') for org context, ensure the session is initialized for the target operating unit before relying on results. Oracle Proprietary, Confidential Information.