Results for “pick_slip_number”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMI_PICK_SLIP_NUMBER_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMI Process Manufacturing Inventory module. Its purpose is narrow and well defined: it exposes the set of distinct OPM (Oracle Process Manufacturing) pick slip numbers that currently exist in the transactional system. The view is referenced by the value set GMI_PICK_SLIP_NUMBERS, which drives list-of-values behavior for pick slip entry and query fields in OPM Inventory and Order Management screens. When a user searches for "pick_slip_number" in an EBS environment, this view is the object that most commonly resolves the value list behind that field.

Because the view is a simple projection with a DISTINCT filter, it is inexpensive to query and is intended primarily for validation and selection purposes rather than for transactional reporting. It carries no date, organization, or item context, so consumers relying on it must join back to the underlying transaction table should they need additional detail.

Underlying Base Objects

The view is defined over a single base object, IC_TRAN_PND, which appears in the ETRM metadata as a synonym. IC_TRAN_PND is the Process Manufacturing pending-transaction table, the staging structure into which OPM inventory movements and order-driven transactions are written before they are processed or posted. The view definition is:

• SELECT DISTINCT PICK_SLIP_NUMBER FROM IC_TRAN_PND WHERE PICK_SLIP_NUMBER > 0 AND DOC_TYPE = 'OMSO'

Three filters shape the result set. The predicate PICK_SLIP_NUMBER > 0 excludes rows where no pick slip has been assigned, which also protects against nulls and zero placeholders. The predicate DOC_TYPE = 'OMSO' restricts the output to Order Management Sales Order transactions, ensuring that pick slip numbers belonging to other document types, such as transfer orders or internal movements, are not surfaced. The DISTINCT operator collapses the many transaction rows that can share a single pick slip number into one row per pick slip.

Key Columns

The view exposes exactly one column, PICK_SLIP_NUMBER, which is a numeric identifier for an OPM pick slip. Key characteristics include:

• PICK_SLIP_NUMBER — the pick slip identifier used within OPM inventory picking and Order Management fulfillment.
• The column is returned as a distinct, non-null, positive value; negative or zero placeholders are filtered out by the view predicate.
• No descriptive attributes such as organization, item, or status are exposed, so the view functions as a lookup key list rather than an information source.

Common Use Cases and Queries

The principal use case is value set validation: the GMI_PICK_SLIP_NUMBERS value set queries this view to populate a pick slip list of values. Beyond that, the view is useful for ad hoc discovery of valid pick slip numbers and for reconciling Order Management sales order picks recorded in IC_TRAN_PND.

To retrieve the full list of pick slip numbers:

• SELECT pick_slip_number FROM apps.gmi_pick_slip_number_v ORDER BY pick_slip_number;

To confirm that a specific pick slip number exists before referencing it in a concurrent process or a custom report:

• SELECT pick_slip_number FROM apps.gmi_pick_slip_number_v WHERE pick_slip_number = :p_pick_slip;

To obtain transactional detail for a pick slip, join the view back to IC_TRAN_PND on the pick slip number and filter on DOC_TYPE = 'OMSO'. Because the view applies DISTINCT, joins must be executed against the base table rather than the view when row-level transaction attributes are required. In integration scenarios, the view is best treated as a lightweight reference for validating pick slip identifiers received from external systems prior to writing them into OPM pending transactions.