Results for “ipa_project_interests_v”

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

Overview

IPA_PROJECT_INTERESTS_V is a concurrent-processing reporting view defined in the APPS schema of Oracle E-Business Suite. It is owned by the IPA (Capital Resource Logistics – Projects) product and exposes capital interest configuration records established against projects. The view is classified as VALID in the documented ETRM 12.2.2 metadata and is also documented for 12.1.1 environments, where the underlying IPA implementation is unchanged.

The view presents one row for each project interest definition stored in the IPA_PROJECT_INTERESTS entity, enriched with descriptive project attributes drawn from PA_PROJECTS_ALL. Its principal role is to provide a denormalized, reporting-friendly projection of capital interest setups — specifically the rate code applied, the interest capitalization flag, the threshold amount, and the effective period bounded by EFFECTIVE_DATE_FROM and EFFECTIVE_DATE_TO. Because it joins the operational interest table to the project definition, it allows report authors and integrators to display project number and project name alongside the interest parameters without writing the join themselves.

Underlying Base Objects

The view is defined over two documented base objects:

• IPA_PROJECT_INTERESTS (accessed via synonym) — the primary transactional entity holding capital interest definitions, including the effective dating columns and the threshold and capitalization attributes.
• PA_PROJECTS_ALL (accessed via synonym) — the Oracle Projects project definition table, supplying SEGMENT1 (project number) and NAME (project name).

The join condition is IPI.PROJECT_ID = PAP.PROJECT_ID, an inner equi-join on PROJECT_ID. Because PA_PROJECTS_ALL contains projects across all operating units and organizations, the view returns interest records for every project that has at least one matching PA_PROJECTS_ALL row. The view does not filter by date, organization, or project status; all such filtering must be applied by the consuming query. Note that PA_PROJECTS_ALL is the _ALL variant, so the view is not restricted by any function-based security applied at the view level.

Key Columns

• ROW_ID — the ROWID of the IPA_PROJECT_INTERESTS row, used for row identification and locking.
• PROJECT_INTEREST_ID — primary key of the interest record.
• RATE_CODE — the interest rate code assigned to the project interest setup.
• PROJECT_ID — foreign key to the project.
• PROJECT_NUMBER / PROJECT_NAME — SEGMENT1 and NAME from PA_PROJECTS_ALL, providing human-readable project identification.
• CAPITALIZE_INTEREST — flag indicating whether interest is capitalized for the project.
• EFFECTIVE_DATE_FROM / EFFECTIVE_DATE_TO — the effective date range of the interest definition; these columns are the standard filter for point-in-time reporting.
• THRESHOLD_AMOUNT — the monetary threshold governing interest calculation.
• COMMENTS — free-text annotation on the interest record.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include determining which interest rate and threshold are in force for a project as of a given date, auditing capitalization settings, and feeding downstream reporting or extracts.

Example: current effective interest setups

• SELECT project_number, project_name, rate_code, threshold_amount, effective_date_from, effective_date_to FROM ipa_project_interests_v WHERE SYSDATE BETWEEN effective_date_from AND NVL(effective_date_to, SYSDATE + 1);

Example: point-in-time lookup for a specific project

• SELECT project_number, rate_code, capitalize_interest, threshold_amount FROM ipa_project_interests_v WHERE project_number = :project_number AND :as_of_date BETWEEN effective_date_from AND NVL(effective_date_to, :as_of_date);

Example: capitalization audit

• SELECT project_number, project_name, effective_date_from, effective_date_to FROM ipa_project_interests_v WHERE capitalize_interest = 'Y' ORDER BY project_number, effective_date_from;

Queries should always supply an effective-date predicate, since multiple interest records can exist per project over time. Reports should also consider project organization security separately, as the view itself applies none.