Results for “wsh_release_seq_rules”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_RELEASE_SEQ_RULES is a reference configuration table in Oracle E-Business Suite that defines release sequence rules used by the shipping execution and order entry modules to determine the order in which picking, release, and shipment activities are processed. The table resides in the OE (Order Entry) schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its Description, "Release sequence rules," confirms its role as a control table governing sequencing logic rather than transactional data.

The object is product-tagged to OE - Order Entry, but its dependencies in the receiving schema (WSH, SO) reflect how the sequencing rules are consumed during warehouse operations. The heuristic Data Vault classification mined from the foreign-key structure is hub-leaning. Under the Data Vault modeling convention, this suggests the table behaves as a durable, relatively stable keyed entity whose surrogate identifier is referenced by multiple dependent (satellite/link-style) structures. It is best treated as a reference or configuration hub from which ordering behavior is derived.

Key Information Stored

The table is documented with 40 columns in the 12.2.2 physical schema. The most significant columns group into identity, sequencing criteria, and auditing/context fields.

• RELEASE_SEQ_RULE_ID — Surrogate primary key (WSH_RELEASE_SEQ_RULES_PK). A unique index, WSH_RELEASE_SEQ_RULES_U1, also covers this column, making it the principal business-key candidate and the join point for all dependent tables.
• NAME and DESCRIPTION — Human-readable identifiers for the rule, used in setup forms and reporting.
• Priority/Sort pairs — Six functional criteria each represented by a PRIORITY column and a matching SORT column: ORDER_ID_PRIORITY/ORDER_ID_SORT, INVOICE_VALUE_PRIORITY/INVOICE_VALUE_SORT, SCHEDULE_DATE_PRIORITY/SCHEDULE_DATE_SORT, SHIPMENT_PRI_PRIORITY/SHIPMENT_PRI_SORT, and DEPARTURE_PRIORITY/DEPARTURE_SORT. These define what attribute drives sequencing and whether it is applied ascending or descending.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Effective-dating controls that determine when the rule set is in force.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield (DFF) storage, allowing organizations to extend rule definitions without schema changes.
• 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 provide standard EBS WHO-column traceability and concurrent program context.

Common Use Cases and Queries

Release sequence rules are queried most often during shipping setup and troubleshooting of pick release behavior. A typical lookup retrieves active rules by name:

• Validate that a rule is currently active: filter on START_DATE_ACTIVE and END_DATE_ACTIVE relative to SYSDATE.
• Identify which attribute drives sequencing by querying the PRIORITY columns and comparing non-null entries.
• Resolve the rule applied to a picking batch by joining SO_PICKING_BATCHES_ALL.RELEASE_SEQ_RULE_ID to WSH_RELEASE_SEQ_RULES.RELEASE_SEQ_RULE_ID.
• Determine which picking rule sets reference this release sequence rule via SO_PICKING_RULES.RELEASE_SEQ_RULE_SET_ID.
• Audit configuration changes using CREATED_BY, LAST_UPDATED_BY, and PROGRAM_ID to trace which concurrent program modified the rule.

A representative query pattern:

SELECT r.NAME, r.DESCRIPTION, r.ORDER_ID_PRIORITY, r.ORDER_ID_SORT
FROM   OE.WSH_RELEASE_SEQ_RULES r
WHERE  SYSDATE BETWEEN NVL(r.START_DATE_ACTIVE, SYSDATE)
                   AND NVL(r.END_DATE_ACTIVE, SYSDATE);

Related Objects

The following objects reference or depend on WSH_RELEASE_SEQ_RULES through documented foreign keys and parameters:

• SO_PICKING_BATCHES_ALL.RELEASE_SEQ_RULE_ID — Foreign key to WSH_RELEASE_SEQ_RULES; records the rule applied to each pick wave/batch.
• SO_PICKING_RULES.RELEASE_SEQ_RULE_SET_ID — Foreign key linking picking rule sets to the release sequence rule.
• WSH_PARAMETERS.RELEASE_SEQ_RULE_ID — Foreign key that assigns a default release sequence rule at the shipping parameter level.
• WSH_RELEASE_SEQ_RULES_PK — Primary key constraint on RELEASE_SEQ_RULE_ID.
• WSH_RELEASE_SEQ_RULES_U1 — Unique index supporting the business-key candidate.

Together these relationships confirm WSH_RELEASE_SEQ_RULES as a central configuration hub consumed by pick release and shipping parameter setups across the OE and WSH schemas.