Results for “ipa_interest_batches_v”

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

Overview

The IPA_INTEREST_BATCHES_V view is a valid database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides within the IPA — Capital Resource Logistics — Projects product family, which governs capitalized interest processing for capital projects. The view presents a denormalized, reporting-ready representation of interest batch records by joining the interest batch base table to project and task master data. Its principal purpose is to expose the INTEREST_BATCH_ID and its associated descriptive context—project number, task number, task name, rate type, applied interest amount, processing status, GL period, and period boundary dates—in a single queryable object, sparing report developers and integrators from writing repetitive multi-table joins.

Underlying Base Objects

The view is defined over three documented base objects:

• IPA_INTEREST_BATCHES (synonym) — the driving table, aliased IB, supplying all batch-level interest attributes.
• PA_PROJECTS (synonym) — aliased P, joined on P.PROJECT_ID = IB.PROJECT_ID to supply the project segment value (PROJECT_NUMBER).
• PA_TASKS (synonym) — aliased T, joined on T.TASK_ID = IB.EXPENDITURE_TASK_ID to supply task number and task name.

The view text performs inner joins across all three sources, so a row is only returned where the project and expenditure task references resolve successfully. Because the two PA tables are join-only participants, the view is read-mostly in nature and should not be used for DML; interest batch maintenance is performed against IPA_INTEREST_BATCHES directly.

Key Columns

• INTEREST_BATCH_ID — the unique identifier of the interest batch row; the primary key exposed by the view and the value most commonly supplied in user searches.
• BATCH_ID — the parent batch identifier grouping related interest processing runs.
• PROJECT_ID / PROJECT_NUMBER — the project surrogate key and its user-facing segment value from PA_PROJECTS.
• RATE_TYPE — the interest rate classification applied to the batch.
• INTEREST_APPLIED — the interest amount calculated and applied for the batch.
• STATUS — processing state of the batch, typically indicating whether interest has been applied, reversed, or is pending.
• GL_PERIOD — the General Ledger period to which the interest accounting belongs.
• PERIOD_BEGIN_DATE / PERIOD_END_DATE — the inclusive date range over which interest accrual is computed.
• EXPENDITURE_ITEM_DATE — the expenditure item date driving the interest calculation.
• EXPENDITURE_TASK_ID / TASK_NUMBER / TASK_NAME — the task key and its descriptive identifiers from PA_TASKS.
• REVERSAL_DATE — the date on which the interest batch was reversed, where applicable.

Common Use Cases and Queries

Typical usage includes reconciliation of capitalized interest by project and task, GL period reporting, reversal tracking, and downstream integration extracts. Because the view already resolves project and task descriptions, it is convenient for ad hoc reporting and BI data sources.

Retrieve a single batch by identifier:

• SELECT interest_batch_id, batch_id, project_number, task_number, task_name, rate_type, interest_applied, status, gl_period, period_begin_date, period_end_date, reversal_date FROM apps.ipa_interest_batches_v WHERE interest_batch_id = :p_batch_id;

List all applied interest for a project within a GL period:

• SELECT interest_batch_id, task_number, task_name, rate_type, interest_applied, status FROM apps.ipa_interest_batches_v WHERE project_number = :p_project_number AND gl_period = :p_gl_period AND status = 'APPLIED' ORDER BY task_number;

Identify reversed batches over a date range:

• SELECT interest_batch_id, project_number, task_number, reversal_date, interest_applied FROM apps.ipa_interest_batches_v WHERE reversal_date BETWEEN :p_from_date AND :p_to_date;