Results for “funding_party”

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

Overview

OKE_POOL_PARTIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the OKE – Project Contracts product. Its documented description is "Funding pool parties view." The view consolidates the funding-party allocation records held against a project funding pool and enriches them with the descriptive names of the pool, the trading party, and the daily conversion type. In ETRM implementations on 12.1.1 and 12.2.2 the object carries a VALID status and is treated as a read-only presentation layer over the transactional funding pool party table.

The view is significant for users searching on the term "funding_party." The underlying column S.PARTY_ID is exposed through the view under the alias FUNDING_PARTY, so the view is the natural access point when a query or integration must resolve which party funds a given pool, how much of the pool that party has committed, and in what currency. In reporting terms it serves as the semantic layer that converts surrogate identifiers into human-readable names, removing the need for report authors to join OKE_POOL_PARTIES, OKE_FUNDING_POOLS, and HZ_PARTIES manually.

Underlying Base Objects

The view text joins four objects, each referenced through an APPS synonym. The driving table is OKE_POOL_PARTIES (aliased S), which stores one row per funding pool and party combination together with the financial amounts, currency, conversion attributes, and the standard WHO columns. OKE_FUNDING_POOLS (aliased F) is joined on FUNDING_POOL_ID = S.FUNDING_POOL_ID and supplies the pool name exposed as FUNDING_POOL_NAME. HZ_PARTIES (aliased H) is joined on S.PARTY_ID = H.PARTY_ID and supplies the party name exposed as FUNDING_PARTY. GL_DAILY_CONVERSION_TYPES (aliased G) is joined with an outer join on G.CONVERSION_TYPE (+) = S.CONVERSION_TYPE and supplies the display conversion type exposed as CONVERSION_TYPE_DISP.

The inner-join construction against OKE_FUNDING_POOLS and HZ_PARTIES means a pool party row is only returned when both the parent pool and the party record are present. Because the conversion type lookup is an outer join, rows with a null CONVERSION_TYPE are still returned, with CONVERSION_TYPE_DISP null.

Key Columns

• POOL_PARTY_ID – primary identifier of the pool party allocation record.
• FUNDING_POOL_ID / FUNDING_POOL_NAME – the pool identifier and its descriptive name from OKE_FUNDING_POOLS.
• PARTY_ID / FUNDING_PARTY – the party identifier and the corresponding HZ_PARTIES party name; FUNDING_PARTY is the column most often targeted by "funding party" searches.
• AMOUNT / INITIAL_AMOUNT / AVAILABLE_AMOUNT – the current committed amount, the originally allocated amount, and the remaining un-consumed balance for the party on the pool.
• CURRENCY_CODE – currency in which the amounts are denominated.
• CONVERSION_TYPE / CONVERSION_TYPE_DISP – the stored conversion type code and its user-facing description from GL_DAILY_CONVERSION_TYPES.
• CONVERSION_DATE / CONVERSION_RATE – the rate date and rate applied for currency conversion.
• START_DATE_ACTIVE / END_DATE_ACTIVE – the effective date range during which the funding party allocation is active.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard audit (WHO) columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – the descriptive flexfield columns available for client-specific data.
• ROW_ID – the row identifier derived from S.ROWID, typically used by Oracle Forms-based maintenance screens.

Common Use Cases and Queries

Typical uses include funding pool availability reporting, reconciliation of committed versus available balances per party, and integration extracts that feed downstream budgeting or project costing processes. Because the view already resolves names, it is well suited to concurrent-program extracts and BI Publisher data templates where no further joins are desired.

A representative query lists all funding parties for a pool:

• SELECT funding_pool_name, funding_party, amount, available_amount, currency_code FROM oke_pool_parties_v WHERE funding_pool_id = :p_pool_id;
• SELECT funding_party, SUM(available_amount) FROM oke_pool_parties_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE)) GROUP BY funding_party;
• SELECT pool_party_id, funding_party, conversion_type_disp, conversion_rate FROM oke_pool_parties_v WHERE currency_code <> 'USD';

The view is read-only; all maintenance is performed against OKE_POOL_PARTIES. Any custom reporting should filter on START_DATE_ACTIVE and END_DATE_ACTIVE to respect allocation validity windows.