Search Results pending_interface_flag




Overview
Explore in AI Chat

Overview

APPS.WSH_SRS_TRIP_STOPS_V is an Oracle E-Business Suite internal database view owned by the APPS schema and registered under the FND Design Data identifier WSH.WSH_SRS_TRIP_STOPS_V. It exposes trip stop information drawn from the Oracle Shipping (WSH) module, presenting freight trip stops together with their associated location details and trip identifiers in a single denormalised result set. The view carries a documented status of VALID in both Oracle EBS 12.1.1 and 12.2.2.

The view is classified as Internal, and the documentation explicitly warns that it is for Oracle Internal Use Only. Oracle Corporation does not support access to application data through this object except from standard Oracle Applications programs. Its role is therefore that of a supporting object used by Oracle's own shipping and transportation execution logic, including the Service Rendering Scheduler (SRS) functionality implied by the object name, rather than a formally published interface for customer reporting.

Underlying Base Objects

The view is defined over three documented base objects, each referenced in the dependency information as an APPS synonym:

  • WSH_TRIP_STOPS — the primary transactional table holding individual stop records for a freight trip. It supplies the core stop-level attributes.
  • WSH_TRIPS — the parent trip table, providing the trip context to which each stop belongs.
  • WSH_LOCATIONS — the shipping location definition table, supplying location codes and descriptive text joined to the stop location.

The view does not reference any additional objects beyond these three, and the documentation records that APPS.WSH_SRS_TRIP_STOPS_V is not referenced by any other database object, confirming it is a terminal, read-only projection rather than a dependency for further views or packages.

Key Columns

The view exposes seven columns, all of which are nullable except where noted by the metadata:

  • STOP_ID (NUMBER) — unique identifier of the trip stop, derived from WSH_TRIP_STOPS.
  • STOP_DESCRIPTION (VARCHAR2(223)) — descriptive text for the stop, assembled within the view definition.
  • STOP_LOCATION_ID (NUMBER) — foreign key to the stop's location record.
  • LOCATION_CODE (VARCHAR2(181)) — the short code of the location, sourced from WSH_LOCATIONS.
  • LOCATION_DESCRIPTION (VARCHAR2(500)) — the long descriptive name of the location.
  • TRIP_ID (NUMBER) — identifier of the parent trip from WSH_TRIPS, linking each stop to its trip.
  • PENDING_INTERFACE_FLAG (VARCHAR2) — a flag indicating whether the stop record is still awaiting interface processing. This column is the attribute most commonly searched for, as it allows identification of stops not yet passed to downstream interface or integration processes.

Common Use Cases and Queries

The principal practical use of this view is the identification of trip stops that have not yet been interfaced, driven by the PENDING_INTERFACE_FLAG column. A representative query returning all pending stops with their location detail is:

  • SELECT TRIP_ID, STOP_ID, STOP_DESCRIPTION, LOCATION_CODE, LOCATION_DESCRIPTION, PENDING_INTERFACE_FLAG FROM APPS.WSH_SRS_TRIP_STOPS_V WHERE PENDING_INTERFACE_FLAG = 'Y';
  • Joining the view to WSH_TRIPS or other WSH tables on TRIP_ID to obtain trip-level attributes for reporting or reconciliation.
  • Diagnostic queries listing all stops for a given TRIP_ID to confirm sequencing and location assignment before interface submission.

Because the object is documented as Internal and unsupported for direct customer access, any query usage should be validated against the specific 12.1.1 or 12.2.2 environment, and production integration should rely on supported APIs wherever possible.