Search Results sr_inv_org_pk




Overview
Explore in AI Chat

Overview

GMP_SR_SHIPMENT_DATA_V is a database view owned by the APPS schema in Oracle E-Business Suite, and forms part of the GMP (Process Manufacturing Process Planning) product family. Its documented purpose is to expose shipment data for consumption by the Demand Planner, providing a normalized read interface over shipment transactions such as booked, requested, promised, scheduled, and shipped dates, along with associated quantities and dimensional attributes.

In the ETRM 12.2.2 metadata, this view is recorded with a status of VALID but, notably, its definition is a placeholder rather than a functional query. The view text selects a fixed set of typed NULL expressions from SYS.DUAL with the predicate WHERE 1 <> 1, meaning the view is structurally valid but returns no rows. This is characteristic of a seed or template definition used during product installation, where customer-specific or site-specific shipment sources are expected to be substituted — most commonly by a customer-defined view or a Planning Server data collection program that replaces the stub with a query against the actual shipment transaction tables.

For integration and reporting purposes, the view therefore defines the contract or interface shape that downstream Demand Planner processes expect, rather than serving as a source of live data in its shipped form.

Underlying Base Objects

Per the documented metadata, the only referenced base object is SYS.DUAL. No transaction tables (for example, shipping, order management, or inventory tables) are referenced in the delivered definition. The implication is that the view does not, by itself, source shipment records from any operational table in the ETRM 12.2.2 baseline.

Because the delivered text is a no-op select, the view functions as a declaration of column names, data types, and ordering. Any implementation that supplies actual shipment data must either redefine the view or redirect the Demand Planner integration to an alternate source. Administrators should verify the live definition in their instance, since the stub may have been customized during implementation or superseded by a later patch.

Key Columns

The view exposes a dimension-and-measure style column set. The user searched term, SHIPPED_DATE, is present as a DATE column and represents the date on which a shipment was actually dispatched. The principal columns are:

Common Use Cases and Queries

The primary use case is supplier-demand integration: the Demand Planner consumes shipment history (particularly SHIPPED_DATE and QTY_SHIPPED) to build forecasts and replenishment signals. A typical query validates column availability:

  • SELECT SHIPPED_DATE, SR_ITEM_PK, QTY_SHIPPED FROM APPS.GMP_SR_SHIPMENT_DATA_V;
  • SELECT TRUNC(SHIPPED_DATE,'MM') month, QTY_SHIPPED FROM APPS.GMP_SR_SHIPMENT_DATA_V;
  • SELECT COUNT(*) FROM APPS.GMP_SR_SHIPMENT_DATA_V WHERE SHIPPED_DATE IS NOT NULL;

Because the shipped definition returns zero rows, such queries succeed syntactically but yield no data until the view is replaced or extended. Consultants should treat GMP_SR_SHIPMENT_DATA_V as an interface specification and confirm the actual data source with the site's implementation documentation.