Search Results shipped_amt_b




Overview
Explore in AI Chat

Overview

APPS.ISC_EDW_BOOK_SUM1_F_FCV is a reporting view within the Oracle E-Business Suite Enterprise Data Warehouse (EDW) layer, delivered as part of the Order Management and Supply Chain intelligence schemas. It exposes a flattened, pre-joined representation of the Booking Summary star — a preconformed fact view ("FCV") intended for consumption by Oracle Business Intelligence, Discoverer workbooks, and custom operational reporting. The view presents order booking activity at a summary grain, combining booking, fulfilment, shipment, and invoicing metrics against a compact set of foreign key references and descriptive dimensions.

In Oracle EBS 12.1.1 and 12.2.2, the object resides in the APPS schema and acts as an abstraction layer between the physical ETL targets and the reporting tools. Because it is a view rather than a table, no rows are stored; all content is resolved at query time from the underlying collection view.

Underlying Base Objects

The view is defined as a straight projection over a single source object, ISCBV_EDW_BOOK_SUM1_FCV, selecting a fixed column list with no joins, filters, or aggregations applied in the view text itself. No base tables are documented in the ETRM metadata for this object, indicating that the transformation logic and dimensional lookups are encapsulated within the source FCV (an EDW "collection view" typically backed by an internal materialized structure or synonym). Practically, the underlying source traces back to the Booking Summary fact tables populated by the Order Management EDW/OSM collection programs, with dimension keys resolving to customer, currency, date, operating unit, and set of books dimensions.

Because the dependency chain is entirely delegated to ISCBV_EDW_BOOK_SUM1_FCV, any data latency or refresh behaviour observed in this view mirrors the refresh schedule of the EDW booking summary collection.

Key Columns

Common Use Cases and Queries

Typical consumption includes booking-versus-shipment trend reporting, backlog valuation using list versus net amounts, and dimensional analysis by operating unit or set of books. A representative query retrieving list-value bookings by operating unit is:

SELECT OPERATING_UNIT_FK, SUM(BOOKED_LIST_AMT_B) BOOKED_LIST_B, SUM(BOOKED_LIST_AMT_G) BOOKED_LIST_G FROM APPS.ISC_EDW_BOOK_SUM1_F_FCV WHERE DATE_BOOKED_FK = :p_date_fk GROUP BY OPERATING_UNIT_FK;

Order-level drill-through joins the view to the header using HEADER_ID, while currency-specific reporting selects the _B columns when base currency is required and the _G columns for functional reporting. Because there is no filtering in the view definition, report authors should always constrain queries by INSTANCE_FK, SET_OF_BOOKS_FK, or DATE_BOOKED_FK to avoid full-scans of the EDW fact collection.