Search Results du_tu_type_name




Overview

The APPS.IGI_EXP_NUM_SCHEMES_V view belongs to the Oracle E-Business Suite Public Sector / Grants and Foreign Military Sales (FMS) functional family, specifically the IGI (International Government Industry) schema, which is delivered with Oracle EBS 12.1.1 and 12.2.2. This view exposes numbering scheme configuration for document and transaction unit types, providing a consolidated read-only presentation layer over numbering scheme definitions used by expense/FMS processing. It is particularly relevant in the context of U.S. federal government contracting scenarios where obligated documents (for example, Military Standard Billing System / MILSBILLS transactions) require controlled, sequentially numbered identifiers driven by configurable prefixes, suffixes, fiscal years, and sequence values.

The view's principal role is to present a unified list of numbering schemes across two distinct document classifications — Document Units (DU) and Transaction Units (TU) — by resolving the underlying type header to yield a human-readable type name. This simplifies reporting and integration, since consumers do not need to join the base scheme table to either of the two separate header tables depending on the numbering type. It serves as a standard reference object for reporting, data extraction, and interface building in IGI-enabled environments.

Underlying Base Objects

Per the ETRM documented metadata for 12.2.2, the view is owned by APPS and is defined over three referenced base objects, all exposed as synonyms:

The view is constructed as a UNION ALL of two SELECT statements. The first joins IGI_EXP_NUM_SCHEMES to IGI_EXP_DU_TYPE_HEADERS_ALL on DU_TU_TYPE_ID = DU_TYPE_HEADER_ID, filtered by NUMBERING_TYPE = 'DU'. The second joins IGI_EXP_NUM_SCHEMES to IGI_EXP_TU_TYPE_HEADERS_ALL on DU_TU_TYPE_ID = TU_TYPE_HEADER_ID, filtered by NUMBERING_TYPE = 'TU'. Both branches project identical columns, aliasing the resolved type name as DU_TU_TYPE_NAME.

Key Columns

  • NUM_SCHEME_ID — primary identifier for the numbering scheme record.
  • NUMBERING_TYPE — discriminator indicating whether the scheme governs a Document Unit ('DU') or Transaction Unit ('TU').
  • NUMBERING_CLASS — classification of the numbering scheme.
  • DU_TU_TYPE_ID — foreign key to the corresponding DU or TU type header.
  • DU_TU_TYPE_NAME — resolved descriptive name of the document or transaction unit type (from the joined header table).
  • PREFIX / SUFFIX — characters prepended or appended to the generated number.
  • FISCAL_YEAR — fiscal year context for the numbering scheme.
  • NEXT_SEQ_VAL — the next sequence value to be assigned.
  • ORG_ID — operating unit / organization identifier supporting multi-org filtering.
  • ROW_ID — the ROWID of the base scheme row, exposed for direct row addressing.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include validating and reporting on configured numbering schemes, diagnosing sequence gaps, and extracting scheme metadata for interfaces. A representative query lists all schemes with their resolved type names:

  • SELECT NUM_SCHEME_ID, DU_TU_TYPE_NAME, NUMBERING_TYPE, PREFIX, SUFFIX, FISCAL_YEAR, NEXT_SEQ_VAL FROM APPS.IGI_EXP_NUM_SCHEMES_V ORDER BY NUMBERING_TYPE, DU_TU_TYPE_NAME;
  • Filter by type: ... WHERE NUMBERING_TYPE = 'DU';
  • Multi-org filter: ... WHERE ORG_ID = :p_org_id;

Because the view performs the type-name resolution internally, it is the preferred source for reports requiring descriptive scheme listings across both document and transaction units.