Search Results line_var_amount

Overview

CST_AP_VARIANCE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the BOM (Bills of Material) product family. It consolidates Accounts Payable invoice price variances against the cost layers and purchase order distributions that generated them, joining variance header, line, and batch records to purchasing, receiving, inventory, and payables data. The view serves as the primary denormalized source for investigating purchase price variance (PPV) at the batch, invoice, and item level.

Because the view exposes BATCH_ID adjacent to CAVB.DESCRIPTION, it directly supports the user search term batch_description: the batch description is the human-readable label for a cost adjustment batch created when AP variances are processed. Analysts use this view to trace how a specific invoice variance batch flowed into inventory valuation, accrual balances, and project costs.

Underlying Base Objects

The view joins core variance tables with transactional and master data. Documented base objects include:

• CST_AP_VARIANCE_HEADERS (CAVH) and CST_AP_VARIANCE_LINES (CAVL) — the variance transaction header and line records, supplying variance amounts, transaction dates, and IDs.
• CST_AP_VARIANCE_BATCHES (CAVB) — the batch summary providing DESCRIPTION and ADJUSTMENT_ACCOUNT.
• CST_QUANTITY_LAYERS (CQL) — the inventory cost layer matched by item, organization, and cost group, supplying layer quantity and item cost.
• PO_DISTRIBUTIONS (PDA), PO_LINE_LOCATIONS_ALL (PLLA), PO_LINES_ALL (PLA), PO_HEADERS_ALL (PHA) — the purchasing chain resolving PO number, line, and distribution.
• AP_INVOICES_ALL (AIA) — invoice number for the matched variance.
• MTL_TRANSACTIONS_INTERFACE (MTI) and MTL_TXN_COST_DET_INTERFACE (MTCDI) — transaction and cost detail interface rows supplying transaction date and value change.
• CST_COST_GROUPS (CCG), ORG_ORGANIZATION_DEFINITIONS (OOD), and PA_PROJECTS_ALL (PPA, outer-joined) — cost group, organization code, and project context.

The view also references HR_GENERAL and HR_SECURITY packages internally, consistent with organization security enforcement.

Key Columns

• BATCH_ID / DESCRIPTION — batch identifier and its description, the primary search target.
• VARIANCE_HEADER_ID / VARIANCE_LINE_ID — unique variance transaction identifiers.
• HEADER_VAR_AMOUNT / LINE_VAR_AMOUNT — variance value at header and line granularity.
• CURRENT_QUANTITY / CURRENT_ITEM_COST — cost layer quantity and unit cost.
• VALUE_CHANGE / PCNT_VALUE_CHANGE — absolute and percentage change in layer value.
• PO_NUMBER, PO_LINE_NUM, PO_DISTRIBUTION_NUM, INVOICE_NUM, INVOICE_DIST_LINE_NUM — full purchasing-to-payables linkage.
• ORGANIZATION_CODE, COST_GROUP, PROJECT_NUMBER, ACCRUAL_ACCOUNT_ID, ADJUSTMENT_ACCOUNT — accounting and organizational context.

Common Use Cases and Queries

Typical uses include batch-level variance auditing, PPV reconciliation to AP invoices, and cost layer revaluation analysis.

Locate a variance batch by its description:

SELECT batch_id, description, organization_code, cost_group,
       header_var_amount, transaction_date
FROM   apps.cst_ap_variance_v
WHERE  description LIKE '%'||:batch_description||'%';

Reconcile PPV to an invoice:

SELECT invoice_num, po_number, po_line_num, current_quantity,
       current_item_cost, value_change, pcnt_value_change
FROM   apps.cst_ap_variance_v
WHERE  invoice_num = :invoice_num
ORDER  BY variance_line_id;

Report total variance by batch and organization:

SELECT batch_id, description, organization_code,
       SUM(header_var_amount) total_variance
FROM   apps.cst_ap_variance_v
GROUP  BY batch_id, description, organization_code;