Search Results wsh_doc_sequence_categories




Overview
Explore in AI Chat

Overview

WSH_DOC_SEQUENCE_CATEGORIES is a Shipping Execution (WSH) base table that stores the configuration of shipping document categories used to generate and number outbound shipping paperwork such as bills of lading, packing slips, commercial invoices, manifest documents, and export declarations. Each row defines a document category that combines a document type with a document code, a numbering prefix, suffix, and delimiter, and an enabled flag, allowing Oracle EBS to produce sequentially numbered shipping documents per operating unit or per shipping location. The table is owned by the WSH schema, is marked VALID, and is documented with 35 physical columns in ETRM 12.2.2, a structure that is consistent with the 12.1.1 schema in all material respects.

The relationship metadata suggests a satellite-leaning Data Vault classification. Under that modeling heuristic, WSH_DOC_SEQUENCE_CATEGORIES acts as a descriptive satellite attached to an operational business key (the document category configuration), rather than as a pure hub of independent business entities. It carries descriptive and control attributes — prefix, suffix, delimiter, enabled flag, and the standard EBS audit columns — alongside a foreign reference to HR_LOCATIONS_ALL, which anchors it to a physical inventory or shipping location.

Key Information Stored

The surrogate primary key is DOC_SEQUENCE_CATEGORY_ID, which is also the single validated unique index (WSH_DOC_SEQUENCE_CATEGORIES_U1) and the column referenced by child tables. The remaining columns fall into configuration, reference, and audit groups.

  • DOCUMENT_TYPE — the class of shipping document being numbered (for example a bill of lading or packing slip).
  • DOCUMENT_CODE — the specific document code within the type, used to distinguish variants of the same document class.
  • CATEGORY_CODE — the category identifier that groups numbering rules for a document.
  • PREFIX — the leading text inserted before the generated document number.
  • SUFFIX — the trailing text appended to the generated document number.
  • DELIMITER — the separator character placed between prefix, sequence number, and suffix.
  • ENABLED_FLAG — controls whether the category is active for document generation; disabled rows are ignored by the numbering logic.
  • APPLICATION_ID — identifies the owning Oracle application, supporting multi-application ownership.
  • LOCATION_ID — foreign key to HR_LOCATIONS_ALL, tying the category to a shipping or inventory location.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield columns used for customer-specific extensions without schema change.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID.

There is no compound business unique key documented beyond the surrogate primary key, so the DOCUMENT_TYPE/DOCUMENT_CODE/CATEGORY_CODE/LOCATION_ID combination functions as an operational identifier rather than a database-enforced one.

Common Use Cases and Queries

The most frequent requirement is reporting on active document numbering configurations and validating that each shipping document type has an enabled category. A typical query joins the category to the location master:

  • SELECT d.DOC_SEQUENCE_CATEGORY_ID, d.DOCUMENT_TYPE, d.DOCUMENT_CODE, d.CATEGORY_CODE, d.PREFIX, d.SUFFIX, d.DELIMITER, d.ENABLED_FLAG, l.LOCATION_CODE FROM WSH.WSH_DOC_SEQUENCE_CATEGORIES d, HR.HR_LOCATIONS_ALL l WHERE d.LOCATION_ID = l.LOCATION_ID AND d.ENABLED_FLAG = 'Y';
  • Detecting duplicate or overlapping numbering rules by grouping on DOCUMENT_TYPE, DOCUMENT_CODE, and CATEGORY_CODE.
  • Auditing configuration changes over time using LAST_UPDATE_DATE, LAST_UPDATED_BY, and REQUEST_ID to trace the concurrent program or user that modified a category.
  • Cross-referencing generated documents by joining to WSH_DOCUMENT_INSTANCES on DOC_SEQUENCE_CATEGORY_ID to confirm which category produced a given printed document.

Related Objects

  • WSH_DOCUMENT_INSTANCES — the principal dependent table; its DOC_SEQUENCE_CATEGORY_ID foreign key references WSH_DOC_SEQUENCE_CATEGORIES, so every generated document instance points back to its category definition.
  • HR_LOCATIONS_ALL — referenced by WSH_DOC_SEQUENCE_CATEGORIES.LOCATION_ID, providing the location context for the numbering category.
  • WSH_DOC_SEQUENCE_CATEGORIES_PK / WSH_DOC_SEQUENCE_CATEGORIES_U1 — the primary key constraint and unique index on DOC_SEQUENCE_CATEGORY_ID, the integrity anchors for the table.
  • FND_APPLICATION — relates to APPLICATION_ID for identifying the owning application.
  • WSH_DOC_SEQUENCES and related WSH shipping document setup tables — the sibling configuration objects that consume category, prefix, suffix, and delimiter values during document generation.

Together these objects place WSH_DOC_SEQUENCE_CATEGORIES at the centre of shipping document numbering and audit reporting in Oracle EBS Shipping Execution.