Search Results rowi_id

Overview

APPS.WSH_PACKING_SLIPS_DB_V is a seeded Oracle E-Business Suite database view owned by the APPS schema and registered in FND Design Data as WSH.WSH_PACKING_SLIPS_DB_V. Within Oracle Shipping Execution (WSH), the view presents packing slip document information maintained in the shipping document infrastructure. Packing slips are generated for outbound deliveries and capture the printed document number, status, print date, proof-of-delivery evidence, and the delivery and entity context associated with each document. This view therefore serves as a reporting and integration access point for packing slip data without requiring consumers to navigate the underlying shipping document tables directly.

The view is flagged Oracle Internal Use Only. Oracle Corporation does not support access to applications data through this object except from standard Oracle Applications programs. Implementations that query it do so at their own risk, and the view should be regarded as a read-only construct whose shape may change across point releases of Release 12.1.1 and 12.2.2.

Underlying Base Objects

The documented dependency list identifies three base objects, each referenced through an APPS synonym: WSH_DELIVERY_LEGS, WSH_DOCUMENT_INSTANCES, and WSH_NEW_DELIVERIES. WSH_DOCUMENT_INSTANCES is the primary source of packing slip document records and supplies the document instance identifier, document type, packing slip number, status, and final print date. WSH_NEW_DELIVERIES supplies the delivery header context, including the delivery identifier and delivery name. WSH_DELIVERY_LEGS provides the delivery leg association used to relate the document to a specific shipment leg.

The view is itself referenced by other shipping and service objects, notably OKE_DELIVERABLE_SHIPPING_V, OKE_DTS_SHIPPING_V, and WSH_NEW_DELIVERY_ACTIONS. This layering confirms that WSH_PACKING_SLIPS_DB_V is an intermediate presentation layer in the shipping document model rather than a terminal reporting object.

Key Columns

• ROWI_ID — ROWID (length 10). The physical row identifier of the underlying row, exposed for uniqueness and for correlated updates in Forms-based or programmatic processing. Because it is a ROWID, its value is not stable across row migration or table reorganization and must not be persisted as a durable key.
• DOCUMENT_INSTANCE_ID — NUMBER. The document instance identifier linking the row to the shipping document generated for the delivery.
• DOCUMENT_TYPE — VARCHAR2(30). Classifies the document; packing slip rows carry the relevant shipping document type.
• PACKING_SLIP_NUMBER — VARCHAR2(50). The printable packing slip number presented on the printed document.
• STATUS — VARCHAR2(30). Current lifecycle status of the document instance.
• FINAL_PRINT_DATE — DATE. Timestamp at which the packing slip was finalized for printing.
• ENTITY_NAME and ENTITY_ID — Identify the owning entity, commonly the organization or party context for the document.
• DOC_SEQUENCE_CATEGORY_ID — NUMBER. Document sequencing category used for legal or audit numbering.
• POD_FLAG, POD_BY, POD_DATE — Proof-of-delivery indicators, the user who recorded POD, and the POD date.
• REASON_OF_TRANSPORT and DESCRIPTION — VARCHAR2(30) attributes describing the transport reason and document description.
• DELIVERY_ID and DELIVERY_NAME — The delivery header identifier and its user-visible name.

Common Use Cases and Queries

Typical usage includes reconciling printed packing slips against deliveries, auditing proof-of-delivery capture, and feeding downstream documents in order fulfillment. The documented query text is a straightforward projection:

• SELECT ROWI_ID, DOCUMENT_INSTANCE_ID, PACKING_SLIP_NUMBER, STATUS, FINAL_PRINT_DATE, DELIVERY_ID, DELIVERY_NAME FROM APPS.WSH_PACKING_SLIPS_DB_V WHERE DELIVERY_ID = :p_delivery_id;
• SELECT PACKING_SLIP_NUMBER, POD_FLAG, POD_BY, POD_DATE FROM APPS.WSH_PACKING_SLIPS_DB_V WHERE POD_FLAG = 'Y';
• SELECT STATUS, COUNT(*) FROM APPS.WSH_PACKING_SLIPS_DB_V GROUP BY STATUS;

Because the view joins delivery, leg, and document instance data, queries should always be filtered by delivery, date, or status to avoid full scans of the shipping document tables.