Results for “tu_type_header_id”

50+ results




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

Overview

The IGI_EXP_TU_TYPE_DETAILS_ALL table is a core configuration object within the IGI (Public Sector Financials International) product family of Oracle E-Business Suite, available in both release 12.1.1 and 12.2.2. It stores the detail-level information that defines a TU (Transaction Unit) Type, complementing the header-level definition held in IGI_EXP_TU_TYPE_HEADERS_ALL. In practice, TU Types are used by public sector organizations to model the composition of a transaction — for example, the sets of expenditure or budgetary line attributes that roll up under a given transaction definition. This table therefore acts as the fine-grained descriptor container for each TU Type, capturing the specific detail rows (and their associated DU Type linkage) that the application applies when validating or deriving transaction attributes.

From a Data Vault modeling perspective, the metadata's heuristic classification places this object as a link. This is a modeling suggestion rather than a functional designation: the table's foreign keys tie a TU Type Header to a DU Type Header, and it carries its own surrogate key plus standard audit columns, making it a natural candidate for a link entity that resolves a many-to-many relationship between two header hubs.

Key Information Stored

The documented physical schema consists of nine columns. The most significant are:

Taken together, the detail rows define which DU Types participate in each TU Type. The absence of a documented name or description column means that all descriptive text is likely resolved by joining to the referenced header tables.

Common Use Cases and Queries

Typical applications include configuration validation, migration and cloning, and reporting on which DU Types a TU Type comprises.

  • Retrieving all details for a given TU Type:
SELECT d.tu_type_detail_id,
       d.tu_type_header_id,
       d.du_type_header_id,
       d.org_id
FROM   igi.igi_exp_tu_type_details_all d
WHERE  d.tu_type_header_id = :p_tu_type_header_id
AND    d.org_id            = :p_org_id;
  • Resolving detail rows to their header descriptions:
SELECT d.tu_type_detail_id, t.tu_type_name, u.du_type_name
FROM   igi.igi_exp_tu_type_details_all d,
       igi.igi_exp_tu_type_headers_all t,
       igi.igi_exp_du_type_headers_all u
WHERE  d.tu_type_header_id = t.tu_type_header_id
AND    d.du_type_header_id = u.du_type_header_id;
  • Validating duplicates or orphaned rows prior to migration (checking that each tu_type_detail_id is unique and that both foreign keys resolve).
  • Reporting the DU Type coverage across all TU Types for an operating unit.

Related Objects

The table's principal relationships are defined by its foreign keys and its own primary key:

  • IGI_EXP_TU_TYPE_HEADERS_ALL — parent table; joined on TU_TYPE_HEADER_ID.
  • IGI_EXP_DU_TYPE_HEADERS_ALL — referenced table; joined on DU_TYPE_HEADER_ID.
  • IGI_EXP_TU_TYPE_DETAILS_PK — primary key constraint on TU_TYPE_DETAIL_ID.
  • IGI_EXP_TU_TYPE_DETAILS_U1 — unique index on TU_TYPE_DETAIL_ID, the documented business-key candidate.

Because the table is an _ALL object owned by the IGI schema, access is normally mediated through the corresponding multi-org views and the IGI setup forms rather than direct DML. Any integration or reporting effort should treat IGI_EXP_TU_TYPE_HEADERS_ALL and IGI_EXP_DU_TYPE_HEADERS_ALL as the primary header-level companions to this detail table.