Results for “ipa_interest_batch_details”

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

Overview

IPA_INTEREST_BATCH_DETAILS is a transactional detail table within the IPA (Capital Resource Logistics – Projects) product family of Oracle E-Business Suite. Its documented purpose is to store the source expenditure lines on which a calculated interest amount is based. Each row represents a single expenditure item that contributed to an interest calculation run and captures the rate, period, and amount applied to that item.

The table functions as a child (line-level) table to a batch header structure. The parent batch record is referenced through the INTEREST_BATCH_ID foreign key, which points to AR_INTEREST_BATCHES_ALL. Each individual source expenditure item is referenced through EXPENDITURE_ITEM_ID, which points to PA_EXPENDITURE_ITEMS_ALL. This places the table at the intersection of interest processing and project expenditure accounting.

From a Data Vault modeling perspective, the heuristic classification supplied with the metadata is standalone. In practical terms the table behaves as a detail or link-style structure: it connects a batch (INTEREST_BATCH_ID) to an expenditure item (EXPENDITURE_ITEM_ID) while carrying descriptive attributes such as RATE_APPLIED, PERIOD, and EXPENDITURE_AMOUNT. Analysts designing a dimensional or vault model should treat it as a link between the batch hub and the expenditure item hub, with the remaining numeric and code columns as satellite-style attributes.

Key Information Stored

The table contains ten documented columns. The most significant are:

• INTEREST_BATCH_DETAIL_ID – The surrogate primary key for each detail row. It is the sole business-key candidate, enforced by unique index IPA_INTEREST_BATCH_DETAILS_U1.
• INTEREST_BATCH_ID – Foreign key to AR_INTEREST_BATCHES_ALL, identifying the interest batch or calculation run that produced this line.
• EXPENDITURE_ITEM_ID – Foreign key to PA_EXPENDITURE_ITEMS_ALL, identifying the source expenditure item against which interest was computed.
• EXPENDITURE_AMOUNT – The expenditure amount used as the basis for the interest calculation on this line.
• RATE_APPLIED – The interest rate actually applied to the expenditure amount.
• RATE_CODE – The rate code identifying which rate schedule or rate definition was used.
• INTEREST_RATE_TYPE – Classifies the type of interest rate applied, supporting differentiation between rate methodologies.
• INTEREST_TYPE – Categorizes the nature of the interest being calculated.
• PERIOD – The accounting or interest period to which the calculation line belongs.
• SOURCE_TASK_ID – Identifies the project task associated with the source expenditure, enabling task-level traceability.

The surrogate key (INTEREST_BATCH_DETAIL_ID) is system-generated, whereas the unique index establishes it as the enforced business key. All remaining columns are attribute or foreign-key columns.

Common Use Cases and Queries

Typical reporting scenarios include reconciling interest calculated back to the originating expenditure items, auditing rate application by period, and tracing batch totals to their component detail lines.

A common pattern joins the detail table to its parent batch and to the expenditure item:

• Join IPA_INTEREST_BATCH_DETAILS.INTEREST_BATCH_ID = AR_INTEREST_BATCHES_ALL.INTEREST_BATCH_ID to retrieve batch-level context.
• Join IPA_INTEREST_BATCH_DETAILS.EXPENDITURE_ITEM_ID = PA_EXPENDITURE_ITEMS_ALL.EXPENDITURE_ITEM_ID to obtain project, task, and expenditure type information.
• Aggregate EXPENDITURE_AMOUNT and RATE_APPLIED grouped by PERIOD and INTEREST_TYPE to produce interest accrual summaries.
• Filter by RATE_CODE or INTEREST_RATE_TYPE to analyze exposure to specific rate schedules.

Typical SQL shape: select the batch ID, expenditure item ID, expenditure amount, rate applied, and period, filtered by a specific interest batch or period range, and summed for control totals against the parent batch record.

Related Objects

• AR_INTEREST_BATCHES_ALL – Parent header table; joined on INTEREST_BATCH_ID.
• PA_EXPENDITURE_ITEMS_ALL – Source expenditure item table; joined on EXPENDITURE_ITEM_ID.
• PA_EXPENDITURE_ITEMS_ALL (task context) – Used alongside SOURCE_TASK_ID for task-level analysis.
• IPA_INTEREST_BATCH_DETAILS_U1 – Unique index enforcing the primary business key.
• IPA interest calculation and processing routines that populate this table during interest batch runs.

Because the table is classified as standalone in the mined relationship data, it holds no child tables of its own; all dependencies flow upward to the batch and expenditure item parents.