Results for “tu_description”

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

Overview

IGI_EXP_TUS_V is a database view owned by the APPS schema within the IGI — Public Sector Financials International product family. It is delivered as a VALID object in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The view presents a consolidated, human-readable projection of Transmission Unit records, exposing the descriptive attributes, approval routing information, and audit context required by the "Define Transmission Units" screen. Because it joins operational Transmission Unit data to lookup meanings and user names, it functions both as the backing query for that maintenance form and as a reporting surface for integrations that must resolve internal identifiers into business-meaningful values.

The view is particularly relevant to the search term tu_by_user_id, which corresponds to a column of the same name. This column stores the identifier of the user who created or submitted the Transmission Unit, and the view resolves it to a display name through a join to FND_USER, allowing consumers to avoid a secondary lookup against the user reference table.

Underlying Base Objects

The documented view text defines IGI_EXP_TUS_V over the following base objects, each resolved through APPS synonyms in the 12.2.2 metadata:

• IGI_EXP_TUS (synonym for the base table) — the driving table, supplying the ROWID as ROW_ID and all core TU columns, including TU_BY_USER_ID, TU_STATUS, approval identifiers, the fifteen descriptive attributes, and the currency code.
• IGI_EXP_TU_TYPE_HEADERS — supplies the Transmission Unit type header identifier and TU_TYPE_NAME, joining on TU_TYPE_HEADER_ID.
• IGI_EXP_APPRV_PROFILES — supplies APPRV_PROFILE_NAME, joining on APPRV_PROFILE_ID.
• FND_USER — referenced twice. The alias FU resolves NEXT_APPROVER_USER_ID to NEXT_APPROVER_USER_NAME through an outer join, since the next approver may not yet be assigned. The alias FU1 resolves TU_BY_USER_ID to TU_BY_USER_NAME through an inner join.
• IGI_LOOKUPS (itself a view) — supplies TU_STATUS_DESC, joining LOOKUP_CODE to TU_STATUS where LOOKUP_TYPE is 'IGI_EXP_TU_STATUS'.

The inner join against FU1 means a Transmission Unit record is returned only when the creating/submitting user resolves to a valid FND_USER row. Only the next-approver join is nullable.

Key Columns

• TU_ID, ROW_ID — primary identifier and physical row locator for the Transmission Unit, used by the maintenance screen for updates.
• TU_ORDER_NUMBER, TU_LEGAL_NUMBER, TU_DESCRIPTION, TU_AMOUNT, TU_FISCAL_YEAR, TU_DATE, TU_CURRENCY_CODE — the core descriptive and monetary attributes of the unit.
• TU_STATUS / TU_STATUS_DESC — the stored lookup code and its translated meaning from IGI_LOOKUPS.
• TU_BY_USER_ID and TU_BY_USER_NAME — the user who created/submitted the unit and the resolved user name; this pair directly serves the tu_by_user_id search.
• NEXT_APPROVER_USER_ID and NEXT_APPROVER_USER_NAME — pending approver, resolved via an outer join.
• APPRV_PROFILE_ID, APPRV_PROFILE_NAME, TU_TYPE_HEADER_ID, TU_TYPE_NAME — approval profile and type context.
• ORG_ID — the multi-org operating unit securing column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the DFF/descriptive flexfield segment values.

Common Use Cases and Queries

Typical use is to retrieve Transmission Unit details with decoded status, type, approval profile, and user names, filtered by status or by the submitting user. The following query returns all Transmission Units submitted by a given user:

• SELECT tu_id, tu_order_number, tu_legal_number, tu_status_desc, tu_amount, tu_currency_code, tu_by_user_name, next_approver_user_name FROM igi_exp_tus_v WHERE tu_by_user_id = :p_user_id ORDER BY tu_date DESC;

For reporting on units awaiting approval, the outer-joined approver column is queried alongside the status lookup:

• SELECT tu_order_number, tu_status_desc, next_approver_user_name, tu_fiscal_year FROM igi_exp_tus_v WHERE next_approver_user_id IS NOT NULL AND tu_status_desc = 'Pending Approval';

Because the view already decodes TU_STATUS and resolves user names, it is suitable for concurrent report definitions, Discoverer workbooks, and integration extracts that must publish Transmission Unit data without re-implementing the lookup and FND_USER joins. Reporting queries should still restrict by ORG_ID where multi-org operating unit isolation is required.