Results for “ece_dsno_allowance_charges_v”

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

Overview

ECE_DSNO_ALLOWANCE_CHARGES_V is a database view historically shipped within the Oracle e-Commerce Gateway (EC) module. ETRM documentation for both Oracle E-Business Suite 12.1.1 and 12.2.2 classifies this object with the description "No longer used," and the implementation notes state that it is "Not implemented in this database." This means the view is a legacy artifact retained in the data dictionary metadata for backward compatibility and historical reference, but it is not created or populated in a standard, current installation.

The view was originally designed to present allowance and charge information—freight charges, special services, and special charges—associated with outbound delivery and picking transactions destined for external trading partners via the e-Commerce Gateway. It flattened delivery, container, picking line, picking line detail, and freight charge data into a single row per charge, exposing currency conversion attributes so that downstream EDI or flat-file extracts could transmit monetary amounts with the correct currency, conversion type, conversion date, and conversion rate.

Underlying Base Objects

The view text joins five base tables:

• SO_PICKING_LINES_ALL (SPL) — picking line header information, including delivery, order line, and inventory item references.
• SO_PICKING_LINE_DETAILS (SPLD) — picking line detail records, supplying the picking line detail identifier.
• WSH_DELIVERIES (DLV) — delivery records, providing the actual departure identifier for shipment tracking.
• SO_FREIGHT_CHARGES (SFC) — the freight and allowance/charge records, which are the driving rows of the view.
• SO_FREIGHT_CHARGE_TYPES (SFCT) — the freight charge type definition, providing the human-readable handling code name.

Because the view is documented as "not implemented," these base objects remain the authoritative source in supported releases. Any reporting on freight charges and allowances should query SO_FREIGHT_CHARGES and SO_FREIGHT_CHARGE_TYPES directly rather than relying on this view.

Key Columns

Among the most relevant columns exposed, particularly for users searching on currency_conversion_type_code, are the following:

• CURRENCY_CONVERSION_TYPE_CODE — sourced from SFC.CONVERSION_TYPE_CODE; identifies the Oracle currency conversion type (for example, Spot, Corporate, User-defined) applied to the charge amount.
• CURRENCY_CONVERSION_DATE and CURRENCY_CONVERSION_RATE — the effective date and rate for converting the charge into the target currency.
• CURRENCY_CODE — the transaction currency of the charge.
• AC_INDICATOR and AC_AMOUNT — DECODE logic derives 'A' for negative amounts (allowances) and 'C' otherwise (charges); AC_AMOUNT returns the absolute value, separating sign from magnitude for EDI reporting.
• AC_HANDLING_CODE_INT — the freight charge type name from SFCT.NAME.
• AC_SPECIAL_SERVICES_CODE and AC_SPECIAL_CHARGES_CODE — drawn from AC_ATTRIBUTE1 and AC_ATTRIBUTE2.
• AETC_NUMBER, AETC_RESPONSIBILITY_CODE, AETC_REASON_CODE — attributes three, four, and five, supporting allowance/charge authorization tracking.
• DELIVERY_ID, DEPARTURE_ID, CONTAINER_ID, ORDER_LINE_ID, ITEM_ID, PICKING_LINE_ID, PICKING_LINE_DETAIL_ID — the identifying keys linking the charge to the shipment hierarchy.

Common Use Cases and Queries

In legacy implementations, this view supported extraction of allowance and charge data for outbound EDI documents such as the 810 invoice or shipment notices, where each charge required its own currency conversion context. A typical historical query pattern would resemble:

• SELECT delivery_id, order_line_id, ac_indicator, ac_amount, currency_code, currency_conversion_type_code, currency_conversion_date, currency_conversion_rate FROM ece_dsno_allowance_charges_v WHERE currency_conversion_type_code = :conv_type;
• Filtering by AC_HANDLING_CODE_INT to isolate freight versus special-service charges.
• Joining back to WSH_DELIVERIES or SO_PICKING_LINES_ALL on the exposed identifiers for shipment-level roll-ups.

Because the view is not implemented in current 12.1.1 or 12.2.2 environments, these queries will fail against a fresh instance. Practitioners encountering this object in legacy scripts should migrate the logic to SO_FREIGHT_CHARGES and its associated tables, applying the same DECODE sign logic and selecting the conversion columns directly.