Results for “igi_exp_du_type_details_all”

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

Overview

IGI_EXP_DU_TYPE_DETAILS_ALL is a table owned by the IGI schema within the IGI - Public Sector Financials International product family. It stores the detail-level information associated with a Distinctive Unit (DU) type definition used in the Oracle E-Business Suite Public Sector Financials localization for Italy. In EBS 12.1.1 and 12.2.2, this table functions as the child of the DU type header definition, capturing the lower-granularity attributes that further qualify each DU type.

From a Data Vault modeling perspective, the mined foreign key structure suggests this object behaves as a satellite-leaning table. It carries a surrogate primary key and a foreign key to its parent header, with no documented downstream children, which is characteristic of a detail or descriptive table that hangs off a hub-like header entity rather than a link table reconciling multiple hubs. This classification is a heuristic suggestion, not an EBS-imposed constraint.

Key Information Stored

The table comprises nine documented columns. The most significant are:

• DU_TYPE_DETAIL_ID — the surrogate primary key, enforced by IGI_EXP_DU_TYPE_DETAILS_PK and also backed by the unique index IGI_EXP_DU_TYPE_DETAILS_U1. It uniquely identifies each detail record and serves as the primary business-key candidate.
• DU_TYPE_HEADER_ID — the foreign key referencing IGI_EXP_DU_TYPE_HEADERS_ALL. This links each detail row to its parent DU type definition and is the principal join column for parent-child queries.
• TRANSACTION_TYPE — identifies the transaction category the DU type detail applies to, allowing a given DU type definition to be qualified by transaction context.
• ORG_ID — the operating unit identifier, enabling multi-org (multi-organization) partitioning of the detail records.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO columns providing audit lineage and concurrency tracking on insert and update.

The surrogate key (DU_TYPE_DETAIL_ID) is distinct from the business-key candidate exposed through the unique index; the ORG_ID column further contextualizes rows within a multi-org deployment.

Common Use Cases and Queries

Typical usage involves retrieving all detail lines for a given DU type, or enumerating configurations for reporting and reconciliation. A representative query joins the detail table to its header:

• Retrieve details by header: SELECT d.du_type_detail_id, d.transaction_type, d.org_id FROM igi.igi_exp_du_type_details_all d WHERE d.du_type_header_id = :header_id;
• Join to header for descriptive context: SELECT h.*, d.* FROM igi.igi_exp_du_type_headers_all h, igi.igi_exp_du_type_details_all d WHERE h.du_type_header_id = d.du_type_header_id;
• Org-scoped reporting: filter on d.org_id for a specific operating unit.
• Audit and change tracking: order by last_update_date or filter using last_updated_by to monitor configuration changes.

These patterns support DU type setup validation, Public Sector Financials reporting, and data migration verification between 12.1.1 and 12.2.2 environments.

Related Objects

The documented relationships define a small but cohesive object cluster:

• IGI_EXP_DU_TYPE_HEADERS_ALL — the parent table referenced via DU_TYPE_HEADER_ID; the primary FK relationship.
• IGI_EXP_DU_TYPE_DETAILS_PK — the primary key constraint on DU_TYPE_DETAIL_ID.
• IGI_EXP_DU_TYPE_DETAILS_U1 — the unique index supporting the primary business-key candidate.

Additional dependent views or concurrent programs that consume DU type detail configuration typically resolve through the header join, so IGI_EXP_DU_TYPE_HEADERS_ALL remains the pivotal related object. No other foreign-key children are documented for this table in the ETRM metadata.