Results for “ipa_task_interests_v”

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

Overview

IPA_TASK_INTERESTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the IPA (Capital Resource Logistics – Projects) product family. It exposes task-level interest configuration records used by Oracle Projects to determine how capitalized interest is calculated, applied, and tracked against individual project tasks. The view consolidates the task interest definition from IPA_TASK_INTERESTS with descriptive attributes from the project and task master tables, so that a single query returns the interest rate code, the effective date range, the capitalization flag, and the human-readable project and task identifiers. This denormalized shape makes the view suitable for both ad hoc reporting and integration extracts without requiring callers to re-implement the three-way join. In 12.1.1 and 12.2.2 the object is documented as VALID, confirming that its definition is compiled and available at runtime.

Underlying Base Objects

The view is defined over three referenced base objects, all exposed through synonyms in the APPS schema:

• IPA_TASK_INTERESTS — the driving table, aliased ITI, which stores the interest rule per task including RATE_CODE, EFFECTIVE_DATE_FROM, EFFECTIVE_DATE_TO, TASK_THRESHOLD, and CAPITALIZE_INTEREST.
• PA_PROJECTS_ALL — aliased PAP, joined on PROJECT_ID, supplying the project number via SEGMENT1.
• PA_TASKS — aliased PAT, supplying TASK_NUMBER and TASK_NAME and joined on both PROJECT_ID and TASK_ID.

The join predicate links PAT.PROJECT_ID to PAP.PROJECT_ID and ITI.TASK_ID to PAT.TASK_ID, so a row is returned only where the task interest record resolves to an existing task within an existing project. Because the view selects ROWID from IPA_TASK_INTERESTS as ROW_ID, it retains a stable identifier that can be used to identify the underlying task interest row in the base table.

Key Columns

• ROW_ID — the ROWID of the IPA_TASK_INTERESTS row; useful as a unique key for updates or drill-through.
• TASK_INTEREST_ID — the primary key of the task interest record.
• RATE_CODE — the interest rate identifier associated with the task.
• TASK_ID, TASK_NUMBER, TASK_NAME — the task key and its descriptive attributes.
• PROJECT_ID, PROJECT_NUMBER — the owning project key and project number (PAP.SEGMENT1).
• EFFECTIVE_DATE_FROM, EFFECTIVE_DATE_TO — the validity window during which the interest rule applies. Filtering on EFFECTIVE_DATE_FROM is the standard approach to isolate currently active or future-dated rules.
• CAPITALIZE_INTEREST — indicates whether interest is capitalized for the task.
• TASK_THRESHOLD — the threshold amount governing interest calculation.
• COMMENTS — free-text annotation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO columns for audit and change tracking.

Common Use Cases and Queries

Typical usage includes validating interest setup across projects, reporting active rate assignments as of a given date, and feeding downstream capitalization processes. A common query filters on the effective date window:

• SELECT task_interest_id, project_number, task_number, rate_code, capitalize_interest, effective_date_from, effective_date_to FROM apps.ipa_task_interests_v WHERE effective_date_from <= SYSDATE AND (effective_date_to IS NULL OR effective_date_to >= SYSDATE); — returns currently effective interest rules.
• SELECT project_number, task_number, rate_code, task_threshold FROM apps.ipa_task_interests_v WHERE capitalize_interest = 'Y' ORDER BY project_number, task_number; — lists tasks configured for interest capitalization.
• SELECT * FROM apps.ipa_task_interests_v WHERE last_update_date >= :p_since; — incremental audit extract using the WHO columns.