Results for “ship_set_number”

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

Overview

The SO_PICKING_RULES table in the OE (Order Entry) schema stores reusable picking parameters, commonly called pick release rules, that govern how Oracle Order Management selects, groups, and releases sales order lines for shipment. Each row represents a named rule that can be invoked during the Pick Release process to filter the population of order lines eligible for picking, define sequencing rules, and control downstream delivery behavior. In Oracle EBS 12.1.1 and 12.2.2, these rules allow warehouse and order management personnel to standardize release criteria by warehouse, customer, order type, item group, ship method, and date range, thereby avoiding repetitive manual selection.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as a link. This is a reasonable modeling suggestion because SO_PICKING_RULES primarily associates several master entities — customers, customer sites, order types, item groups, release sequence rule sets, and pick slip rule sets — while also carrying descriptive filter attributes. Its surrogate primary key is PICKING_RULE, constrained by SO_PICKING_RULES_PK; the unique index SO_PICKING_RULES_U1 also covers PICKING_RULE, confirming it as the business-key candidate for the rule identifier.

Key Information Stored

The table contains 50 documented columns in the 12.2.2 physical schema. The most operationally significant are:

• PICKING_RULE — the surrogate primary key and unique rule identifier.
• HEADER_ID — references a specific order in SO_HEADERS_ALL when the rule is header-specific.
• ORDER_TYPE_ID — restricts release to a given order type via SO_ORDER_TYPES_115_ALL.
• CUSTOMER_ID and SITE_USE_ID — scope the rule to a customer or ship-to site from RA_CUSTOMERS and RA_SITE_USES_ALL.
• GROUP_ID — links the rule to an item group in SO_ITEM_GROUPS.
• WAREHOUSE_ID, SUBINVENTORY, and INVENTORY_ITEM_ID — narrow release to a warehouse, subinventory, or specific item.
• SHIP_METHOD_CODE and SHIP_SET_NUMBER — constrain by carrier or shipment grouping.
• DATE_REQUESTED_FROM/_TO and SCHEDULED_SHIPMENT_DATE_FROM/_TO — define requested and scheduled shipment date windows.
• START_DATE_ACTIVE and END_DATE_ACTIVE — control rule validity periods.
• BACKORDERS_ONLY_FLAG, EXISTING_RSVS_ONLY_FLAG, PARTIAL_ALLOWED_FLAG, INCLUDE_PLANNED_LINES_FLAG, and AUTOCREATE_DELIVERY_FLAG — behavioral switches affecting which lines qualify and whether deliveries are auto-created.
• RELEASE_SEQ_RULE_SET_ID and PICK_SLIP_RULE_ID — reference WSH_RELEASE_SEQ_RULES and WSH_PICK_SLIP_RULES respectively.

Standard audit columns such as CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, and the ATTRIBUTE1–ATTRIBUTE15 flex fields are also present for extensibility and traceability.

Common Use Cases and Queries

A frequent requirement is to list active picking rules for a given warehouse so operators can choose the correct release criterion. For example:

SELECT picking_rule, warehouse_id, order_type_id, customer_id, start_date_active, end_date_active FROM oe.so_picking_rules WHERE warehouse_id = :warehouse AND SYSDATE BETWEEN start_date_active AND end_date_active;

Reporting scenarios include auditing which rules reference specific customers, item groups, or release sequence rule sets, and identifying rules that permit partial releases or backorder-only picking. A join to SO_ORDER_TYPES_115_ALL or RA_CUSTOMERS enriches such reports with descriptive names. Integration teams also query this table when migrating or cloning pick release configurations between environments.

Related Objects

The following tables are the most significant related objects, based on documented foreign keys:

• SO_HEADERS_ALL — joined on SO_PICKING_RULES.HEADER_ID.
• WSH_RELEASE_SEQ_RULES — joined on SO_PICKING_RULES.RELEASE_SEQ_RULE_SET_ID.
• SO_ORDER_TYPES_115_ALL — joined on SO_PICKING_RULES.ORDER_TYPE_ID.
• RA_CUSTOMERS and RA_SITE_USES_ALL — joined on CUSTOMER_ID and SITE_USE_ID.
• SO_ITEM_GROUPS — joined on GROUP_ID.
• WSH_PICK_SLIP_RULES — joined on PICK_SLIP_RULE_ID.

Collectively these relationships position SO_PICKING_RULES as a central configuration link between Order Management master data and Warehouse Management release execution.