Search Results invoice_base_amount

Overview

The IGI_CIS_INVOICE_PAYMENTS view is a public-sector reporting object owned by the APPS schema within the IGI (Public Sector Financials International) product family of Oracle E-Business Suite. As documented, its purpose is to display records of invoice payments coupled with Construction Industry Scheme (CIS) Payment Voucher details. It consolidates the payment-level accounting and cash information held in Oracle Payables with the CIS-specific voucher attributes captured by IGI, thereby presenting a single queryable structure for reporting and integration.

The view is registered as VALID and is preserved across both the 12.1.1 and 12.2.2 releases. Because it joins Payables payment data to CIS voucher data, it is primarily consumed by reporting layers, extracts, and third-party interfaces that must reconcile subcontractor payments with the vouchers issued under the CIS regime. The view is read-only in practice; the underlying transactional maintenance is performed against the base Payables tables and the IGI voucher tables, while this view supplies a denormalised projection for downstream consumption.

Underlying Base Objects

According to the ETRM metadata, the view is defined over two referenced base objects, both accessed through public synonyms:

• AP_INVOICE_PAYMENTS (SYNONYM) — the Oracle Payables table storing individual invoice payment records, aliased as AIP in the view text.
• IGI_CIS_PAYMENT_VOUCHERS (SYNONYM) — the IGI table holding CIS Payment Voucher details.

The view text is dominated by columns sourced from the AIP alias, indicating that the projection is anchored on the Payables invoice payment record and enriched by the CIS voucher. Columns such as INVOICE_PAYMENT_ID, INVOICE_ID, CHECK_ID, and ACCOUNTING_EVENT_ID establish the link to the payment and accounting events, while the CIS voucher contributes the scheme-specific context that distinguishes this view from a plain Payables payment extract.

Key Columns

The view exposes a broad set of accounting, cash, and descriptive attributes. Significant columns include:

• INVOICE_PAYMENT_ID, INVOICE_ID, CHECK_ID, PAYMENT_NUM, ACCOUNTING_EVENT_ID, ACCOUNTING_DATE, PERIOD_NAME, and SET_OF_BOOKS_ID — core identifiers linking the record to its payment, invoice, and accounting period.
• AMOUNT, INVOICE_BASE_AMOUNT, and PAYMENT_BASE_AMOUNT — the transaction and base-currency amounts.
• ACCTS_PAY_CODE_COMBINATION_ID, ASSET_CODE_COMBINATION_ID, GAIN_CODE_COMBINATION_ID, LOSS_CODE_COMBINATION_ID, and FUTURE_PAY_CODE_COMBINATION_ID — account code combinations used in the accounting entries. In the context of the searched term, LOSS_CODE_COMBINATION_ID identifies the Account Code Combination applied to exchange loss amounts arising from foreign-currency settlement of the payment, and should be joined to the accounting flexfield tables for descriptive reporting.
• DISCOUNT_TAKEN, DISCOUNT_LOST, EXCHANGE_RATE, EXCHANGE_RATE_TYPE, and EXCHANGE_DATE — discount and currency conversion detail.
• Flags such as ACCRUAL_POSTED_FLAG, CASH_POSTED_FLAG, POSTED_FLAG, and FUTURE_PAY_POSTED_FLAG, together with JE_BATCH_ID and CASH_JE_BATCH_ID, indicate posting status and journal batch linkage.
• ORG_ID — supporting Multi-Org access control, and the ATTRIBUTE1 through ATTRIBUTE15 plus GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE20 descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include reconciling CIS payment vouchers to posted Payables payments, analysing exchange gain and loss postings, and extracting voucher-level detail for statutory reporting. The following sample query identifies payments where an exchange loss code combination was applied within a given period:

SELECT invoice_payment_id, invoice_id, payment_num, amount,
       loss_code_combination_id, period_name
  FROM igi_cis_invoice_payments
 WHERE loss_code_combination_id IS NOT NULL
   AND period_name = :period_name;

A second common pattern lists unposted CIS payments for reconciliation:

SELECT payment_num, accounting_date, amount, cash_posted_flag
  FROM igi_cis_invoice_payments
 WHERE posted_flag = 'N';

Because the view surfaces code combination identifiers rather than descriptive accounting flexfield strings, queries that require account descriptions should additionally join the code combination and flexfield value tables on the relevant *_CODE_COMBINATION_ID column. Filtering by ORG_ID is recommended wherever Multi-Org security applies.