Warehouse Overview

Oracle Warehouse Management Overview
Overview
Copyright Oracle, 2004. All rights reserved.
Oracle Warehouse Management Overview %&&ective mm'dd'yy
(age
o& $#
!"4#$""!.doc )ev
Oracle Warehouse Management Overview

System References
Examples: (Please delete the red text examples once you have added your information) Product Name > Window / Form Name racle Wor! in Process > "iscrete #o$s racle rder %ana&ement > 'ales rders racle (nventory > )ransactions
Distribution
#o$ )itle*
Ownership
)he #o$ )itle +list,-our.ompany/com0'u$1ect2E"3xxxxx4 is responsi$le for ensurin& that this document is necessary and that it reflects actual practice/
(age 2 o& $#
!"4#$""!.doc )ev
i Oracle Warehouse Management Overview
(age * o& $#
!"4#$""!.doc )ev
O+,ectives
(age 4 o& $#
!"4#$""!.doc )ev
Agenda
(age " o& $#
!"4#$""!.doc )ev
Agenda
(age $ o& $#
!"4#$""!.doc )ev
What is a Warehouse-
(age # o& $#
!"4#$""!.doc )ev
(rocesses o& a Warehouse
Processes of a Warehouse )he followin& is an a$$reviated list of the functions users can perform in racle Warehouse %ana&ement (Warehouse %ana&ement): 5 6eceivin&: 6eceive materials and finished &oods/ 5 Put away: Put away materials and finished &oods you receive/ 5 'tora&e: 'tore items within the warehouse/ 5 Pic!in&: Pic! orders for manufacturin& and shippin&/ 5 Pac!in&: Pac! orders for shippin&/ 5 'hippin&: 'hip orders to customers/
(age . o& $#
!"4#$""!.doc )ev
Additional (roduct )e/uirements
Additional Product Requirements )o use Warehouse %ana&ement7 you must implement racle (nventory ((nventory)7 racle Purchasin& (Purchasin&)7 racle 8ills of %aterial (8ills of %aterial)7 and racle rder %ana&ement ( rder %ana&ement)/ -ou use (nventory to set up items7 or&ani9ations7 su$inventories and locators/ -ou use 8ills of %aterial to define people7 resources7 and calendars/ rder %ana&ement and Purchasin& provide the $asic shippin& and receivin& capa$ilities on which Warehouse %ana&ement $uilds/ 5 For more information on (nventory setup see7 verview of 'ettin& 3p7 Oracle Inventory Users Guide/ 5 For more information on 8ills of %aterial setup see7 verview of 'ettin& 3p7 Oracle Bills of Material Users Guide/ 5 For more information on receivin& setup see7 verview of 'ettin& 3p7 Oracle Purchasing Users Guide/ 5 Fore more information on shippin& setup see7 racle 'hippin& Execution 'etup7 Oracle Order Management Implementation Manual.
(age ! o& $#
!"4#$""!.doc )ev
Warehouse Management Application 0ierarchy
Warehouse Management Application ierarchy )he a$ove &raphic represents the relationship $etween existin& racle manufacturin& applications7 Warehouse %ana&ement7 and racle %o$ile 'upply .hain :pplications (%'.:)/ %'.: provides a mo$ile user interface for existin& inventory7 receivin&7 manufacturin&7 ;uality7 and shippin& transactions/ )he mo$ile environment provides users with an alternate set of pa&es to perform the transactions supported in these environments/ 3sers can use hand< held fre;uency devices to perform transactions in $oth Warehouse %ana&ement and %'.:/ Warehouse %ana&ement extends the capa$ilities availa$le in %'.: to encompass the demands placed on a dynamic hi&h<volume warehouse/ Warehouse Management !eatures Warehouse %ana&ement provides the followin& features in addition availa$le in %'.:: 5 )as! mana&ement 5 %aterial trac!in& with =icense Plate Num$ers (=PNs) 5 : confi&ura$le rules en&ine that ena$les you create custom pic!in& rules7 put away rules7 and compliance la$elin& rules/
(age 0 o& $#
!"4#$""!.doc )ev
:dvanced inventory and materials mana&ement includin& material status7 lot7 and serial support/ Warehouse %ana&ement also is heavily inte&rated with7 and extends some of the current functionality in racle manufacturin& applications/
(age
o& $#
!"4#$""!.doc )ev
1nventory, Warehouse Management and M2CA
"nventory# Warehouse Management and MS$A When you implement Warehouse %ana&ement7 you must implement (nventory as well/ (n addition7 you must consider additional attri$utes such as =PN mana&ement when you implement Warehouse %ana&ement/ %'.: does not have the same capa$ilities as Warehouse %ana&ement/ %'.: has the same capa$ilities as the (nventory7 racle >uality (>uality)7 and racle Wor! in Process (W(P) des!top applications7 except it presents transactions on a mo$ile user interface/ Warehouse %ana&ement extends these capa$ilities $eyond the $ase functionality (nventory and %'.: provide as indicated in the a$ove dia&ram/
(age 2 o& $#
!"4#$""!.doc )ev
)adio 3re/uency 4evices
Radio !requency Devices When you implement Warehouse %ana&ement7 you can use any 6F device that supports ).P/(P and telnet/ -ou can use either a character mode interface7 or a &raphical user interface (?3() that mimics the des!top application/ )he type of interface you choose depends on the type of data entry in your implementation7 and the capa$ilities of the mo$ile device/ (f you plan to use the ?3( interface7 you must install a #@%E compati$le #ava virtual machine and the ?3( client application on the mo$ile device/
(age * o& $#
!"4#$""!.doc )ev
Agenda
(age 4 o& $#
!"4#$""!.doc )ev
Overview o& 1n+ound 5ogistics
Overview of "nbound %ogistics Warehouse %ana&ement in$ound lo&istics refers to receivin&7 inspection7 and put away processes within the warehouse/ (t includes the followin& features: 5 6eceivin&: Warehouse %ana&ement uses the three standard Purchasin& receipt modes: standard receipt7 direct receipt7 and inspection receipt/ (t also handles return material authori9ations (6%:s)7 internal re;uisitions7 and in<transit shipments/ 5 >uality (nspection: Warehouse %ana&ement inspects incomin& material $ased on supplier7 product7 or or&ani9ation level default/ 5 =a$el Printin&: Warehouse %ana&ement can print product or pac!a&in& la$els on demand accordin& to any num$er of criteria you define for your implementation/ 5 "irected Put :way and 'tora&e ptimi9ation: Warehouse %ana&ement matches the material handlin& constraints and item or inventory attri$utes to provide users with an availa$le stora&e location for put away/ 5 .ross "oc!in&: Warehouse %ana&ement chec!s $ac!ordered sales orders and redirects in$ound items at receipt/ (f necessary7 it routes the material directly from the receivin& doc! to a sta&in& lane or shippin& doc! without placin& it in a put away location/
(age " o& $#
!"4#$""!.doc )ev
:dvanced )as! Framewor!: -ou can use Warehouse %ana&ement to create operation plans that ena$le users to perform multi<step directed put away throu&hout the warehouse/
(age $ o& $#
!"4#$""!.doc )ev
)everse 5ogistics
Reverse %ogistics 5 6eturn %aterial :uthori9ation (6%:): Warehouse %ana&ement ena$les users to record the inspection and receipt information of customer authori9ed returned items/ 3sers can verify receipt items7 date7 and ;uantity a&ainst the 6%:/ 5 6eturn to Aendor (6)A): Warehouse %ana&ement ena$les users to return material $ac! to the appropriate supplier from a previously received purchase order or purchase a&reement/ 5 6efur$ishment and 6ecyclin&: ptionally7 if you install racle 'ervice and racle "epot 6epair7 then you can use Warehouse %ana&ement as part of the refur$ishment or recyclin& process/
(age # o& $#
!"4#$""!.doc )ev
Agenda
(age . o& $#
!"4#$""!.doc )ev
Overview o& Out+ound 5ogistics
Pic& Release )he pic! release process selects sales order lines to release for pic!in& and shippin&/ -ou can perform manual pic! release7 or create a series of rules to automate the process/ )he system uses the followin& rules to release orders: pic! release rules7 release se;uence rules7 and pic! slip &roupin& rules/ Pic! release rules determine how the system selects sales orders for release/ (f trips are not scheduled for doc! doors7 then pic! release rules also determine the appropriate sta&in& lane for sales orders/ :fter the system determines which sales orders to release7 it uses release se;uence rules to determine the se;uence delivery lines are released for pic!in& $ased on sales order num$er7 outstandin& invoice value7 scheduled date7 departure date7 and shipment priority/ Pic! slip &roupin& rules esta$lish how tas!s are &rouped on a move order pic! slip/ )hey wor! in con1unction with the different pic! methodolo&ies/ Pic! methodolo&ies refer to the different ways users perform pic!in& tas!s/ For example7 a user may select to pic! an order $y itself7 or to pic! multiple orders at the same time/ nce you esta$lish the rules for your implementation7 the system &enerates pic!in& tas!s and dispatches them to ;ualified users/ :fter users complete pic!s7 the system su&&ests the appropriate num$er and si9e of containers the order re;uires for shippin&/ WMS $ontrol 'oard
(age ! o& $#
!"4#$""!.doc )ev
)he W%' .ontrol 8oard provides warehouse mana&ers with a real<time snap shot of the warehouse7 and ena$les them to redistri$ute users as needed/ )hey can monitor the pro&ress of tas!s as well as manually dispatch tas!s to users/ $onsolidation Warehouse %ana&ement ena$les users to consolidate partially filled containers into fewer and $etter<optimi9ed containers/ Pac&ing Warehouse %ana&ement ena$les users to pac! containers with multiple levels of nestin&7 and sends notifications if an order contains special pac!in& instructions/ 3sers can perform pac!in& durin& pic!in& or as an independent process/ Doc& Appointments for (rips %ana&ers can use Warehouse %ana&ement to schedule out$ound carrier appointments7 doc! door availa$ility7 and sta&in& lane usa&e within the warehouse/ Shipment )erification and $lose nce users pic! and load an order7 the system automatically determines the items and ;uantities to deduct from inventory/
(age 20 o& $#
!"4#$""!.doc )ev
Agenda
(age 2 o& $#
!"4#$""!.doc )ev
6alue Added 2ervices
)alue Added Services 5 Bittin& and "e<!ittin&: 'upports !it to stoc! (supported $y wor! order<less completion) and !it to order (supported $y pic! to order)/ 5 %ixed<%ode %anufacturin&: 'upports assem$le to order (:) )7 pro1ect<$ased or en&ineer to order (E) )7 discrete and repetitive or flow environments concurrently/ 5 %anufacturin& .omponent Pic!in&: 'upports pic!in& for wor! in process (W(P) throu&h the mo$ile user interface/ 5 %anufacturin& :ssem$ly .ompletion and Put :way: 'upports W(P completion and put away throu&h the mo$ile user interface/ 5 Product .ompliance =a$elin&: 'upports product specific la$els7 $ased on rules you define/ 5 %anufacturin& >uality (nspections: )he system automatically &enerates material movement transactions to move an item into the ;uality control inspection area from manufacturin&7 $ased on options you define durin& implementation/ 5 (nte&ration with Pro1ect %anufacturin&7 Flow %anufacturin&7 and 'hop Floor %anufacturin&: Warehouse %ana&ement inte&rates with Pro1ect %ana&ement7 Flow %anufacturin&7 and 'hop Floor %ana&ement/
(age 22 o& $#
!"4#$""!.doc )ev
6adio Fre;uency (dentification (6F("): Warehouse %ana&ement supports 6F("/ 6F(" is an automated data collection technolo&y that ena$les e;uipment to read ta&s attached to the o$1ects without contact or line of si&ht/ 6F(" uses radio fre;uency (6F) waves to transfer data $etween a reader and an item to identify7 trac!7 or locate the item/
(age 2* o& $#
!"4#$""!.doc )ev
Agenda
(age 24 o& $#
!"4#$""!.doc )ev
2torage and 3acility Management
Storage and !acility Management 5 :dvanced =ot and 'erial .ontrol: Warehouse %ana&ement ena$les users to split7 mer&e7 and rename lots/ For more information see7 "escri$in& =ot 'plit7 %er&e7 and ?enealo&y7 Oracle Warehouse Management Users Guide/ 5 .ontainer %ana&ement: Warehouse %ana&ement ena$les users to trac! the contents of any container in receivin&7 W(P7 inventory7 shippin&7 and in<transit/ 5 %aterial 'tatus .ontrol: %aterial status control ena$les users to control the eli&i$ility of material for various transactions/ 5 Ban$an %ana&ement: Warehouse %ana&ement supports $oth internal and external supplier !an$ans/ Ban$an is a means of supportin& pullC$ased replenishment in manufacturin& systems/ For more information on !an$an mana&ement see: verview of Ban$an %ana&ement7 Oracle Inventory Users Guide/ 5 (nventory Features: Warehouse %ana&ement facilitates the movement of &oods in to7 out of7 and within the warehouse/ 5 Wor!flow 8ased Exception %ana&ement: -ou can confi&ure real<time alerts and wor!flow $ased notifications of supply chain events to improve the efficiency of $usiness operations/ For example7 when a user pic!s less than the re;uired amount for an order7 wor!flow sends a notification to the user to count the locator/
(age 2" o& $#
!"4#$""!.doc )ev
.ountin&: 3sers can perform cycle counts and physical inventory counts/ For more information see verview of .ycle .ountin&7 and verview of Physical (nventory7 Oracle Inventory Users Guide/ 6eplenishment 5 Warehouse %ana&ement ena$les mana&ers to mana&e inventory levels usin& any com$ination of plannin& and replenishment features7 includin&: min<max plannin&7 reorder point plannin&7 or !an$an replenishment/ -ou can use (nventory and %6P replenishment plannin&7 dynamic replenishment7 and replenishment direct from receivin&/
(age 2$ o& $#
!"4#$""!.doc )ev
Agenda
(age 2# o& $#
!"4#$""!.doc )ev
Oracle Mo+ile Applications Architecture
Mobile Applications %o$ile applications ena$les users to input real<time transactions and receive warehouse tas!s the system assi&ns/ Warehouse %ana&ement and %'.: use the same applications architecture/
(age 2. o& $#
!"4#$""!.doc )ev
5icense (late 7um+ers 85(7s9
*+plaining %icense Plate ,umbers -%P,s. :n =PN is any o$1ect that exists in a location and holds items/ -ou can use Warehouse %ana&ement to trac!7 transact7 and nest =PNs and their contents/ /sing %P,s -ou can use =PNs in the followin& ways: 5 'tore information a$out an =PN such as item7 revision7 lot7 serial7 or&ani9ation7 su$inventory7 or locator 5 )rac! contents of any container in receivin&7 inventory7 or in<transit 5 6eceive7 store7 and pic! material $y =PN 5 Aiew on<hand $alances $y =PN 5 %ove multiple items in a transaction $y =PN 5 )ransfer =PN contents 5 Pac!7 unpac!7 consolidate7 split7 and update =PNs 5 Print la$els and reports for referencin& container contents 5 )rac! nested =PNs 5 6euse empty =PNs
(age 2! o& $#
!"4#$""!.doc )ev
7esting 5(7s
,esting %icense Plate ,umbers -ou can nest =PNs within other =PNs/ Nested =PNs must $e associated with an o$1ect/ )he o$1ect may either $e a collection of items or another =PN/ (n the a$ove example7 item : is pac!ed in =PN @7 and =PND7 =PN@7 and =PNE are nested within =PNF/ When you transact =PNF7 all of the =PNs nested within it are transacted
(age *0 o& $#
!"4#$""!.doc )ev
:enerating 5(7s
0enerating %icense Plate ,umbers -ou can &enerate an =PN to match industry standards7 such as ''..7 that includes the re;uired chec! di&it/ -ou can also confi&ure the num$erin& scheme to match an existin& internal method/
(age * o& $#
!"4#$""!.doc )ev
5(7 Conte;t
%P, $onte+t Warehouse %ana&ement defines a context for each =PN to denote the current state/ -ou can use these contexts to define speciali9ed pic!in& and put away rules/ Resides in "nventory :n =PN with this context indicates material associated with this =PN is costed and accounted for in inventory/ : user cannot this context when receivin& material a&ainst a standard or inspection routed receipt7 $ut can use it for a direct delivery routed receipt/ 3sers can perform out$ound transactions on =PNs with this context/ Resides in W"P :n =PN with this context indicates material associated with this =PN is currently part of a W(P operation/ )he material does not reside in inventory7 and is not costed/ Resides in Receiving :n =PN with this context indicates material associated with this =PN was received usin& a standard routin& or inspection routin& receipt7 $ut still resides at the receivin& doc!/ )he material does not reside in inventory and is not costed/ Resides in "n1transit
(age *2 o& $#
!"4#$""!.doc )ev
:n =PN with this context indicates material is movin& from one location to another/ For example7 when an =PN moves from one or&ani9ation to another/ =PNs in this context are in an intermediary state7 $ut are accounted for in the system/ )his context is used only for inter<or& transit or internal sales orders where an indirect shippin& networ! is defined $etween the or&ani9ations/
(age ** o& $#
!"4#$""!.doc )ev
5(7 Conte;t
%P, $onte+t "ssued out of Stores =PNs with this context do not reside in the warehouse/ Gowever7 the system retains the =PN transaction history/ =PNs shipped out of inventory receive this context and can not $e re< received/ Pre1generated Pre<&enerated =PNs exist in the system7 $ut7 are not associated with any physical material/ Pac&ing $onte+t )he system uses this context internally as an intermediary/ "o not use it anywhere7 includin& the setup of pic!in& or put away rules/ Pic&ed Pic!ed =PNs receive this context/ )hey are in<transit within the warehouse/
(age *4 o& $#
!"4#$""!.doc )ev
5(7 Conte;t
%P, $onte+t Defined but not /sed )his context refers to an =PN defined that does not contain material/ :n example is a reusa$le tote a user can use to pic! orders/ Resides at )endor Site When a vendor sends an :dvanced 'hipment Notice (:'N) :'N7 Warehouse %ana&ement &enerates an =PN and associates it with the material information on the :'N/ Warehouse %ana&ement does not reco&ni9e material associated with =PNs of this context as on<hand or costed/ Pre1Pac& of W"P =PNs that reside in W(P7 and are associated with material pre<pac!ed in W(P7 receive this context/ )his context is used after Warehouse %ana&ement associates the =PN with the material7 $ut the material is not physically pac!ed in the =PN/ %oaded for Shipment )his context refers to material loaded for shipment onto a carrier that is ready to leave the warehouse/ nce the carrier leaves the doc!7 the =PN context chan&es to resides in in<transit7 or issued out of stores/
(age *" o& $#
!"4#$""!.doc )ev
Material 2tatus
Defining Material Status $ontrol %aterial status control provides more &ranular transaction control than item status control/ (t controls the types of transactions you can perform/ -ou can assi&n material status to an item lot7 serial7 su$inventory7 or locator/ (ransaction $ontrol -ou use material status control to specify material statuses at the su$inventory7 locator7 lot7 or serial level/ )his ena$les you to specify the allowed and disallowed transactions for inventory material/ (t also ena$les you to ;uery material $y current status7 and to &enerate and view reports of all historical status chan&es for material in the warehouse/ Assigning and /pdating Material Status $ontrol 5 assi&n material status control to lot and serial controlled items upon entrance to the warehouse/ 5 "etermine the allowed transactions for su$inventories and locators durin& set up/ 5 3pdate material status control as necessary/ 5 "isallowed material status transactions are cumulative/
(age *$ o& $#
!"4#$""!.doc )ev
2u+inventory and 5ocator Material 2tatus
Subinventory and %ocator Material Status -ou can set each status to allow or disallow various inventory transactions/ For example7 you may disallow all transactions for items with the Gold status7 allow all transactions for material with the status of ?ood7 and allow scrappin& transactions for material with the status of 'crap/
(age *# o& $#
!"4#$""!.doc )ev
5ot 2tatus
%ot Status =ot 'tatus is used to control how you use an inventory lot/ -ou can indicate if a lot controlled item is also status controlled at the item level/ (f the item is lot<status ena$led7 you can set a default lot status upon receipt of a new lot of the item/ For example7 if you receive a lot is from a supplier you could set the status to Gold to prevent use until ;uality testin& is complete/ nce tested7 you can chan&e the status to either Fail7 or ?ood/ (f the lot is dama&ed7 re<tested7 and is unusa$le7 or out of date7 you could chan&e the status to 'crap or 6ewor!/ (f the lot matures after production it may have a status of >uar/ -ou can reserve the lot for a shipment $ut not allow it ship until you chan&e the status to ?ood/
(age *. o& $#
!"4#$""!.doc )ev
2erial 2tatus
Serial Status -ou can use serial status to control transactions of serial controlled items/ For example7 a company that supplies and maintains photocopiers on contract has a new machine in stoc! with the status New/ When the company ships the copier to a client the status $ecomes (nHuse/ (f the client reports a pro$lem the copier status chan&es to Fault/ nce repaired7 the status chan&es $ac! to (nHuse/ When the contract ends7 and the client returns the machine7 the status chan&es to Worn/ (f the company reconditions the copier7 the status $ecomes 6econ and is availa$le for delivery to a client7 $ut at a different rate than a New machine/ When the useful life of the copier is over7 the status chan&es to 'crap7 and the company disposes of the machine/ Each status can have a different set of allowed transactions/
(age *! o& $#
!"4#$""!.doc )ev
5ot and 2erial Attri+utes
%ot and Serial Attributes =ot and serial attri$utes trac! the characteristics of items $ased on lot or serial num$ers/ "escriptive flexfields ena$le you to confi&ure lot and serial attri$ute flexfields to capture additional information/ -ou can define re;uired or optional attri$utes7 or trac! information at the item or item cate&ory level/ 'ample lot and serial attri$ute values include &rade7 cycles since new7 and $est $uy date/ )o setup attri$utes and attri$ute value sets7 you associate them with a flexfield se&ment/ For example7 you can set up a value set for the ?rade se&ment/ )he ?rade value set includes three &rades: Excellent7 :vera&e7 and Poor/ /sing %ot and Serial Attributes -ou can $uild pic! and put away rules $ased on lot and serial attri$utes/
(age 40 o& $#
!"4#$""!.doc )ev
Cost :roups
$ost 0roups .ost &roups associate account information with related inventory items/ .ost &roups provide a way to trac! the inventory accountin& attri$utes of material in the warehouse7 and ena$le mana&ers to effectively mana&e inventory with different accountin& attri$utes/ %aterial receives a cost &roup upon receipt into inventory/ %aterial enters the warehouse $y: 5 6eceivin& (from external source)7 includin&: - 'tandard receivin& - "irect receivin& - 6eceivin& with inspection - %iscellaneous receipt - (n<transit receipt - "irect or& transfer 5 W(P transactions (from internal manufacturin&)7 includin&: - W(P assem$ly completion - W(P component return $ost 0roup "nformation
(age 4 o& $#
!"4#$""!.doc )ev
)he rules en&ine can use any num$er of different attri$utes to assi&n cost &roups includin&: 5 'upplier 5 "escriptive flexfield information 5 .ustomer 5 (tem 5 =ocation 5 (tem cate&ory 5 (tem status 5 (tem disposition (used7 new7 and refur$ished) $ost 0roup Restrictions :fter the rules en&ine assi&ns the cost &roup7 the transaction mana&er chec!s for conflicts $etween the assi&ned cost &roup and cost &roups of existin& material in the location/ $ommingling %ultiple cost &roups of a sin&le item can reside in the same locator or =PN if material within each cost &roup that resides in the =PN or locator is uni;uely identifia$le/ -ou cannot perform a transaction in a commin&led =PN or locator/
(age 42 o& $#
!"4#$""!.doc )ev
<as= Assignment
*+plaining (as&s Warehouse %ana&ement uses tas!s to control the flow of material throu&h the warehouse/ (t dispatches tas!s to users $ased on s!ill sets/ -ou can &roup users into common s!ill set &roups and desi&nate them as resources/ -ou must define each s!ill and associate it with an employee $efore the system can dispatch tas!s to ;ualified users/ Warehouse %ana&ement uses the 8 % 6esource window to capture the s!ill sets of the employees re;uired to perform specific tas!s/ For each tas! that re;uires a uni;ue set of s!ills7 you must define a new resource/ Gowever7 if users that have the same set of s!ills can perform a variety of tas!s7 then you do not need to define individual resource types/ Describing the (as& (ype Assignment Process )he tas! type assi&nment process ena$les the system to assi&n tas! types you define $ased on any num$er of criteria includin&: 5 %aterial type: For example7 the tas! type assi&nment en&ine dispatches a refri&erated material pic! differently than a ha9ardous material pic!/ 5 )as! splittin& and mer&in&: )he system splits tas!s if the e;uipment re;uired cannot hold the num$er of containers the tas! re;uires7 or if the pac!in& containers the tas!
(age 4* o& $#
!"4#$""!.doc )ev
5 5
re;uires cannot fit the entire tas! ;uantity/ )he system mer&es tas!s if $ul! pic!in& is selected/ perator location: )he tas! dispatch en&ine considers the current location of the user and dispatches the next tas! $ased on proximity if the user meets the tas! criteria/ Exception messa&es: )he tas! dispatch en&ine has a set of predefined exception messa&es and transaction reasons7 which handle all &eneric exceptions durin& tas! dispatch7 and tri&&er appropriate actions and wor!flows $ased on these exceptions/
(age 44 o& $#
!"4#$""!.doc )ev
)ules and the )ules %ngine
Rules and the Rules *ngine -ou can use the rules en&ine to create rules to effectively dispatch tas!s and mana&e inventory/ -ou can use it to streamline pic!in& and put away of material7 assi&n newly received material to a cost &roup7 ensure customer compliant la$elin&7 assi&n tas!s to a resource with the appropriate trainin& and e;uipment7 and select the correct operation plan for tas!s/ -ou can create rules $ased on nearly any attri$ute in the data$ase7 includin& flexfields you define/ Restriction :ll rules have restrictions/ -ou compare two different attri$utes to define restrictions/ For instance7 a put away restriction that puts material away to the su$inventory 83=B7 e;uates the destination su$inventory with the text 83=B/ Strategies : strate&y is a se;uence of rules the rules en&ine runs to try to allocate material7 allocate space7 or fulfill a re;uest/ Pic!in&7 put away and cost &roup assi&nment rules use strate&ies/ -ou construct strate&ies in the 'trate&ies window from one or more rules/ -ou can reuse rules for multiple strate&ies/ (f a strate&y cannot find enou&h material to fulfill a pic! or find enou&h space for a put away7 then the material is $ac!ordered or the put away fails/ )his may $e the desired outcome7 or you may wish to put less restrictive rules at the end of the strate&y/ Other Rules $omponents
(age 4" o& $#
!"4#$""!.doc )ev
6ules and strate&ies have other components as well7 such as ;uantity functions7 allocation modes7 consistency restrictions7 return values7 and strate&y assi&nments7 which are covered in later modules/
(age 4$ o& $#
!"4#$""!.doc )ev
)ules %ngine >ses
Rules *ngine /ses -ou can use the rules en&ine to create six different types of rules7 includin& pic!in&7 put away7 tas! type assi&nment7 cost &roup assi&nment7 la$el format assi&nment7 and operation plan assi&nment/ Material Allocations for Pic&ing "irected pic!in& determines how material is allocated for an order7 and directs users to pic! material from specific locators/ Warehouse %ana&ement allocates stoc! to meet customer re;uirements such as stoc! condition7 stoc! ;uality7 lot expiration date7 or country of ori&in/ -ou can use a rule to allocate material $ased on F(F (first in first out) or FEF (first expired7 first out) rule at the or&ani9ation level/ -ou can also use pic!in& rules to perform a pic! that depletes a location in order to free up additional warehouse space7 or to perform a pic! $y cost &roup/ Directed Put Away Rules "irected put away directs users to put material receipts into the most appropriate locators/ 'ome common processes the rules model include: 5 %inimi9e item fra&mentation 5 .ontrol lot commin&lin& in a locator
(age 4# o& $#
!"4#$""!.doc )ev
5 "irect ha9ardous materials to a correspondin& ha9ardous stora&e location 5 'tore seasonal items in a su$inventory dependent on time of year 5 Put away material $ased on inspection results7 purchase order type7 or item cate&ory/ -ou can also put away material to locations the rules en&ine su&&ests for any items anywhere within the warehouse/ Note: Pic!in& and put away rules also have a ;uantity function7 which specifies how to determine the material availa$le for pic!in&7 or the space availa$le for put away/ (as& (ype Assignment Rules )as! type assi&nment captures s!ill sets and e;uipment re;uired for a warehouse tas!/ 3sers can si&n onto a mo$ile 6F device7 and optionally specify the availa$le e;uipment/ Warehouse %ana&ement assi&ns tas!s to users $ased on s!ill set7 e;uipment re;uirements and capacity7 or su$inventory/ For instance7 the system assi&ns ha9ardous tas!s to users with the appropriate ha9mat trainin&7 and can limit material put away to the top rac!s to users si&ned onto hi&h< reach for!lifts/ $ompliance %abeling Rules -ou can use the rules en&ine to select the appropriate la$el format7 type7 and printer for material7 $ased on customer7 carrier7 item cate&ory7 or transportation method/ -ou can then &enerate a la$el with the re;uired information and $arcode sym$ols for the material $ased on the result/ )he system can print different la$els for frei&ht carrier or shipment type/ )he rules en&ine can also &enerate la$els for use inside the warehouse/ $ost 0roup Rules .ost &roups capture the material valuation accounts necessary for trac!in& inventory value/ For instance7 you can set up different accounts for refur$ished7 consi&ned7 and company<owned inventory/ When material is received into the warehouse7 Warehouse %ana&ement determines the ownin& cost &roup and the material valuation accounts/ Operation Plan Selection Rules -ou create operation plan selection rules to determine the operation plan for consolidation/ For example7 if you want certain item cate&ories to &o throu&h a consolidation step7 and item cate&ories to $e dropped directly to a sta&in& lane7 you can create an operation plan selection rule that selects the operation plan $ased on the item cate&ory/
(age 4. o& $#
!"4#$""!.doc )ev
Material Allocation %;ample
Material Allocation *+ample 'uppose you run a warehouse that sells straw$erries/ )he straw$erries are set up as a lot controlled and expiration date controlled item/ )hey are also trac!ed $y the lot attri$ute ?rade/ Excellent7 ?ood7 and :vera&e are the possi$le &rades within the system/ 'upreme 8erries is a straw$erry distri$utor7 and does not accept :vera&e straw$erries/ )hey re;uest Excellent straw$erries if they are availa$le7 $ut will accept ?ood straw$erries if necessary/ )he system allocates &raded lots on a FEF $asis/ .ost .utters ma!es straw$erry 1am/ )hey can use any &rade of straw$erry7 $ut $ecause they do not pay top dollar7 you prefer to ship them :vera&e straw$erries/ Gowever7 if there are no :vera&e straw$erries availa$le7 you ship hi&her &rade straw$erries/ =ots are allocated on a F(F $asis/ :ll other customers have no preference on the &rade of straw$erries they receive7 and they are allocated lots on a FEF $asis/
(age 4! o& $#
!"4#$""!.doc )ev
Allocation 4ecision <ree
Allocation Decision (ree )his decision tree represents the $usiness scenario from the previous slide/ "rawin& a decision provides a $aseline for the strate&ies and rules to define/ 8efore you set up rules and strate&ies7 you must understand the types of rules to model/ )hou&h you can create new rules and strate&ies without code chan&es7 it is important to carefully thin! throu&h your rules and strate&ies durin& implementation/ :dditionally7 well defined rules and strate&ies can $e reused in multiple strate&y assi&nments/
(age "0 o& $#
!"4#$""!.doc )ev
)ules 2etup
Rules Setup )he setup for pic!in& rules7 put away rules7 and cost &roup rules are similar/ 'ettin& up these rules involves three steps covered in the followin& slides/
(age " o& $#
!"4#$""!.doc )ev
4e&ining )ules? )estrictions
Rule Restrictions -ou define rules for pic!in& and put away tas!s $ased on availa$le items and locators/ Pic!in& rules can place restrictions on lot attri$utes7 source su$inventory or locator7 item cate&ory7 or any of hundreds of other item attri$utes/ )he rules en&ine does not allocate material that does not meet the rule restrictions/ (f the availa$le ;uantity is as indicated a$ove7 and the sin&le restriction Ilot &rade of ExcellentJ is imposed7 then the rules en&ine does not consider &ood and avera&e straw$erries/
(age "2 o& $#
!"4#$""!.doc )ev
4e&ining )ules? 2ort Criteria
Sort $riteria 'ort criteria specify the most desira$le material that meets the restrictions of the rule/ )he example a$ove sorts the excellent straw$erries in order of expiration dateK those that expire first are shipped first/
(age "* o& $#
!"4#$""!.doc )ev
4e&ining )ules? 4e&ault
Defining Rules2 Default -ou can also define a default rule that does not have any restrictions/ -ou can assi&n a default rule as part of a strate&y7 or as the or&ani9ation default pic!in& or put away rule7 that executes if the rules en&ine does not return an applica$le strate&y assi&nment/ (n this example any availa$le $ox of straw$erries meets these restrictions/
(age "4 o& $#
!"4#$""!.doc )ev
2trategies
Strategies : strate&y is a list of se;uential rules the rules en&ine applies until a tas! is performed/ nce the rules en&ine determines the strate&y it does not search for another strate&y if it cannot fulfill the tas!/ )herefore7 unless you want the strate&y to fail7 the last rule of a strate&y should $e a &eneric rule with no restrictions/ Assigning Strategies in the Rules Wor&bench -ou can assi&n strate&ies to various o$1ects or com$inations of o$1ects in the rules wor!$ench such as customer7 vendor7 transaction type7 or item cate&ory/ -ou can also specify dates for strate&ies in the rules wor!$ench/
(age "" o& $#
!"4#$""!.doc )ev
<as= <ype, 5a+el 3ormat, and Operation (lan 2election )ules
(as& (ype# %abel !ormat and Operation Plane Selection Rules )as! type rules7 la$el format rules7 and operation plan rules are not assi&ned to strate&ies7 $ut are automatically lin!ed directly to an or&ani9ation/ 6ule wei&hts determine the search order7 and you can set a rule wei&ht for each rule/ 6ules with hi&her wei&hts ta!e precedence over rules with lower wei&hts/ For example7 an or&ani9ation has three types of tas!s: 5 G:L%:) tas! < 6e;uired whenever item has a G:L%:) code 5 Gi&h reach < 6e;uired whenever an item is in a locator with rac! num$er &reater than F 5 "efault tas! < :ll other tas!s :ssumin& the G:L%:) tas! ta!es priority (if a tas! is $oth a G:L%:) tas! and a hi&h reach tas!7 then G:L%:) tas! should $e returned)7 three rules are re;uired: D/ Gi&h wei&ht rule: (f item has a G:L%:) code7 return G:L%:) tas! @/ %id wei&ht rule: (f item is in a rac! &reater than F7 return hi&h reach tas!/ E/ =ow wei&ht rule: 6eturn default tas!/
(age "$ o& $#
!"4#$""!.doc )ev
Consistency )e/uirements
$onsistency Requirements .onsistency 6e;uirements are uni;ue to pic!in& rules/ )hey ensure all allocations for a particular line have one or several common criteria/ )he most common consistency re;uirement is customer acceptance of a sin&le lot/ )his means a customer does not accept an order if it contains more than one lot/ -ou can set up a rule strate&y for a customer that prefers a sin&le lot7 $ut accepts mixed lots if necessary/ -ou can also use consistency re;uirements for other lot and allocation attri$utes/ Note: 6ules that include consistency restrictions do not perform partial allocations/ (f the allocation ;uantity cannot $e found in its entirety7 the rule does not allocate at all/
(age "# o& $#
!"4#$""!.doc )ev
)ules 2imulation
Rules Simulation For more information on rules simulation see: Explainin& the W%' 6ules En&ine 'imulator7 Oracle Warehouse Management Users Guide.
(age ". o& $#
!"4#$""!.doc )ev
)314 <echnology
R!"D 6F(" is a technolo&y that ta&s physical items with a uni;ue identifier a scanner can read/ -ou can associate the identifier with a system representation of the o$1ect that contains all associated item records/ :n 6F(" device can communicate directly with Warehouse %ana&ement via the racle 'ensor Ed&e server7 which receives the physical details of an 6"(" reader and filters out $ac!&round noise/ Warehouse %ana&ement can tri&&er a response messa&e to si&nal a li&ht stac!7 $u99er7 or messa&e $oard via the 'ensor Ed&e server to provide the user with physical confirmation of the transaction7 which is performed without a 3( or mo$ile device/
(age "! o& $#
!"4#$""!.doc )ev
5a+eling
Supplier %abeling -ou can scan and print $ar codes for material you receive in to the warehouse/ )his results in less receipt processin& time7 immediate reco&nition of availa$le materials7 and hi&her receivin& accuracy/ $ustomer %abeling -ou can produce customer specific la$els on demand for each shipment7 to comply with customer re;uirements for $ar code la$elin& and advance shipment notifications (:'Ns)/ Manufacturing -ou can use compliance la$elin& within manufacturin&/ )here are four ma1or points identified where Warehouse %ana&ement prints la$els for manufacturin&: 5 Prior to the start of the first operation < For example7 a la$el that contains routin& information/ 5 "urin& any operation < 8ased on a special outcome of an operation7 the location of the next assem$ly routin& may $e dynamically determined/ )he system can print a la$el to route the material to the desired destination such as a scrap su$inventory/
(age $0 o& $#
!"4#$""!.doc )ev
:fter ;uality inspection of an operation C )he material may not pass inspection/ )he system can print a la$el that sends the material to a prior operation7 to scrap7 or forward to the next operation/ 5 :t assem$ly completion < :n or&ani9ation may $uild finished &oods or assem$le to order products/ )he system can print a stoc! la$el that contains the finished &oods information7 or a shippin& la$el for assem$le to order products that contains the shippin& instructions7 address7 and the sales order num$er/ Other (ransactions )he a$ove examples are 1ust a few of the automatically tri&&ered la$el flows/ =a$els can also $e tri&&ered $y cycle countin&7 physical countin&7 purchase order receipts7 pac!in& or movement transactions/
(age $ o& $#
!"4#$""!.doc )ev
5a+el <ypes
%abel (ypes )he system supports the followin& la$el types: 5 %aterials: )his la$el provides information a$out the item7 includin& lot information if applica$le/ 5 'erial: )his la$el provides information specific to the serial num$er of the item/ 5 =ocation: )his la$el provides information a$out specific warehouse locators/ 5 W(P .ontent: )his la$el provides information a$out W(P components pic!ed for a 1o$/ (t includes the component num$er7 serial7 lot7 1o$ num$er7 assem$ly num$er7 and start date/
(age $2 o& $#
!"4#$""!.doc )ev
5a+el <ypes
%abel (ypes -$ont. 5 =PN: )his la$el provides information a$out the =PN/ (t does not contain content information/ -ou use this information to trac! the =PN throu&h the warehouse/ 5 =PN .ontent: )his la$el provides information a$out the =PN and content details/ 5 =PN 'ummary: )his la$el provides information a$out the =PN and a summary of the contents/ (f the =PN contains nested =PNs7 the la$el also summari9es the content of those =PNs/ 5 'hippin&: )his la$el provides information a$out the out$ound shipment/ (t does not include shipment content information/ 5 'hippin& .ontents: )his la$el provides information a$out the out$ound shipment and the contents of the shipment/
(age $* o& $#
!"4#$""!.doc )ev
5a+el 3ormats
(age $4 o& $#
!"4#$""!.doc )ev
Assigning 5a+el <ypes to @usiness 3lows
(age $" o& $#
!"4#$""!.doc )ev
Agenda
(age $$ o& $#
!"4#$""!.doc )ev
2ummary
(age $# o& $#
!"4#$""!.doc )ev

Warehouse Overview

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Warehouse Overview

Diunggah oleh

Hak Cipta:

Format Tersedia

Oracle Warehouse Management Overview

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Oracle Warehouse Management Overview

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

i Oracle Warehouse Management Overview

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

(age " o& $#

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

(rocesses o& a Warehouse

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Additional (roduct )e/uirements

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Warehouse Management Application 0ierarchy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

1nventory, Warehouse Management and M2CA

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

)adio 3re/uency 4evices

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Overview o& 1n+ound 5ogistics

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

(age " o& $#

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Overview o& Out+ound 5ogistics

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

6alue Added 2ervices

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy

2torage and 3acility Management

Oracle Warehouse Management Overview %&&ective mm'dd'yy

(age 2" o& $#

Copyright Oracle, 2004. All rights reserved.

Oracle Warehouse Management Overview %&&ective mm'dd'yy