Search Results wms_carousel_configuration_pk

Overview

WMS_CAROUSEL_CONFIGURATION is a configuration table in the Warehouse Management (WMS) module of Oracle E-Business Suite, owned by the WMS schema. It stores the configuration parameters that govern the behavior of automated carousel devices used in warehouse picking and put-away operations. Each row defines a named configuration element (CONFIG_NAME) and its corresponding value (CONFIG_VALUE) for a specific device type, business event, and optional subinventory context.

The object carries a heuristic Data Vault classification of standalone, derived from its foreign-key structure, meaning it does not participate in a hub-and-satellite relationship with other WMS entities. As a modeling suggestion, it is best treated as a self-contained reference or lookup table rather than a transactional fact or junction table.

Key Information Stored

The table consists of 29 documented columns. The most significant include:

• CAROUSEL_CONFIGURATION_ID — the surrogate primary key, defined by the constraint WMS_CAROUSEL_CONFIGURATION_PK. This is a system-generated identifier with no business meaning.
• CONFIG_NAME — the name of the configuration parameter being set (for example, a rule or behavior attribute).
• CONFIG_VALUE — the value assigned to that parameter; together with CONFIG_NAME this forms a likely business-key candidate.
• DEVICE_TYPE_ID — identifies the type of carousel or automated device to which the configuration applies.
• BUSINESS_EVENT_ID — links the configuration to a specific business event that triggers or uses it.
• SEQUENCE_ID — an ordering value, typically used when multiple configuration rows apply and a processing order must be enforced.
• SUBINVENTORY — scopes the configuration to a particular subinventory, allowing location-specific behavior.
• ACTIVE_IND — a flag indicating whether the configuration row is currently enabled.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield (DFF) columns, providing extensibility for customer-specific configuration data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — the standard WHO (audit) columns, tracking who created and last modified each row and when.

The presence of the WHO columns confirms the table is fully audited and maintained through standard Oracle EBS application interfaces.

Common Use Cases and Queries

This table is referenced during carousel device operation to determine how the device should behave for a given event and subinventory. Typical scenarios include retrieving active configuration settings for a device type, reviewing parameter values before deployment, and auditing configuration changes.

A representative query to retrieve active configuration for a device type and subinventory might be:

• SELECT config_name, config_value, sequence_id FROM wms.wms_carousel_configuration WHERE device_type_id = :device_type AND active_ind = 'Y' AND subinventory = :subinventory ORDER BY sequence_id;

Reporting use cases include listing all configuration parameters grouped by business event, identifying inactive or stale configuration rows, and extracting DFF attribute values for integration or migration activities. Because the table is standalone, queries generally do not require joins to resolve its core meaning, though joins to device and event reference tables may be needed for descriptive reporting.

Related Objects

Given the standalone classification, the table has few enforced dependencies. The most significant related objects are:

• WMS_CAROUSEL_CONFIGURATION_PK — the primary key constraint on CAROUSEL_CONFIGURATION_ID that enforces uniqueness and supports indexed lookups.
• Device type reference — joined via DEVICE_TYPE_ID to resolve the device type description used in reporting.
• Business event reference — joined via BUSINESS_EVENT_ID to describe the triggering event.
• WMS subinventory reference — joined via SUBINVENTORY to validate and describe the location context.
• FND descriptive flexfield setup — referenced through ATTRIBUTE_CATEGORY for DFF validation.
• Standard WHO audit views — rely on the CREATED_BY, LAST_UPDATED_BY, and related columns for audit tracking.

Because the object is proprietary WMS configuration data, direct DML should be avoided; configuration is best maintained through the supported WMS application setup or the Oracle Mobile Supply Chain Applications interfaces.