Search Results iscbv_bookings_fcv




Overview
Explore in AI Chat

Overview

APPS.ISCBV_BOOKINGS_BASE_FCV is a public Oracle E-Business Suite view owned by the Applications schema. It presents aggregated move-order picking information, exposing the latest pick-slip date associated with each transaction source line. The suffix "FCV" denotes a "flexfield conversion view" style naming convention used extensively in the Oracle Inventory and Order Management family, where such views flatten and pre-aggregate transactional data to simplify downstream reporting and integration queries. In EBS 12.1.1 and 12.2.2 the object remains an unstored, runtime-evaluated view; it holds no data of its own and returns rows derived entirely from the inventory move-order transaction tables.

The view is consumed by booking-related functionality and by custom operational reports that require, for a given source document line, the most recent pick activity executed against it. Because it aggregates with MAX() and GROUP BY, it typically returns one row per source line rather than one row per transaction.

Underlying Base Objects

The view is defined over a single base table, MTL_TXN_REQUEST_LINES, the move-order lines table in Oracle Inventory. No other referenced base objects are documented in the ETRM metadata. The defining SQL restricts the underlying rows with two filter predicates: TRANSACTION_TYPE_ID must be 52 or 53, and TRANSACTION_SOURCE_TYPE_ID must be 2 or 8. These code combinations select the pick-related move-order transaction categories, ensuring that the aggregate reflects picking activity only. The result set is grouped by TXN_SOURCE_LINE_ID, which is the foreign key back to the originating source document line.

Because the view performs no joins, its performance characteristics mirror those of MTL_TXN_REQUEST_LINES. Index availability on TRANSACTION_TYPE_ID, TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_SOURCE_TYPE_ID, PICK_SLIP_DATE, and TXN_SOURCE_LINE_ID materially affects the cost of querying it. In 12.2.2 the underlying table structure is unchanged from 12.1.1 with respect to these columns, so the view behaves consistently across both releases.

Key Columns

  • LINE_ID — the alias assigned to TXN_SOURCE_LINE_ID. This is the transaction source line identifier, the key referenced by the search term "txn_source_line_id." It identifies the source document line from which the move-order request originated and is the grouping key of the view.
  • DATE_LATEST_PICK — the alias assigned to MAX(PICK_SLIP_DATE). It represents the most recent pick-slip date recorded across all qualifying move-order lines for that source line. A NULL value indicates that no qualifying pick transaction exists for the line.

No other columns are projected. Consumers joining this view to order or delivery data do so on LINE_ID.

Common Use Cases and Queries

The principal use case is determining when a given source line was last picked, supporting booking logic, shipment confirmation, and reconciliation reporting. A representative query joining the view to a source document follows:

  • SELECT b.line_id, b.date_latest_pick FROM apps.iscbv_bookings_base_fcv b WHERE b.line_id = :txn_source_line_id; — retrieves the latest pick date for a single source line.
  • SELECT line_id, date_latest_pick FROM apps.iscbv_bookings_base_fcv WHERE date_latest_pick >= :from_date; — identifies lines picked since a given date.
  • SELECT l.line_id, l.date_latest_pick FROM apps.iscbv_bookings_base_fcv l JOIN oe_order_lines_all o ON o.line_id = l.line_id; — correlates the latest pick date with order lines for booking validation.

Because the view is a grouping construct, queries filtering on txn_source_line_id benefit from an index on that column in MTL_TXN_REQUEST_LINES. Reports should anticipate NULL results for lines that have no qualifying pick transactions.