Results for “client_code”

2 results




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

Overview

The WSH_STND_DOC_NUMBERS_V view is a documented database object owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the WSH product family, known as Shipping Execution, and is classified as a VIEW with a VALID status. The central purpose of this view is to expose standalone delivery document numbers that have already been processed through the shipping transaction history stream. Specifically, it returns distinct document numbers along with their associated client codes for records matching a restricted set of transaction states and interface actions.

In the broader EBS reporting and integration landscape, this view serves as a filtered access point rather than a transactional entry point. Users searching for "document_number" in the context of Shipping Execution will typically encounter this object when investigating standalone delivery numbering or auditing records produced by the WSH transaction history and interface mechanisms.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both exposed through synonyms: WSH_NEW_DEL_INTERFACE and WSH_TRANSACTIONS_HISTORY. The view text confirms this by joining both objects directly. The pivotal join predicate is WTH.ENTITY_NUMBER = DELIVERY_INTERFACE_ID, which correlates a transaction history entity to its corresponding delivery interface record. Because both base objects are referenced as synonyms, the view is defined at the APPS level and inherits the standard EBS synonym layer used for cross-schema access.

Key Columns

  • DOCUMENT_NUMBER — Derived from WTH.DOCUMENT_NUMBER, this column is cast with TO_NUMBER to guarantee a numeric value. The filter logic uses a translation and decode expression to confirm the source string contains only digits before casting; otherwise a sentinel value of -99999 is applied. Only positive numeric document numbers survive the WHERE clause.
  • CLIENT_CODE — Sourced from WNDI.CLIENT_CODE on the delivery interface, this identifies the client associated with the standalone delivery interface record.

Common Use Cases and Queries

Because the view is restricted to a narrow population, its primary use cases involve auditing standalone delivery numbering and validating which document numbers have reached the "AP" (Applied) or "ER" (Errored) transaction status. The fixed filter chain — transaction status in ('AP','ER'), entity type of 'DLVY_INT', and interface action code '94X_STANDALONE' — means queries against this view return only standalone interface deliveries rather than the full shipping universe.

A typical query retrieves document numbers and client codes ordered by the numeric document number:

  • SELECT document_number, client_code FROM wsh_stnd_doc_numbers_v ORDER BY document_number;
  • SELECT document_number FROM wsh_stnd_doc_numbers_v WHERE client_code = :client_code;

Because the view text terminates with ORDER BY TO_NUMBER(WTH.DOCUMENT_NUMBER), the second query inherits the view's inherent ordering. Report writers and integration developers should note that the DISTINCT clause and the numeric casting restrict output to valid, positive, standalone document numbers only; non-numeric or negative values are excluded by design.