Search Results document_type_meaning




Overview
Explore in AI Chat

Overview

APPS.WSH_DOC_SEQUENCE_CATEGORIES_V is a VALID Oracle E-Business Suite database view owned by the APPS schema and registered under FND Design Data as WSH.WSH_DOC_SEQUENCE_CATEGORIES_V. Within the Oracle EBS 12.1.1 and 12.2.2 releases, it exposes the document sequence category definitions used by the Warehouse Management (WSH) and Shipping Execution modules. In this context a "document sequence category" defines the numbering rules applied to shipping and inventory documents, specifying the prefix, suffix, delimiter, and sequence assignment that produce human-readable document codes.

The view is classified by Oracle as Internal Use Only. Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs. Its principal role is therefore reporting, diagnostics, and integration reference for implementers and technical consultants who need to resolve document sequence configuration for a given location, document type, or category. The presence of the DOCUMENT_TYPE_MEANING column makes the view particularly convenient for lookups, since it presents decoded descriptions alongside the stored lookup codes without requiring a join to the lookup tables.

Underlying Base Objects

Per the documented view metadata for 12.2.2, WSH_DOC_SEQUENCE_CATEGORIES_V is defined over the following base objects:

Because the definition spans both the common Application Object Library sequence categories and the WSH operational tables, the view behaves as a consolidated presentation layer that joins sequence configuration to the shipping location in which it applies.

Key Columns

  • DOC_SEQUENCE_CATEGORY_ID — Primary identifier of the sequence category row.
  • LOCATION_ID, LOCATION_CODE — Warehouse or location to which the sequence is scoped.
  • DOCUMENT_TYPE, DOCUMENT_TYPE_MEANING — The lookup code for the document type and its decoded meaning, the column most frequently used for searching and reporting (for example, resolving "document_type_meaning" queries).
  • DOCUMENT_CODE, DOCUMENT_CODE_MEANING — The specific document code within the type, with its decoded description.
  • CATEGORY_CODE, NAME, DESCRIPTION — The category identifier and its descriptive text.
  • PREFIX, SUFFIX, DELIMITER — The literal formatting components used to construct the generated document number.
  • ENABLED_FLAG — Indicates whether the sequence category is active.
  • APPLICATION_ID, TABLE_NAME — Identify the owning application and the table the sequence applies to.
  • Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments.
  • ROW_ID — Rowid of the underlying row, exposed for the internal view type.

Common Use Cases and Queries

Typical uses include validating sequence configuration before or after a shipping transaction, troubleshooting gaps in generated document numbers, and reporting on which sequences are enabled for a location.

List all enabled sequence categories for a location:

SELECT document_type_meaning, document_code_meaning, name, prefix, suffix, delimiter
FROM   apps.wsh_doc_sequence_categories_v
WHERE  enabled_flag = 'Y'
AND    location_code = :p_location_code;

Resolve a specific document type description:

SELECT doc_sequence_category_id, document_code_meaning, category_code
FROM   apps.wsh_doc_sequence_categories_v
WHERE  document_type_meaning = :p_document_type_meaning
AND    enabled_flag = 'Y';

Filter by document type and code for a given application:

SELECT location_code, table_name, prefix, suffix, delimiter, name
FROM   apps.wsh_doc_sequence_categories_v
WHERE  document_type = :p_document_type
AND    document_code = :p_document_code
AND    application_id = :p_application_id;

Because the view is documented as Oracle Internal Use Only, queries should be restricted to read-only reporting and diagnostics, and any reliance on undocumented behavior should be avoided in production integrations in favor of supported Oracle APIs.