Search Results wsh_ship_confirm_rules_pk

Overview

The WSH_SHIP_CONFIRM_RULES table is a core data object within the Oracle E-Business Suite (EBS) Shipping Execution (WSH) module. It serves as the repository for defining and storing Automated Ship Confirm Rules. In the context of EBS 12.1.1 and 12.2.2, these rules are a critical component of the shipping workflow, enabling the automation of the ship confirmation process. Ship confirmation is the final step where the system records that a delivery line has been physically shipped, updating inventory, creating invoices, and triggering downstream financial processes. This table allows administrators to predefine the business logic and conditions under which shipments are automatically confirmed, thereby streamlining operations, reducing manual intervention, and improving data accuracy.

Key Information Stored

The table's primary purpose is to hold the configuration for each automated rule. While the full column list is proprietary, the documented primary key, SHIP_CONFIRM_RULE_ID, uniquely identifies each rule definition. Based on its function, the table typically stores metadata such as the rule name, description, and an enabled flag. Crucially, it stores the rule's execution criteria—conditions based on source document type (e.g., Sales Order, Return), shipping parameters, or carrier information. It also defines the action to be performed, which is the automated confirmation itself, and may link to associated setups like concurrent programs or batch parameters. The structure is designed to support a flexible rules engine that can evaluate deliveries and shipments against the stored criteria.

Common Use Cases and Queries

The primary use case is the batch automation of the ship confirm process. A concurrent request evaluates open deliveries against the active rules defined in this table. Common administrative tasks include auditing active rules or troubleshooting automation failures. Sample SQL patterns for reporting and analysis include:

• Listing all active rules: SELECT ship_confirm_rule_id, name FROM wsh_ship_confirm_rules WHERE enabled_flag = 'Y';
• Identifying rules associated with a specific source type or carrier.
• Joining with execution history or log tables (often named with suffixes like *_ALL or with related log tables) to monitor rule performance and volume of automated confirmations.

Direct data manipulation (DML) on this table is strongly discouraged; configuration should be performed through the official Oracle EBS user interface or supported APIs to maintain data integrity.

Related Objects

WSH_SHIP_CONFIRM_RULES is central to the ship confirm automation subsystem. It is directly referenced by the concurrent engine and the shipping confirmation processing logic. Key related objects include:

• Primary Key Constraint: WSH_SHIP_CONFIRM_RULES_PK on SHIP_CONFIRM_RULE_ID, ensuring uniqueness.
• Concurrent Programs: Such as "Automated Ship Confirm" (WSHSCS), which reads the active rules from this table to process eligible deliveries.
• Shipping APIs: Particularly the WSH_SHIP_CONFIRM package, which contains the procedures invoked by the automated rules engine.
• Setup and Audit Views: The WSH module likely provides descriptive views (e.g., WSH_SHIP_CONFIRM_RULES_V) for reporting purposes, which join this table with descriptive flexfields and other reference data.
• Execution Logs: Related tables that log the results of rule execution for specific delivery lines, which would foreign key back to SHIP_CONFIRM_RULE_ID.