Results for “so_sales_channels_v”

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

Overview

SO_SALES_CHANNELS_V is a lightweight lookup view owned by the APPS schema within the Oracle E-Business Suite Order Entry (OE) product family. Its purpose is narrow and well defined: it exposes the list of valid sales channel values that Oracle Order Management uses to classify the origin or method by which an order was placed. Rather than storing transactional data, the view projects the decoded meaning and the underlying lookup code for a single lookup type — SALES_CHANNEL — from the SO_LOOKUPS table. Because sales channels are administered as reference data through the standard Oracle lookups framework, this view provides a stable, presentation-ready surface that report writers, concurrent programs, and integration interfaces can query without hard-coding lookup type strings or join logic. In EBS 12.1.1 and 12.2.2 the object remains a simple, VALID view with no PL/SQL body beyond the underlying synonym and the packaged global utility reference, making it inexpensive to query and safe to embed in high-frequency reporting.

Underlying Base Objects

The documented definition selects from SO_LOOKUPS, which is resolved in the APPS schema as a synonym to the base Order Entry lookup table, filtered on LOOKUP_TYPE = 'SALES_CHANNEL'. The view therefore returns exactly the set of lookup rows that Oracle Order Management treats as sales channels, inheriting the standard lookup semantics: each row carries a machine-readable code and a user-facing meaning, and the set is controlled by lookup maintenance rather than by application code. The ETRM metadata additionally lists FND_GLOBAL (PACKAGE) among the referenced objects. FND_GLOBAL is the standard EBS global context package, typically referenced for multi-org or session context (for example ORG_ID or USER_ID) rather than for row data itself; its presence indicates that the view's evaluation is sensitive to the current application session context, which is normal for APPS-owned lookup views in a multi-organization environment. Because SO_LOOKUPS is accessed through a synonym and the view filters on a bound lookup type, there is no dependency on order headers or lines — the view is purely descriptive reference data.

Key Columns

• SALES_CHANNEL — The displayed (translated or meaningful) name of the sales channel, aliased from the lookup row's MEANING column. This is the value intended for presentation on reports, LOVs, and output documents.
• SALES_CHANNEL_CODE — The underlying LOOKUP_CODE value, aliased as SALES_CHANNEL_CODE. This is the stored, language-independent key that transactional tables and interfaces normally persist and compare against.

Consistent with all Oracle lookups, MEANING is subject to translation, so SALES_CHANNEL may render differently depending on the session language, while SALES_CHANNEL_CODE remains constant. Consumers joining transactional data should match on the code and use the meaning only for display.

Common Use Cases and Queries

Typical uses include populating sales channel drop-downs and LOVs, driving grouping and trending reports, enriching order extracts with a human-readable channel description, and validating inbound interface values before they reach order import. A basic retrieval of all channels is:

SELECT sales_channel_code, sales_channel
FROM   apps.so_sales_channels_v
ORDER  BY sales_channel;

To confirm that a value supplied by an external system is a currently defined channel:

SELECT 'VALID'
FROM   apps.so_sales_channels_v
WHERE  sales_channel_code = :p_channel_code;

To decorate order data, the view is joined on the code rather than the description, preserving index usage on the transactional side. For example, grouping order headers by channel:

SELECT v.sales_channel, COUNT(*) order_count
FROM   apps.oe_order_headers_all h,
       apps.so_sales_channels_v   v
WHERE  h.sales_channel_code = v.sales_channel_code
GROUP  BY v.sales_channel;

In all cases, report and interface logic should be aware that the channel list is maintenance-driven; new codes can be added by the business without a code change. Where performance is critical, direct queries against SO_LOOKUPS with the same LOOKUP_TYPE filter mirror the view's behaviour, but SO_SALES_CHANNELS_V remains the preferred, supported interface because it isolates consumers from the underlying lookup structure.