Search Results ac_attribute_category

Overview

WSH_CHARGES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Order Entry (OE) product family and exposes freight charge information captured against deliveries, picking headers, picking line details, and packed containers within the Oracle Shipping Execution and Order Management flow. The view presents a denormalized, presentation-ready projection of freight charges, joining charge detail to freight charge type definitions, lookup meanings, order headers, and container sequencing so that downstream reports, interfaces, and concurrent programs can retrieve charge data without reproducing the underlying multi-table joins.

The object carries a VALID status in the ETRM repository, confirming that it is a supported, compiled database object. Because it is a view rather than a table, it stores no data of its own; all values are resolved at query time from the base synonyms and the FND_GLOBAL package. This characteristic makes it suitable for read-only reporting and outbound integration, but unsuitable as a target for direct DML.

Underlying Base Objects

The view is defined over the following documented base objects:

• SO_FREIGHT_CHARGES — the primary charge table, aliased as FC, supplying charge amounts, currency, conversion data, descriptive flexfield (DFF) attributes, and the AC_ATTRIBUTE1 through AC_ATTRIBUTE15 columns plus AC_ATTRIBUTE_CATEGORY.
• SO_FREIGHT_CHARGE_TYPES — aliased as FT, providing the freight charge type name and code.
• SO_LOOKUPS — aliased as L, supplying the charge type meaning where LOOKUP_TYPE equals 'FREIGHT_CHARGE_TYPE'.
• SO_PICKING_HEADERS_ALL — aliased as PH, outer-joined to the charge on PICKING_HEADER_ID.
• SO_HEADERS_ALL — aliased as H, outer-joined to the picking header on ORDER_HEADER_ID, providing ORDER_NUMBER and HEADER_ID.
• WSH_PACKED_CONTAINERS — aliased as PC, outer-joined on CONTAINER_ID, providing the container sequence number.
• FND_GLOBAL — referenced as a package for session context resolution within the view definition.

The outer joins ensure that a freight charge is returned even when no picking header, order header, or container is associated, which is important for charges recorded at the delivery level.

Key Columns

• FREIGHT_CHARGE_ID — primary identifier for the charge record.
• DELIVERY_ID, PICKING_LINE_DETAIL_ID, PICKING_HEADER_ID, CONTAINER_ID — foreign keys linking the charge to its shipping context.
• HEADER_ID and ORDER_NUMBER — the associated sales order header and its user-facing number.
• CONTAINER — the packed container sequence number.
• AMOUNT, CURRENCY_CODE, CONVERSION_RATE, CONVERSION_DATE, CONVERSION_TYPE_CODE — monetary and currency conversion attributes.
• FREIGHT_CHARGE_TYPE_ID, FREIGHT_CHARGE_TYPE_NAME, FREIGHT_CHARGE_TYPE_CODE, CHARGE_TYPE_MEANING — charge classification and translated meaning.
• INVOICE_STATUS — indicates whether the charge has been invoiced.
• CONTEXT, ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield segment values.
• AC_ATTRIBUTE_CATEGORY and AC_ATTRIBUTE1–AC_ATTRIBUTE15 — the global descriptive flexfield context and segments. The user query for "ac_attribute1" resolves to this column, which stores the first global DFF segment value on the freight charge.

Common Use Cases and Queries

Typical uses include freight cost analysis, invoice reconciliation, and extraction of global DFF data for downstream systems. The following query retrieves charges with their global attribute1 value:

• SELECT freight_charge_id, order_number, freight_charge_type_name, amount, currency_code, ac_attribute_category, ac_attribute1 FROM apps.wsh_charges_v WHERE ac_attribute1 IS NOT NULL;
• SELECT order_number, SUM(amount) FROM apps.wsh_charges_v WHERE charge_type_meaning = 'Freight' GROUP BY order_number;
• SELECT freight_charge_id, delivery_id, container, invoice_status FROM apps.wsh_charges_v WHERE invoice_status = 'N';

Because the view references FND_GLOBAL and applies outer joins across several shipping tables, queries should be filtered by delivery, order, or date ranges to maintain acceptable performance on high-volume environments.