Results for “pending_request_flag”

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

Overview

The WSH_SS2_SHIPMENT_V view is a Shipping Execution (WSH) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a consolidated, denormalized projection of shipment batch activity derived from shipping transaction history, presenting operational shipment attributes alongside organization context. The view is specifically scoped to batch-level outbound shipment records: transaction history rows are filtered by ENTITY_TYPE = 'BATCH', DOCUMENT_DIRECTION = 'O', and DOCUMENT_TYPE = 'SR'. Because it joins historical action data to shipment batch master data, it is well suited to auditing, downstream reporting, and integration extracts requiring shipment batch state and business terms such as freight terms and FOB code.

Underlying Base Objects

Per documented ETRM metadata, the view is defined over the following objects:

• WSH_TRANSACTIONS_HISTORY (synonym) — supplies document-level action history, aliased WTH; the driver table for action type, creation date, and document number.
• WSH_SHIPMENT_BATCHES (synonym) — the shipment batch master, aliased WSB; joins on WTH.ENTITY_NUMBER = WSB.NAME.
• ORG_ORGANIZATION_DEFINITIONS (view) — resolves the operating unit organization code via WSB.ORGANIZATION_ID = OOG.ORGANIZATION_ID.
• HR_GENERAL and HR_SECURITY (packages) — referenced for organizational security and context resolution used implicitly by the organization definition view.

The relationships are strictly operational: history rows drive the record grain, batch records supply attributes, and organization definitions provide the human-readable organization code.

Key Columns

• DOCUMENT_NUMBER — shipment batch document identifier from transaction history.
• SHIPMENT_BATCH_ID — primary key of the shipment batch.
• ACTION_TYPE, CREATION_DATE — the historical action performed and its timestamp.
• ORGANIZATION_ID, ORGANIZATION_CODE, ORG_ID — operating unit identifiers, with ORG_ID supporting multi-org filtering.
• SHIP_FROM_LOCATION_ID, CUSTOMER_ID — shipping origin and ship-to customer.
• SHIP_TO_SITE_USE_ID, INVOICE_TO_SITE_USE_ID, DELIVER_TO_SITE_USE_ID — party site references for the respective address roles.
• SHIP_TO_CONTACT_ID, INVOICE_TO_CONTACT_ID, DELIVER_TO_CONTACT_ID — associated contact identifiers.
• SHIP_METHOD_CODE, FREIGHT_TERMS_CODE, FOB_CODE, CURRENCY_CODE — commercial and logistics terms carried on the batch.
• PENDING_REQUEST_FLAG — indicates outstanding processing requests against the batch.

The FOB_CODE column is the attribute most commonly targeted in searches, reflecting its importance for freight responsibility and title-transfer determination.

Common Use Cases and Queries

Typical scenarios include auditing shipment batch actions by date range, extracting FOB and freight terms for landed cost or contract analysis, and reconciling batch documents against organization context for multi-org reporting. A representative query filtering on FOB code:

SELECT v.document_number, v.organization_code, v.fob_code, v.freight_terms_code, v.action_type, v.creation_date FROM apps.wsh_ss2_shipment_v v WHERE v.fob_code = :p_fob_code AND v.org_id = :p_org_id AND v.creation_date >= :p_from_date;

Equivalently, users searching the fob_code keyword can retrieve all batch history rows carrying a specific FOB term, joined to organization code for reporting. Because the view already restricts to outbound shipment batch documents, no additional transaction-type predicates are required. Standard multi-org security applies through ORG_ID and the underlying HR security packages, so queries should always bind or filter the operating unit to avoid cross-org exposure in shared environments.