Results for “inl_ship_lines”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.INL_ADJ_ASSOCIATIONS_V is a reporting and integration view in the Oracle E-Business Suite (EBS) Logistics and Transportation module (ETRM — formerly Oracle Transportation Management integration, distributed as part of the shipping and trade compliance stack). It exposes association records held in the INL_ASSOCIATIONS base table while resolving the polymorphic parent identifiers into concrete, single-table primary keys. In the EBS 12.1.1 and 12.2.2 data models, associations express relationships between shipping, charge, and tax line entities, and this view collapses those generic association rows into a form that is directly joinable to the adjustment and detail views.

The view is significant because INL_ASSOCIATIONS stores from_parent_table_name and to_parent_table_name as descriptive labels (for example, INL_SHIP_LINES, INL_CHARGE_LINES, INL_TAX_LINES) paired with generic numeric parent IDs. Consumers that need the concrete adjusted line identifier — such as the ship line, charge line, or tax line — rely on this view to perform the DECODE-based resolution, making it the natural access point for reporting on trade compliance tax associations and inter-entity adjustments.

Underlying Base Objects

The view is defined over INL_ASSOCIATIONS, which supplies the association header attributes (association_id, ship_header_id, source and target parent table names and IDs, allocation basis, and allocation UOM). The DECODE logic additionally references the adjustment detail views INL_ADJ_SHIP_LINES_V, INL_ADJ_CHARGE_LINES_V, and INL_ADJ_TAX_LINES_V, and the base tables INL_CHARGE_LINES and INL_SHIP_LINES_ALL (and INL_TAX_LINES), using hierarchical CONNECT BY queries against parent_ship_line_id, parent_charge_line_id, and parent_tax_line_id to resolve leaf/summary relationships.

Documented base objects include the synonyms INL_ASSOCIATIONS, INL_CHARGE_LINES, INL_SHIP_LINES_ALL, and INL_TAX_LINES. The view therefore acts as a semantic bridge: it takes the generic association tuples and returns the concrete line-level keys required by downstream consuming code.

Key Columns

• association_id — Primary identifier of the association record, carried directly from INL_ASSOCIATIONS.
• ship_header_id — The shipment header to which the association belongs, the primary grouping key for reporting.
• from_parent_table_name / to_parent_table_name — Labels identifying the source and target entity type (ship line, charge line, or tax line).
• from_parent_table_id — Resolved source line identifier; the DECODE returns ship_line_id, charge_line_id, or tax_line_id based on the table name, falling back to the original ID.
• to_parent_table_id — Resolved target line identifier, resolved analogously for the source side and, on the target side, through NVL and hierarchy traversal.
• allocation_basis / allocation_uom_code — Describe how amounts are apportioned across associated lines and the unit of measure governing that allocation.

The INL_TAX_LINES branch is the one that surfaces tax_line_id, which is why searches for that column land on this view.

Common Use Cases and Queries

Typical usage includes reconcile reports tracing which tax lines are associated with a given shipment or charge line, trade compliance audits, and integration feeds that must flatten polymorphic associations to concrete keys. A representative query filtering on the tax association is:

SELECT association_id, ship_header_id, from_parent_table_id, to_parent_table_id, allocation_basis FROM apps.inl_adj_associations_v WHERE from_parent_table_name = 'INL_TAX_LINES';

Because the resolution logic embeds scalar subqueries with ROWNUM constraints and CONNECT BY traversal, queries should generally be constrained by association_id, ship_header_id, or table-name filters to avoid unnecessary hierarchy processing.