My Oracle Support Banner

How Can You Prevent A Customized WMS Rule From Being Regenerated and Overwritten By The Concurrent Program "Generate All Rules"? (Doc ID 2728646.1)

Last updated on MARCH 12, 2021

Applies to:

Oracle Warehouse Management - Version 12.2.9 and later
Information in this document applies to any platform.

Goal

We have customized a WMS Rule per the instructions in the following Oracle document:

         Oracle® Warehouse Management Implementation Guide Release 12.2
         Section: Custom Rule Definition

The problem is our customized rule will get overwritten if we run the concurrent program "Generate All Rules".
Besides being able to manually submit this program, it may also be run without our knowledge when installing certain WMS patches.

The Oracle® Warehouse Management Implementation Guide even mentions that your customized code can be overwritten:

This can be a fairly powerful and non-invasive way to customize the Oracle Warehouse Management
rules engine, but there are two caveats to this customization approach. If you regenerate a rules
PL/SQL package, the system overwrites the customizations.



 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Rule Regeneration Methods:
 
The following function will be used by the VPD policy to restrict certain rule_id(s) from being regenerated:
 
The following VPD policy utilizes the function above and only works against the WMS_RULES_B table:
 
Steps to implement:
 Test:
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.