Results for “update_sequence”

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

Overview

FII_AP_INV_B is a table owned by the FII (Financial Intelligence) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores Accounts Payable summary information and exists specifically to support the AP (Accounts Payable) and POA (Payables, Operations, and Analytics) portlets delivered through the Financial Intelligence product. Rather than holding transactional invoice data at posting-level detail, FII_AP_INV_B functions as a pre-aggregated summary layer that has been denormalized and flattened to accelerate dashboard rendering for payables-related analytics.

The table contains 59 columns in the documented 12.1.1 schema, with a status of VALID. Its structure spans invoice header attributes, distribution-level detail flags, project and task references, and multi-currency amount fields, indicating that it consolidates information from both AP invoice headers and their associated distributions. This design lets portlet queries avoid expensive joins across the base transaction tables.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is link. This classification reflects the table's role as an intersection of multiple business entities — supplier sites, purchase order releases, expense report headers, employees, and companies — rather than a pure descriptive satellite or a standalone hub. Analysts modeling this domain in a Data Vault should treat FII_AP_INV_B as a connecting relationship carrying descriptive measures.

Key Information Stored

The most important columns fall into several logical groups. The surrogate primary key is INVOICE_ID, which uniquely identifies each summarized invoice record. Business-key candidates include INVOICE_NUM combined with SUPPLIER_ID and ORG_ID, since invoice numbers are only unique within a supplier and operating unit context.

• Amounts and currency: AMOUNT_B (base/ledger amount), AMOUNT_T (transaction amount), PRIM_AMOUNT_G and SEC_AMOUNT_G (primary and secondary ledger group amounts), plus INV_CURRENCY_CODE and TRANS_CURRENCY_CODE.
• Invoice identity and status: INVOICE_NUM, INVOICE_TYPE, INVOICE_DATE, SOURCE, POSTED_FLAG, and APPROVED_FLAG.
• Party references: SUPPLIER_ID, SUPPLIER_SITE_ID, COMPANY_ID, and EMPLOYEE_ID.
• Purchasing linkage: PO_HEADER_ID, PO_RELEASE_ID, PO_NUM, PO_DISTRIBUTION_ID, and PO_MATCHED_FLAG.
• Accounting and dimensions: SET_OF_BOOKS_ID, LEDGER_ID, DIST_CCID, CHART_OF_ACCOUNTS_ID, COST_CENTER_ORG_ID, COST_CENTER_ID, PROJECT_ID, TASK_ID, and USER_DIM1_ID / USER_DIM2_ID.
• Expense and audit: EXP_REPORT_HEADER_ID, AE_HEADER_ID, REF_AE_HEADER_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Common Use Cases and Queries

Because FII_AP_INV_B is a summary table, its primary use is reporting and portlet rendering rather than transaction processing. Typical scenarios include payables aging summaries, top supplier spend analysis, PO-matched versus non-matched invoice counts, and multi-ledger amount reconciliation.

A representative query for supplier spend by ledger might resemble the following pattern:

• SELECT SUPPLIER_ID, SUM(AMOUNT_B) FROM FII_AP_INV_B WHERE LEDGER_ID = :ledger GROUP BY SUPPLIER_ID;
• SELECT COUNT(*) FROM FII_AP_INV_B WHERE POSTED_FLAG = 'Y' AND APPROVED_FLAG = 'Y';
• SELECT PO_MATCHED_FLAG, SUM(AMOUNT_T) FROM FII_AP_INV_B WHERE INVOICE_DATE BETWEEN :start AND :end GROUP BY PO_MATCHED_FLAG;

Note that amount filtering should always be scoped by SET_OF_BOOKS_ID or LEDGER_ID in a multi-ledger environment, and by ORG_ID where operating unit security applies. Because the table is a summary, reconciliation users should treat it as an analytical aid, not as the system of record for payables balances.

Related Objects

The documented foreign key relationships define the most significant dependent objects:

• AP_EXPENSE_REPORT_HEADERS_ALL — joined via EXP_REPORT_HEADER_ID; links summarized invoices originating from expense reports.
• PO_RELEASES_ALL — joined via PO_RELEASE_ID; associates invoices with purchase order releases.
• PSB_EMPLOYEES — joined via EMPLOYEE_ID; resolves the employee associated with the summarized record.
• PN_COMPANIES_ALL — joined via COMPANY_ID; supplies company-level context.
• GL_MGT_SEG_UPGRADE_H — joined via CHART_OF_ACCOUNTS_ID; relates to chart of accounts upgrade history.
• AP base tables such as AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, and AP_SUPPLIERS are the natural upstream sources from which this summary is derived, even where an explicit FK is not documented.
• Financial Intelligence portlet views and the POA analytics layer consume this table directly to render payables dashboards.