on this requirement can be found in the Rules Engine chapter of the Oracle Warehouse ManagementImplementation Guide.To use the seeded rules, no changes need be made to the rules, but they must be assigned to user-defined strategies, and in turn, these strategies assigned to objects defined in the strategy search order.Seeded rules can also be copied, and the copies modified, to provide even greater flexibility.
Many of the more complex rules that can be used require multiple warehouse-specific restrictions, or additional flexfield or data setup. These will be documented in this guide, with detailed explanationsof what the rule does, why each object was used, how the rule could behave differently with slightlydifferent parameters, and what additional setup, if any, is required to make the scenario work.Almost none of these rules and strategies will be able to be used as-is in any given warehouse.However, they will describe some complex scenarios that the Rules Engine can be used to model,many of which at first glance might not appear possible to do without customization. Therefore, theseadditional examples should prove very helpful to complex implementations where customization is being considered.
All of these rules have been tested functionally, but only some of them have been tested for performance considerations. Therefore, some of the complex rules may provide the correct resultsand may be fast in a demo environment, but may be unusable in a production environment. Nonetheless, the examples in this document should be helpful in understanding how various complexrequirements can be modeled and the different questions that need to be answered when buildingrules.Whenever performance problems crop up, review the performance section of the Rules Engine chapter in the WMS Implementation Guide.
Rather than providing screenshots of the rules and strategies, the rules and strategies will be defined intabular format.
Rules will be specified in the following format, where LOG is either AND or OR, and OP is theconnecting operator such as =, <=, IS NULL, or LIKE. The sequence number is not specified, but isimplied by the order of the rows. The first column indicates whether the row is a restriction, a sortcriteria, or in the case of picking rules, a consistency requirement.
Rule NameRule DescriptionAllocation mode (for picking rules)R LOG ( Object Attribute OP Object Attribute Val )S Object Attribute Sort order C Object Attribute
Strategies will be specified in the following format, where DTYPE is the date type used for the rule,as well as the from and to dates.