Search Results inl_ship_statuses




Overview
Explore in AI Chat

Overview

APPS.INL_CHARGE_OVERALL_V is a supplementary database view in the Oracle E-Business Suite ETRM (Enterprise Trade and Transportation Management) module, owned by the APPS schema and registered under FND Design Data as INL.INL_CHARGE_OVERALL_V. Its status is VALID in both 12.1.1 and 12.2.2 environments. Oracle classifies this view as a "supplementary view used to simplify forms coding," which means it was created primarily to consolidate charge, shipment, and party information into a single denormalized structure that Oracle Forms-based ETRM screens can query efficiently without embedding complex joins.

A critical caveat accompanies this classification: Oracle explicitly warns that this is not a supported public interface. Customers are advised not to query or alter data through the view, since its definition may change materially between minor or major releases. In practice, organizations use it for read-only diagnostics, ad-hoc reporting, and data extraction, but production integrations should rely on documented open interfaces or base tables instead.

Underlying Base Objects

The view is defined over a documented set of referenced objects. These include the synonym INL_SHIP_HEADERS, which supplies shipment-level attributes; INL_SHIP_LINE_GROUPS, which provides line group and party associations; INL_ASSOCIATIONS, which links shipments to charge structures; and the nested view INL_ADJ_CHARGE_LINES_V, which contributes charge line detail. Party master data is sourced from the HZ_PARTIES and HZ_PARTY_SITES synonyms, providing group party names, party site names, and identifiers. The join of shipment headers, line groups, associations, party records, and charge lines is what allows the view to present a single row per charge line enriched with both shipment and trading-party context.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling shipment charges against landed cost, auditing unmatched or pending matches, and extracting charge detail by trading partner. Because SHIP_STATUS_CODE draws from INL_SHIP_STATUSES, analysts frequently join to that lookup for descriptive status text.

SELECT v.ship_num,
       v.ship_date,
       v.ship_status_code,
       f.meaning AS ship_status,
       v.charge_line_num,
       v.charge_amt,
       v.currency_code,
       v.landed_cost_flag,
       v.group_party_name
FROM   apps.inl_charge_overall_v v,
       fnd_lookup_values f
WHERE  f.lookup_type = 'INL_SHIP_STATUSES'
AND    f.lookup_code = v.ship_status_code
AND    f.language = USERENV('LANG')
AND    v.org_id = :p_org_id
AND    v.ship_date BETWEEN :p_from AND :p_to;

This query returns shipment status descriptions alongside charge line amounts, enabling cost audits by operating unit and date range. All access should be read-only given Oracle's support restrictions on the view.