Configure Severity of Shipping Messages

Tailor operational responses by configuring the severity level of messages generated during the shipping confirmation process, specifically for:

1. Order header and line level holds (Shipping Holds)
2. Unreleased delivery details.

Before Release 12.2.14, there was no flexibility to adjust the severity of these messages, which could result in either unnecessary halts in processing or overlooked critical issues due to uniform message handling.

Business Benefits

• Organizations can define messages as follows:
  • "Warning" that permits continuation or
  • "Error" that halts further processing
• Customize workflow controls in logistics, supporting use cases such as ensuring critical holds stop processing while minor issues only alert users without disruption.

Implementation considerations include assessing which messages require strict enforcement versus those that can be advisory, ensuring that configurations reflect operational policies and risk tolerance.

Steps to enable and configure

You don't need to do anything to enable this feature.

Tips and considerations

- Carefully evaluate the business impact of setting messages as "Warning" versus "Error" to avoid unintended workflow interruptions or oversights. 

- Document the configured severity levels and communicate them to users to ensure consistent handling of shipping messages. 

- Periodically review severity configurations to adapt to changing business needs or operational challenges.

Key resources

Ship Confirm Message Configuration, Oracle Shipping Execution User’s Guide