Search Results adjustment_num

Overview

GMF_LC_ADJ_DETAILS_V is a reporting view owned by the APPS schema within the Process Manufacturing Financials (GMF) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes detailed information for each actual Landed Cost (LC) adjustment processed through the Oracle Inventory Landed Cost and matching infrastructure, and is primarily consumed to reconcile landed cost adjustments against their originating payables invoices, invoice lines, and invoice distributions. The view resolves the association between an adjustment record in INL_ALLOCATIONS and the underlying matching entity — a charge line, a tax line, or a ship line — and surfaces the corresponding supplier invoice detail so that users can determine which invoice document caused a given landed cost adjustment.

The view also computes a derived CURRENT_ADJUSTMENT_FLAG using nested DECODE logic, comparing the adjustment number against related charge lines, tax lines, and sibling ship lines. This flag allows reporting to distinguish the currently effective adjustment from superseded or replacement adjustments on the same shipment structure.

Underlying Base Objects

The view is defined over eight documented base objects, all referenced through APPS synonyms:

• INL_ALLOCATIONS — source of adjustment records (adjustment number, ship header, ship line, source table name and ID).
• INL_CHARGE_LINES — landed cost charge lines, joined on CHARGE_LINE_ID and MATCH_AMOUNT_ID to resolve charge-based adjustments.
• INL_TAX_LINES — tax lines, joined on TAX_LINE_ID and MATCH_AMOUNT_ID for tax-based adjustments.
• INL_SHIP_LINES_ALL — ship lines, used three times (SL, SL2, SLP) to resolve parent/child ship line relationships and MATCH_ID linkage.
• INL_MATCHES — the matching record that ties an allocation to an invoice distribution.
• AP_INVOICES_ALL, AP_INVOICE_LINES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL — the Payables invoice header, line, and distribution detail providing invoice number, date, party, currency, and distributed amount.

The join path is driven by INL_ALLOCATIONS.FROM_PARENT_TABLE_NAME, which conditionally routes to INL_CHARGE_LINES, INL_TAX_LINES, or INL_SHIP_LINES. Outer joins (+) are applied to SL2, TL, and CL so that rows are retained when the adjustment does not reference a particular entity type.

Key Columns

• PARENT_SHIP_LINE_ID — NVL of the ship line's parent ID; provides a normalized grouping key across sibling lines.
• ADJUSTMENT_NUM — the landed cost adjustment identifier.
• CURRENT_ADJUSTMENT_FLAG — derived Y/N indicator of whether the adjustment is current for the ship line group.
• SHIP_HEADER_ID, SHIP_LINE_GROUP_ID, SHIP_LINE_ID — shipment hierarchy identifiers.
• MATCH_ID, ADJ_GROUP_DATE, FROM_PARENT_TABLE_NAME, FROM_PARENT_TABLE_ID — matching linkage and adjustment grouping date.
• INVOICE_NUM, INVOICE_DATE, PARTY_ID, PARTY_SITE_ID — supplier invoice identity and party information.
• INVOICE_LINE_NUMBER, INVOICE_DISTRIBUTION_ID, INVOICE_DISTR_AMT, INVOICE_CURRENCY_CODE — invoice line and distribution detail, including the distributed amount and currency used for landed cost valuation.

Common Use Cases and Queries

Typical reporting scenarios include tracing landed cost adjustments back to the supplier invoice that generated them, listing all adjustments for a shipment, and identifying current versus superseded adjustments. The following query lists current adjustments with their invoice detail:

• SELECT adjustment_num, ship_header_id, ship_line_id, invoice_num, invoice_date, invoice_distr_amt, invoice_currency_code FROM apps.gmf_lc_adj_details_v WHERE current_adjustment_flag = 'Y';
• SELECT parent_ship_line_id, adjustment_num, from_parent_table_name, match_id FROM apps.gmf_lc_adj_details_v WHERE ship_header_id = :p_ship_header_id ORDER BY parent_ship_line_id, adjustment_num;
• SELECT invoice_num, SUM(invoice_distr_amt) FROM apps.gmf_lc_adj_details_v WHERE current_adjustment_flag = 'Y' GROUP BY invoice_num;

Because the view spans Payables and landed cost tables, queries against it may perform poorly without filters on SHIP_HEADER_ID, PARENT_SHIP_LINE_ID, or ADJUSTMENT_NUM. The three-way self-join on INL_SHIP_LINES_ALL and the conditional DECODE joins warrant the use of targeted predicates in production reporting.