Search Results seal_code

Overview

WMS_WP_LINES_GTMP_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, validated in release 12.1.1 and 12.2.2. It belongs to the Warehouse Management (WMS) product family and is defined over the global temporary table WMS_WP_LINES_GTMP. The view presents a wide, denormalized projection of wave-planning line data, spanning delivery, shipment, item, lot/serial, weight/volume, and transportation attributes. Its principal role is to give reporting, integration, and concurrent-processing components a stable, named interface to the transient wave pick line staging data held in the underlying GTMP table.

Because the base object is a global temporary table, rows in WMS_WP_LINES_GTMP_V are session-scoped and typically populated during wave planning and pick-release processing, then purged at transaction or session end. This makes the view unsuitable as a permanent reporting source, but valuable as an intermediate structure for real-time diagnostic queries and data extraction during wave execution.

Underlying Base Objects

The ETRM metadata documents exactly one referenced base object: the synonym WMS_WP_LINES_GTMP. The view text is a simple pass-through of every column from that synonym, with no joins, filters, or transformations. Consequently the view does not add business logic; it only re-exposes the GTMP structure under a stable APPS-owned name.

Key implications:

• The view is dependent on the GTMP table and synonym definition; if the synonym points to a different underlying object in a given environment, the view follows it.
• No aggregation, decoding, or lookup joins are performed, so all interpretation must occur in the calling query.
• Session visibility rules of the GTMP apply to the view; other sessions cannot see a session's staged rows.
• Because no WHERE clause is embedded, the view may return many rows and should generally be constrained by the caller.

Key Columns

The view exposes a large attribute set. The most operationally significant columns include:

• TRACKING_NUMBER — the shipment tracking identifier for the delivery line; this is the column most directly associated with the user's search term and is used to correlate wave lines with carrier shipments.
• DELIVERY, DELIVER_TO, SHIP_TO, SHIP_TO_CUSTOMER — delivery and destination identification for the line.
• ORDER_NUMBER, SOURCE_LINE_NUMBER, ORDER_TYPE — originating sales order context.
• ITEM, ITEM_DESCRIPTION, REVISION, LOT, LOCATOR, BATCH — inventory identity and location attributes used in picking.
• REQUESTED_QTY, SHIPPED_QTY, DELIVERED_QTY, PICK_FILL_RATE, SHIP_FILL_RATE — quantities and fill-rate performance.
• DATE_REQUESTED, DATE_SCHEDULED, EARLIEST_SHIP_DATE, LATEST_DELIVERY_DATE — scheduling and promise dates.
• CARRIER, SHIP_METHOD, MODE_OF_TRANSPORT, SERVICE_LEVEL, FREIGHT_TERMS, FOB — transportation and commercial terms.
• GROSS_WEIGHT, NET_WEIGHT, TARE_WEIGHT, VOLUME, WEIGHT_UOM, VOLUME_UOM — load and capacity metrics used in load planning.
• TRIP, LOADING_SEQUENCE, SEAL_CODE — trip and load build attributes.
• LINE_STATUS, LINE_PROGRESS, WAVE_FIRMED_FLAG, REMOVE_FROM_WAVE_FLAG, MESSAGE — processing state and error messaging during wave execution.
• EXCEPTION_ID, TASK_NUMBER — linkage to exception handling and task execution.
• PROJECT, CUSTOMER, CUSTOMER_CLASS — project and customer classification for reporting.

Secondary quantity columns (SECONDARY_REQUESTED_QTY, SECONDARY_SHIPPED_QTY, SECONDARY_DELIVERED_QTY) and their UOMs support dual-unit-of-measure operations.

Common Use Cases and Queries

Typical scenarios include diagnosing a specific wave line by tracking number, verifying fill rates before shipment confirmation, extracting load weights and volumes for trip building, and reconciling exceptions raised during pick release.

A representative query identifying lines by tracking number:

• SELECT order_number, delivery, item, requested_qty, shipped_qty, tracking_number, line_status FROM wms_wp_lines_gtmp_v WHERE tracking_number = :p_tracking_number;

A diagnostic query for unfirmed or errored wave lines:

• SELECT wave_firmed_flag, remove_from_wave_flag, exception_id, message, task_number FROM wms_wp_lines_gtmp_v WHERE message IS NOT NULL;

Because the view carries no filtering logic and reads from a global temporary table, queries must always be executed in the session that populated the staging data, and should include restrictive predicates to limit result size.