Search Results document_code_meaning

Overview

WSH_DOC_SEQUENCE_CATEGORIES_V is an APPS-owned database view within the Oracle E-Business Suite Shipping Execution (WSH) product family. It exposes document sequence category configuration used by Shipping Execution to generate sequential, auditable document numbers for shipping-related artifacts such as packing slips, bills of lading, and shipping manifests. The view consolidates translated lookup meanings, location context, and the underlying Oracle Application Object Library (FND) document sequence category definitions into a single denormalized result set.

Because it is a view, no physical storage exists at the WSH_DOC_SEQUENCE_CATEGORIES_V level; it is a runtime projection over its base objects. This makes it suitable for read-only reporting, integration extracts, and validation queries that require human-readable document sequence information without joining the underlying lookup and sequence tables manually. Availability is consistent across Oracle EBS 12.1.1 and 12.2.2, where the object retains a VALID status in the APPS schema.

Underlying Base Objects

According to the ETRM metadata, the view is defined over four referenced objects, all exposed through synonyms in the APPS schema:

• WSH_DOC_SEQUENCE_CATEGORIES — the primary driver table holding Shipping Execution document sequence category records, including document type, prefix, suffix, delimiter, and category code.
• FND_DOC_SEQUENCE_CATEGORIES — the Oracle Application Object Library table that defines the application-level document sequence category, supplying the descriptive name, table name, and description.
• WSH_LOCATIONS — provides shipping location context through the UI_LOCATION_CODE, joined to the location identifier.
• WSH_LOOKUPS — a view over lookup values used to translate the DOCUMENT_TYPE and DOCUMENT_CODE into their user-facing meanings.

The view text reveals an inner join to FND_DOC_SEQUENCE_CATEGORIES on APPLICATION_ID and CATEGORY_CODE, and to WSH_LOOKUPS for DOCUMENT_TYPE, with outer joins to WSH_LOCATIONS and to a second WSH_LOOKUPS alias for DOCUMENT_CODE. A UNION ALL branch (filtering out BOL document types) reconciles additional rows. This structure ensures every category is returned with its translated meaning and sequence attributes.

Key Columns

• DOC_SEQUENCE_CATEGORY_ID — unique identifier for the sequence category record.
• LOCATION_ID / LOCATION_CODE — shipping location identifier and its UI location code, useful for location-specific sequence rules.
• DOCUMENT_TYPE — the code identifying the shipping document type; translated via WSH_LOOKUPS.
• DOCUMENT_CODE — the specific document code, with an associated lookup meaning.
• APPLICATION_ID / CATEGORY_CODE — link to the FND document sequence category definition.
• PREFIX / SUFFIX / DELIMITER — formatting components that determine how generated document numbers are composed.
• ENABLED_FLAG — indicates whether the sequence category is active.
• NAME / TABLE_NAME / DESCRIPTION — from FND_DOC_SEQUENCE_CATEGORIES, describing the sequence category.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus the 15 ATTRIBUTE columns and audit request columns.

Common Use Cases and Queries

Typical scenarios include validating that a document sequence category is enabled before shipment confirmation, auditing prefix and delimiter configurations across locations, and extracting sequence definitions for integration or reconciliation reports.

Example: list enabled sequence categories with their composed number format.

• SELECT DOCUMENT_TYPE, MEANING, CATEGORY_CODE, PREFIX, SUFFIX, DELIMITER, ENABLED_FLAG, LOCATION_CODE FROM APPS.WSH_DOC_SEQUENCE_CATEGORIES_V WHERE ENABLED_FLAG = 'Y' ORDER BY DOCUMENT_TYPE;

Example: retrieve sequence configuration for a specific location and document type.

• SELECT CATEGORY_CODE, NAME, TABLE_NAME, PREFIX, SUFFIX, DELIMITER FROM APPS.WSH_DOC_SEQUENCE_CATEGORIES_V WHERE LOCATION_CODE = :p_location AND DOCUMENT_TYPE = :p_doc_type;

Because the view joins the FND and lookup tables, these queries avoid manual outer joins and return display-ready values, making the view a practical starting point for shipping execution reporting and diagnostic validation in both 12.1.1 and 12.2.2 environments.