Results for “igi_exp_tus”

32 results




Overview
Explore in AI Chat

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

Overview

APPS.IGI_EXP_TUS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that presents the header-level records of expense "Travel Units" (TUs) processed through the ETRM/Expense subsystem. Travel Units represent the discrete expense claims that flow through an approval workflow, and this view denormalizes the raw TU header table into a business-friendly form by joining it to its associated TU type, approval profile, lookup-meaning, and the FND_USER directory. The view is owned by the APPS schema, making it accessible to any responsibility or concurrent program that runs under APPS, and is commonly surfaced through Oracle Reports, BI Publisher, OAF pages, and custom SQL extracts. The column TU_BY_USER_NAME, which originates from the FND_USER join, is the element users typically search for under the term "tu_by_user_name", since it resolves the internal TU_BY_USER_ID into the human-readable name of the user who created the travel unit.

Underlying Base Objects

The view is documented as an inner join over the following base objects, all referenced through APPS synonyms except the lookup view:

Because the TU_BY_USER_ID to FU1 join is an inner join, any TU whose creator ID does not resolve to a valid FND_USER row is excluded from the view. The NEXT_APPROVER_USER_ID join is outer, so unassigned approvers do not filter the result set.

Key Columns

  • ROW_ID — the IET.ROWID, usable for locating and updating the underlying row in tools such as OAF.
  • TU_ID, TU_TYPE_HEADER_ID, TU_TYPE_NAME — unique key and classification of the travel unit.
  • TU_ORDER_NUMBER, TU_LEGAL_NUMBER, TU_DESCRIPTION — descriptive identifiers for the claim.
  • TU_STATUS, TU_STATUS_DESC — the internal status code and its lookup meaning (from IGI_LOOKUPS).
  • TU_AMOUNT, TU_CURRENCY_CODE — monetary value and currency of the TU.
  • APPRV_PROFILE_ID, APPRV_PROFILE_NAME — the approval profile governing the workflow.
  • NEXT_APPROVER_USER_ID, NEXT_APPROVER_USER_NAME — the current pending approver; an outer-joined FND_USER value.
  • TU_BY_USER_ID, TU_BY_USER_NAME — the internal ID and resolved user name of the person who raised the TU; the anchor for "tu_by_user_name" searches.
  • TU_FISCAL_YEAR, TU_DATE — fiscal and transaction dates.
  • ORG_ID — the operating unit, subject to MOAC and VPD policies.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF columns available for customer-defined data.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include reporting all travel units raised by a given user, identifying outstanding approvals per approver, and feeding downstream extracts with the descriptive TU type and profile names. Because ORG_ID is exposed, queries should respect operating-unit security by not disabling VPD.

Example: list all TUs created by a specified user name.

  • SELECT tu_id, tu_order_number, tu_amount, tu_currency_code, tu_status_desc, tu_date FROM apps.igi_exp_tus_v WHERE tu_by_user_name = :user_name ORDER BY tu_date DESC;

Example: find PENDING TUs and their next approvers.

  • SELECT tu_id, tu_by_user_name, next_approver_user_name, tu_amount FROM apps.igi_exp_tus_v WHERE tu_status_desc = 'Pending' AND next_approver_user_name IS NOT NULL;

Example: summarize amounts by TU type and status for a fiscal year.

  • SELECT tu_type_name, tu_status_desc, COUNT(*) num_tus, SUM(tu_amount) total_amount FROM apps.igi_exp_tus_v WHERE tu_fiscal_year = :fiscal_year GROUP BY tu_type_name, tu_status_desc;

Always qualify with APPS.IGI_EXP_TUS_V and apply ORG_ID or MOAC predicates in multi-org deployments.