Results for “original_invoice_amount”

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

Overview

OKL_AM_RMK_BILLING_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined against the OKL (Leasing and Finance Management) product. The suffix "RMK" reflects its use in the Asset Management / remarketing billing flow. The view consolidates billing, asset return, order, contract, item, and accounts receivable data into a single denormalized result set, allowing reporting and integration consumers to retrieve invoice information tied to returned leased assets without joining the constituent base objects directly.

The view joins asset return records to the originating order line and order header, the associated lease contract, the inventory item definition, the consolidated AR invoice line, and the customer bill-to address. This makes it a convenient single source for inquiries that need to correlate a returned asset with the invoice generated against it, including both the invoice totals and the remaining outstanding balance from AR payment schedules.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKL_ASSET_RETURNS_ALL_B — asset return header information, driving the ART_ID and KLE_ID keys.
• OKL_K_LINES_FULL_V — the lease line view supplying asset name, description, and status (ASSET_NUMBER, ASSET_DESCRIPTION, STATUS).
• OKC_K_HEADERS_B — the contract header, providing CONTRACT_NUMBER.
• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — the originating sales order header and line, supplying ORDER_NUMBER, ORDERED_DATE, LINE_NUMBER, and INVENTORY_ITEM_ID.
• OKL_BPD_TLD_AR_LINES_V — the billing/AR line view (TLD_NEW) that supplies the invoice number, invoice amount, tax amount, line amount, invoice dates, customer transaction IDs, and the TOTAL_INVOICE_AMOUNT column.
• MTL_SYSTEM_ITEMS_B_KFV — the item key flexfield view, supplying ITEM_NUMBER, ITEM_NAME, and ITEM_DESCRIPTION.
• HZ_CUST_ACCT_SITES_ALL, HZ_PARTY_SITES, and HZ_LOCATIONS — the customer site and location hierarchy used to build the bill-to address columns.
• AR_PAYMENT_SCHEDULES_ALL — the AR payment schedule, supplying OUTSTANDING_INVOICE_AMOUNT via AMOUNT_LINE_ITEMS_REMAINING.
• ARP_ADDR_LABEL_PKG and OKL_BILLING_UTIL_PVT — PL/SQL packages referenced for address formatting and billing utility logic.

Key Columns

The view returns identifiers linking returned assets to invoices, including ART_ID, KLE_ID, ORDER_NUMBER, LINE_NUMBER, INVENTORY_ITEM_ID, CONTRACT_NUMBER, and LSM_ID (aliased from TLD_NEW.TLD_ID). Financial columns include INVOICE_AMOUNT, TOTAL_INVOICE_AMOUNT, TAX_AMOUNT, ORIGINAL_INVOICE_AMOUNT (the line amount), and OUTSTANDING_INVOICE_AMOUNT. Date columns are ORDERED_DATE, INVOICE_DATE, and BILL_DATE. Address columns expose individual bill-to components plus a formatted BILL_TO_FULL_ADDRESS generated via ARP_ADDR_LABEL_PKG.FORMAT_ADDRESS. AR linkage columns TRX_ID and TRX_LINE_ID map to CUSTOMER_TRX_ID and CUSTOMER_TRX_LINE_ID.

Common Use Cases and Queries

A frequent requirement is reconciling invoiced amounts against amounts still outstanding per returned asset. For example:

• SELECT ORDER_NUMBER, CONTRACT_NUMBER, ASSET_NUMBER, INVOICE_NUMBER, TOTAL_INVOICE_AMOUNT, OUTSTANDING_INVOICE_AMOUNT FROM APPS.OKL_AM_RMK_BILLING_UV WHERE CONTRACT_NUMBER = :p_contract;
• SELECT ASSET_NUMBER, SUM(TOTAL_INVOICE_AMOUNT) FROM APPS.OKL_AM_RMK_BILLING_UV GROUP BY ASSET_NUMBER;
• SELECT INVOICE_NUMBER, BILL_TO_FULL_ADDRESS FROM APPS.OKL_AM_RMK_BILLING_UV WHERE TRX_ID = :p_trx_id;

Because the user search term "total_invoice_amount" maps to TLD_NEW.AMOUNT, the view is commonly queried to report headline invoice totals alongside tax and outstanding balances for reporting extracts and reconciliation scripts.