Search Results igi_stp_net_type_alloc




Overview
Explore in AI Chat

Overview

The APPS.IGI_STP_PACKAGES_V view is a reporting and integration construct within Oracle E-Business Suite that exposes settlement and payment package records originating from the IGI (Global Intercompany / Treasury) module. It consolidates data across Receivables and Payables contexts, presenting a unified projection of payment packages, netting transactions, customer and supplier references, currency conversion information, and site identifiers. The view serves as a denormalized read model that joins header-level package data with master reference data, allowing downstream reports, extracts, and integration interfaces to retrieve settlement detail without navigating the underlying normalized schema directly.

The view is defined conditionally: the first branch resolves records where the application context is Receivables (PCK.APPLICATION = 'AR'), joining customer account, party, and site-use data. A second branch (the UNION) resolves records against the Payables supplier site (IGI_PO_VENDORS) context. This dual construction explains why SITE_CODE is sourced from either HZ_CUST_SITE_USES.LOCATION or IGI_PO_VENDORS.VENDOR_SITE_CODE depending on the originating application.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented base objects: IGI_STP_PACKAGES (the primary driver, supplying package, batch, transaction, amount, currency, and exchange rate attributes), IGI_STP_NET_TYPE_ALLOC (netting transaction type allocation), IGI_LOOKUPS (resolving netting type lookup meanings), HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_CUST_SITE_USES (customer name and site context), RA_CUST_TRX_TYPES (Receivables transaction types), GL_DAILY_CONVERSION_TYPES (currency conversion type definitions), FND_APPLICATION_VL (application name resolution), AP_SUPPLIER_SITES_ALL, IGI_PO_VENDORS, and AP_LOOKUP_CODES (Payables-side supplier and lookup context). The FND_GLOBAL package is referenced for session/context attributes. Because GL_DAILY_CONVERSION_TYPES is joined with an outer join ((+)) on NVL(PCK.EXCHANGE_RATE_TYPE,'X') = GL.CONVERSION_TYPE, exchange rate type lookups are preserved even when no matching conversion type exists.

Key Columns

Common Use Cases and Queries

Because the object exposes the USER_RATE_TYPE attribute alongside the stored EXCHANGE_RATE_TYPE, it is commonly queried to verify how currency conversions were resolved during settlement processing, or to reconcile the user-defined conversion type against the rate type actually stored on the package.

SELECT PACKAGE_NUM, TRX_NUMBER, CURRENCY_CODE,
       EXCHANGE_RATE_TYPE, USER_RATE_TYPE, EXCHANGE_RATE
FROM   APPS.IGI_STP_PACKAGES_V
WHERE  USER_RATE_TYPE = :p_rate_type;

Typical reporting scenarios include settlement package extracts by operating unit, netting transaction reporting, customer/supplier site reconciliation, and integration feeds into treasury or reconciliation systems. A representative query filters by org and accounting period:

SELECT ORG_ID, NETTING_TRX_TYPE, CUSTOMER_NAME, SITE_CODE,
       AMOUNT, CURRENCY_CODE, ACCOUNTING_DATE
FROM   APPS.IGI_STP_PACKAGES_V
WHERE  ORG_ID = :p_org_id
AND    ACCOUNTING_DATE BETWEEN :p_from AND :p_to
ORDER  BY ACCOUNTING_DATE;

Note that the view is granted to the APPS schema and is intended for read-only query access; reports and interfaces should treat it as a denormalized projection rather than a base table. Because the view performs DISTINCT aggregation across a multi-table join with a UNION, performance-sensitive extracts should filter aggressively on indexed columns such as ORG_ID, BATCH_ID, or PACKAGE_ID.