Search Results wsh_doc_sequence_categories_u1

Overview

WSH.WSH_DOC_SEQUENCE_CATEGORIES is a reference and configuration table within the Oracle E-Business Suite shipping (WSH) schema that stores the shipping document categories used to control document sequencing. Each row defines a category for which a document sequence can be generated, including the location context, document type and code, the underlying Oracle document sequence category, and the formatting attributes (prefix, suffix, delimiter) applied to generated sequence numbers. It resides in the APPS_TS_SEED tablespace, confirming its role as a seeded, setup-oriented table rather than a high-volume transactional table.

The table carries the FND Design Data identifier WSH.WSH_DOC_SEQUENCE_CATEGORIES and the status VALID in the documented releases (12.1.1 and 12.2.2). Its physical definition contains 35 columns. Based on the foreign key structure mined from the schema, the object is classified as satellite-leaning: it holds descriptive and contextual attributes that extend a core business key rather than acting as an independent hub or as a pure associative link.

Key Information Stored

The surrogate primary key is DOC_SEQUENCE_CATEGORY_ID, a NUMBER column that uniquely identifies each row and is enforced by the primary key constraint WSH_DOC_SEQUENCE_CATEGORIES_PK. The same column is the single column of the unique index WSH_DOC_SEQUENCE_CATEGORIES_U1 (the object the user searched for), making it the documented business-key candidate from the index perspective.

The most significant descriptive columns are:

• LOCATION_ID — references HR_LOCATIONS_ALL.LOCATION_ID, tying the category to a physical operating location.
• DOCUMENT_TYPE and DOCUMENT_CODE — the type and code of the document category, resolved against FND_LOOKUPS lookup types and codes.
• APPLICATION_ID — the owning application identifier, referencing FND_DOC_SEQUENCE_CATEGORIES.APPLICATION_ID.
• CATEGORY_CODE — the category code, referencing FND_DOC_SEQUENCE_CATEGORIES.CODE.
• PREFIX, SUFFIX, and DELIMITER — the string fragments used to compose the printed document sequence number.
• ENABLED_FLAG — indicates whether the category is active.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments for extensibility.
• Standard WHO/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.

Common Use Cases and Queries

Typical usage centers on validating and reporting on document sequence setup for shipping documents, and on resolving the sequence format applied to a given location and document type. A common pattern is to query enabled categories for a location while joining lookup values to translate the coded values into user-facing meanings:

SELECT dsc.doc_sequence_category_id, dsc.category_code, dsc.document_type, dsc.document_code, dsc.prefix, dsc.suffix, dsc.delimiter FROM wsh.wsh_doc_sequence_categories dsc WHERE dsc.location_id = :p_location_id AND dsc.enabled_flag = 'Y';

Because the table is frequently filtered by location, a query that also joins HR_LOCATIONS_ALL often supports location-level reporting. The nonunique index WSH_DOC_SEQUENCE_CATEGORIES_N1 covers LOCATION_ID, DOCUMENT_TYPE, and DOCUMENT_CODE, and WSH_DOC_SEQUENCE_CATEGORIES_N2 covers APPLICATION_ID and CATEGORY_CODE, so predicates and joins on those column sets are supported efficiently. Back-office reconciliation reports frequently join this table to WSH_DOCUMENT_INSTANCES to confirm which category produced a given sequence instance.

Related Objects

The most significant relationships documented for this object are:

• WSH.WSH_DOCUMENT_INSTANCES — references this table via DOC_SEQUENCE_CATEGORY_ID; the primary downstream consumer of category definitions.
• HR.HR_LOCATIONS_ALL — referenced by LOCATION_ID, supplying the location context.
• FND_DOC_SEQUENCE_CATEGORIES — the Oracle document sequencing category definition that APPLICATION_ID and CATEGORY_CODE point to.
• FND_LOOKUPS — the lookup source for DOCUMENT_TYPE and DOCUMENT_CODE values.
• FND document sequence APIs and concurrent programs — consume the PREFIX, SUFFIX, and DELIMITER attributes when generating and formatting document numbers.