Search Results group_party_name




Overview

INL_CHARGE_OVERALL_V is a reporting view owned by the APPS schema in Oracle Landed Cost Management (INL), a module that lets organizations estimate, accrue, and reconcile the landed cost of purchased goods. The view consolidates shipment header information, charge line detail, and charge-associated party data into a single denormalized result set. Its stated purpose, per the ETRM metadata, is to "show overall information on Charges."

Because it joins shipment-level attributes to the adjustment charge lines belonging to a shipment, the view is suited to operational reporting, reconciliation, and downstream integration. Reports and interfaces can query one object instead of joining INL_SHIP_HEADERS, INL_SHIP_LINE_GROUPS, INL_ADJ_CHARGE_LINES_V, and the HZ party tables directly. The view exposes the charge context together with supplier or party identification, which is why the search term "group_party_name" leads here — GROUP_PARTY_NAME is one of its exposed columns.

Underlying Base Objects

The ETRM 12.2.2 metadata records the following referenced base objects:

  • INL_SHIP_HEADERS — source of shipment header attributes such as SHIP_HEADER_ID, SHIP_NUM, SHIP_DATE, and SHIP_STATUS_CODE.
  • INL_SHIP_LINE_GROUPS — provides line group party identifiers through the outer join on SHIP_HEADER_ID.
  • INL_ADJ_CHARGE_LINES_V — the principal charge line view supplying CHARGE_LINE_ID, CHARGE_AMT, currency conversion details, and party identifiers.
  • INL_ASSOCIATIONS — used in the subquery that filters charge lines to those associated with the shipment header, matching on the parent charge line or charge line itself.
  • HZ_PARTIES and HZ_PARTY_SITES — outer-joined to resolve PARTY_ID and PARTY_SITE_ID into displayable names.

The joins are predominantly outer joins (the (+) operator), so charge lines are retained even where no party, party site, or line group has been assigned.

Key Columns

Common Use Cases and Queries

Typical uses include landed cost charge roll-ups by shipment, reconciliation of estimated versus invoiced charges, and extraction of charge records for tax or partner reporting. A query returning shipment charges with their party names:

  • SELECT ship_num, charge_line_num, charge_amt, currency_code, group_party_name FROM inl_charge_overall_v WHERE ship_header_id = :p_ship_header_id;
  • SELECT group_party_name, SUM(charge_amt) FROM inl_charge_overall_v WHERE org_id = :p_org_id GROUP BY group_party_name;
  • SELECT ship_num, charge_line_id, parent_charge_line_id, charge_amt FROM inl_charge_overall_v WHERE pending_matching_flag = 'Y';

Because INL_ADJ_CHARGE_LINES_V and the HZ objects are joined in the view definition, filters on GROUP_PARTY_NAME should be applied as outer-join-safe predicates where possible, and queries should be scoped by ORG_ID or SHIP_HEADER_ID to limit scan cost on large shipments.