Search Results oe_bis_cust_sat_v




Overview
Explore in AI Chat

Overview

OE_BIS_CUST_SAT_V is an APPS-owned, VALID Oracle E-Business Suite view in the Order Entry (OE) product family. It serves as a reporting and analytics interface that exposes customer sales satisfaction data in a denormalized, business-friendly form. The view sits on top of the OE_BIS_CUST_SAT_T2 synonym and presents a flattened result set that spans order management, general ledger, human resources, inventory, and receivables dimensions. In Oracle EBS 12.1.1 and 12.2.2, the "_BIS_" naming convention indicates Business Intelligence System objects designed primarily for Oracle Business Intelligence and Discoverer reporting rather than for transactional forms. The view delivers a pre-joined, pre-aggregated star-like dataset that consultants and analysts can query directly to build dashboards, extract data feeds, or support custom reporting in subledger and general ledger analyses.

The column list confirms the wide, analytic role: set of books, legal entity, operating unit, inventory organization, item, category, customer, geographic area, and country all appear alongside quantitative measures (DEL_SALES, RET_SALES, NET_SALES) and time hierarchy members (YEAR_PERIOD, QUARTER_PERIOD, MONTH_PERIOD). This makes the view particularly valuable for multi-dimensional sales analysis across organizational and customer hierarchies.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: OE_BIS_CUST_SAT_T2, accessed through a SYNONYM. The view text is a straightforward SELECT of every column from that object without joins, filters, or functions at the view level:

SELECT SET_OF_BOOKS_ID, ... , REGION FROM OE_BIS_CUST_SAT_T2

The "_T2" prefix indicates a Business Intelligence staging/transformation table (T = table). In a typical OE BIS architecture, T1, T2, and T3 tables represent successive data transformation layers that feed BIS materialized views. OE_BIS_CUST_SAT_V therefore acts as the presentation layer over the intermediate T2 object, exposing a clean column-oriented interface without requiring report developers to reference internal staging objects directly. It is important to note that because the view performs no aggregation itself, any sums, averages, or ratios returned by upstream objects are passed through unchanged.

Key Columns

Because the user query referenced legal_entity_name, that column warrants specific attention. It is the descriptive name corresponding to LEGAL_ENTITY_ID, allowing reports to group or filter sales figures by legal entity without performing a lookup against HR_LEGAL_ENTITIES or XLE_ENTITY_PROFILES. This is a common requirement in subledger accounting, tax reporting, and statutory consolidations.

Common Use Cases and Queries

The view supports sales performance dashboards, legal entity roll-ups, product/customer profitability analysis, and returned-goods monitoring. A simple query to aggregate net sales by legal entity and accounting period is shown below:

SELECT legal_entity_name,
       year_period,
       month_period,
       SUM(net_sales) net_sales_total
FROM   oe_bis_cust_sat_v
WHERE  year_period = :p_year
GROUP  BY legal_entity_name, year_period, month_period
ORDER  BY legal_entity_name, month_period;

To report top customers by delivered sales within an operating unit:

SELECT customer_name,
       SUM(del_sales) del_sales_total
FROM   oe_bis_cust_sat_v
WHERE  operating_unit_id = :p_org_id
GROUP  BY customer_name
ORDER  BY del_sales_total DESC;

Because the view is a pass-through of OE_BIS_CUST_SAT_T2, data freshness depends on the concurrent programs that refresh the underlying BIS tables. Consultants should confirm refresh schedules before relying on the view for intraday reporting, and should apply the appropriate MOAC VPD context via the operating unit columns where multi-org security is required.