Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword or section
Like this
39Activity

Table Of Contents

0 of .
Results for:
No results containing your search query
P. 1
WMS Rules Engine Examples

WMS Rules Engine Examples

Ratings:

5.0

(1)
|Views: 3,448 |Likes:
Published by floatingbrain
Oracle Warehouse management Rules Engin Examples
Oracle Warehouse management Rules Engin Examples

More info:

Categories:Types, School Work
Published by: floatingbrain on Jun 10, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

07/19/2013

pdf

text

original

 
Oracle Warehouse ManagementRules Engine Examples
 An Oracle Topical EssayOctober 2002; updated October 2004
 
 1
Oracle Warehouse ManagementRules Engine Examples
RULES ENGINE EXAMPLES
This document is a tool to assist implementation of Oracle Warehouse Management, by documentingthe seeded rules and strategies and additional rules and strategies that might be helpful for both simpleand complex operational requirements. All types of rules are documented, including picking, putaway, cost group, label type, and task type assignment rules. In addition, picking and putawaystrategies are documented.The most difficult part of setting up the Rules Engine is not defining the rules in the application, butrather, defining the business logic that needs to be modeled. The rules and strategies contained herecan help an implementation team ask the right questions in beginning to define the requirements for the Rules Engine.This document assumes familiarity with the Rules Engine and does not go into the specifics of how totranslate the rules and strategies documented here to the system. Please refer to the Oracle WarehouseManagement Guide for assistance understanding the basic user interface. Please refer to the RulesEngine chapter of the Oracle Warehouse Management Implementation Guide for detailed explanationsof how the Rules Engine functions, including performance and implementation considerations,customization details, and debugging and trouble shooting assistance.
Seeded Rules & Strategies
 No two warehouses are alike. However, some warehouses have very simple needs that can bemodeled by generic rules and strategies that do not refer to any entities defined specifically for thatwarehouse. For instance, a FIFO/FEFO rule that ensures stock rotation is used by many warehouses,and requires no references to warehouse-specific data. Whenever possible, simple genericrequirements have been provided for with seeded rules and strategies. Common picking and putawayrules and strategies have been seeded in the application.To use the seeded strategies, no changes need be made, but rather, all that need be done is define thestrategy search order and make the strategy assignments. As these common picking strategies areoften applicable for the entire organization, the strategy search order may only require the SourceOrganization for the picking search order, and the Destination Organization for the putaway searchorder.Of course, the putaway search order must also include the transaction type object and an assignmentof a putaway strategy without any restrictions in the rules to the staging transfer transaction type toindicate that sales order staging transfers are always valid. This assignment must be made for bothInternal and Sales Order Pick if both internal sales orders and external sales orders are used. Details
 
 2
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.
Additional Examples
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.
Performance
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.
Format
Rather than providing screenshots of the rules and strategies, the rules and strategies will be defined intabular format.
Rules
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
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.

Activity (39)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
ankurs_41 liked this
kavinb liked this
kavinb liked this
raj liked this
manhan9 liked this
raj liked this
manhan9 liked this
elriba liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->