Results for “child_order_line_id”

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

Overview

FII_AR_REVENUE_B is a base summary table owned by the FII (Financial Intelligence) schema within Oracle E-Business Suite. Its documented purpose is to store summarized Receivables revenue data that supports revenue-related portlets delivered through the Financial Intelligence product. In EBS 12.1.1 and 12.2.2, the table functions as a denormalized aggregation layer that consolidates revenue facts from Receivables and adjacent modules, enabling dashboard and portlet queries to return results without executing the full transactional join path against Oracle Receivables base tables.

The table is documented as a standalone object based on a heuristic Data Vault classification mined from its foreign key structure. No parent hub or link relationship is enforced through the FK graph, so a Data Vault modeling suggestion would treat FII_AR_REVENUE_B as a self-contained satellite-like structure, or, given the presence of AMOUNT_T, AMOUNT_B, and the two global amount columns, as a pre-aggregated fact table. The absence of strict FK dependencies on its immediate sources supports ETL-style population independent of referential enforcement on the source side.

Key Information Stored

The physical schema documented for 12.1.1 contains 42 columns. The surrogate primary key is REVENUE_PK, enforced by the unique index FII_AR_REVENUE_B_U1, which is the only documented unique index and therefore the sole business-key candidate at the physical level. The most significant columns fall into four groups:

• Ledger and organization context: SET_OF_BOOKS_ID, LEDGER_ID, OPERATING_UNIT_ID, ORGANIZATION_ID, and ITEM_ORGANIZATION_ID establish the accounting and inventory context for each revenue record.
• Source document references: INVOICE_ID, INVOICE_LINE_ID, ORDER_LINE_ID, CHILD_ORDER_LINE_ID, INVOICE_NUMBER, and ORDER_NUMBER link the summary row back to the originating Receivables invoice and Order Management line.
• Dimensional attributes: BILL_TO_PARTY_ID, INVENTORY_ITEM_ID, TOP_MODEL_ITEM_ID, PROD_CATEGORY_ID, FIN_CATEGORY_ID, FIN_CAT_TYPE_CODE, SALES_CHANNEL, TRANSACTION_CLASS, COMPANY_ID, COST_CENTER_ID, and COMPANY_COST_CENTER_ORG_ID provide the slicing dimensions used by revenue portlets.
• Measures and accounting metadata: AMOUNT_T, AMOUNT_B, PRIM_AMOUNT_G, and SEC_AMOUNT_G hold transaction and ledger currency amounts; GL_DATE, GL_DATE_ID, INVOICE_DATE, and REV_BOOKED_DATE carry the relevant dates; POSTED_FLAG, FUNCTIONAL_CURRENCY, and TRANSACTION_CURRENCY complete the financial context.

Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, UPDATE_SEQUENCE) support incremental extraction. CHART_OF_ACCOUNTS_ID, COMPANY_ID, and INVOICE_LINE_ID carry documented foreign keys.

Common Use Cases and Queries

Typical usage centers on revenue portlet rendering and period-over-period revenue reporting. A representative query aggregates booked revenue by ledger and GL period:

• SELECT ledger_id, TRUNC(gl_date,'MM') gl_month, SUM(amount_b) FROM fii.fii_ar_revenue_b WHERE posted_flag = 'Y' GROUP BY ledger_id, TRUNC(gl_date,'MM');
• Revenue by customer and product category: join BILL_TO_PARTY_ID to customer master and PROD_CATEGORY_ID to the product dimension, filtering on TRANSACTION_CLASS.
• Drill-down from a portlet summary to invoice detail using INVOICE_ID and INVOICE_LINE_ID.
• Incremental loads keyed on LAST_UPDATE_DATE and UPDATE_SEQUENCE for warehouse refresh routines.

Related Objects

Documented foreign keys establish three direct relationships:

• FII_AR_REVENUE_B.INVOICE_LINE_ID → FTE_INVOICE_LINES, linking summary rows to the invoice line staging structure used by Financial Intelligence extraction.
• FII_AR_REVENUE_B.COMPANY_ID → PN_COMPANIES_ALL, resolving the company dimension used in portlet filtering.
• FII_AR_REVENUE_B.CHART_OF_ACCOUNTS_ID → GL_MGT_SEG_UPGRADE_H, supporting chart-of-accounts mapping during upgrade and migration handling.

Beyond documented FK paths, the table logically depends on Receivables transaction tables (RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL) via INVOICE_ID and INVOICE_LINE_ID, on GL_JE_LINES or GL_BALANCES for ledger currency amounts tied to SET_OF_BOOKS_ID and LEDGER_ID, and on Order Management tables referenced through ORDER_LINE_ID. The related staging companion table FII_AR_REVENUE_T is commonly referenced in Financial Intelligence ETL flows.