Search Results mc_defer_interface_flag




Overview
Explore in AI Chat

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

Overview

WSH_SHIP_CONFIRM_RULES is a Shipping Execution (WSH) configuration table that stores automated ship confirm rules in Oracle E-Business Suite 12.1.1 and 12.2.2. Ship confirm is the transaction that closes the picking and shipping cycle, relieving inventory, updating order lines, and triggering downstream interface activity such as Advance Shipping Notices (ASNs). Rather than forcing operators to specify every ship confirm option manually, Oracle EBS allows administrators to define reusable rules that prescribe default actions and flags for the ship confirm process.

Each row in this table represents one named, time-bound rule. Rules are date-effective: an EFFECTIVE_START_DATE and EFFECTIVE_END_DATE bracket the period during which the rule is valid, and a NAME (enforced unique through the WSH_SHIP_CONFIRM_RULES_U1 index) identifies the rule for selection by users and setup screens. The table is referenced from several operational objects — picking rules, picking batches, and shipping parameters — so a single rule definition can be reused consistently across shipping workflows. From a heuristic Data Vault modeling perspective, the mined FK structure classifies this table as standalone; in Data Vault terms it behaves as a reference or configuration hub, since it is a source of authoritative rule identities that other objects point to rather than a transactional link or a pure descriptive satellite.

Key Information Stored

The surrogate primary key is SHIP_CONFIRM_RULE_ID, defined by the WSH_SHIP_CONFIRM_RULES_PK constraint and used as the foreign key target by dependent tables. The business-key candidate is NAME, enforced by the unique index WSH_SHIP_CONFIRM_RULES_U1, and effective dating is captured through EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.

Behavioral control columns determine how the ship confirm executes:

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) support change tracking.

Common Use Cases and Queries

Typical uses include identifying the currently active rule for a warehouse or batch, auditing which flags are enabled for a given rule, and reporting on configuration drift across environments.

To list currently effective rules:

  • SELECT ship_confirm_rule_id, name, effective_start_date, effective_end_date FROM wsh_ship_confirm_rules WHERE SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE);

To trace which batches use a rule:

  • SELECT b.* FROM wsh_picking_batches b, wsh_ship_confirm_rules r WHERE b.ship_confirm_rule_id = r.ship_confirm_rule_id AND r.name = :rule_name;

Reporting commonly focuses on SEND_945_FLAG, ACTION_FLAG, and the AC_/MC_ flag pairs to verify that automated interface behavior matches business policy.

Related Objects

Documented foreign keys referencing this table are:

WSH_SHIPPING_PARAMETERS supplies the default ship confirm rule at the organization level, while WSH_PICKING_RULES and WSH_PICKING_BATCHES attach rules to picking and batch execution. Related WSH tables such as WSH_DELIVERIES, WSH_DELIVERY_ASSIGNMENTS, and the ship confirm APIs (WSH_DELIVERY_DETAILS_PUB / ship confirm public APIs) consume the resulting confirmations rather than referencing this configuration table directly. The WSH_PICKING_BATCHES, WSH_PICKING_RULES, and WSH_SHIPPING_PARAMETERS joins remain the most significant functional dependencies.