P. 1
WMS Rules Engine Examples

WMS Rules Engine Examples

5.0

|Views: 4,493|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

The available volume on the locator is kept current on every transaction with the volume of the items
that reside in that locator, not the volume of the container item. For instance, if a pallet of 20 items,
each sized 1 ft3

were put away to a locator, the available volume in that locator would decrease by 20

ft3

. However, the pallet’s volume is not considered in the available capacity of the locator. So if the
footprint of the pallet consumed, say, 30 ft3

, there would be a discrepancy between the volume truly

available, and the volume the system believes is available.
If the container items have non-trivial sizes, this can be addressed in one of several ways, all via
custom rule restrictions. Alternate approaches that address this limitation via a custom quantity
function are also possible.
But first, several assumptioms must be defined. The volume that will be considered as the volume of
consumed by the material could be the volume of the items (as is currently the case), the volume of
the container items, or a maximum of the volume of the container item and the contents. The latter,
though the most complicated, may also be the most accurate for two reasons: if a container item is not
assigned to an LPN, then there is no volume to fall back on other than the volume of the contents, and
the volume of the container item may be defined as a container on which you stack items (i.e.: a
wooden pallet) or a container into which you pack items (i.e.: a drum).
Also, in the first approach below, the volume that will be considered is the liquid volume, in that the
space will not be “cubed out”. For instance, a 3x3x3 locator can hold 3 2x2x2 items by liquid volume
(33

/23

>3), yet only one of those 23

items can fit in there if it is, in fact, a solid item.
The following rule with a custom restriction puts away an LPN to a locator if the volume capacity of
the locator is sufficient for the container item being put away, taking into consideration only the
volumes of the container items already in the locator.

Rule Direct Consider LPN container item volume when putting away
Description Only put away into locator where available volume considering current container items & this container item is sufficient

R

License Plate

License Plate Number= Expression

select
wlpn.license_plate_n
umber from
mtl_system_items
msilpn,
mtl_item_locations
millpn
where
msilpn.inventory_ite
m_id =
wlpn.inventory_item_
id and
msilpn.organization_i
d =
wlpn.organization_id
and

30

decode(mptdtv.type_
code,1,NVL(mptdtv.t
o_locator_id,base.loc
ator_id),2,base.locato
r_id) =
millpn.inventory_loca
tion_id and
mil.max_cubic_area
>
nvl(msilpn.unit_volu
me,0) + (select
nvl(sum(nvl(msiall.u
nit_volume,0)),0)
from
mtl_system_items
msiall,
wms_license_plate_n
umbers wlpnall where
wlpnall.lpn_id in
(select distinct
wlpnall.lpn_id
from
mtl_onhand_quantitie
s_detail moqdall,
wms_license_plate_n
umbers wlpnall where
moqdall.locator_id =
decode(mptdtv.type_
code,1,NVL(mptdtv.t
o_locator_id,base.loc
ator_id),2,base.locato
r_id) and
moqdall.lpn_id =
wlpnall.lpn_id) and
wlpnall.inventory_ite
m_id =
msiall.inventory_item
_id and
wlpnall.organization_
id =
msiall.organization_i
d)

Note that this restriction is incomplete, in that it does not yet handle the following common scenarios,
though it should provide a framework for a complete restriction:
• Does not handle UOM conversions, in that the locator capacity or container item volume may
be stored in different UOMs
• Does not handle if the LPN container item is null, or the container item volume is null or 0,
other than treating it as a 0 volume
• Does not handle pending putaways that are already suggested, or loaded tasks for which a
container item may have been removed but not yet dropped to the destination locator
All these limitations can be addressed by a more complete custom rule restriction.
Alternatively, a much simpler custom rule restriction can be used if the restriction is instead based on
just the number of LPNs in the locator under consideration, which would be reasonable if the locators
(for which the rule applies) are all roughly similar in size, and the container items are similarly
roughly equivalent in size.
If, instead, there are several different LPN container item sizes, with different combinations of each
possible in any given locator among a group of similarly sized locators, a custom user-defined table
can be pre-defined to enumerate all possible combinations of container items that can fit in that

31

locator, and a custom rule restriction – or even a custom PL/SQL function called by such a rule
restriction – can be defined to compare the LPN and locator under consideration with the current
contents of the locator.

32

You're Reading a Free Preview

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