Results for “dlvy_int”

28 results




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

Overview

APPS.WSH_STND_DOC_NUMBERS_V is a reporting view in the Oracle E-Business Suite Shipping (WSH) module. It exposes a de-duplicated list of numeric document numbers that have been associated with "standalone" delivery interface transactions, paired with the client code under which those transactions were processed. In EBS 12.1.1 and 12.2.2 the view is owned by the APPS schema and is intended primarily for reporting, reconciliation, and downstream integration queries rather than for transactional processing.

The name reflects its function: "STND" denotes standalone, and "DOC_NUMBERS" indicates that the view returns only the numeric document identifiers. Its design isolates a specific, narrow subset of shipping activity — delivery interface records processed with the 94X_STANDALONE interface action code — and makes those identifiers available without requiring the report author to reconstruct the join logic against the underlying Shipping tables themselves.

Underlying Base Objects

The view is defined over two base objects, both referenced through synonyms: WSH_TRANSACTIONS_HISTORY and WSH_NEW_DEL_INTERFACE. The join between them is driven by the delivery interface identifier:

WTH.ENTITY_NUMBER = WNDI.DELIVERY_INTERFACE_ID

  • WSH_TRANSACTIONS_HISTORY supplies the transaction history rows that record the state transitions and document numbers associated with delivery interface activity.
  • WSH_NEW_DEL_INTERFACE supplies the interface records themselves, including the interface action code and the client code used for multi-organization or third-party integration contexts.

Because the view references WSH_TRANSACTIONS_HISTORY, the returned data reflects historical transaction states rather than only currently open interface records.

Key Columns

  • DOCUMENT_NUMBER — the numeric document number from WSH_TRANSACTIONS_HISTORY, cast via TO_NUMBER so that consumers receive a numeric rather than character value. Only values that translate cleanly to digits are retained.
  • CLIENT_CODE — the client code from WSH_NEW_DEL_INTERFACE, identifying the client or integration context to which the standalone delivery interface transaction belongs.

Filtering Logic

The view applies several restrictive predicates that define its population:

  • TRANSACTION_STATUS must be 'AP' (approved) or 'ER' (error).
  • ENTITY_TYPE must equal 'DLVY_INT', restricting rows to delivery interface entities.
  • INTERFACE_ACTION_CODE must equal '94X_STANDALONE', isolating standalone processing.
  • A numeric-validity check is applied: the document number is translated to strip digits, right-trimmed, and compared to NULL. Only rows where the remaining value is NULL — meaning the original string contained digits only — are kept. Non-numeric values are mapped to -99999 and excluded.

DISTINCT and an ORDER BY on the numeric document number ensure a clean, sorted result set.

Common Use Cases and Queries

Typical uses include reconciling standalone delivery interface transactions, auditing approved versus errored interface activity, and feeding downstream systems that require only the numeric identifiers.

A basic query retrieves all standalone document numbers with their client codes:

SELECT document_number, client_code FROM apps.wsh_stnd_doc_numbers_v ORDER BY document_number;

To locate errored standalone interfaces for investigation:

SELECT document_number, client_code FROM apps.wsh_stnd_doc_numbers_v WHERE client_code = :p_client;

Because the view excludes non-numeric document numbers by design, it is unsuitable for scenarios where alphanumeric identifiers must be reported; in those cases the base tables should be queried directly.