Results for “next_approver_user_id”

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

Overview

IGI_EXP_DUS_V is a VALID view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the IGI - Public Sector Financials International product family, the module that supports public-sector expenditure tracking, including dialog units and transaction units used to record, approve, and report on committed expenditure. The view returns details of all dialog units and is primarily consumed by the "Define Dialog Units" form, where it populates the block that end users query and maintain. Because it joins the dialog unit entity to its parent transaction unit, lookup meanings, currency, customer, and approver attributes, it functions as a denormalized reporting surface for dialog unit data rather than a transactional base table. In reporting and integration terms, the view provides a single, form-friendly projection that avoids repeated joins to FND_USER, IGI_LOOKUPS, HZ_CUST_SITE_USES, and IGI_EXP_DU_TYPE_HEADERS. The DU_FISCAL_YEAR column, which the user searched for, is exposed directly by this view and is one of the key descriptive attributes of a dialog unit.

Underlying Base Objects

The view is defined over ten documented base objects, several of which are synonyms or views in their own right. The driving table is IGI_EXP_DUS (synonym for the dialog unit entity), outer-joined to IGI_EXP_TUS_ALL (synonym, transaction units) on TU_ID. The dialog unit type header is resolved through a join to IGI_EXP_DU_TYPE_HEADERS_ALL, which supplies DU_TYPE_NAME and APPLICATION_ID. Status and other coded values are decoded via IGI_LOOKUPS, which is itself a view, restricted to the lookup type 'IGI_EXP_DU...' as shown in the view text. The next approver is obtained from FND_USER. Third-party details are drawn from HZ_CUST_ACCOUNTS, HZ_PARTIES, HZ_CUST_SITE_USES_ALL, and their supporting views such as AR_CUSTOMERS_V, rather than from the supplier tables; the documented metadata also lists AP_SUPPLIER_SITES_ALL and PO_VENDORS, indicating that supplier or vendor attributes are additionally referenced. FND_APPLICATION_VL and FND_CURRENCIES provide application and currency context. Because the driving table is joined with outer joins to the transaction unit and user, a dialog unit is returned even when it has no associated transaction unit or approver.

Key Columns

• DU_ID, ROW_ID — Primary key of the dialog unit and its ROWID for form-level locking.
• DU_ORDER_NUMBER, DU_LEGAL_NUMBER — Ordering and legal reference identifiers for the dialog unit.
• DU_STATUS, DU_STATUS_DESC — Internal status code and its decoded meaning from IGI_LOOKUPS.
• DU_FISCAL_YEAR — The fiscal year to which the dialog unit is attributed; used for period and budget reporting.
• DU_DATE, DU_AMOUNT, DU_PREPAY_AMOUNT — Date, total amount, and prepaid portion of the unit.
• DU_CURRENCY_CODE — Currency of the amounts, validated against FND_CURRENCIES.
• TU_ID, TU_ORDER_NUMBER, TU_LEGAL_NUMBER — Parent transaction unit linkage.
• NEXT_APPROVER, NEXT_APPROVER_USER_ID — User name and ID of the pending approver.
• DU_TYPE, DU_TYPE_HEADER_ID, APPLICATION_ID — Dialog unit type classification.
• DU_THIRD_PARTY, DU_THIRD_PARTY_SITE — Customer name and site for third-party dialog units.
• ORG_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Multi-org and audit columns, plus ATTRIBUTE1 through ATTRIBUTE15 for descriptive flexfield data.

Common Use Cases and Queries

The view supports dialogs around dialog unit maintenance and fiscal-year reporting. A typical query retrieves open dialog units for a fiscal year, ordered by date:

• SELECT DU_ID, DU_ORDER_NUMBER, DU_FISCAL_YEAR, DU_DATE, DU_AMOUNT, DU_CURRENCY_CODE, DU_STATUS_DESC FROM APPS.IGI_EXP_DUS_V WHERE DU_FISCAL_YEAR = '2019' AND ORG_ID = :p_org_id ORDER BY DU_DATE;
• SELECT NEXT_APPROVER, COUNT(*) FROM APPS.IGI_EXP_DUS_V WHERE DU_STATUS_DESC = 'Pending Approval' GROUP BY NEXT_APPROVER;
• SELECT DU_TYPE, TU_LEGAL_NUMBER, DU_THIRD_PARTY, SUM(DU_AMOUNT) FROM APPS.IGI_EXP_DUS_V WHERE DU_FISCAL_YEAR = :p_year GROUP BY DU_TYPE, TU_LEGAL_NUMBER, DU_THIRD_PARTY;

Additional uses include reconciliation of dialog units to their parent transaction units, aging analysis of unapproved units, and integration extracts feeding downstream budget execution or financial reporting systems. Because the view is not a base table, no DML should be issued against it; it should be queried for reporting only, with filters on ORG_ID to respect multi-org security.