Search Results cst_lc_adj_interface_v




Overview
Explore in AI Chat

Overview

The CST_LC_ADJ_INTERFACE_V view, owned by the APPS schema, is a reporting and integration construct within the BOM – Bills of Material product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, human-readable projection of the landed cost adjustment interface transactions held in the base table CST_LC_ADJ_INTERFACE. Landed cost adjustments represent changes to the acquisition cost of received inventory, typically caused by freight, duty, insurance, or other charges applied after the original receipt. The base interface table stores these adjustments in a raw form keyed by internal identifiers, while the view resolves those identifiers against receipt, purchasing, inventory, and organization tables to expose descriptive attributes such as PO number, line number, receipt number, item description, and organization code.

Because the view exposes the descriptive PO_LINE_NUM column alongside the surrogate PO_LINE_ID, it is frequently used when analysts search for purchasing line references in the context of landed cost processing. The view is read-only and is intended for query and reporting rather than for inserting adjustment records.

Underlying Base Objects

The view is defined over a join of the landed cost interface table and a set of reference objects. The documented base objects are:

All joins are inner joins on the corresponding identifier columns, so an adjustment transaction is only visible when its related receipt, PO, item, and organization rows all exist and match.

Key Columns

The view returns both the raw interface columns and the joined descriptive columns. Important columns include:

Common Use Cases and Queries

Typical scenarios include auditing landed cost adjustments by PO line, reconciling prior versus new landed cost by receipt, and monitoring processing phase and status for pending or failed interface records. A representative query locating adjustments for a specific PO line is shown below.

SELECT organization_code,
       po_number,
       po_line_num,
       receipt_num,
       item_description,
       prior_landed_cost,
       new_landed_cost,
       process_status_meaning,
       process_phase_meaning
  FROM apps.cst_lc_adj_interface_v
 WHERE po_line_num = :p_line_num
   AND organization_code = :p_org_code
 ORDER BY transaction_id;

To review adjustments awaiting or pending processing, filter on the decoded status meaning:

SELECT transaction_id, po_number, po_line_num, receipt_num,
       process_status_meaning, creation_date
  FROM apps.cst_lc_adj_interface_v
 WHERE process_status_meaning <> 'Processed'
 ORDER BY creation_date DESC;

Because the view joins multiple receiving, purchasing, and inventory objects, queries should be constrained by organization, PO, or date wherever possible to limit the joined result set.