Warehouse Management

Warehouse Management
The Oracle Warehouse Management system (WMS) is a component of Oracles Supply Chain Management and Manufacturing solution. It spans the areas of warehouse resource management warehouse configuration tas! management ad"anced pic! methodologies and "alue added ser"ices.
Warehouse Activities
Receiving: #ecei"e Materials and finished goods Put away: $ut away materials and finished goods you recei"e (the process of mo"ing recei"ed items to storage and recording the related transaction) Storage: Store Items within the warehouse Picking: $ic! orders for manufacturing and shipping Packing: $ac! orders for shipping Shipping: Ship order to customers Value Added Services% $rinting
Comparison of the modules

In comparison to In"entory WMS pro"ides the following ad"antages &.& #ules ' Operation $lan $utaway Cost (roup Tas! Type $ic!ing and )a*el $rinting &.+ Material Management')$,s &.- Tas! Management &.. )a*or Management +.& In *ound logic +.+ Out *ound )ogic +.- Cross doc!ing +.. Cartoni/ation Consolidation and $ac!ing +.0 Shipping
-.&. Cost (roup -.+ )a*el $rinting 1 #2I3
Warehouse Management Setup

This section pro"ides an o"er"iew of the setup re4uirements for Oracle Warehouse Management system (WMS).Setting up Oracle WMS includes setting up related Oracle applications such as Oracle In"entory and Oracle 5ills of Material. Therefore you might only need to ma!e WMS modifications specific to e6isting data li!e e6isting items. Chec! with your implementation team to determine which setup re4uirements ha"e already *een fulfilled. Oracle Warehouse Management system re4uires that Oracle In"entory Oracle $urchasing (#ecei"ing) and Oracle Order Management (Shipping) are installed and set up. This chapter co"ers the following topics% &. +. -. .. 0. 9. :. ;. O"er"iew of Oracle Warehouse Management Setup Warehouse Organi/ation Setup Set 7p Su*in"entory $arameters Set 7p )ocator $arameters Setting 7p )ocator 8ones Material Setup 3efining Shipping $arameters Implementing $rofile Options
ocator !ones
< /one is a logical grouping of locators. < /one may represent a specific wor! area(s) such as a $ac!ing station(s) or it may =ust indicate an area where material mo"ement occurs. The locators for a /one may span one or more su*in"entories >ou can specify a /one for an operation when you define the operation plan. This association determines the candidate set of locators where the particular operation is performed. >ou can use /ones to define the path that material ta!es in the course of completing an acti"ity. 3efining /ones is not mandatory especially if the warehouse is small and the operations are not comple6 where su*in"entories and ? or locators could suffice. >ou can also use /ones for wor!load *alancing and optimi/ation. 7sers can optionally sign'on to /ones and conse4uently can only perform tas!s that originate within the /one.
&. ,a"igate to the 8one Summary window. +. @nter the name of the /one in the ,ame field. -. Optionally enter a description of the /one in the 3escription field. .. Optionally select a 3isa*le 3ate from the list of "alues. If you enter a date in this field the /one is disa*led on this date. 0. Choose the @na*led 2lag to ena*le the /one. 9. Sa"e your wor!. :. Choose Aiew?Modify to open the Aiew Modify )ocators window
"ask Setup Steps

Su*mitted *y <nonymous on Mon &B?+0?+B&B ' B+%BTag%
Warehouse Management ?
Tas! planning is the release of wor! to the warehouse floor in order to optimally run the day'to'day warehousing operations. Tas!s are comprised of demand pic! tas!s for sales orders wor! orders and replenishment. Tas!s are also comprised of in*ound recei"ing and put away tas!s slotting in"entory transfer tas!s in"entory control related cycle counting tas!s and in*ound'out*ound hy*rid crossdoc!ing tas!s. Once multiple tas!s are created from the "arious tas! creation sources they are placed in one single pool and released appropriately to the warehouse floor for optimal operation of the warehouse. Optimi/ation is performed *y tas! interlea"ing and resource'wor!load *alancing. Wa"e planning in warehousing plans the allocation and release of material to the warehouse floor in the form of wor!?tas!s in order to fulfill the "arious !inds of material demand. It plans the release of material to fulfill sales orders wor! orders and replenishments. >ou need to *e a*le to plan the release of tas!s in the warehouse on a day'to'day *asis so that you can run operations optimally to minimi/e cost and ma6imi/e producti"ity. To do this you need a single wor!*ench that ena*les you to "iew the entire wor!load for one or more days. 7sing the Warehouse Control 5oard you can 4uery tas!s *ased on multiple criteria re'prioriti/e and interlea"e them and release them to the warehouse floor in the form of tas! wa"es.
#$uipment % #mployee
Su*mitted *y <nonymous on Tue &B?+9?+B&B ' B&%+0 Tag%
WMS &' Set up &' Resources &' #$uipment
Rules % Strategies
Su*mitted *y <nonymous on Wed &+?&0?+B&B ' &-%&C Tag%
>ou use a series of Oracle Warehouse Management rule types to set up "arious rules for your warehouse. <lthough you use the same windows to set up all rules the setup that is re4uired for Cost (roup $ic!ing and $ut <way rules differ from the setup that is re4uired for Tas! Type )a*el 2ormat and Operation $lan Selection rules. >ou do not assign tas! type la*el format and operation plan selection rules to strategies. #ather the rules engine automatically lin!s these types of rules directly to the organi/ation when you ena*le the rule . The search order is determined *y a weight applied. The larger the num*er the higher the weight. >ou can assign weights only to tas! type assignment la*el rormat and operation plan selection rules. 7se the following windows to set up rules% &. #ules window +. Strategies window -. #ules Wor!*ench Rules
< rule is one or more restrictions that must *e fulfilled to satisfy a *usiness or customer re4uirement. 2or pic!ing and put away rules you assign a sort criteria that determines in which order the system uses a rule to suggest an allocation. $ic!ing and put away rules also ha"e a 4uantity function that specifies the 4uantity considerations used to determine the material a"aila*le for pic!ing or the space a"aila*le for put away. Cost group tas! type la*el assignment and operation plan selection rules ha"e a return "alue that returns a "alue *ased on the type of rule that you define. If all of the restrictions are met for a particular cost group tas! type la*el assignment or operation plan selection rule then the return "alue pro"ides the name of the tas! type la*el format cost group or operation plan.
#(amples of )uantity *unctions D $ic!ing rule% a"aila*le to reser"e D $ut away *ased on locator weight capacity only D $ut away% use a custom function to determine the destination locator capacity #(amples of Return Values #eturn "alues are used in cost group tas! type la*el format and operation plan selection rules. If the rule restrictions are met then the rules engine returns the "alue specified. 2or e6ample if an item has a E<8M<T code then the return "alue for a tas! type might *e Ea/ardous. In this case the system assigns the tas! to an operator who is 4ualified to handle ha/ardous materials. Strategies < strategy is an ordered se4uence of rules that the system uses to fulfill comple6 *usiness demands. The system selects the rules of a strategy in se4uence until it fully allocates a pic!ing or put away tas! or until it finds a cost group that meets restrictions. When you define strategies you also specify the date or range of dates on which the strategy is effecti"e.
When setting up strategies you also specify whether you want the system to use a rule if it can only allocate some of the material or space re4uired *y that allocation. ,ote% Strategies are not used for tas! type la*el format and operation plan selection rules. Strategy #(ample The following figure pro"ides a graphical e6ample of a simple strategy that includes two rules% a rule that specifies to put the item away to an empty refrigerated location and a rule to put away to any refrigerated location. +,-ects O*=ects are the entities that you use within a rule. They correspond to ta*les and their attri*utes (or columns). Oracle Warehouse Management also includes two o*=ects you can use to specify constant "alues% Constant Character and Constant ,um*er. >ou select constant character or constant num*er when you want to specify a specific parameter "alue for an o*=ect. 2or e6ample you might set the parameter item num*er e4ual to the constant num*er +-.0.. In this case the constant "alue would *e +-.0. and represents the item num*er.
WMS Rules #ngine

Su*mitted *y <nonymous on Wed &+?-B?+BBC ' &9%.& Tag%
The Oracle Warehouse Management (WMS) rules engine pro"ides a repository for restrictions and *usiness policies related to your warehouse. >ou define and implement rules directly from standard Oracle <pplications forms without ha"ing to write custom code. Instead you can compose rules *y selecting "arious elements from lists of "alues. Special security features ha"e *een included in the rules engine to pre"ent modification of rules that are currently in use. Rules #ngine Capa,ilities and Rule "ypes
5ased on the restrictions that you define the WMS rules engine performs the following acti"ities%

@na*les directed pic!ing ' 3irected pic!ing @na*les directed put away ' 3irected put away <ssigns cost groups to recei"ed material ' Cost group assignment <ssigns tas!s to a resource with the appropriate training and e4uipment ' Tas! type assignment 3etermines which operation plan will *e used for consolidation ' Operation plan selection @nsures customer compliant la*eling ' )a*el format assignment
Put Away Rules $ut away rules directs operators to put newly recei"ed material into the most appropriate location. >ou can *ase the rule on "irtually any *usiness process and the rules engine pro"ides intelligent suggestions for put away locations for the material. Some typical processes that put away rules are capa*le of modeling include the following% D 3irect an operator to put away an item in the same locator where other 4uantity of the item already resides. This minimi/es item fragmentation. D $rohi*it commingling of different items or different lots of the same item in a single locator D <"oid lot commingling in a locator D 5ase the put away location on inspection results the type of purchase order or item category >ou can also use the rules engine to suggest locations to put away any item anywhere within the warehouse. Picking Rules 3irected pic!ing creates material allocations and directs operators to pic! material from specific locations. To ensure proper stoc! rotation you can set up pic!ing rules to allocate material using 2I2O (2irst In 2irst Out) or 2@2O (2irst @6pired 2irst Out). >ou can also set up the rules engine to meet customer re4uirements such as stoc! conditionor 4uality. 2urthermore you can set up different rules to deplete a locator to free up additional warehouse space or to pic! *y cost group ownership for particular customers.
"ask "ype Assignment Rules 5ased on user'defined criteria such as the source su*in"entory locator or item attri*utes the rules engine can identify the tas! type for each tas! that is generated *y the system. Tas! type assignment captures the s!ill sets and e4uipment re4uired for a warehouse tas! ensures the system assigns the tas! to the appropriate operator . <n operator can sign onto a mo*ile radio fre4uency (#2) de"ice and optionally specify the e4uipment they are using. 5ased on the operator s!ill set the e4uipment re4uirements and the e4uipment capacity the rules engine can then assign tas!s to the operator. In some cases the system assigns tas!s *ased on the su*in"entory in which the tas! occurs. 2or e6ample the rules engine assigns ha/ardous tas!s to personnel who ha"e completed ha/ardous material handling training. <nother tas! assignment e6ample might include limiting put aways to top rac!s to those operators who signed on to a high'reach for!lift. Cost .roup Rules Cost groups capture the material "aluation accounts necessary for trac!ing in"entory "alue. 2or e6ample you might set up different accounts for refur*ished "ersus new goods or for consigned goods that might ha"e cost groups that are tied to the owning company. When material is recei"ed into the warehouse the rules engine can automatically determine the owning cost group. The rules engine automates cost group assignment decisions thus remo"ing the comple6ity of ma!ing this decision from the warehouse floor. 2or e6ample the rules engine can ma!e a cost group assignment *ased on sales channel *y assigning different cost groups to internet orders and in'store orders. The rules engine can also ma!e a cost group assignment *ased on inspection results. It can assign an item that fails inspection to a FEoldF cost group. The rules engine can also assign cost groups *y "endor site item category item. If you do not assign a cost group rule for a particular item then the system uses the default cost group of the storage su*in"entory where the item resides. a,el *ormat Assignment Rules The rules engine selects the appropriate la*el format and content for the *usiness need. With the compliance la*eling feature la*els with the re4uired information *ar'code sym*ols and layout can *e generated for each item and container. +peration Plan Selection Rules Consolidation is the process of *ringing material from "arious parts of the warehouse together. Operation plan selection rules correspond to the three modes of consolidation% )$, )ocator and )$, and )ocator. There are three types of operation plans in*ound crossdoc! and out*ound. >ou use these plans to *uild the operation plan selection rules. >ou also use operation plan selection rules to determine if you can consolidate material across out*ound deli"eries. Oracle Warehouse Management allows you to create in*ound and crossdoc! operation plans. >ou cannot create out*ound operation plans. Oracle Warehouse Management is seeded with the following out*ound operation plans% D )$, *ased consolidation in staging lane within deli"ery D 3irect consolidation in staging lane across deli"eries
Rules Window
Su*mitted *y <nonymous on Tue &+?&.?+B&B ' &;%09
Tag%
7se the Oracle Warehouse Management #ules window to set up any of the si6 rules types% $ic!ing $ut away Cost group Tas! type )a*eling Operation plan selection &. Setup for pic!ing and put away rules differs from the setup for cost group tas! type la*el assignment and operation plan selection rules. $ic!ing and put away rules re4uire a 4uantity function and use an optional sort criteria while the assignment'type rules re4uire a return "alue. $ic!ing rules also ha"e optional consistency re4uirements as well as the choice of allocation modes. +. In the header section of the Oracle Warehouse Management #ules window you select the type of rule to define. >ou also specify a name and description for the rule and the 4uantity function or return "alue. If you are creating a pic!ing rule you also specify the allocation mode for the rule. -. >ou must also ena*le the rule if you want the system to consider it for use in a strategy. <fter you ena*le it the system also chec!s the rule for proper synta6. ,ote% <fter you ena*le a rule you cannot change it. 2urthermore rules that you assign to a strategy cannot *e disa*led. To modify a rule already assigned to a strategy you must disa*le the strategy and then disa*le the related rule. If an ena*led rule has not *een assigned to a strategy and you need to modify it clear the @na*led chec! *o6. .. >ou can optionally ma!e the rule a"aila*le to all of the organi/ations in your company. If you ena*le a pic!ing or put away rule in all organi/ations then other organi/ations can include it in strategies. If you ma!e a tas! type la*el format and operation plan selection rules a"aila*le to all organi/ations then all organi/ations will use the rule *ecause there are no strategy assignments for these types of rules.
0. The rules engine comes seeded with se"eral *asic rules. 2or seeded rules the 7ser 3efined chec! *o6 is clear. >ou cannot edit seeded rules *ut you can use the rule copy function on the Tools menu to copy a rule. Restrictions "a, >ou specify the *usiness o*=ects their related parameters and the restrictions of the rule. @ach line in corresponds to a restriction on the #estrictions ta*. >ou use the <,3 and O# operators to =oin multiple lines of restrictions. >ou use the open and close parenthesis to create comple6 compound statements. The Se4uence ,um*er field in this window ena*les you to specify the se4uence in which the restrictions are lin!ed together. ,ote% When you set up restriction se4uence num*ers consider a num*ering scheme such as &B +B -B. This ena*les you to easily add more restriction lines if necessary.
Rules Work,ench
Su*mitted *y <nonymous on Wed &+?&0?+B&B ' &.%+: Tag%
The #ules Wor!*ench ena*les you to assign strategies rules and cost group "alues directly to any num*er of o*=ects in an assignment matri6. The #ules Wor!*ench pro"ides you with the following functionality% D <dd update or delete strategies rules and cost group "alues in the selection criteria D @na*le and disa*le selection criteria in the assignment matri6 D Eide and show columns of the strategy selection matri6 *ased on user preferences D Guery where a rule strategy or cost group "alue is assigned D <ssign crossdoc! criteria to *usiness o*=ects for planned and opportunistic
The #ules Wor!*ench is comprised of two regions%
Rules Work,ench "ree #ules Wor!*ench tree displays a "iew of all the rules and strategies that are a"aila*le in the organi/ation. In the #ules Wor!*ench a rule type to "iew to assign The #ules Wor!*ench contains the following rule types%

$ic!ing $utaway Cost group $lanned crossdoc! Opportunistic crossdoc!
@6pand the #ule Type node in the tree to see a list of all "alid rules and strategies you can use in the organi/ation. The strategies can then *e e6panded to see the rules that are used for that strategy. >ou can hide the tree from "iew so that a greater area of the window is a"aila*le to ma!e the return type assignments.
#ules Wor!*ench Matri6
>ou assign rules to *usiness o*=ects in the rules wor!*ench matri6. >ou identify the return type which is a strategy rule or "alue and the name of the strategy rule or "alue. >ou enter the specific strategy to e6ecute date effecti"ity and se4uence. The rules wor!*ench uses the other
columns to indicate under what conditions each assignment is applica*le. >ou can also ma!e assignments *ased on supplier item item category transaction type user unit of measure pro=ect and many other o*=ects. The "alues in each field are restricted to "alid "alues for the organi/ation. The organi/ation column always defaults to the current organi/ation and cannot *e changed *ecause all rule assignments are organi/ation specific. Rules #ngine /ehavior The #ules @ngine e"aluates the assignments in the #ules Wor!*ench after filtering out any assignments that are not ena*led or not currently effecti"e. The remaining assignments are e"aluated in the user'defined se4uence and the system returns the first return type in which all the "alues in the assignment match the attri*utes of the record in the #ules @ngine. If the #ules @ngine returns a strategy instead of a rule then the system e"aluates the rules in the strategy in se4uence. If after the #ules @ngine e"aluates all the pic!ing or putaway rules in a strategy and the allocation is not wholly allocated then the remaining 4uantity remains unallocated. If the system cannot find a cost group rule in the strategy then the system uses the default cost group for the su*in"entory. The #ules @ngine ne"er attempts to retrie"e a second strategy from the #ules Wor!*ench. If it cannot find a match then the system uses the default pic!ing and put away rules for the organi/ation and the default cost group for the su*in"entory.
Strategies Window
Su*mitted *y <nonymous on Wed &+?&0?+B&B ' &-%.; Tag%
<fter you define your rules you must set up a strategy and then associate the applica*le rules. <fter you assign rules to a strategy the rules engine can e6ecute the strategies on any o*=ects to which the strategy applies. The rules engine e6ecutes each su*se4uent rule in your strategy until an allocation is completely filled. <fter the rules engine finds a strategy it will not continue to another strategy if the tas! cannot *e fulfilled *ased on the first strategy. Therefore unless you want the strategy to fail if specific restrictions are not met the last rule in your rule strategies should *e a default rule that includes no restrictions. >ou set up strategies in the Oracle Warehouse Management Strategies Window. When you define strategies "erify that the 7ser 3efined chec! *o6 is selectedH for seeded strategies the 7ser 3efined chec! *o6 is clear. >ou cannot modify system defined strategies howe"er you can copy them using the strategy copy function located in the windowIs tool *ar. Ma!e sure you ena*le the strategies so that the strategies can later *e assigned in the #ules Wor!*ench. To add rules strategy you specify a se4uence num*er in which you want the rule to *e considered (within the strategy) and then use the list of "alues in the #ule ,ame field to select the rule that you want to add. The $artial Success <llowed chec! *o6 ena*les the system to only partially fulfill the re4uirements of a ruleIs allocation and then mo"e onto the ne6t rule in the strategy. ,ote% @na*led strategies cannot *e modified. To modify a strategy you must disa*le the strategy *y clearing the Strategy @na*led chec! *o6
Material Management
Su*mitted *y <nonymous on Sun &B?&:?+B&B ' &9%B0 Tag%
P0 Management: Warehouse Management ena*les operators to trac! the contents of any container in recei"ing WI$ in"entory shipping and in'transit. In Oracle Warehouse Management a license plate num*er ()$,) is any o*=ect that holds items. <lthough )$,s are associated with containers they do not need to represent a physical entity such as a *o6. Thus you can define an )$, as a collection of items. Oracle Warehouse Management ena*les you to trac! transact and nest )$,s. Advanced ot and Serial Control: Warehouse Management ena*les operators to split merge and rename lots. Material Status Control: Material status control ena*les operators to control the eligi*ility of material for "arious transactions. Material Status control restricts the mo"ement and usage of portions of on'hand in"entory. 7sing material status control ena*les you to control whether you can pic! or ship an internal order or sales order or issue material for a wor! order. >ou can also specify whether material needs to *e 4uarantined until you inspect it. In addition you can determine whether products with a particular status can *e reser"ed included in a"aila*le to promise calculations or netted in production planning. >ou assign material statuses at four le"els% su*in"entory locator lot and serial. 1nventory *eatures: Warehouse Management facilitates the mo"ement of goods in to out of and within the warehouse. Counting: operators can perform cycle counts and physical in"entory counts. Replenishment: Warehouse Management ena*les managers to manage in"entory le"els using any com*ination of planning and replenishment features including% min'ma6 planning reorder point planning or !an*an replenishment. >ou can use In"entory and M#$ replenishment planning dynamic replenishment and replenishment direct from recei"ing.
2an,an Management: Warehouse Management supports *oth internal and e6ternal supplier !an*ans. Jan*an is a means of supporting pullK*ased replenishment in manufacturing systems. Workflow /ased #(ception Management: >ou can configure real'time alerts and wor!flow *ased notifications of supply chain e"ents to impro"e the efficiency of *usiness operations. 2or e6ample when an operator pic!s less than the re4uired amount for an order wor!flow sends a notification to the operator to count the locator.
icense Plate 0um,ers 3 P0s4

Su*mitted *y <nonymous on Sun &B?&:?+B&B ' &C%.B Tag%
In Oracle Warehouse Management a license plate num*er ()$,) is any o*=ect that holds items. <lthough )$,s are associated with containers they do not need to represent a physical entity such as a *o6. Thus you can define an )$, as a collection of items.
< single )$, contain many 4uantities of the same item and or? differnt item @6% )$, )BB& contains the item BB& )$, )BB+ contains &B 4uantities of item BB& )$, )BB- contains &B 4uantities of item BB& and & 4ty of item BB+ )$, )BB. contains &B 4uantities of item BB& item BB+ and item BBOracle Warehouse Management ena*les you to trac! transact and nest )$,s. >ou can use )$,s in the following ways%
&. Store information a*out an )$, such as item re"ision lot serial organi/ation su*in"entory or locator +. Trac! contents of any container in recei"ing in"entory or in'transit -. #ecei"e store and pic! material *y )$, .. Aiew on hand *alances *y )$, 0. Mo"e multiple items in a transaction *y )$, 9. Transfer )$, contents :. $ac! unpac! consolidate split and update )$,s ;. $rint la*els and reports for referencing container contents C. Trac! nested )$,s Oracle Internal 1 O<I 7se OnlyOracle Only &B. #euse empty )$,s &&. #ecei"e and send )$, information on an <S, 0esting icense Plate 0um,ers
Oracle Warehouse Management ena*les you to nest )$,s. 2or e6ample pallet )$, $0000 contains three nested )$,s% )$, $000+ )$, $000- and )$, $000.. In the system you would see )$, $0000 as the top'le"el )$, and each of the of the three *o6 )$,s would fall under )$, $0000. >ou can nest )$,s within other )$,s. In the a*o"e e6ample item < is pac!ed in )$, + and )$,& )$,+ and )$,- are nested within )$,.. When you transact )$,. all of the )$,s nested within it are transacted. 0ote: If Oracle Warehouse Management is ena*led in an Oracle $ro=ect Manufacturing organi/ation co' mingling of pro=ect and tas! material is not allowed in an )$, at any le"el of nesting. <lso pro=ect and tas! material cannot *e mi6ed with non'pro=ect and tas! material in an )$,.
P0 Conte(t
Su*mitted *y <nonymous on Mon &B?&;?+B&B ' B&%+0 Tag%
Warehouse Management
Warehouse Management defines a conte6t for each )$, to denote the current state. >ou can use these conte6ts to define speciali/ed pic!ing and put away rules. >ou can also 4uery *y conte6t in the material wor!*ench. 565 Pre&generated $re'generated )$,s e6ist in the system *ut are not associated with any physical material. 567 8efined ,ut not 9sed This conte6t refers to a defined )$, that does not contain material. <n e6ample is a reusa*le tote an operator can use to pic! orders. 765 Resides at Vendor Site When a "endor sends an <d"anced Shipment ,otice (<S,) <S, Warehouse Management generates an )$, and associates it with the material information on the <S,. Warehouse Management does not recogni/e material associated with )$,s of this conte6t as on hand or costed. 767 Resides in Receiving <n )$, with this conte6t indicates material associated with this )$, was recei"ed using a standard routing or inspection routing receipt *ut still resides at the recei"ing doc!. The material does not reside in in"entory and is not costed.
76: Resides in 1nventory <n )$, with this conte6t indicates material associated with this )$, is costed and accounted for in in"entory. an operator cannot this conte6t when recei"ing material against a standard or inspection routed receipt *ut can use it for a direct deli"ery routed receipt. operators can perform out*ound transactions on )$,s with this conte6t. :65 Pre&Pack for W1P )$,s that reside in WI$ and are associated with material pre'pac!ed in WI$ recei"e this conte6t. This conte6t is used after Warehouse Management associates the )$, with the material *ut the material is not physically pac!ed in the )$,. :67 Resides in W1P <n )$, with this conte6t indicates material associated with this )$, is currently part of a WI$ operation. The material does not reside in in"entory and is not costed. ;65 Picked $ic!ed )$,s recei"e this conte6t. They are in'transit within the warehouse. ;67 Packing The system uses this conte6t internally as an intermediary during pic!ing put away or pac!ing. 3o not use it anywhere including the setup of pic!ing or put away rules. ;6: oaded for Shipment This conte6t refers to material loaded for shipment onto a carrier that is ready to lea"e the warehouse. Once the carrier lea"es the doc! the )$, conte6t changes to resides in in'transit or issued out of stores. ;6; 1ssued out of Stores )$,s with this conte6t do not reside in the warehouse. Eowe"er the system retains the )$, transaction history. )$,s shipped out of in"entory recei"e this conte6t and cannot *e recei"ed again. <6 Resides in 1n&transit <n )$, with this conte6t indicates material is mo"ing from one location to another. 2or e6ample when an )$, mo"es from one organi/ation to another. )$,s in this conte6t are in an intermediary state *ut are accounted for in the system. This conte6t is used only for inter'org transit or internal sales orders where an indirect shipping networ! is defined *etween the organi/ations.
.enerating icense Plate 0um,ers

Su*mitted *y <nonymous on Sun &B?&:?+B&B ' +-%&; Tag%
>ou can generate )$,s using one of the following methods%
&. <utomatically *y su*mitting a concurrent re4uest +. Manually *y generating )$,s using a mo*ile de"ice >ou can su*mit a concurrent re4uest to generate multiple )$,s. &L These )$,s might *e associated with a particular container item or they could *e simply la*els with no physical container association. +L Those )$,s can *e generated at the su,inventory and locator or they could ha"e no location until they are pac!ed. 2or e6ample assume that you want to assign )$,s to large *o6es that will *e stored in a particular su*in"entory and locator. In this case you can su*mit a re4uest to direct the system to generate the num*er of )$,s that you need *ased on the parameters that you specify in the concurrent re4uest. In another e6ample a warehouse manager might pregenerate hundreds of )$, la*els and distri*ute these preprinted la*els to the warehouse operators. This way whene"er an operator needs a new )$, he or she can peel off the ne6t la*el and use it rather than ha"ing to print a la*el with each new transaction. Su,mitting a concurrent re$uest
To su*mit the )$, generation re4uest you must select the (enerate )icense $lates option from the Oracle Warehouse Management ,a"igator. ,e6t select (enerate )$, as the re4uest that you want to su*mit and then indicate the appropriate )$, generation parameters in the $arameters window
9sing a Mo,ile 8evice to .enerate P0s
)$,s can *e generated at their point of use in mo*ile receipt and tas! forms. When the cursor is in the )$, field press (enerate to automatically generate the )$,. The system default shortcut !ey for (enerate is MCT#)NOM(N. This can *e customi/ed for each mo*ile de"ice. The actual !ey mapping is stored in the default.ini file
Viewing P0s
Su*mitted *y <nonymous on Mon &B?&;?+B&B ' BB%0C Tag%
>ou can use the Material Wor!*ench or the mo*ile user interface to "iew the contents of an )$,.
In the Material Wor!*ench you can "iew the attri*utes of a particular )$,. 7se the following instructions to "iew the contents of an )$,. &. ,a"igate to the Material Wor!*ench window +. In the Aiew 5y field select )$, from the list of "alues. -. @6pand the Organi/ations folder to display a list of )$,s for the organi/ation. .. Select the )$, that you want to "iew. The system displays the contents of the )$, in the right panel of the window. >ou can also e6pand an )$, in the left column to "iew its specific contents. Continue e6panding the )$, to see increasing le"els of detail. 0. When you are finished close the Material Wor!*ench to return to the na"igator.
Maintaining P0s
Su*mitted *y <nonymous on Sat &B?+-?+B&B ' +-%&; Tag%
9pdating P0s
>ou can update the attri*utes of a )$, including% &. +. -. .. Weight 7OM Aolume 7OM Aolume content Container item
7se the following instructions to update a )$,. &. )og onto the mo*ile de"ice. +. ,a"igate to Warehousing 'L )$, Transactions 'L )$, 7pdate. -. In the )$, field enter or select the )$, whose attri*utes you want to update. .. 7pdate each of the following optional fields as appropriate% D Weight% This is the weight of the )$,. It defaults to the current weight of the )$,. D Wt 7OM% This is the unit of measure for the weight. It defaults to the current weight unit of measure of the )$,. D Aolume% This is the total "olume of the )$,. It defaults to the current "olume of the )$, which is the ma6imum of the content "olume and the container item "olumeKif one is a"aila*le. D Aol 7OM% This is the unit of measure for the "olume. It defaults to the current "olume unit of measure of the )$,. D Container% This is the container item that is associated with this )$,. It defaults to the current container associated with the )$,. Thus you could not associate an )$, to a container item if there are none of that item in the location or if there are containers *ut they are all already associated to other container items. <fter a )$, has *een associated with a container item it cannot *e disassociated or changed. 0. <fter you update the attri*utes of this )$, select P7pdate )$,L to sa"e your changes to the )$,Is attri*utes.
Reusing #mpty P0s It is possi*le to reuse empty )$,s in a warehouse. <ll empty )$,s will *e updated to a state of 3efined 5ut ,ot 7sed. This allows the )$, to *e used from any mo*ile page as a new )$, for any transaction. )$,s that ha"e *een used for pic!ing *ut later split so that they are empty will *e updated using the Shipping <$I to unassign them from the original deli"ery they were pic!ed for. The <$I will *e used to unassign them from the deli"ery as well as reset all the information on the deli"ery detail record that pertains to the original Sales Order (Customer Ship'To Ship Method).
1nventory "ransactions with P0s

Su*mitted *y <nonymous on Wed &+?&0?+B&B ' &9%&+ Tag%
>ou can use Oracle Warehouse Management to pac! )$,s with any grouping of material into a locator. >ou can then enter the )$, to transact the material. The system transacts all contents of the )$, including the contents of any )$, nested within the )$,. >ou can associate )$,s with the following in"entory transactions%

Miscellaneous issues Su*in"entory transfers 3irect inter'organi/ation transfers Mo"e order transactions
>ou use a mo*ile de"ice to perform )$, in"entory transactions. When you ena*le Oracle Warehouse Management you can enter the )$, or the item information for each transaction. If you enter the )$, then the system transacts all the contents of the )$,. If you do not enter an )$, then you can enter the item 4uantity source locations and all necessary re"ision lot and serial information. ,ote% >ou must use the mo*ile user interfaces to transact material in )$,s. The des!top transaction windows do not include )$, fields. 2urthermore the a"aila*ility "alue in the forms reflect unpac!ed 4uantities. <ll in"entory transactions update the weight "olume and units stored in locators. The Oracle Warehouse Management #ules @ngine uses these "alues to determine locator for put away suggestions. The weight and "olume of a container item assigned to an )$, is also used to update the weight and "olume of the locator. The locator is updated *y the gross weight of the )$, which is the net (weight of contents) plus tare (weight of container). The "olume of the )$, is appro6imated *y the ma6imum of the "olume of the contents and the "olume of the )$, defined on the container item. >ou can use the mo*ile de"ice to perform miscellaneous issues for an )$,. The following figure pro"ides an e6ample of what occurs when you perform a miscellaneous )$, issue. In this e6ample assume that )$, )+9:C< contains fi"e items. When you perform a miscellaneous issue for the )$, the system allocates all of the items in the )$,. Thus this transaction includes issuing the fi"e items included in the )$,.
,ote% 5ecause only Oracle Warehouse Management ena*led organi/ations use )$,s organi/ation transfers can only *e performed using )$,s if the destination organi/ation is also Oracle Warehouse Management ena*led. If the destination is not Oracle Warehouse Management ena*led the )$, must *e unpac!ed and the indi"idual contents must *e transferred.
ocator Alias
Su*mitted *y <nonymous on Wed &+?&0?+B&B ' &:%+; Tag%
< locator alias is an alternati"e identifier that corresponds to a physical locator. It can *e a chec! digit a uni4ue identifier or a non'uni4ue identifier. 2or e6ample you can use the chec! digit &- as the locator alias for the locator B9'B9'B&. The system does not suggest a locator alias to you during a transaction it suggests the actual locator. )ocator aliases ensure the presence of a user at the physical location. >ou can use a *arcode to represent the locator alias. This ensures that when the alias is scanned a user must *e present at the physical location. ocator Alias Setup >ou ena*le locator aliases when you setup your organi/ation. >ou must also ena*le locator aliases for indi"idual su*in"entories. When you create you locators you also create locator aliases. If you ena*le locator aliases for a su*in"entory then you must enter a locator alias for all transactions in and out of the su*in"entory. If the su*in"entory is under dynamic locator control you cannot create a locator during a mo*ile transaction. The only way you can generate a locator for this type of su*in"entory is during a des!top transaction. ocator Alias 9ni$ueness There are three uni4ueness options for locator alias% no uni4ueness constraints uni4ue within a su*in"entory and uni4ue within an organi/ation. 2or e6ample if you set the @nforce )ocator <lias 7ni4ueness parameter at the organi/ation le"el and you create the locator alias &+ for locator C&.&.& in organi/ation W& then you cannot use that locator alias anywhere else in the organi/ationH howe"er you can use locator alias organi/ation W+. If you set the @nforce )ocator <lias 7ni4ueness $arameter at the organi/ation le"el then the su*in"entory le"el parameter is disa*led. >ou can also use the same locator aliases for more than one su*in"entory or within the same su*in"entory if you set no uni4ueness constraints. 2or e6ample you can use chec! digit &- as the locator alias for locators B9'B9'B& and B9'B9'B+ in su*in"entory 2(I. >ou define locator alias uni4ueness in the )ocators Maintenance window. >ou define the organi/ation'le"el uni4ueness in the Organi/ation $arameters window.>ou define the su*in"entory'le"el uni4ueness in the Su*in"entories window.
ocator Alias /ehavior 2or user and system directed pages the locator alias *eha"ior depends upon locator uni4ueness. 3uring a transaction the system prompts you to enter the locator alias when you na"igate to the locator field on that page. If the locator alias is uni4ue then the locator segments appear and you can na"igate to the ne6t field. If you enter an incorrect alias then the system displays an error message and prompts you to enter the correct alias. If the locator alias is not uni4ue then after you enter the locator alias you must also enter the locator segments that correspond to the locator alias.
ot "ransactions
Su*mitted *y <nonymous on Sun &B?+.?+B&B ' B&%09 Tag%
ot and Serial Attri,utes
)ot and serial attri*utes trac! the characteristics of items *ased on lot or serial num*ers.3escripti"e fle6fields ena*le you to configure lot and serial attri*ute fle6fields to capture additional information. >ou can define re4uired or optional attri*utes or trac! information at the item or item category le"el. Sample lot and serial attri*ute "alues include grade cycles since new and *est *uy date. To setup attri*utes and attri*ute "alue sets you associate them with a fle6field segment. The difference *etween lot and serial attri*utes and common fle6fields is once you define a set of attri*utes ( a conte6t) you can assign the set to an item or category. When an operator creates a lot or serial the system prompt the operator for the category attri*utes. 2or e6ample you can set up a "alue set for the (rade segment. The (rade "alue set includes three grades% @6cellent <"erage and $oor.
7sing )ot and Serial <ttri*utes >ou can *uild pic! and put away rules *ased on lot and serial attri*utes. Read the ,asics of +" = http%??www.oracleug.com?user'guide?oracle'in"entory?lot'control Oracle Warehouse Management ena*les you to split merge and translate lots. >ou can split a single lot into multiple lots and merge multiple lots into a single resulting lot. >ou can also translate a lot into a new lot. ,ote% >ou can use the In"entory open interface to split merge and translate items under *oth lot and serial control. ot Splitting )ot splitting ena*les you to split a parent lot into multiple child lots. This is useful when a portion of the lot does not ha"e the same lot attri*utes or material status as the rest of the lot. <fter you split the lot you can change the attri*utes or status of the resulting lots. >ou can also split a lot when a portion of the lot characteristics differs from the rest of the lot. 2or e6ample if you store a lot in multiple locations and damage occurs to one of the lots then you can split the lot and assign new characteristics to the new lot that contains the damaged 4uantity. ot Merging )ot merging ena*les you to merge multiple lots into a single lot instance. 2or e6ample you can merge lots if you store them in a single "at or silo. ot "ranslate )ot Translate ena*les you to either change the name of an in"entory lot to another name or to con"ert one product to another product. 2or e6ample you can change the lot name item re"ision or su*in"entory of an e6isting lot and mo"e it to another assem*ly. Restricting ot "ransactions >ou should not perform lot transactions on some items. When you split a lot the resulting lot inherits the attri*utes from the parent lotH howe"er you can update the lot attri*utes *efore you sa"e the new lot. When you merge a lot the resulting lot inherits the attri*utes of the largest merged lot. If you merge lots with identical 4uantities then the system uses the attri*utes of the first lot that you enter on the transactions page. When you translate a lot into the same item the resulting lot inherits the attri*utes of the starting lotH howe"er you can update the lot attri*utes *efore you sa"e the new lot. When you translate a lot into a new item and the lot attri*ute conte6t of the resulting item is the same as the lot attri*ute conte6t of the starting item then the system deri"es the lot attri*utes from the starting lot. If the conte6ts of the lot attri*utes differ then the system uses the default attri*ute "alues. ,ote% < reser"ed lot cannot *e merged or split. Oracle Warehouse Management has the following le"els at which you can restrict lot splitting merging and translating% D Item le"el control D )ot le"el control 1tem& evel ot Restrictions >ou must ena*le the lot attri*utes )ot Split @na*led )ot Translate @na*led and )ot Merge @na*led on the Item Master in In"entory to perform lot transactions on a lot controlled item.
ot& evel Restrictions )ot split lot merge and lot translate are transaction types. >ou can disallow lot transactions for material statuses that you create. 2or e6ample if you assign a material status that disallows lot split to the lot locator or su*in"entory in which the lot resides then the system cannot split the lot. Similarly if the lot locator or su*in"entory in which the lot resides has a material status that disallows lot merge or lot translate then the system cannot merge or translate the lot. *ull Versus Partial ot Split < full lot split consists of splitting the entire 4uantity of a starting lot into resulting lots. < partial split consists of splitting only a portion of the starting lot into resulting lots and lea"es remaining 4uantity in the starting lot. Child ot Splitting and Merging < child is a lot that has a su*ordinate relationship to another lot !nown as the parent lot. When the system splits or merges a lot it stores the parent'child relationship *etween the two lots. The parent'child su*lot architecture supports an unlimited num*er of parent'child le"elsH therefore you can split a lot numerous times. When you split a lot with a parent'child relationship you can enter the parent lot as a new "alue the parent lot of the parent lot or the child lot. P0 ot Support Oracle Warehouse Management supports splitting merging and translating for *oth loose and pac!ed material. It can split lots within an )$, or it can pac! the split lots into new )$,s. >ou can also perform a su*in"entory transfer when you perform a lot split merge or translate. Manual and Automatic ot Splits When the system splits a lot into a small num*er of resulting lots you can manually specify the resulting lot num*ers and lot 4uantities. When a lot is split into a large num*er of resulting lots you can specify the num*er of resulting lots or the appropriate 4uantity of the resulting lot that you want the system to automatically create. 2or e6ample you might specify that a *atch of &BB pallets *e split into &BB su*lots of & pallet per su*lot. In this case the system automatically creates a new lot and the resultant lot 4uantity and then uses the parent lot attri*utes as the default attri*utes for the resulting lot. ot&Specific Conversions >ou can create lot'specific con"ersions if you set the parameter <uto Create )ot 7OM Con"ersion to >es on the Organi/ation $arameters window. See 3efining #e"ision )ot Serial )$, $arameters Oracle In"entory 7serIs (uide for more information. This parameter determines whether the system creates lot' specific con"ersion *ased on the resulting lot 4uantities. The con"ersion is not inherited from the source lot. The system creates con"ersions only if the item is under dual 7OM control and the 7OMs are in different classes. If you set the parameter to user confirmation then the system prompts you to create the lot con"ersion. If you select PSa"e Con"L you can sa"e the newly created con"ersion. ,ote% >ou cannot automatically create lot 7OM con"ersions for lots that are created in Oracle Wor! in $rocess. Merging 1ndivisi,le ots >ou can merge part of an indi"isi*le lot. This is essentially a miscellaneous issue from one lot and a
miscellaneous receipt into another lot. <n e6ception occurs if a reser"ation e6ists against the resulting lot. >ou cannot merge into a lot that has an e6isting reser"ation
ask Management
Su*mitted *y <nonymous on Sun &B?+.?+B&B ' +&%-: Tag%
Tas! planning is the release of wor! to the warehouse floor in order to optimally run the day'to'day warehousing operations. Once multiple tas!s are created from the "arious tas! creation sources they are placed in one single pool and released appropriately to the warehouse floor for optimal operation of the warehouse. Optimi/ation is performed *y tas! interlea"ing and resource'wor!load *alancing. Tas!s are comprised of &. +. -. .. 0. 3emand pic! tas!s for sales orders wor! orders and replenishment. In*ound recei"ing and put away tas!s In*ound'out*ound hy*rid cross'doc!ing tas!s. In"entory transfer tas!s In"entory control related cycle counting tas!s
Warehouse Management creates and dispatches tas!s *ased on a configura*le set of rules you define and maintain. >ou create tas! type assignment rules in the same way you create other rules. Tas! management optimi/es the se4uencing of tas!s *ased on tas! priority locator pic! se4uence appro6imate distance *etween the locator 6'y coordinates and the current location of the warehouse operator currently signed on to the e4uipment. 7sing tas! management decreases the num*er of operator trips and distance tra"eled and increases operator efficiency and producti"ity. >ou need to *e a*le to plan the release of tas!s in the warehouse on a day'to'day *asis so that you can run operations optimally to minimi/e cost and ma6imi/e producti"ity. To do this you need a single wor!*ench that ena*les you to "iew the entire wor!load for one or more days. 7sing the Warehouse Control 5oard you can 4uery tas!s *ased on multiple criteria re'prioriti/e and interlea"e them and release them to the
warehouse floor in the form of tas! wa"es. "ask "ypes @ach tas! the system generates re4uires a System Tas! Type. Warehouse Management contains pre'defined system tas! types grouped *y similar sets of features. When Warehouse Management creates a tas! it assigns the System Tas! Type. >ou cannot edit a system tas! type for an e6isting tas!. The rules engine can use 7ser Tas! Types to further classify System Tas! Types. The System Tas! Types are%
&. +. -. .. 0. 9.
$ic! $ut away Mo"e order issue Mo"e order transfer #eplenishment Cycle count
>ou use the 5OM Standard Operations window to define 7ser Tas! Types. >ou must create a 7ser Tas! Type for each tas! that re4uires a uni4ue com*ination of human and e4uipment type resources. >ou must set up at least one pic! one mo"e order issue and one replenishment tas! type. >ou can also define one cycle count tas! type if you want to dispatch cycle counts as tas!s. 3o not define more than one cycle count tas! type for the organi/ation. "ask "ype Rules The Oracle Warehouse Management #ules @ngine ena*les the system to assign tas! types to tas!s. )i!e the pic!ing and put away rules tas! type assignment rules can *e *ased on a "ariety of data including the following% D 7nit of measure (7OM) defined for the pic! line% for e6ample if the pallets need to *e pic!ed the Tas! Type <ssignment engine can dispatch tas!s to the pallet pic!ers. D Ownership of the material% for e6ample if the item *elongs to Q>8 company and Q>8 re4uires that their ha/ardous material *e handled *y a resource that has ha/ardous material handling s!ills then the Tas! Type <ssignment engine will dispatch tas!s associated with Q>8Is ha/ardous material handling re4uirements. D Type of material *eing handled% for e6ample the Tas! Type <ssignment engine might handle refrigerated material different than ha/ardous material Tas! type assignment rules are prioriti/ed *ased on their
respecti"e weights that you specify. 2or e6ample you might assign different weights for two rules to handle a specific tas!s. In this case the Tas! Type <ssignment engine will e6ecute the rule with the higher weight first. "ask 8ispatch #ngine
Whene"er a new tas! is re4uested *y the operator the tas! dispatch engine handles the actual e6ecution of a tas!. The tas! dispatch engine dispatches an appropriate tas!s to a 4ualified operator. The tas! dispatch engine also handles e6ception management and automatically triggers correcti"e actions whene"er a discrepancy is recorded. The tas! dispatch engine also performs the following functions% D Identifies resource and e4uipment re4uirements for a particular tas! D @"aluates s!ill sets D 2ilters appropriate tas!s to resources The Tas! 3ispatch engine also includes a set of predefined e6ception messages and transaction reasons that handle all of the generic e6ceptions during tas! dispatching and will trigger a set of actions and wor!flows *ased on these e6ceptions.
Set up +peration Plans

Su*mitted *y <nonymous on Wed &+?&0?+B&B ' +B%&9 Tag%
Operation plans define the material mo"ement path and the se4uence of operations to perform to complete an acti"ity. >ou can use *oth in*ound and out*ound operation plans. >ou can create in*ound Operation plans using the following in*ound operation plan types%
Standard% Standard operation plans apply to any mo"e order lines that does not re4uire inspection or was not crossdoc!ed. < standard operation plan can end in a recei"ing or in"entory locator. It can also tra"erse multiple recei"ing and in"entory locators. >ou cannot follow a drop to an in"entory locator *y a drop to a recei"ing locator *ecause once you drop material to an in"entory locator it is deli"ered to in"entory. 1nspect% Inspect operations plans apply to mo"e order lines that ha"e the Inspect #e4uired flag set. The inspect step is the last step in the operation plan. Inspect operation plans do not allow drops to in"entory locators. Crossdock% Crossdoc! operation plans apply to crossdoc!ed mo"e order lines. The crossdoc! step is the last step in the operation plan. The crossdoc! step implies a load and a drop to a staging locator. The drop operation *efore a crossdoc! operation does not happen in in"entory.
5efore you can put your operation plans into effect you must complete the following setups% &. Set up 8ones% If you choose to segregate your material *y /ones you must create /ones. +. Set up Operation $lan <ssignment #ules% >ou must set up operation rules in the #ules window to tie your operation plans to your system rules.
"o set up +peration Plans> ,a"igate to the Operations $lans window &.& Select a $lan Type from the list of "alues. >ou choices are Standard Inspection or Crossdoc!ing. &.+ @nter a name for the operation plan in the ,ame field. Optionally enter a description for the operation plan in the 3escription field. &.- Select the Crossdoc! to WI$ chec! *o6 to use this operation plan to crossdoc! items to WI$ instead of for out*ound shipment. +.& @nter the first se4uence num*er in the Se4uence field. The operations performed within an operation plan follow the ascending se4uence in which you define the operations. +.+ Select )oad from the Operation list of "alues. The first operation in all operation plans must *e )oad. The ne6t se4uence num*er defaults in the se4uence field and 3rop automatically populates in the Operations field. -.& Optionally select the in In"entory chec! *o6. >ou can select this chec! *o6 only if your operation plan type is Standard. Selecting this chec! *o6 transfers the material to in"entory at this step in the operation plan. <ll su*se4uent steps ha"e this chec! *o6 chec!ed *y default. :67 ocator determination method: This is a mandatory field and you can set it for 3rop operations only. Select the determination method. >ou are re4uired to enter a locator determination method and optionally can enter a /one su*in"entory or Into )$, method. The determination methods are as follows% D $respecified% If you choose prespecified you can enter the su*in"entory locator and /one where you would li!e to drop the material. This is the only determination method for su*in"entories and /ones. D Standard <$I' Standard <$I' If you choose Standard <$I as the locator determination method you in"o!e an <$I that determines the locator. If you choose Standard <$I for locator you must enter a pre'specified su*in"entory or /one. >ou can also choose Standard <$I as the )$, determination method. D Custom <$I' If you choose Custom <$I as the locator or )$, determination method you pro"ide the $)?SG) <$I. The <$I needs to conform to the signature as the seeded standard <$I and registered "ia #egister custom <$I concurrent program. -.- If you selected Standard <$I as the locator determination method select a )ocator Material (rouping method from the list of "alues. The a"aila*le choices are as follows% D Operation $lan Type% If you select Operation $lan type the system deri"es the locator grouping method from the operation plan type such as inspection Standard or Crossdoc!ing. D 3estination Su*in"entory% This is the final in"entory destination su*in"entory the putaways rule suggests. D 3estination )ocator% This is the final in"entory destination locator the putaway rule suggests. -.. If you selected Standard <$I or Custom <$I as the locator determination method enter a $) ? SG) procedure. The a"aila*le choices for Standard <$I are as follows% D )ocator 3etermination with Item D )ocator 3etermination without Item -.0 If you selected an )$, 3etermination method select an )$, Material grouping method from the list of "alues. The a"aila*le choices are% D Operation $lan Type% If you select Operation $lan type then the system deri"es the locator grouping method from the operation plan such as inspection Standard or Crossdoc!ing.
D 3estination Su*in"entory% This is the final in"entory destination su*in"entory the putaway rule suggests. D 3estination )ocator% This is the final in"entory destination locator the putaway rule suggests. -.9 If you selected an )$, 3etermination method enter a $) ? SG) procedure in the Into )$, fields. The a"aila*le choices for Standard <$I are as follows% D )ocator 3etermination with Item D )ocator 3etermination without Item ..& Select the 8one ? Su*in"entory ? )ocator Ta*. ..+ Optionally if your plan type is Inspect or Crossdoc!ing enter the Inspect or Crossdoc!ing se4uence. In an Inspect or Crossdoc!ing plan this is the last operation. ..- If you entered crossdoc! in the pre"ious step select a Crossdoc! Method to lin! the crossdoc! operation plan to an out*ound operation plan. The choices are% D )$, *ased consolidation in staging lane within deli"eries D )ocator *ased consolidation in consolidation locator within deli"eries D )$, *ased consolidation locator within deli"eries D 3irect consolidation in staging lane within deli"ery D )$, *ased consolidation in staging lane across deli"eries D 3irect consolidation in staging lane across deli"eries D )$, *ased consolidation in consolidation locator across deli"eries D )ocator *ased consolidation in consolidation locator across deli"eries ... Select @na*led to ena*le the operation plan.
+ut,ound operation plans
@ight seeded out*ound operation plans are a"aila*le they are% &. +. -. .. 0. 9. :. ;. 3irect consolidation in staging lane across deli"eries 3irect consolidation in staging lane within deli"ery )$, *ased consolidation in staging lane within deli"ery )$, *ased consolidation in staging lane across deli"eries )$, *ased consolidation in consolidation locator across deli"eries in staging lane )$, *ased consolidation in consolidation locator within deli"ery in staging lane )ocator *ased consolidation in consolidation locator across deli"eries in staging lane )ocator *ased consolidation in consolidation locator within deli"ery in staging lane.
Setup "ask *ilters

Su*mitted *y <nonymous on Tue &+?+;?+B&B ' &:%09
Tag%
The tas! filter window ena*les you to determine which tas!s the pic!ing page can perform. If you include a tas! type then the pic!ing page can perform the tas! type. >ou can use tas! filters to control the types of tas!s the system dispatches to operators. 2or e6ample you can create tas! filters so an operator recei"es internal order pic! tas!s *ut not replenishment tas!s.
&.,a"igate to the Tas! 2ilters window. +.@nter the filter name in the ,ame field. -.@nter a *rief description of the filter in the 7ser ,ame field. ..@nter a long description in the 3escription field. 0.In the Tas! Source alternati"e region select the Include chec! *o6 to include the associated tas! source. That tas! sources are as follows% D Internal Orders D Mo"e Order Issues D Mo"e Order Transfers D #eplenishments D Sales Orders
D Wor! Orders D Cycle Counting 9.Sa"e your wor!.
ask 8ispatch and Assignment

Su*mitted *y <nonymous on Tue &+?+;?+B&B ' +B%BC Tag%
The a*o"e figure shows the pic!ing tas! processes. 2irst the system e"aluates the pic!ing rules to come up with a material allocation.
,e6t the system e"aluates the tas! type assignment rules in the se4uence indicated *y the rule weight and then assigns the tas! type of the first rule where the restrictions are met. In this e6ample the rules ha"e *een set up *ased solely on the su*in"entory of the tas! resulting in the tas! type assignments indicated a*o"e. ,ow the tas! will *e split *ased on e4uipment capacity. 2inally after performing the material allocation tas! type assignment and tas! splitting the Tas! 3ispatch engine dispatches the tas!s to each operatorIs mo*ile de"ice *ased on their e4uipment and tas! type assignment. When the operator completes the tas! and re4uests the ne6t tas! the system dispatches the ne6t closest tas! that the operator is 4ualified to perform with the e4uipment that is currently a"aila*le. ,ote% The pre"ious e6ample pro"ides a detailed "iew of pic!ing tas!s. Eowe"er the Oracle Warehouse Management performs replenishment tas!s using an identical process. "ask Management Setup Setting up tas! type assignment and dispatch includes setting up the following% #esources @4uipment items @4uipment resources 3epartments Setting up tas! type assignment rules "ask "ype assignment Rules The Oracle Warehouse Management #ules @ngine ena*les the system to assign tas! types to tas!s. )i!e the pic!ing and put away rules tas! type assignment rules can *e *ased on a "ariety of data including the following% 9nit of measure 39+M4 defined for the pick line: for e6ample if the pallets need to *e pic!ed the Tas! Type <ssignment engine can dispatch tas!s to the pallet pic!ers +wnership of the material: for e6ample if the item *elongs to Q>8 company and Q>8 re4uires that their ha/ardous material *e handled *y a resource that has ha/ardous material handling s!ills then the Tas! Type <ssignment engine will dispatch tas!s associated with Q>8Is ha/ardous material handling re4uirements "ask "ype Assignment and 8ispatch <ssume that your warehouse has the following human resources each assigned to the roles and e4uipment shown in the following ta*le.
@ach tas! type re4uires the appropriate set of s!ills and e4uipment. 2or e6ample case pic!ing tas!s re4uire a cart and an operator that can pic! up the re4uired cases. <lternati"ely cold pic! tas!s re4uire a for!lift and a pic!er who can operate the for!lift. 5ased on the information pro"ided a*o"e tas! type assignment rules would need to *e set up that assign the appropriate tas! type whene"er the tas! has certain attri*utes. 2or e6ample pic!s of refrigerated items should *e assigned the C3$J tas! type while case pic!s should *e assigned the CS$J tas! type.
Warehouse Control /oard

Su*mitted *y <nonymous on Wed &+?+C?+B&B ' +B%+0 Tag%
Ora cle Warehouse Management creates tas!s such as pic!s put away mo"es and replenishments and dispatches pending tas!s on demand to mo*ile radio fre4uency de"ices. The Warehouse Control 5oard is a tool that Oracle Warehouse Management and super"isors use to monitor plan control and e6ecute "arious warehouse operations including the following% D @ffecti"ely use resources D Guery tas!s D $lan tas!s D #elease tas!s to the warehouse floor D <ssign reassign and prioriti/e the progress of tas!s D $erform manual scheduling D Cancel crossdoc! tas!s The Warehouse Control 5oard ena*les you to "iew wor!loads across the entire warehouse manage e6ceptions and re"iew release reassign and re'prioriti/e tas!s. Specifically the Control 5oard ena*les you to do the following% D Aiew tas!s% including unreleased pending 4ueued dispatched acti"e loaded completed and e6ception tas!s ,ote% <t the time of pic! release (Sales Order or WI$) you can specify whether or not to plan the release of tas!s. If planning is opted pic! tas!s are created with a status of 7nreleased so that you cannot perform or e6ecute them immediately. If you do not want to plan the tas!s pic! tas!s are created with a status of $ending.
D Manage tas! assignments% including mass selection?refinement through add remo"e and filtering features the mass change?update of tas! status priority resource assignments and sorting on "arious fields for the resultant tas! record set "iew D Aiew tas! e6ceptions% including a description of the cause for failure >ou can also "iew the status of each tas! including the time in which it was dispatched the time it was pic!ed up and the time it was dropped into a staging lane. If any errors occurred in processing the tas! you ha"e full "iew of the error reported and the tas! in 4uestionIs current status. "ask Status The tas! status is the current tas! state. Tas! statuses are as follows% 9nreleased: The tas! was created *ut is not eligi*le for dispatch. Managers use this status to control when the tas! is released. Managers can update tas!s in this status to $ending (eligi*le for dispatching) or Gueued. Pending: The tas! was created and can *e sent to any a"aila*le operator. $ending tas!s are dispatched to operators in se4uence of priority su*in"entory pic!ing order and locator pic!ing order in relation to the operators last !nown position. Warehouse Management filters tas!s *y tas! type current operator e4uipment and su*in"entory. It dispatches a tas! in $ending status only when there are no more Gueued and 3ispatched tas!s assigned to the operator. )ueued: Managers use this tas! type to manually assign a tas! to a particular operator in the warehouse control *oard. 8ispatched: The tas! is dispatched to an operator *ut the operator has not started the tas!. ,ote% 3ispatched *eha"es li!e 4ueued e6cept the system assigns the operator to the tas! *ased on pic! methodology instead of *y a manager in the control *oard. Active: The tas! the operator is performing. The system dispatched the tas! to the mo*ile de"ice *ut the user has not loaded or dropped the tas!. The status of the tas! changes as soon as either the tas! is loaded or dropped. The operator assigned to the tas! also displays in the WMS Control 5oard. oaded: The tas! is loadedH howe"er no material transaction has posted. To complete the tas! the operator must drop the tas!. Completed: The tas! has *een completely transacted.
Performing "ask
Su*mitted *y <nonymous on Wed &+?+C?+B&B ' &C%B& Tag%
#(plaining "ask 9nloading < tas! that has *een loaded can *e unloaded at any point prior to the tas! drop. 7nloading a tas! ena*les you to re"erse the tas! load returning the material or full )$, to the same locator from which it was pic!ed. If the material re4uirement that has created that tas! has *een cancelled then the tas! will *e cancelled when it is unloaded. This is particularly for change management of sales orders and wor! orders. >ou can use the Manual 7nload page to unload tas!s loaded using ad"anced pic! load. To unload a tas!% &. ,a"igate to the Manual 7nload page. +. @nter the tas! to unload in the Current Tas! field. -. Choose P7nloadL to unload the tas! or PCancelL to cancel the tas! unload. .. If you choose P7nloadLthe 7nload page appears. The unload page displays the 2rom )$, 2rom Su*in"entory 2rom )ocator Item 7OM and Gty or displays the Su*in"entory and )ocator information if you are unloading the entire )$,. 0. Choose P7nloadL to unload the tas! or choose PCancelL to cancel the unload. #(plaining "ask Skipping <n operator may *e una*le to perform a tas! that has *een dispatched to them due to conditions outside their control and do not warrant another type of tas! e6ception. 2or e6ample the aisle to which he or she was directed may *e temporarily *loc!ed. The operator may s!ip the tas! it is returned to the pool of pending tas!s and dispatched again.
"ask #(ceptions If at any point during the pic! process the user reports a discrepancy warehouse manage can initiate a correcti"e action wor!flow. 3iscrepancies might include any of the following%

$ic!ing a different 4uantity than the 4uantity suggested *y the system 3ropping material into a different staging lane than the staging lane suggested *y the system. If a discrepancy is reported the system immediately directs the user to an audit screen where he or she is prompted to indicate a reason for the mismatch.
@ach reason has an associated correcti"e action wor!flow which will *e initiated immediately after an e6ception occurs. 2or e6ample a correcti"e action wor!flow might notify the warehouse super"isor through pager mail or other alert mechanism that an e6ception has occurred. Correcti"e actions can also notify customer ser"ice that a potential *ac!ordered situation e6ists on a sales order. Correcti"e actions can also place a location on hold so that su*se4uent material allocations do not source material from that locator. These actions can also re4uest a cycle count for a particular locator or re'release the *alance of the sales order line so that it can *e sourced from another location. When you enter an e6ception during the pic!ing process you can enter a reason for the e6ception. >ou setup the e6ception reasons in Oracle in"entory.
1n,ound ogistics
Su*mitted *y <nonymous on Mon B-?B+?+BBC ' &.%-. Tag%
Oracle WMS in*ound logistics refers to recei"ing inspection and put away processes within the warehouse. The ma=or in*ound features of Oracle WMS include the following%
Support for handling <d"anced Shipment ,otices (<S,s). The WMS system supports suppliers sending <S,s that might include item 4uantity lot and serial information pro=ect num*er and tas! (with Oracle $ro=ect Manufacturing ) as well as the )$,s into which the material is pac!ed. >ou can recei"e <S,s through a standard <S, receipt where )$, contents are "erified *y the recei"er or through an @6press <S, receipt where the )$, contents do not need to *e "erified.
2unctionality to recei"e material directly into uni4ue license plate num*ers ()$,s). <ll material recei"ed through Oracle WMS is associated with a uni4ue )$,. This ena*les material to *e easily trac!ed and transacted throughout the warehouse without scanning the item 4uantities lots or serials.
2eatures that ena*le you to specify and capture lot and serial information at receipt.
With standard Oracle $urchasing at the time of receipt you are not allowed to enter lot and serial num*ers. With Oracle WMS howe"er you can enter lot and serial num*ers immediately at the time of receipt. >ou can also enter related material statues or attri*utes that might apply to the lot or to the serial =ust recei"ed.
2unctionality to automate the matching of material recei"ed to e6pected material. <utomatically Matching Material #ecei"ed to @6pected Material Oracle WMS matches the item and 4uantity recei"ed to the document that the material was recei"ed against. This means that the recei"er does not need to manually select lines or shipments indi"idually. Eowe"er Oracle WMS does not show the e6pected 4uantity to *e recei"ed rather the system re4uires the recei"er to enter the actual 4uantity recei"ed and then through a *ac!ground process the system matches the actual 4uantity against the e6pected 4uantity. Instead of ha"ing to spend time re"iewing the related purchasing documentation a the time of receipt automatically matching the recei"ed material also ena*les operators to efficiently process in*ound material.
Support for Oracle Guality. System suggested put away locations. Opportunistic Cross 3oc!ing for *ac!ordered sales order lines. Support for , step material mo"ement path.
Complete 1n ,ound Process 56 Receiving prior to &&.0.&B Material is always recei"ed to an )$,. In &&.0.&B the concept of recei"ing su* in"entory and locator is introduced. ,ow you can recei"e the material in an )$, and can physically locate the recei"ing su* in"entory and locator where it resides . ,ote% #un #ecei"ing Transaction $rocessor if transaction mode is not online. If pre generate is ena*led then systemRll create a tas! after the recei"ing else tas! are created after loading the material. 76 1nspect the material If the receipt routing is inspection then inspect the material *y na"igating into In*ound 'L Inspect. #emem*er you inspect the )$, that is already *eing recei"ed into the recei"ing location. :6 Put away 3 oad % 8rop4 <fter inspection )$,s resides in recei"ing doc!. 7ser who wants to mo"e the material to in"entory scans the )$, to load it. To )oad the material na"igate to Tas! 'L Manual Tas!'L Manual )oad System creates a tas! as per the tas! type assignment. <n operation plan is assigned to the tas! as per the operation plan assignment rule. <fter loading the material the status of the tas! remains as loaded. 8rop To drop the material na"igate to Tas! 'L 3irected Tas! 'L 3irected Mo"e 'L Mo"e any )$,. @nter the )$, num*er and press 3rop. <s per the operation plan system would suggest To Su* in"entory (SI&) and To )ocator ()&). Once drop is
completed and #T$ is run systemRll change the status of the tas! to completed. In #ecei"ing transaction summary you can "erify that the receipt?deli"ery status of the material . If the a*o"e tas! is generated for an operation se4. with one drop ?or the last drop of an operation plan then the a*o"e process completes the in*ound process else system would generate another tas! (planned tas! K pending 1 plan in progress) as per the operation plan to mo"e the material from )&'SI& to another location. Once you load the new tas! systemRll change the status of the planned tas! to loaded (plan tas! wont *e there any more) and finally you need to drop that )$, into the final destination location.
WMS 1n,ound *eatures

Su*mitted *y <nonymous on Mon B-?B+?+BBC ' &C%B. Tag%
The WMS system also supports the following% +ptional in,ound material inspections: The system supports an in*ound inspection flow that includes a receipt step an inspection step and a put'away step. The system does not increment on'hand *alances until the inspection and put away are complete. Inspections can *e performed using standard Oracle $urchasing Inspection or using the optional module of Oracle Guality. Commingling of accepted and re=ected material into the same )$, is not pre"ented *y the system. It should *e done operationally. If WMS is ena*led in a $ro=ect Manufacturing organi/ation Oracle Guality can *e set up to trigger collection plans *ased on pro=ect and tas! num*ers. System assigned cost groups: <t the time of receipt the system will assign a cost groupKpro"iding that you ha"e set them upKto the in*ound material. WMS separates physical in"entory accounting from standard cost group accounting. This ena*les you to assign split portions of an )$, different cost groups. System suggested put&away locations: 7sing the WMS #ules @ngine the system will suggest an optimal put away location for in*ound material. $ut away suggestions are not enforced *y the system and therefore you can o"erride them at the time of put away. Workflow ena,led discrepancy actions: If you o"erride a put away suggestion at the time of put away then you must pro"ide a reason for the change. >ou can optionally *uild wor!flow notifications and correcti"e actions that are triggered on put away o"erride reasons. System suggested opportunistic cross&docking: If you ena*le cross doc!ing for your warehouse then *efore suggesting a put away location the WMS will attempt to cross'doc! in*ound material directly to an out*ound staging area to fulfill *ac!ordered sales order lines. Monitor and track in,ound material using receiving locators: The in*ound area can *e defined as a recei"ing su*in"entory and segmented into locators. The in*ound material can *e recei"ed in recei"ing locators in order to monitor and trac! mo"ement within the in*ound area.
8escri,ing Receiving 8ocuments The WMS supports the following recei"ing documents%

$urchase orders with or without <S,s #eturn material authori/ations (#M<s) Inter'org intransit shipment documents Internal re4uisitions 5lan!et purchase orders
Oracle WMS supports two modes of recei"ing% @6press and Confirm. To enter receipts using @6press mode you need only enter the document num*er and optionally the )$,. 2or Confirm mode you need to enter all of the information a*out the material *eing recei"ed. 8escri,ing Receiving Methods Oracle WMS supports recei"ing material according to the same three routings that are used in standard Oracle $urchasing% Standard #outing Inspection #e4uired and 3irect 3eli"ery. 3irect 3eli"ery includes the following steps% S Material receipt S Material put away (optional in this routing *ecause on'hand in"entory has already *een incremented)
This routing should *e used when it is important that material show up in the on'hand *alance immediately after it is recei"ed into the warehouse or whene"er the recei"er will *e recei"ing the material directly into its in"entory storage location. With WMS you can recei"e material directly into an on'hand storage location. That material can optionally *e put away from that storage location into a final storage location. 3irect deli"ery can *e effecti"ely used to model a recei"ing staging lane where material is initially recei"ed into the warehouse and it is important that on'hand *alances are incremented at the time of receipt. )ater the material can *e put away from the temporary staging lane to a final storage location.
Standard routing includes the following steps% S #ecei"ing the material S )ater putting the material away
>ou should use this routing when the material needs to *e recei"ed (chec!ed'in) initially and then at some later point put away into an in"entory storage location. >ou can assign recei"ing locators to items with a purchase order. #ecei"ing locators ha"e infinite capacity. >ou can enter a capacity *ut it has no influence on putaway rules. With Standard #outing the system does not increment the on'hand *alance until the put away tas! has *een completed. Inspection #e4uired includes the following steps% S Material receipt S Material inspection S Material put away
>ou should use Inspection #e4uired when the material that you are recei"ing re4uires inspection. >ou can accept or re=ect material during the inspection and put away to separate locations *ased on the inspection result. The system does not increment the on'hand *alance until the put away step tas! *een completed. >ou can assign recei"ing locators to inspected items that ha"e a purchase order. #ecei"ing locators ha"e infinite capacity. >ou can enter a capacity *ut it has no influence on putaway rules.
1n,ound Setup
Su*mitted *y <nonymous on Mon B-?B+?+BBC ' &9%&0 Tag%
&. #ecei"ing area layout &.& Segregate in"entory and recei"ing in warehouse http%??www.oracleug.com?user'guide?oracle'in"entory?recei"ing'su*'in"entory &.+ Su*di"ide recei"ing area into functional /one http%??www.oracleug.com?user'guide?warehouse'management?locator'/ones &.- Su*di"ide /ones into locators and assign locator types http%??www.oracleug.com?user'guide?oracle'in"entory?0'define'locators +. In*ound material flow +.& #oute the material in the physical warehouse lay out http%??www.oracleug.com?user'guide?warehouse'management?set'operation'plans +.+ 3efine the rules 1 strategies Organi/ation $arameter
Put Away Rules $ut away rules ena*le the system to direct operators to put newly recei"ed material into the most appropriate location. The follow is a list of possi*le uses for put away rules%

3irect operators to put an item away in the same locator where the item is already stored $rohi*it commingling of different items or different lots of the same item in a single locator <"oid lot commingling in a locator 5ase the put away location on inspection results the type of purchase order or item category 3irect operators to put away items *ased on refrigeration restrictions.
2or e6ample if your implementation has items that re4uire a storage temperature of -+ degrees or *elow you can create a put away rule to put away those items into a refrigerated su*in"entory and locator. <n operator can o"erride put away rule suggestions. 2or e6ample if the system suggests a put away location the operator can instead put the material into any locator and o"erride the suggestion. If the operator chooses to o"erride a suggestion then they must also enter a reason code for the o"erride. If necessary you can setup an Oracle Wor!flow to send a notification of the o"erride to the appropriate personnel or to trigger an appropriate action such as a cycle count. >ou first define the put away rule. ,e6t you *uild a put away strategy and include your rule in that strategy. <fter you set up the strategy you associate the strategy to an o*=ect in the #ules Wor!*ench.
8efine Rules
&. In the Guantity 2unction field use the list of "alues to select the e4uation that you want the system to use to determine the capacity of the potential locators for this put away rule. +. In the O*=ect field use the list of "alues to select the first *usiness o*=ect for the rule. -. In the parameter field enter the "alue associated with the *usiness o*=ect. .. In the Operator field select the mathematical operator that supports the rule conditions for e6ample e4uals or greater than. 0. If you want the system to sort the locators that will *e returned *y the rule enter the sort criteria on the Sort Criteria ta* *y selecting the o*=ect parameter and ascending?descending specification. <fter you finish defining all of your rule restrictions and ha"e specified the appropriate sort criteria return to the #estrictions ta* and select the @na*led chec! *o6 if you want to ena*le the rule. Select the Common to <ll Orgs chec! *o6 if you want the rule to *e a"aila*le for all organi/ations. WMS Strategies < strategy is a list of rules to apply in se4uence until the put away is complete.
Assign strategy to item
Receiving Parameters
#ecei"ing parameters represent the options that you want to go"ern how your organi/ation handles receipts in your system. >ou set up recei"ing options in the #ecei"ing Options window.
#ecei"ing options are set up at the Organi/ation'le"el. Eowe"er most of the options that you set in the #ecei"ing Options window can *e o"erridden for specific suppliers items and purchase orders fore details chec!
Receiving +ptions 3Mo,ile % 8esktop4

Su*mitted *y <nonymous on Wed B&?B0?+B&& ' ++%09 Tag%
Mo,ile Receiving +ptions Receiving Su,stitutes Operators can use the mo*ile de"ice to recei"e su*stitutes if <llow Su*stitutes is ena*led on the shipment line and su*stitutes are defined for the item. Receive #(pense 1tems Operators can use the mo*ile de"ice to recei"e e6pense items *ut the e6pense items cannot *e traced in the warehouse after receipt. Receive Vendor 1tem Operators can use the mo*ile de"ice to recei"e "endor items *y the "endor item num*er. Eowe"er "endor items are traced through the original item num*er in the warehouse. Receive ,y ."10 0um,er Operators can use the mo*ile de"ice to recei"e num*ers *y (TI, num*er instead of the internal item num*er. #na,le Shortage 0otification Messages The system can generate shortage notifications after receipt when material shortage is ena*led for items and a *ac!ordered sales order or WI$ =o* e6ists. 9navaila,le Mo,ile Receiving +ptions Warehouse Management does not support the following recei"ing options% /lind receipts& Warehouse management does not support *lind receipts. Receipts without a document or item& Operators cannot use the mo*ile de"ice to recei"ing material if they do not ha"e the document information or the item information.
9nordered receipts& Operators cannot use the mo*ile de"ice to recei"e unordered material in to the warehouse. Receipt Corrections' Operators cannot use the mo*ile de"ice to ma!e receipt corrections. P0 Receipts
Receiving P0s 9sing a Mo,ile 8evice 7sing the mo*ile de"ice for receipts helps operators to trac! material in the warehouse. Operators can reuse defined *ut not in use )$,s and nest an )$, for a normal receipt. The system re4uires )$,s for receipts e6cept in the following cases%

@6pense items 3irect receipts
8esktop Receiving Operators cannot use the des!top application to recei"e )$,s. The system recei"es the material as loose and does not retain the nesting information for <S,s internal re4uisitions inter'organi/ation transfers and in'transit receipts ot and Serial Receiving Operators can use a configura*le hot !ey on the mo*ile de"ice to dynamically generate )$, lot or serial num*ers. The default !ey is ctrl'g. Warehouse Management generates a num*er according to the se4uencing rules set up for the *usiness o*=ect. Operators can map the hot !ey to any a"aila*le *utton on the mo*ile de"ice. <s an implementer you can also set up multiple configurations in the same warehouse depending on the de"ice type or the =o* function. 7pon receipt of lot or seriali/ed material the system prompts the operator to enter a material status code for the lot serial num*er or user'defined attri*utes for the lot or serial num*er. The operator can accept the default "alues or modify them if necessary. This page does not appear if the in*ound material is not lot or serial controlled is not material status ena*led or has no attri*utes defined.
Performing Receipts
Su*mitted *y <nonymous on Mon B-?B+?+BBC ' &C%..
Tag%
To start the standard receipt process an operator scans the incoming document or enters the document num*er. ,e6t the operator scans the )$, if it e6ists. If an )$, does not e6ist the operator can create a new )$,. The operator then scans or enters the item num*ers 4uantity lot num*er and serial num*ers if applica*le. The system then matches the material to the document shipping lines according to the matching algorithm. The operator then enters the receipt header information and finally puts away the material. The system does not increment the on hand *alance for the material until the operator transfers the material from a recei"ing su*in"entory in to a storage su*in"entory.
Standard Receipt *low
The direct recei"ing flow is "ery similar to the standard receipt flow. <n operator scans the incoming document or enters the document num*er to start the recei"ing process. ,e6t the operator scans the )$, if it e6ists. If an )$, does not e6ist the operator can create a new )$,. ,e6t the operator can scan or enter the item num*ers 4uantity lot num*er and serial num*er if applica*le. 2inally the operator scans or enters an in*ound staging lane or stoc! locator for the material. The system then matches the material entered to the document shipment lines according to the matching algorithm. The system increments the on hand *alance for this material as soon as the operator completes the receipt. <n operator can optionally choose to perform a put away to ena*le the rules engine to suggest a storage location *ut if the operator recei"ed the material directly in an appropriate storage location no further transactions are necessary.
Receipts 9sing the Receiving Common 1nterface 5usinesses need to *e a*le to perform receipts without !nowing the document types they are recei"ing against. The single recei"ing common user interface allows receipts against all in*ound document types. 3ocument types include $urchase Orders #eturn Material <uthori/ations Intransit Shipments <S, and Internal #e4uisitions. If your *usiness does not need to use one common user interface to perform all the receipts it is ad"isa*le to use the different menu entries for each of the types of receipts. This will increase the performance while "alidating the list of "alues. &. ,a"igate to the #eceipts screen *y selecting <ll from the #ecei"ing menu. The #eceipts screen displays the document field where you can enter the document num*er without !nowing the document type you are recei"ing against.
+. The 3ocument field is an )OA that includes all the open purchase orders return material authori/ations intransit shipments and internal re4uisitions against which the material can *e recei"ed. Warehouse Management will determine the document type displaying a list of "alues if there are multiple matches. -. 5ased on the document type once you e6it the 3ocument field the user interface changes to loo! e6actly as if you would ha"e performed the receipt for that document type after initiating it directly from the menu. 2or e6ample if the scanned document is a purchase order the Supplier and )ine ,um fields would display on the user interface. <lso *ased on the document type selected the prompt for the 3ocument field changes. In this e6ample it changes to $O ,um so you understand you are performing a $O receipt.
P0 Put Away Process

Su*mitted *y <nonymous on 2ri B+?&;?+B&& ' B&%-C Tag%
In addition to supporting )$, put away from a Standard #outing Oracle Warehouse Management ena*les you to initiate a put away *y scanning an )$, anywhere in the warehouse. <fter you scan an )$, you ha"e the option of loading that )$, onto your current e4uipment or dropping the )$, immediately. If you load the )$, you can scan additional )$,s onto their e4uipment then *egin dropping )$,s whene"er they are at the appropriate locations to *e dropped. ,ote% $utaway transactions must *e carried out using the manual load directed drop drop an )$, or manual drop pages. Manual oads < manual load is a put away tas! that you create. >ou can use the Manual )oad page to fully load the contents of one )$, into another )$, to put away the outer )$,.
>ou can also transfer the contents of one )$, into another )$, in order to put away the second )$,. 2inally you can use the Manual )oad page to select items from an )$, and put away only those items. 2or efficient warehouse operations you sometimes need to put away indi"idual contents of an )$, and then consolidate the content at "arious warehouse storage locations. To accomplish this you load an entire )$, and then specify which items of the )$, to put away at the "arious storage locations. To perform a manual load complete the following steps%
&. ,a"igate to the Manual )oad $age. +. @nter or scan the )$, to load. -. @nter the Into )$, to nest the )$,. .. Select P)oad 2ull )$,L to nest the loaded )$, in the to )$, select PTransfer ContentsL to transfer the contents from one )$, to another )$, or choose PSelect ContentsL to open the Item )oad page and select loose content from the loaded )$,. 0. If you selected P)oad 2ull )$,L or PTransfer ContentsL repeat the pre"ious steps to load or transfer additional )$,s. If you selected PSelect ContentsL complete the following steps. 9. @nter the item num*er to load. :. @nter the re"ision information if re4uired. ;. Confirm the 4uantity to load in the Confirm field. If the item is under dual unit of measure control the system displays the secondary unit of measure and secondary 4uantity. Manual 8rops >ou can use the manual drop page to drop items loaded using the Manual )oad.
8irected 8rops 3irected drops allow you to drop any )$, loaded *y the manual load page and the pic! load page. 2or a directed drop the system selects the drop location using the Oracle Warehouse Management #ules @ngine put away rules. Move any P0 >ou can use Mo"e any )$, to drop any loaded )$,s or perform an implicit load followed *y a drop. This is applica*le only to in*ound )$,s. 8rop All P0s >ou can drop multiple loaded )$,s and the system directs you to drop the )$,s in the optimal drop se4uence.
Cross 8ocking
Su*mitted *y <nonymous on Sat B&?B;?+B&& ' &.%+C Tag%
Crossdocking is the use of in*ound receipts to satisfy out*ound demands. >ou can use crossdoc!ing to match out*ound shipments to scheduled receipts in ad"ance. This ena*les you to achie"e faster flow'through times and optimi/e warehouse resources. 5efore system uses the rules engine to determine a put away suggestion Warehouse Management chec!s for *ac!ordered sales order lines or WI$ =o*s that incoming material can fulfill if you ena*le cross doc!ing for the organi/ation. If Warehouse Management finds an eligi*le line it prompts operator to put away the incoming material directly to an out*ound staging lane or issue it to the WI$ =o*. This flow a"oids the unnecessary material handling and material processing. If only a portion of the incoming material is needed to fulfill the re4uirement the system directs the operator to cross doc! the material needed to fulfill re4uirement. The system then uses the rules engine to find an optimal storage location for the remaining 4uantity. The system chec!s for cross doc!ing opportunities *efore it suggests storage put away locations if you ena*le cross doc!ing for the organi/ation. Cross doc!ing is a"aila*le only for standard and inspection routing receipts. 3epending on the parameter setting for the organi/ation the system may prioriti/e WI$ demand *efore or after sales order demand. Crossdock planning hori?on@window Crossdoc!ing occurs during a period of time !nown as the crossdoc! planning hori/on. The crossdoc! planning hori/on is the time period within which the system considers demands with a schedule shipment date for crossdoc!ing.
The earliest crossdoc! time is the *eginning of the crossdoc! planning hori/on. This is the ma6imum time difference that a scheduled receipt can lag with respect to the scheduled shipment time. 2or e6ample if the earliest crossdoc! time is four hours and a demand e6ists with a scheduled shipment time of 9%BB p.m. then the system does not consider material with a scheduled receipt time that is earlier than +%BB p.m. The latest crossdoc! time is the end of the crossdoc! planning hori/on. This is the minimum time difference that a scheduled receipt can lag with respect to the scheduled shipment time. 2or e6ample if the latest crossdoc! time is one hour and a demand e6ists with a scheduled shipment time of 9%BB p.m. then the system does not consider material with a scheduled receipt time that is later than 0%BB p.m. The crossdoc! window is the difference *etween the earliest and latest crossdoc! time. 2or e6ample if the earliest crossdoc! time is four hours and the latest crossdoc! time is one hour then the crossdoc! window is three hours. #(ample : )et @arliest cross doc! time T : hours )atest cross doc! time T + hours < SO is scheduled to *e shipped U &B$M Then cross doc! window is (: K +) T 0 hours <nd cross doc! hori/on starts U (&B K :) - $M and ends (&B '+) ; $M Cross 8ocking "ypes Oracle Warehouse Management supports two types of crossdoc!ing planned crossdoc!ing and opportunistic crossdoc!ing. $lanned crossdoc!ing matches e6pected receipts to a demand source and opportunistic crossdoc!ing matches demands to recei"ed supply. In case of $lanned crossdoc!ing the pre'allocation is done during $ic! #elease. In opportunistic crossdoc!ing dynamic allocation is done during material putaway. >ou use planned crossdoc!ing and opportunistic crossdoc!ing for different scenarios. $lanned crossdoc!ing wor!s *est when you !now your supply in ad"ance. It ena*les you to control the throughput of your warehouse and matches !nown demand with e6pected supplies. Opportunistic crossdoc!ing helps with uncertainties. It uses the rules engine to match newly arri"ing supply to e6isting demands. This helps in cases in which a supply or demand source is changed modified or cancelled.
Crossdocking Setup
Su*mitted *y <nonymous on Sat B&?B;?+B&& ' +B%00 Tag%
>ou use the Cross doc! Criteria window to determine the eligi*le supply and demand sources for crossdoc!ing. <fter you create a crossdoc! criterion you ena*le it in the rules wor!*ench ?or else can default it from organi/ation parameter for opportunistic cross doc!ing. To Create a Crossdoc! Criterion na"igate to the Crossdoc! Criteria window. 565 @nter a name and a description for the crossdoc! criteria. &.+ Select the Criterion Type. $lanned crossdoc!ing attempts to select a supply from among eligi*le supply sources and matches it to a gi"en demand source. Opportunistic crossdoc!ing selects from eligi*le demand sources and matches it to a gi"en supply source. 765 @nter the time *uc!et for which the system considers documents for crossdoc!ing. >ou can enter a crossdoc! window in days hours or minutes. +.+ @nter the Order $rocessing Time. This is the time re4uired to process the order. If you do not enter a "alue in this field then the system automatically assumes the "alue is /ero. >ou can enter an order processing time in hours days or minutes. +.- @nter a 5uffer Time. This is the time re4uired to safely fulfill an order. The system uses the order processing time and the *uffer time to trigger e6ceptions. The system does not consider supply and demand that occur within the *uffer /one for crossdoc!ing. If you do not enter a "alue in this field then the system automatically assumes the "alue is /ero. >ou can enter a *uffer time in hours days or minutes. +.. @nter a $ast 3ue Supply Cut'Off. This is the offset time the system uses to determine the past due supply cut off time fence. This parameter is used for planned crossdoc!ing. The system does not consider any supply that occurs *eyond this time fence for crossdoc!ing. #(ample The following demand e6ists for which crossdoc!ing needs to *e planned at ;%BB a.m. The order processing time is two hours the *uffer time is one hour and the crossdoc! window is four hours. Shipment & has a shipment time of -%BB p.m. and Shipment + has a scheduled ship time of .%BB p.m. The time fences for the demand sources are%
2or Shipment & the system considers supply sources with a scheduled receipt time later than &+%BB p.m. or earlier than ;%BB a.m. ineligi*le for crossdoc!ing. The system automatically e6cludes any supply more than one hour late from crossdoc! planning. +.0 @nter the Crossdoc!ing (oal. >ou can choose to ma6imi/e crossdoc! minimi/e wait or create custom crossdoc!ing logic. :65 Chec! $rioriti/e 3ocuments if you want the rules engine to consider document priority during crossdoc!ing. -.+ Chec! the Integer Guantities only chec! *o6. >ou use this option if your recei"ing 7nit of measure is different from the demand unit of measure and you want to ensure that you crossdoc! the recei"ed units as a whole. ;65 Chec! the Schedule 3emand anytime on Shipment 3ate chec! *o6 if the demand does not ha"e a doc! door appointment. This ena*les the system to assume the sales order is scheduled anytime during a one'day window. ;67 Chec! the Schedule Supply anytime on $romise 3ate chec! *o6 if an in*ound doc! schedule does not e6ist for incoming supply. This ena*les the system to assume the purchase order is scheduled anytime during one'day window. ,ote% This parameter is a"aila*le only for planned crossdoc!ing. ;6: 2or documents with doc! door appointments select the demand and supply schedule for crossdoc!. The choices are% D @arliest <ppointment Time% If an appointment is from +%BB p.m. to .%BB p.m. the system recogni/es +%BB p.m. as the scheduled receipt or shipment time for crossdoc!. D Mean <ppointment Time% If an appointment is from +%BB p.m. to .%BB p.m. the system recogni/es -%BB p.m. as the scheduled receipt or shipment time for crossdoc!. D )atest <ppointment Time% If an appointment is from +%BB p.m. to .%BB p.m. the system recogni/es .%BB p.m. as the scheduled receipt or shipment time for crossdoc!. <6 Select the Supply ta* to enter supply sources for planned crossdoc!ing or select the 3emand ta* to enter demand sources for opportunistic crossdoc!ing.
Select an a"aila*le supply source for planned crossdoc!ing from the <"aila*le Supply Sources region. Clic! the greater than *utton to ma!e the supply source eligi*le. >ou can clic! the *utton with two greater than sym*ols to ma!e all supply sources eligi*le for planned crossdoc!ing. The a"aila*le supply sources are% &. +. -. .. 0. <ppro"ed $O <S, Internal #e4uisition Intransit Shipments Material in #ecei"ing
9. @nter 3emand Sources
Select an a"aila*le demand source for opportunistic crossdoc!ing from the a"aila*le 3emand Sources region. Clic! the greater than *utton to ma!e the demand source eligi*le. >ou can clic! the *utton with two greater than sym*ols to ma!e all demand sources eligi*le for crossdoc!ing. The a"aila*le demand sources are%

Sales Order (Scheduled) Sales Order (5ac!ordered) Internal Order (Scheduled) Internal Order (5ac!ordered) WI$ Component 3emand (5ac!ordered )
Planned Crossdocking Setup

Su*mitted *y <nonymous on Mon B&?&B?+B&& ' +-%B9 Tag%
$lanned Crossdoc! is demand dri"en and prior to arri"al of the material demand is planned to *e fulfilled using incoming supply. There are 0 different setups that need to *e done for planned cross doc!ing. In the *elow e6ample we are creating a planned cross doc! criteria *y the name RMIV$lanned Cross 3oc!. <fter defining the criteria weIll attach to it the organi/ation in rules wor! *ench. The ne6t step is to create an operation plan for planned cross doc!ing. #ests of the setups are OM related. Crossdoc!ing Time fences ' Identify eligi*le supply sources (for planned crossdoc!ing) or eligi*le demand sources (for opportunistic crossdoc!ing)

Crossdoc! Window % Wait Time Time during which cross doc!ing ta!es place Order $rocessing Time (O$T) % The time re4uired to complete the shipping processH)oad?unload?mo"e Time 5uffer Time (5T) % @6tra time pro"ided for Safety margin $ast 3ue Supply Cut'off ($3S) % To e6clude uncertain suppliesH <ny supply *efore this time is ignored *y the system.Suppose current time is &B<M and $3S is -B mins then system would ignore any supply *efore C.-B <M
Crossdocking .oal ' Choose one or more supply (or demand) sources from the pool of eligi*le supply (or demand) sources

Ma6imi/e Crossdoc! (2I2O) Minimi/e Wait ()I2O)
Custom
8etermine e(pected arrival time for supply 3oc! appointment time $lanned arri"al date @6pected receipt date Shipped date O Transit time $romise date ,eed *y date 8etermine e(pected departure time for demand 3oc! appointment time $lanned departure date Schedule ship date $romise date Planned Crossdock A /ackward scheduling Current Time ' &&%BB Scheduled Ship time for demand K &9%BB Order $rocessing Time T & Er 5uffer Time T & Er Crossdoc! Window T + Ers $ast 3ue Supply Cutoff T B.0 Ers )atest arri"al time for a supply to *e crossdoc!ed T Scheduled Ship time for demand K ( Order $rocessing Time O 5uffer Time) T &9%BB K (&O&) T &.%BB @arliest arri"al time for a supply to *e crossdoc!ed T )atest arri"al time for a supply to *e crossdoc!ed ' Crossdoc! Window T &.%BB K + T &+%BB
76 Crossdock criteria assignment
Two new #ule Types are introduced in #&+. $lanned Crossdoc! 1 Opportunistic Crossdoc!. In out planned cross doc! test we will select $lanned Crossdoc! type. We create a new assignment with a se4uence num*er. )ower the se4uence higher the precedence. ,ote% <lways remem*er to run R(enerate <ll #ules Concurrent program after you ha"e defined any new rule or made changes to e6isting rule. :6 Crossdock +peration Plan
On operation select Cross doc!. In cross doc! method select appropriate cross doc! method. In our e6ample we select R(3efault) )$, *ased consolidation in staging lane within deli"ery. The other options are%

)ocator *ased consolidation in consolidation locator within deli"ery in staging lane )$, *ased consolidation in consolidation locator within deli"ery in staging lane 3irect consolidation in staging lane within deli"ery )$, *ased consolidation in staging lane across deli"eries 3irect consolidation in staging lane across deli"eries )$, *ased consolidation in consolidation locator across deli"eries in staging lane )ocator *ased consolidation in consolidation locator across deli"eries in staging lane
;6 +M System Parameters
Set a "alue of RB for W#eser"ation Time 2enceX parameter. ,ote% This setting will ensure that no high le"el reser"ations are created when the sales orders are *oo!ed. This is necessary *ecause system will not try to crossdoc! for the demand lines with any reser"ations.
+pportunistic Crossdock
Su*mitted *y <nonymous on 2ri B&?&.?+B&& ' &9%+B Tag%
Opportunistic cross doc!ing is supply initiated. When you recei"e materials against a $O Warehouse Management System can use those newly recei"ing material to fulfill an e6isting demand li!e a SO (scheduled or *ac!ordered) an Internal order (scheduled or *ac!ordered) a WI$ Component demand(*ac!ordered) if you ena*le Opportunistic Cross doc!ing on the Organi/ation $arameters window. Warehouse Management uses the rules wor!*ench to determine the appropriate crossdoc! criterion to use for supply. 3epending on the eligi*le demand sources crossdoc!ing goal and time fences that you specify in the opportunistic crossdoc! criteria the system determines to which demand to crossdoc! the supply. It then stamps and operation plan on the material. To perform opportunistic crossdoc!ing the system% &. +. -. .. 0. Aalidates supply source 3etermines eligi*ility pool $erforms pegging Creates reser"ations Creates deli"ery
56 Validates supply source When you recei"e material WMS first chec!s if opportunistic cross doc! is ena*led or not for the organi/ation. If its ena*led then system pic!s up the rele"ant cross doc! criteria to chec! if there is any a"aila*le demand for which you can cross doc! the recei"ed material. 76 8etermines eligi,ility pool If you can crossdoc! the supply then the system identifies the eligi*le deli"ery lines for crossdoc!ing *ased on the crossdoc! criteria. The a"aila*le demand sources are scheduled sales orders *ac!ordered sales orders scheduled internal orders *ac!ordered internal orders and *ac!ordered WI$ component demand. Warehouse Management performs the following chec!s to determine eligi*le demand% D The deli"ery line item and the recei"ed line item are the same. D The crossdoc! criteria allow the demand document type. D If the recei"ed items are associated with a pro=ect and tas! and the organi/ation does not allow fulfillment
across pro=ect and tas!s then only demand that *elongs to the same pro=ect and tas! or common demand is eligi*le for crossdoc!ing. ,ote% If the organi/ation allows fulfillment across pro=ect and tas! then Oracle Warehouse Management ignores the pro=ect and tas! on supply and demand sources for crossdoc!ing. :6 Pegging <fter the system creates a list of eligi*le deli"ery lines then the crossdoc!ing algorithm performs pegging and selects one more demands sources for crossdoc!ing. If you select the 3ocument $riority chec! *o6 then the system considers the document type with the highest demand first. ;6 Reservation inking Oracle Warehouse Management creates a reser"ation that lin!s the demand to incoming supply. <6 Create 8elivery The system merges the deli"ery lines with an e6isting deli"ery if the out*ound deli"ery is within the crossdoc! window. If no deli"ery is within the crossdoc! window then the system creates a new deli"ery for the crossdoc!ed items. B6 +pportunistic Crossdock Receipt Validations Crossdoc!ing e6ecution performs the following "alidations upon receipt% D Aerifies whether supply source is already planned for crossdoc!ing% If the supply source is already planned for crossdoc!ing and has a "alid demand source then the system chooses an operation plan for the item. D Supply source is ineligi*le for crossdoc!ing or crossdoc!ing is not allowed% If the supply source is ineligi*le or crossdoc!ing is not allowed for the organi/ation then the system directs you to put away the material. D Supply source is reser"ed to a demand source and opportunistic crossdoc!ing is ena*led% The system uses the crossdoc! criteria to "alidate the supply and demand sources. If *oth are eligi*le for crossdoc!ing then the system identifies the recei"ed material for crossdoc!ing and assigns an operation plan. D Supply source is not reser"ed and opportunistic crossdoc!ing is ena*led% The system uses the crossdoc!ing criteria to "alidate the supply source. If the supply source can *e crossdoc!ed then the system identifies the appropriate demand source. The system then uses the crossdoc!ing algorithm to identify the e6act demand source.
+pportunistic Crossdock #(ample

Su*mitted *y <nonymous on 2ri B&?&.?+B&& ' +B%BC
In this e6ample we will show how Opportunistic Crossdoc!ing happens for a $O as Supply and Sales Order as 3emand. We will define an item and assign it to organi/ation W&. Then we will create a $O for the item for 4ty &B. Then we create a Sales Order for the item for 4ty&B. ,ow we do $O receipt for 4uantity of &B. When you try to do put away system will prompt you that crossdoc!ing opportunity e6ists. @6ecute cross doc!ing. Opportunistic Crossdoc! K 2orward scheduling <s per the a*o"e setup Order $rocessing Time T & Er 5uffer Time T & Er Crossdoc! Window T + Ers )et the Current Time *e &&%BB and Supply arri"es at &&%BB @arliest departure time for crossdoc!ing to a demand T Current Time O (Order $rocessing Time O 5uffer Time) T &&%BB O (&O&) T &-%BB )atest departure time for cross doc!ing to a demand T @arliest departure time for crossdoc!ing to a demand O Crossdoc! Window T &-%BB O + T &0%BB
&. Complete the re4uired setups. +. Create a SO and *oo! it the line status changes to awaiting shipping. -. Create a $O with the same item num*er.
.. #ecei"e the $O. <s the cross doc! plan the newly recei"ed $O materialll *e reser"ed against the SO.
Planned Crossdocking
Su*mitted *y <nonymous on Sun B&?BC?+B&& ' &+%B: Tag%
$lanned crossdoc!ing occurs during pic! release. Oracle Warehouse Management uses release se4uence rules to se4uence demand sources and fulfills the demand *ased on the allocation method that you specify during pic! release. When you run pic! release the system uses the allocation method to determine whether crossdoc! should *e planned. If crossdoc! should *e planned then the system uses the crossdoc! criteria that you specified to determine the eligi*le supply. If you did not define the crossdoc! criteria during pic! release then the system uses the rules wor!*ench to determine the appropriate planned crossdoc! criteria to use for the demand. If the system identifies a supply source other than in"entory for fulfillment then it determines the scheduled ship time for the deli"ery lines and assigns the scheduled ship date and times to deli"ery lines as follows%
D If an out*ound trip e6ists then the system *ases the departure time on the doc! schedule. D If the sales order is associated with a deli"ery then the system chec!s to see whether a carrier e6ists. If a carrier e6ists then the system *ases the departure dated on the carrier time and doc! door appointment. If multiple doc! door appointments for the carrier e6ist then the system selects the doc! door and appointment that is closest to the scheduled ship date and time. D If the sales order has a specified ship method then the system determines the carrier and the e6act time for the carrier if the carrier has a doc! door appointment for the same day. If multiple appointments e6ist then the system selects the appointment that is closest to the scheduled ship time and date. D If none of these conditions apply then the system uses the departure time as the scheduled ship time for the orderH howe"er if the crossdoc! criteria allow scheduling fle6i*ility then the system assumes the order can ship anytime during the day. To perform planned crossdoc!ing Oracle Warehouse Management% &. +. -. .. 0. 9. 3etermines supply eligi*ility $erforms pegging Creates deli"ery )in!s reser"ation to supply and demand <ssigns crossdoc! operation plan Changes deli"ery line status to $lanned for Crossdoc!
Supply #ligi,ility The a"aila*le supply sources for planned crossdoc!ing are appro"ed $O <S, internal re4uisition intransit shipments and material in recei"ing. >ou can peg material in recei"ing only if the material is not associated with a putaway suggestion. To peg material in recei"ing you must turn off the organi/ation parameter $regenerate after #eceipt When the system identifies the eligi*le supply lines it performs the following chec!s% D The supply and demand items must *e the same. >ou cannot use a su*stitute item. D If a deli"ery line is associated with a pro=ect and tas! then the system does not allow fulfillment across pro=ects and tas!s. It considers only material that *elongs to the same pro=ect and tas! or common stoc!. ,ote% If the organi/ation allows fulfillment across pro=ects and tas!s then crossdoc! planning ignores the pro=ect and tas! information on supply and demand sources. D The scheduled receipt time of the supply must *e within the crossdoc! window. The system automatically assumes that all past'due supply lines are a"aila*le for crossdoc!ing if they satisfy the past'due supply cutoff. The system assigns scheduled receipt lines a receipt date and time as follows% D If an in*ound trip e6ists then the system assigns the arri"al time *ased on the doc! appointment. D If an <S, e6ists then the system assigns the arri"al time *ased on the <S,. D If neither condition applies then the system assigns the receipt date and time *ased on the $O promise date. If the crossdoc! criteria are fle6i*le then the system assumes the receipt can occur anytime during the day. Pegging <fter Oracle Warehouse Management creates the eligi*le supply list it runs the crossdoc!ing algorithm to perform pegging. It then selects one or more supply sources for crossdoc!ing. If you select the prioriti/e document on the Crossdoc! Criteria window then the system considers the document with the highest priority first.
If a demand is already pegged to a supply then the system considers only the reser"ed supply for crossdoc!ing. It uses the crossdoc! criteria to chec! whether the supply is eligi*le for crossdoc!ing and whether the scheduled receipt date occurs within the crossdoc! window. If the supply meets the criteria then the system considers the prior reser"ation and modifies the reser"ation record to ena*le crossdoc!ing. Reservation inking Oracle Warehouse Management creates a reser"ation that lin!s the supply to an e6isting demand. Create 8elivery If the deli"ery lines are lin!ed to a deli"ery or crossdoc! planning run Oracle Warehouse Management does not create a deli"ery. If no lin! e6ists then it merges the deli"ery lines with the out*ound crossdoc! deli"ery if it occurs within the crossdoc! window. If the deli"ery does not occur within the crossdoc! window then it creates a new deli"ery for the crossdoc!ed lines. Assign +peration Plan <fter Oracle Warehouse Management creates the deli"ery it assigns the appropriate operation plan to the material Change 8elivery ine Status <fter Oracle Warehouse Management pegs the supply creates the reser"ation and deli"ery and assigns and operation plan it changes the status of the crossdoc! lines to $lanned for Crossdoc!. It ignores these lines in future pic! releases and planned crossdoc!ing runs.
Plan Cross8ocking #(ample

Su*mitted *y <nonymous on Mon B&?&B?+B&& ' &9%B&
Tag%
$lanned Crossdoc! is demand dri"en and prior to arri"al of the material demand is planned to *e fulfilled using incoming supply. There are 0 different setups that need to *e done for planned cross doc!ing. In the *elow e6ample we are creating a planned cross doc! criteria *y the name RMIV$lanned Cross 3oc!. <fter defining the criteria weIll attach to it the organi/ation in rules wor! *ench. The ne6t step is to create an operation plan for planned cross doc!ing. #ests of the setups are OM related. Crossdoc!ing Time fences ' Identify eligi*le supply sources (for planned crossdoc!ing) or eligi*le demand sources (for opportunistic crossdoc!ing)

Crossdoc! Window % Wait Time Time during which cross doc!ing ta!es place Order $rocessing Time (O$T) % The time re4uired to complete the shipping processH)oad?unload?mo"e Time 5uffer Time (5T) % @6tra time pro"ided for Safety margin $ast 3ue Supply Cut'off ($3S) % To e6clude uncertain suppliesH <ny supply *efore this time is ignored *y the system.Suppose current time is &B<M and $3S is -B mins then system would ignore any supply *efore C.-B <M
Crossdocking .oal ' Choose one or more supply (or demand) sources from the pool of eligi*le supply (or demand) sources

Ma6imi/e Crossdoc! (2I2O) Minimi/e Wait ()I2O) Custom
8etermine e(pected arrival time for supply 3oc! appointment time $lanned arri"al date @6pected receipt date Shipped date O Transit time $romise date ,eed *y date 8etermine e(pected departure time for demand 3oc! appointment time $lanned departure date Schedule ship date $romise date Planned Crossdock A /ackward scheduling Current Time ' &&%BB Scheduled Ship time for demand K &9%BB Order $rocessing Time T & Er 5uffer Time T & Er Crossdoc! Window T + Ers $ast 3ue Supply Cutoff T B.0 Ers )atest arri"al time for a supply to *e crossdoc!ed T Scheduled Ship time for demand K ( Order $rocessing Time O 5uffer Time) T &9%BB K (&O&) T &.%BB @arliest arri"al time for a supply to *e crossdoc!ed T )atest arri"al time for a supply to *e crossdoc!ed ' Crossdoc! Window T &.%BB K + T &+%BB
76 Crossdock criteria assignment
Two new #ule Types are introduced in #&+. $lanned Crossdoc! 1 Opportunistic Crossdoc!. In out planned cross doc! test we will select $lanned Crossdoc! type. We create a new assignment with a se4uence num*er. )ower the se4uence higher the precedence. ,ote% <lways remem*er to run R(enerate <ll #ules Concurrent program after you ha"e defined any new rule or made changes to e6isting rule. :6 Crossdock +peration Plan
On operation select Cross doc!. In cross doc! method select appropriate cross doc! method. In our e6ample we select R(3efault) )$, *ased consolidation in staging lane within deli"ery. The other options are%

)ocator *ased consolidation in consolidation locator within deli"ery in staging lane )$, *ased consolidation in consolidation locator within deli"ery in staging lane 3irect consolidation in staging lane within deli"ery )$, *ased consolidation in staging lane across deli"eries 3irect consolidation in staging lane across deli"eries )$, *ased consolidation in consolidation locator across deli"eries in staging lane )ocator *ased consolidation in consolidation locator across deli"eries in staging lane
;6 +M System Parameters
Set a "alue of RB for W#eser"ation Time 2enceX parameter. ,ote% This setting will ensure that no high le"el reser"ations are created when the sales orders are *oo!ed. This is necessary *ecause system will not try to crossdoc! for the demand lines with any reser"ations.
+ut,ound ogistics
Su*mitted *y <nonymous on 2ri &+?-&?+B&B ' +-%.0 Tag%
$ic! release is the process of selecting orders for release to the warehouse for pic!ing and shipping. <fter the orders are released Oracle Warehouse Management uses the #ules @ngine to determine the appropriate material allocations. <fter the system completes the allocations the Tas! Type <ssignment engine assigns the appropriate tas! types and the system can then suggest pac!ing configurations. <t this point the tas! is now ready for dispatching to an operator. The operator can then log onto the system optionally sign onto a material handling de"ice and accept pic! tas!s. Optionally the operator can accept all pic! tas!s for a specific tas! grouping as a *undled set of tas!s. Oracle Warehouse Management ena*les the operator to pic! multiple partial )$,s full )$,s and loose pic!s for a single tas!. )oose material and material pac!ed in an )$, can *e pic!ed in any se4uence for a gi"en tas!. Operators can continue to load material as long as there is capacity on the e4uipment. <fter the material is loaded it can *e dropped into staging lanes for further pac!ing and la*eling *efore shipment. This completes the material pic!ing process. <t this time order lines are also split or merged *ased on e4uipment capacity defined for the e4uipment and pic! methodology defined *y pic! slip grouping rules. Out*ound logistics ena*les operators to pic! pac! and ship orders to customers. Out*ound logistics contains the following components% &.& $ic! #elease &.+ #ules (#elease rule release se4 rule and pic!ing rule) &.- Tas!s?Tas! Type <ssignment +.& WMS Control 5oard +.+ )oad +.- 3rop -.& Consolidation?$ac!ing -.+ 3oc! 3oor <ppointments -.- Shipping 565 Pick Release The pic!ing process ena*les operators to pic! material to fulfill orders. Warehouse Management supports
three types of pic!ing% order pic!ing replenishment pic!ing and WI$ pic!ing. The system distri*utes pic!s to operators as tas!s. 567 Rules 3uring implementation you can create rules to fulfill orders in the most efficient manner. The following rules support the pic!ing process% D #elease #ules% The pic!ing criteria of order lines for pic! release. D #elease Se4uence #ules% The order the system releases deli"ery lines for pic!ing. D $ic! Slip (roup #ules% Eow the system groups tas!s on a mo"e order pic! slip report for pic!ing. 56: "asks Warehouse Management creates and dispatches tas!s to 4ualified operators *ased on rules you configure. 765 WMS Control /oard The WMS Control 5oard pro"ides managers with a real'time snap shot of the warehouse and ena*les them to redistri*ute tas!s as needed. They can monitor the progress of tas!s as well as manually dispatch tas!s to operators. :65 Consolidation Warehouse Management ena*les operators to consolidate partially filled containers in to fewer and *etter' optimi/ed containers. Packing Warehouse Management ena*les operators to pac! containers with multiple le"els of nesting and sends notifications if an order contains special pac!ing instructions. Operators can perform pac!ing during pic!ing or as an independent process. :67 8ock Appointments for "rips Managers can use Warehouse Management to schedule out*ound carrier appointments doc! door a"aila*ility and staging lane usage within the warehouse. :6: Shipment Verification and Close Once an operator pic!s and loads an order Warehouse Management automatically determines the items and 4uantities to deduct from in"entory.
+verview of Picking
Su*mitted *y <nonymous on Sat B&?B&?+B&& ' &+%+. Tag%
$ic!ing ena*les operators to pic! material to fulfill orders. Warehouse Management supports three types of pic!ing% order pic!ing replenishment pic!ing and WI$ pic!ing. Warehouse Management dispatches pic!s to operators as tas!s. Managers can perform manual pic! release or you can create a series of rules to automate the process during implementation. $lease read the pic! release *asics U http%??www.oracleug.com?user'guide?order'management?pic!'release Warehouse Management uses the following rules to release orders% pic! release rules release se4uence rules pic!ing rule and pic! slip grouping rules. $ic! release rules determine how the system to selects sales orders for release. If trips are not scheduled for doc! doors then pic! release rules also determine the appropriate staging lane for sales orders. <fter the system determines the sales orders to release it can use release se4uence rules to determine the se4uence deli"ery lines are released for pic!ing *ased on sales order num*er outstanding in"oice "alue scheduled date departure date and shipment priority. $ic! slip grouping rules esta*lish how tas!s are grouped on a mo"e order pic! slip. pic!ing rule in in"entory determine the order in which re"isions lots su*in"entories and locators are pic!ed for sales orders. $ic!ing rule in WMS is used for directed pic!ing creates material allocations and directs operators to pic! material from specific locations.
They wor!in con=unction with the different pic! methodologies. $ic! methodologies refer to the different method an operator performs pic!ing tas!s. 2or e6ample an operator may select to pic! an order *y itself or to pic! multiple orders at the same time. The system generates pic!ing tas!s and dispatches them to 4ualified operators *ased on rules. <fter pic!ing is complete the system pro"ides operators with the appropriate num*er and si/e of containers the order re4uires for shipping. #(plaining Pick Release The pic! release process selects sales order lines to release to the floor for pic!ing and shipping. < pic! release rule stores the criteria that will *e used to select sales orders for release. If trips are not scheduled for doc! doors then the release rule also determines the staging lane to which the material should *e deli"ered. Replenishment Picking
Warehouse Management dispatches replenishment tas!s to 4ualified operators to replenish forward pic!ing areas. W1P Picking Warehouse Management dispatches WI$ pic!ing tas!s to 4ualified operators to pic! material to fulfill wor! order re4uirements *ased on rules you define. Operators can pic! the following supply types% push assem*ly pull and operation pull. ,ote% Operators deli"er all pic!s to a su*in"entory and locator e6cept for WI$ pic!s. Operators can optionally drop WI$ pic!s directly to a =o*. This ena*les operators to perform the pic! and the issue in one step. This capa*ility is ena*led for push components where the supply su*in"entory and locator are *lan! on the 5OM. #(plaining the Pick Allocation Process <fter orders ha"e *een selected for release and prioriti/ed for allocation the rules engine ma!es the material allocations. #ecall that material allocations might *e *ased on characteristics such as customer re4uirements organi/ation'wide *usiness directi"es stoc! rotation policies item handling restrictions item category or *y some other *usiness attri*ute. The rules engine can also di"ide the allocations *y pic! unit of measure. The output of the pic! allocation is a tas! that includes the su*in"entory and locator from which to pic! and if applica*le the re"ision and lot to *e pic!ed. <fter the system performs allocations it must determine the tas! type so that the =o* to pic! the allocated material can *e dispatched to an appropriately trained user. #(plaining the Picking Process
Operators can accept a pic!ing tas! or a set of tas!s directly from the mo*ile de"ice. The system dispatches tas!s through the mo*ile user interface. Through this user interface the pic!er can "iew the item 4uantity su*in"entory and locator from which they can pic! the load. If the item were re"ision or lot controlled the system would also display those details. The pic!ing tas!s assigned *y the system to a user might include any of the following%
$ic! loose items into an )$, $ic! whole )$,s $ic! multiple )$,s for e6ample pic! 0 *o6es of &B each to fulfill a tas! to pic! 0B $ic! from )$,s for e6ample pic! 0 items out of a *o6 of &B $ic! multiple partial )$,s full )$,s and loose pic!s for a single tas! 5uild larger )$,s Aiew cartoni/ation suggestion
The user can confirm a pic! *y scanning one or more )$,s to load. If the material in the storage locator is not identified with an )$, then the user must confirm the item 4uantity and the storage su*in"entory and locator to confirm the pic!. The user can also unpac! an )$, to fulfill the pic! howe"er if the pic! units of measure are appropriately esta*lished during system setup unpac!ing an )$, to fulfil a pic! should not *e necessary. The user can also pic! the items or the whole )$, into another larger )$, (li!e a pallet or carton) thus *uilding a pac!age that can *e shipped during the pic!ing process. If Cartoni/ation is ena*led the user will also see the container suggestion in his or her tas! 4ueue. Auto Pick Confirm >ou can select <uto $ic! Confirm in a Oracle Warehouse Management ena*led organi/ation. In this case e"en if Oracle Warehouse Management $ic! #ules specify )$, allocation no )$,s will *e pic!ed. Only loose material will *e mo"ed to staging. It is imperati"e the in"entory *e a"aila*le loose (not pac!ed in )$,s). The system does not perform this chec! *efore running auto pic! confirm. >ou must enforce that when using auto pic! confirm material is pic!ed from ,on )$, Controlled Su*in"entories. Pick "ask .rouping Oracle Warehouse Management ena*les users to perform all pic! tas!s for a specific tas! grouping as a *undled set of tas!s. This functionality is only a"aila*le through a mo*ile #2 de"ice and is not a"aila*le through the des!top windows. 7pon $ic! #elease pic! tas!s can *e generated and grouped *y a num*er of $ic! Slip (rouping #ules for e6ample Order $ic!ing. Typically this grouping represents a discrete *undle of wor! to *e performed *y a single user. <ll functionality of the pic! tas! screen remains unchanged e6cept that when the tas! has *een completed (either dropped or loaded) a determination will *e made whether more tas!s remain in the current grouping. If so the $ic! )oad screen is presented for the ne6t tas! in the grouping with a message indicating that the pic! has *een completed. If no more tas!s remain for the grouping the Tas! Menu is presented with a message indicating that the last pic! for the grouping has *een completed.
S+ to Pick Confirm & Complete Process

Su*mitted *y <nonymous on Wed B&?B0?+B&& ' &:%-. Tag%
&. Create a sales order
+. )unch the pic! release with *elow parameters <uto $ic! Confirm T ,O (@nsure that re4uire pic! confirm is ena*led in organi/ation parameter if you want to pic! loose material instead of )$,) <uto <llocate T>@S $lan tas! T>@S
7se an )$, controlled su* in"entory as pic! from su* in"entory.
-. ,a"igate to Ware Eouse Manager ' L In4uiry 'L Warehouse Control 5orad and 4uery with the sales order num*er.
Aerify the tas! created in unreleased status and note down the pic! id.
.. ,a"igate to as!s'LManual Tas!s'L$aper 5ased $ic!'L@nter $ic! I3 of 7nreleased Tas! and complete the pic!ing tas!.
Aerify the tas! status
0. ,a"igate to as!s'L3irected Tas!s'L3irected Mo"e'L3rop )oaded )$,s 'L @nter the )$, Complete the pic!ing tas! *y droping the item.
ask oading and 8ropping

Su*mitted *y <nonymous on Wed B&?B0?+B&& ' BB%+Tag%
Tas! loading and dropping includes the following and completes the Oracle Warehouse Management pic!ing tas! process.

)oading material onto e4uipment 3ropping material directly into a staging lane or consolidation locator
<fter the operator pic!s the load they can either drop it directly into a staging lane or load it on to their e4uipment. They can then proceed to the ne6t pic! location. The operator can "iew the current )$,s at any time including information on the customer and the destination address on the e4uipment that are waiting to *e dropped. When the operator is ready to drop the material into a staging lane the system directs the operator to an appropriate staging lane (as determined *y the doc! appointment or pic! release rule). The operator confirms the drop *y scanning the staging lane. If an )$, for the same deli"ery has already *een dropped into the staging lane the operator will *e shown that )$, as a suggested drop )$,. The operator can select another )$, in that lane if multiple )$,s ha"e *een staged for the same deli"ery. <lternati"ely the operator can enter a new )$, to drop into or drop without pac!ing the )$, from the tas! into another )$,. The final pac! can also *e competed as a user'initiated pac!ing transaction.
Tas! dropping completes the Oracle Warehouse Management pic!ing tas! process.
Cartoni?ation> Consolidation and Packing

Su*mitted *y <nonymous on Sun B&?&9?+B&& ' &9%.0 Tag%
Warehouse Management uses cartoni/ation to suggest the *est pac!aging configuration for a group of items. The system presents pac!aging suggestions to operators in the following ways% automatically generating )$,s printing container and shipping la*els and during tas!s. Cartoni/ation can segregate items *y categories you identify during implementation *ased on different pac!aging re4uirements. 2or instance refrigerated goods may re4uire a particular type of insulated cooler while miscellaneous goods can *e pac!ed into any standard corrugated card*oard *o6. In addition the warehouse may use se"eral si/es of each type of container. >ou can also set minimum fill percentages for containers *elow which the system suggests a smaller container. >ou can create multiple le"els of pac!aging along with the re4uisite la*els so operators can generate la*els in a single operation for inner cartons outer cartons and pallets. Operators can halt pac!ing with a
hierarchy of containers midway and then continue again at a later point. Operators can pac! material in a storage container during receipt and pac! it again during sales order pic!ing into a final shipping container. <ll these considerations in addition to the item dimensions weight and "olume in comparison to the physical attri*utes of the container are made when the system selects the container type and 4uantity to use. Cow it works Suppose there are + products K Mo*ile and 3igital Camera which needs different !ind of pac!aging. 2or mo*ile create an item category MO5I)@ with the RCartoni/ation groups as the item category structure. ,e6t attach the item category MO5I)@ to *oth the container item and contained item category sets. Create a mo*ile item MO5B& and attached it with the category set contained item 1 category MO5I)@. Similarly create a mo*ile container item CO,T<I,@#VMO5B& and attached it with the category set container item 1 category MO5I)@. ,ow when system does the Cartoni/ation for the item MO5B& it Rll consider CO,T<I,@#VMO5B& as the pac!aging material. >ou can do the similar !ind setups for 3igital camera products. Consolidation ena*les multiple operators to drop material assigned to a deli"ery in to the same locator or )$, prior to placing the consolidated load in a staging lane. ,ote% If necessary operators can ship material directly from the consolidation location. Packing Material $ac!ing in"ol"es transferring of loose items or )$,S into an )$,. Operators can pac! items either on receipt while they reside in in"entory or during out*ound shipment to customers. Operators can use *oth the des!top and the mo*ile de"ice to pac! material. While des!top pac!ing allows pac!ing for in*ound and out*ound material mo*ile pac!ing allows pac!ing for out*ound material only. The *enefits of pac!ing include% D Consolidation of items into suita*le containers *ased on criteria such as item deli"ery sales order or warehouse location D Confirmation and record the contents of containers while pac!ing D Transaction *y container D $rotection of pac!ed items from damage
Cartoni?ation
Su*mitted *y <nonymous on Sun B+?+B?+B&& ' ++%-; Tag%
Cartoni/ation is the process that suggests a container to pac! items *ased on constraints such as cu*ic "olume of items and container "olume. Oracle Warehouse Management uses cartoni/ation to suggest the *est pac!aging configuration for a group of items. The system can present the pac!aging suggestion to you in one of many ways including automatically generating license plates printing container and shipping la*els and presenting the suggestion to you as part of a tas!. >ou can create multiple le"els of pac!aging along with the re4uisite la*els so you can generate in a single operation la*els for inner cartons pac!ed inside outer cartons and placed on a pallet. >ou can halt pac!ing with a hierarchy of containers midway and then continue again at a later point so you can pac! material in a storage container when it is first recei"ed or completed and then pac! it again during sales order pic!ing into a final shipping container. <ll these considerations in addition to the item dimensions weight and "olume in comparison to the physical attri*utes of the container are made when the system selects the container type and 4uantity to use. Cartoni?ation 9ses Oracle Warehouse Management uses cartoni/ation in three places% &. Sales order and manufacturing pic!ing +. $repac! for manufacturing completion -. In"entory *ul! pac! Cartoni?ation at Pick Release Cartoni/ation is automatically performed when sales order or manufacturing =o*s ? schedules are released for pic!ing if you ena*le the option on for the organi/ation and su*in"entory. <fter the lines are allocated using the #ules @ngine sales order lines are grouped *y deli"ery or *y the deli"ery grouping rule if no deli"eries are created prior to or at pic! release. Manufacturing allocations are grouped *y =o* or schedule.
Cartoni/ation is then performed on each grouping. >ou may use this to suggest the carton to pic! into or the *o6 to place on the con"eyor *elt if you perform con"eyor'*ased pic!ing. Prepack for Manufacturing Completion >ou can use the Container $repac! concurrent re4uest Container $repac! to pre'print la*els in preparation for a manufacturing completion. >ou can then perform the completion in an )$, triggered mode minimi/ing further data entry during the completion. 1nventory /ulk Pack >ou can use *ul! pac!ing of loose material to suggest the containers to pac! material that already resides in in"entory. >ou can use *ul! pac! for *oth loose and pac!ed material. If you pac! loose material you can pac! multiple items in a single operation. >ou can pac! material into additional le"els of pac!aging if you set up multi'le"el pac!aging automatically creating the )$,s and la*els for scenarios where inner cartons should *e pac!ed into outer cartons. Cartoni?ation Rules Starting from #elease &+.&.& customers ha"e the a*ility to choose and create ro*ust rules that automatically determine the *est container during the release process. <utomatic rule engine runs and *ased on rule selected chooses optimal pac!ing materials.
1. Single Item K <n item is always matched to the same container *ased on the static relationship you
setup in the item?container relationship window.

2. Mi6ed Item K 7ses the contained'container item capacity and dimension restrictions defined on the
master item window and chec!s it against the category and category set setup as well. 3. $ic! Slip (rouping K (enerate an )$, for all items that *elong to the same pic! slip. 4. Customer <lgorithm K 7ses a stu* <$I to interface with customer'defined cartoni/ation rules.
Cartoni?ation Process
Su*mitted *y <nonymous on Sun B+?+B?+B&& ' +-%.0 Tag%
The cartoni/ation algorithm Oracle Warehouse Management uses minimi/es the num*er of containers used at each le"el in the pac!aging hierarchy su*=ect to "olume weight and minimum percent fill settings of the containers. The algorithm also "erifies the dimensions of the pac!ed material can fit inside the dimensions of the container. If you defined multi'le"el hierarchy after all the material is pac!ed at the first le"el the algorithm repeats itself with the new containers. The process continues until the top of the pac!aging hierarchy has *een reached the pac!aging process has completed the indicated num*er of le"els or no additional containers are a"aila*le due to minimum percent fill dimensions or other physical attri*utes. The following two e6amples illustrate how cartoni/ation wor!s on a single and a multiple le"el cartoni/ation hierarchy. <lthough la*els are generated at all le"els in the cartoni/ation process )$,s are only created for the outermost le"el for each re4uest.
Single evel Cartoni?ation
Single le"el pac!aging hierarchies are most commonly used during sales order pic! release for $ic! *y )a*el functionality or to select the right pac!ing container. >ou may also use it for pac!ing material in in"entory and generating la*els prior to manufacturing completion if the la*eling re4uirements are simple. Steps &. 3efine an item and assigned contained category group. 3efine a container and assign the container category. +. Create a SO and #un pic! release with <uto Confirm K ,o Create 3eli"ery K >es <uto <llocation K >es $lan tas! K >es. -. ,a"igate to )oad @nter the pic! id (transaction num*er on warehouse control *oard) .. SystemRll show the container num*er as per the setup.
Multi evel Cartoni?ation
7se multi le"el pac!aging hierarchies when you re4uire la*eling for more comple6 pac!aging configurations such as when you need to pac! inner *o6es into outer *o6es that are placed on a pallet. The multiple le"els can *e pac!ed all at once or when using the mo*ile 5ul! $ac! page can *e *ro!en up into se"eral intermediate steps. )a*els can *e generated for each of the many le"els of the hierarchy. Packaging vs6 P0 Only the outermost le"el created at each le"el of cartoni/ation is defined as a license plate. )icense plates are not generated for intermediate le"els. >ou can only calculate material a"aila*ility at the innermost license plate le"el and the rules engine cannot allocate nested )$,s and you cannot pic! them in a single transaction. The way you create license plates and pac!aging entities impacts how la*els print and on'hand *alance maintenance. Content and Summary a,els )a*els generate for each le"el in the pac!aging hierarchy regardless of whether you create a license plate or record the le"el as pac!aging. )$, Summary la*els are printed at e"ery le"el during the cartoni/ation process. These multi'record la*els include all the items contained at or *elow the current cartoni/ation. )$, Content la*els print at e"ery le"el that contains loose material. 2or le"els that license plates are not generated the innermost pac!aging le"el contains loose material and a )$, Content la*el may *e printed. 5ecause material a"aila*ility calculations do not ha"e "isi*ility to pac!aging le"els that do not ha"e license plates the system also prints an )$, Content la*el for the innermost license plate e"en if there are other le"els of pac!aging inside the license plate.
>ou can identify all le"els created *y cartoni/ation with a uni4ue num*er. If a license plate e6ists the num*er is the license plate num*er. If a license plate does not e6ist the num*er is a pac!aging identifier that can *e included on the la*el. >ou can print the identifier (pac!aging or )$,) as well as the immediate parent of the le"el on e"ery content and summary la*el. Thus an )$, Summary la*el may *e identified *y a pac!age I3 and a parent license plate num*er or *y a license plate num*er and a parent pac!age identifier. These relationships help you pac! the material as determined *y the defined pac!aging hierarchies.
Setting up Cartoni?ation
Su*mitted *y <nonymous on Mon B+?+&?+B&& ' BB%+Tag%
>ou must perform se"eral setups steps *efore you can use cartoni/ation. 2or items that always re4uire a specific container use the container load relationship. 2or other items pac!ed into containers in a container group you must create categories to group the container types and the items. >ou must then assign the corresponding items to the categories and assign the physical characteristics such as "olume and weight. 2inally you must define the containers the designate physical characteristics and assign them to the corresponding categories. >ou must ena*le sales order cartoni/ation at the su*in"entory and organi/ation le"els if necessary. 565 Su,inventory and +rgani?ation Setup
>ou must setup cartoni/ation for su*in"entories and organi/ations when you use cartoni/ation during pic! release if cartoni/ation for sales orders or manufacturing is appropriate for your *usiness process. Some su*in"entories may store items in )$,s that are already pac!ed such as a case or a pallet area. $arameters on the Warehouse ta* of the Organi/ation $arameters window control the cartoni/ation le"el and the cartoni/ation processes to use. The F@na*le Cartoni/ationF flag has three options% &. >ou can turn on cartoni/ation in which case pic! released lines are cartoni/ed regardless of the allocation su*in"entory. +. >ou can turn off cartoni/ation in which case no pic! released lines are cartoni/ed. -. >ou can configure cartoni/ation at the su*in"entory le"el. The system first chec!s the cartoni/ation flag on the su*in"entory definition *efore cartoni/ation. In addition there are two flags that independently control whether cartoni/ation is performed during sales order pic! release or manufacturing component pic! release. The cartoni/ation flag on the su*in"entory has only two options% ena*led or disa*led. This flag is used if you set the F@na*le Cartoni/ationF to FControlled at Su*in"entoryF on the Organi/ation $arameters window.
Container oad Relationships

Su*mitted *y <nonymous on Mon B+?+&?+B&& ' B&%&9 Tag%
Some items re4uire specific containers. These items ha"e container load relationships which are direct relationships *etween a container item and a contained item. The relationship specifies how many of the contained item can fit into one container. >ou set up container load relationships in the Container Item #elationship window. <lthough you can esta*lish multiple relationships for a single contained item the cartoni/ation process uses only the preferred relationship. There can *e only one preferred relationship for each content item. $rior to setting up these relationships the container items must *e properly setup. <ny container item setup using the steps a*o"e will is a "alid container item for a direct relationship. <lternati"ely to setup items =ust for direct container load relationships the only re4uired step is to chec! the container flag in the container o*=ect group. ,o other physical attri*utes of the contained item or container item need to *e entered.
Containers and Contained 1tems

Su*mitted *y <nonymous on Mon B+?+&?+B&& ' B&%B. Tag%
<fter you set up the appropriate category codes and category sets you must define the containers and cartons into which you will later pac! items. 5ecause containers represent another type of item you use the Master Items form to set them up. ,ote% >ou must define container items and contained item with the same unit of measure class. 2or e6ample if you ha"e an item defined in inches and a container defined in centimeters the system will ma!e the con"ersion from inches to centimeters (or centimeters to inches) *ecause *oth units of measure are of the 7OM class )ength
8efining Contained 1tem
<fter you set up appropriate category codes and category sets you must modify or update the attri*utes of the items for which you want the system to suggest containers. 2or cartoni/ation to wor! properly you must update the following item attri*utes%

ItemIs category set from the Contained Item category set $hysical dimensions of the item% weight "olume and dimension
,ote% Optionally you may specify a weight "olume and dimension and corresponding 7OMs for items in which you want the system to suggest cartoni/ation otherwise cartoni/ation will assume that the item has B weight "olume and dimension for the case of contents or infinite capacity in the case of containers.
8efine Cartoni?ation .roups

Su*mitted *y <nonymous on Mon B+?+&?+B&& ' BB%.0 Tag%
< fle6field structure called Cartoni/ation (roups is seeded with the system. Therefore to define cartoni/ation groups you need only to select the Cartoni/ation (roups fle6field structure and then set up a category code and description for each group. 56: Assign Cartoni?ation .roups to Cartoni?ation Category Sets <fter you set up the appropriate cartoni/ation groups (also !nown as category codes) you assign the groups to category sets. >ou must assign cartoni/ation groups to the following two category sets% &. Contained item which represents items that are pac!ed +. Container item which represents the actual container such as a *o6 or pallet into which items are pac!ed. 5oth the Contained Item and Container Item ha"e *een seeded with the Oracle Warehouse Management. >ou should assign each category code that you define to *oth the Contained Item and Container Item category sets.
Consolidation
Su*mitted *y <nonymous on Wed B-?BC?+B&& ' &-%.: Tag%
Consolidation is the process of *ringing material from "arious parts of the warehouse together for the purpose of pac!ing and shipping. Consolidation can occur at one or more points during the out*ound flow of material. Most warehouses perform consolidation of pic!ed material so it can *e pac!ed prior to shipment. Some warehouses perform su*se4uent consolidations such as *uilding pallets of pac!ed items and then shipping the pallets. Oracle Warehouse Management allows eight types of system'directed consolidation *ased on the following !ey factors% D Should material *e consolidated in a consolidation locator or directly in a staging laneY D Should consolidation occur at the )$, le"elY D Can material from different deli"eries *e consolidated *ased on the operation plan while upholding the consolidation rules such as no loose material is allowed in the outermost )$,Y 56 P0 /ased Consolidation in Staging ane Within 8elivery This is the default consolidation method. This consolidation method ena*les you to consolidate material for a single deli"ery directly to an )$, in a staging lane. The system suggests the last )$, that is dropped off for deli"ery in the staging lane. 76 8irect Consolidation in Staging ane Across 8eliveries This consolidation method ena*les you to consolidate material across deli"eries in a staging lane. In this consolidation method you do not consolidate material in a consolidation )$, within the staging lane. The system does not suggest a drop into )$, for the material. :6 8irect Consolidation in Staging ane Within 8eliveries This consolidation method ena*les you to consolidate material for a single deli"ery directly in a staging lane. The system does not suggest a drop into )$, for the material. ;6 P0 /ased Consolidation in Consolidation ocator Across 8eliveries in Staging ane This consolidation method ena*les you to consolidate material across deli"eries into a consolidation )$, in
a consolidation locator. <fter you consolidate the material you can use the mass mo"e functionality to mo"e all the material to the staging lane. <6 P0 /ased Consolidation in Consolidation ocator Within 8eliveries in Staging ane This consolidation method ena*les you to consolidate material within a deli"ery into a consolidation )$, in a consolidation locator. <fter you consolidate the material you can use the mass mo"e functionality to mo"e all the material to a staging lane. B6 P0 /ased Consolidation in Staging ane Across 8eliveries This consolidation method ena*les you to consolidate material across multiple deli"eries into a consolidation )$, directly in the staging lane. D6 ocator /ased Consolidation in Consolidation ocator Across 8eliveries in Staging ane This consolidation method ena*les you to consolidate material for each deli"ery in a separate consolidation locator and then consolidate material for multiple deli"eries in the same staging lane. E6 ocator /ased Consolidation in Consolidation ocator Within 8elivery in Staging ane This consolidation method ena*les you to consolidate material for a deli"ery in a consolidation locator and then mo"e the material to a staging lane.
Consolidation 1n$uiry
Su*mitted *y <nonymous on Wed B-?BC?+B&& ' &;%B: Tag%
Once material is consolidated it is ready for further processing such as pac!ing shipping or loading. It is essential that you !now the status of consolidated material so you can ma!e a decision on what material is eligi*le for further processing. Consolidation ocators 1n$uiry The Consolidation )ocators In4uiry page ser"es as the gateway to "iew consolidation locators with material in "arious states so that you can ma!e a determination on what material is ready for further processing. Complete ocators The Complete )ocators mo*ile page ena*les you to "iew consolidation locators that ha"e completely consolidated material. #mpty ocators The @mpty )ocators mo*ile page ena*les you to "iew empty consolidation locators. It displays su*in"entory and locators that are empty one locator at a time. The total num*er of empty locators displays at the *ottom of the page.
0on&#mpty ocators The ,on'@mpty )ocators mo*ile page ena*les you to "iew consolidation locators that ha"e at least one staged )$, in it. It includes locators with either completely or partially consolidated material or *oth. It displays su*in"entory and locators that ha"e at least one )$, with a status of Staged. It shows all locators that ha"e material in them regardless of whether material has *een completely consolidated or not. It also has a P2ind )$,sL *utton that in"o!es the Consolidated )$,s page and displays )$,s that e6ist in the displayed locator. Consolidated P0s 1n$uiry The Consolidated )$, In4uiry page ser"es as the gateway to "iew consolidated )$,s with deli"eries in "arious states so that you can ma!e a determination on what material is ready for further processing. The Consolidated )$, In4uiry can *e performed against any staged )$, deli"ery or order num*er or any com*ination of the three.
Consolidation Setup
Submitted by Anonymous on Wed, 03/09/2011 - 16:38 Tag:
Wa e!ouse "anagement /
When you perform a $ic! 3rop Staging Mo"e or )$, Mass Consolidate for material consolidated across deli"eries the following conditions apply% D <ll lines in the 2rom and To )$, if the material resides in an e6isting )$, must *e assigned to a
deli"ery. D The destination )$, must *e in a locator of type Staging. D The destination )$, must not ha"e any loose material. If )$,s are nested the nested )$,s can contain loose material. D <ll tas!s loaded into the 2rom )$, and To )$, must ha"e an operation plan with the consolidation method set to <cross 3eli"eries. Shipping Validation Transportation @6ecution "alidates material consolidated across deli"eries and determines if a "alid deconsolidation point e6ists and if the ship'from location are the same. <fter consolidation and at ship confirm Shipping @6ecution automatically creates a trip for the second leg from the deconsolidation point to the final ship'to destination as follows%
#$ no t i%s asso&iated to t!e de'i(e ies e)ist $o t!e se&ond 'eg, S!i%%ing *)e&ution & eates a t i% $o ea&! de'i(e y $ om t!e de&onso'idation %oint to t!e $ina' s!i%-to destination. #$ de'i(e ies $o t!e se&ond 'eg e)ist, S!i%%ing *)e&ution de'etes t!e de'i(e y $ om t!e asso&iated t i%, and & eates a ne+ t i% $ om t!e de&onso'idation %oint to t!e $ina' s!i%to destination.
a,el Printing
Su*mitted *y <nonymous on Sun B+?+B?+B&& ' B&%0. Tag%
WMS la*eling features helps you to mo"e in"entory more efficiently through the warehouse. Supplier la*eling speeds'up the recei"ing process *y ena*ling *ar code scanning of in*ound purchase orders that results in less receipt processing time immediate recognition of a"aila*le materials and higher recei"ing accuracy. )a*eling also ena*les you to comply with customer re4uirements for *arcoding. >ou can produce customer' specific la*els on demand for each shipment and for ad"anced shipment notices (<S,s). >ou can also use la*eling in flow manufacturing. @ach step in the manufacturing flow can use la*eling. Customer )a*eling #e4uirements Customer la*els are typically centered on the following ma=or re4uirements% &. +. -. .. )a*el format )a*el data 5ar code specifications Sym*ol content
Oracle Warehouse Management la*eling features ena*le all of these re4uirements to wor! together to meet customer guidelines. It supports the following la*el types%

Materials la*el% $ro"ides information a*out an item including the itemIs lot information if applica*le. Serial la*el% $ro"ides information that is specific to a serial of an item.
)$, la*el% $ro"ides information a*out the )icense $late ,um*er ()$,). This la*el does not contain content information. >ou typically use the )$, la*el to identify )$,s as they tra"el throughout the warehouse. )$, Contents la*el% $ro"ides information a*out the )$, contents. >ou typically use this la*el to identify )$,s as they tra"el throughout the warehouse. )$, Summary la*el% $ro"ides information a*out the )$, and a summary "iew of the )$, contents. If an )$, contains multiple )$,s then all of the contents of all the nested )$,s are summed *y item re"ision and lot. )ocation la*el% $ro"ides information a*out specific warehouse locators. Shipping la*el% $ro"ides information for an out*ound shipment. It does not include information a*out the contents of the shipment. It includes only addresses and information that is pertinent to the shipment itself. Shipping Contents la*el% $ro"ides information a*out out*ound shipment. It includes information a*out all of the contents that are part of the shipment. WI$ Content la*el% $ro"ides information a*out the WI$ components that are pic!ed for a WI$ =o*. It includes component num*er serial lot =o* num*er assem*ly num*er and start date.
#lectronic Product Code If you selected )$, )$, Contents or )$, Summary as the la*el type you can create @lectronic $roduct Code (@$C) information for the la*el. Some retailers re4uire @$C information from their supplier. Oracle Warehouse Management models @$Cs after )$,s. >ou can generate @$Cs while )$,s are completed pac!ed or staged.
a,el Printing Strategies

Su*mitted *y <nonymous on Sun B+?+B?+B&& ' &+%+: Tag%
Oracle WMS and MSC< ha"e ro*ust la*el printing capa*ilities *uilt into the product to easily produce compliance la*els at any point in the *usiness process and with any data. Oracle wor!s with two types of la*el printing partners K direct to' printer and print ser"er K to pro"ide the full end'to'end solution and each of these partners ha"e different strengths. Oracle WMS produces la*el QM) files as part of a transaction or e"ent such as a purchase order receipt pic! confirmation wor! order completion or license plate generation. To print the Oracle generated la*el QM) you will always need the actual la*el printers as well as a la*el design application ()3<) to define the graphical layout of the "aria*le and *oilerplate data. These strategies differ howe"er on the *asis of the integration of the QM) to that format occurs within the printer firmware with no other middleware or in a separate print ser"er application. 8irect&to&print la,el printers that nati"ely understand Oracles QM) allow you to directly print the Oracle generated la*el QM) without any middleware or print ser"er. The print ser"ers on other hand add an intermediary layer *etween Oracle <pplications and actual la*el printer. <lthough the print servers introduce an additional partner and added implementation cost they also pro"ides significant "alue in the areas of print management la*el configuration and manipulation error management and Internet printing. Oracle supports two types of la*el printing configurations% &. $rinting using a third party la*el software and a print ser"er +. $rinting using QM) ena*led 3irect )a*el $rinters. The printing strategy selection depends on se"eral factors K #OI real time latency need for compliance la*eling printer models in current use "olume of la*els to *e printed networ! infrastructure et al. To reiterate each additional layer *etween Oracle WMS and the printer gi"es you additional fle6i*ility while also generally also meaning additional comple6ity and cost. PR10" S#RV#R S+ 9"1+0S
This strategy re4uire s you to ha"e a configuration of Oracle WMS third party la*el printing software print ser"er and a networ! of printers. The )3< allows you to define the different la*el formats that need to *e printed as well as manage the li*rary of formats for an enterprise printing solution. The print ser"er manages the print 4ueue comes with necessary printer dri"ers and the printer parameters associated with them. 2inally the la*el printer actually prints the la*el. The la*el printer can *e from any "endor supported *y the print ser"er. Typically the )3< and print ser"er come same the "endor. This strategy is recommended when you ha"e a high "olume of la*els to print from each printer and also is often simpler to maintain when the la*el formats change fre4uently. The )3< or related application sometimes ena*les you to configure the la*el with the content *eing deri"ed from many sources where the Oracle QM) forms =ust one such source. < print ser"er partner is usually recommended when the Oracle QM) needs to *e manipulated *eyond the capa*ilities of standard Oracle functionality prior to printing such as to pull in additional data elements split an indi"idual la*el re4uest into multiple la*els or control the destination printer *eyond Oracles *asic rules. Many of the third party la*el software will allow you to custom program a la*el in these K and other K ways. Third party la*el print software will use Oracle QM) as the primary data sources for the la*el fields e6ecuting additional logic or O35C calls as re4uired. <nother use of these e6tended capa*ilities from the print ser"er partners is to compensate for the fact that Oracle MSC< lac!s an in*uilt rules engine li!e Oracle WMS to determine the la*el to *e printed. Eowe"er some la*el printing software help you to configure rules to determine the la*el to *e printed and manipulation of the la*el. This strategy is also recommended when you ha"e printers from multiple manufacturers in a single site that all need to print a single format as only some of the printers in your facility may *e a*le to support QM) directly and furthermore each of the 3irect'to'$rinter partners uses different )3<s that produce different pre'compiled output that may need to *e loaded to the printers in different ways and using different tools. <dditionally the ad"anced 4ueuing ? print =o* management capa*ilities ma!e this a preferred option when more than two or three users need to concurrently print large *atches of la*els from a single printer. While the print ser"er partners may re4uire an additional in"estment in software licenses and implementation costs when you ha"e characteristics such as those a*o"e that re4uire the features of these partners your total cost of ownership will actually *e lower than trying to use the simpler architecture of the 3irect'to'QM) printers $rint ser"er sloution wor!s with all the three printing modes % Synchronous TC$?I$ Synchronous (eneric 1 <synchronous. FM 81R#C" PR10"#R In this strategy Oracle WMS sends the QM) directly to the printer. The la*el printer is capa*le of recei"ing QM) that meets Oracles la*el specification and merges with pre'defined la*el formats to print a la*el. This strategy can *e easily deployed when the Oracle QM) does not need any manipulation to produce the la*el desired. The "olume of printing and the num*er of users that would need to print concurrently to a single printer is also a factor. 2or instance when more than three or four users may trigger simultaneous re4uests to print to a single printer the num*er of a"aila*le connections on some of the printers may *e e6ceeded or for large =o*s the *uffers may o"erflow. While Oracle pro"ides multiple mechanisms for reprinting so that the =o*s are not lost these "olume and concurrency considerations should *e included in e"aluating the QM) 3irect printers against each other and against a print ser"er partner. With some QM) 3irect partners QM)'ena*led printers are only supported on their flagship printer models so that you may pay a premium for this capa*ility. On the other hand all QM) 3irect printers to date are capa*le of running *oth modes where*y they can parse *oth QM) from Oracle and the print stream in their
proprietary language typically without any change in configuration and typically also simultaneously so the same printer can *e used in multiple ways and you can easily change to a print ser"er as your re4uirements grow. The QM) 3irect strategy calls for pre'loading the printers with la*el formats. Since there is no centrali/ed print ser"er e"ery time you add a printer to the networ! you need to load the re4uired la*el formats and e"ery time you add a format you need to add it to all the printers. Some partners ha"e printer management software to aid in this decentrali/ed approach. QM) direct printers wor! with *oth Synchronous TC$?I$ and Synchronous (eneric mode of printing. To ena*le to print in TC$?I$ mode you need to set RWMS )a*el $rint Mode to RSynchronous K TC$?I$ and define the TC$?I$ I$ address and port num*er for each printer in the networ!.
a,el Setups
Su*mitted *y <nonymous on Sun B+?+B?+B&& ' B-%B-
)a*el setup consists of defining )a*el 2ormats )a*el Sets and Custom )a*el 2ields against the different in*uilt la*el types. ,e6t you need to complete la*el format assignment rules 1 associating )a*el Types to 5usiness 2lows. 5efore you can specify la*el generation points and construct la*el format rules you must define printer and assign printer I$s if re4uired for synchronous direct QM) printing. 8efining a,el *ormats and Sets When you define la*el formats and sets you are setting up the data fields to include on a particular la*el. >ou can use system'seeded fields or create custom fields to include on a la*el. When you create a la*el set you can associate multiple la*el formats of the same la*el type together. When you select the la*el set for printing then the system prints all of the formats within the la*el set. >ou can create la*el sets for the following la*el types% )$, )$, content material and serial.
To define la*el formats 1 set na"igate to the 3efine )a*el 2ormats and Sets window.
5656 In the )a*el Type field use the list of "alues to select the la*el type for which you want to define la*el formats. &.+. Select the entity type. If you select format you can create a la*el format. If you select Set then you can create a la*el set. 765. In the )a*el 2ormats region ,ame field enter a name for the la*el. This name should *e the name that is recogni/ed *y the third'party printing software. +.+. @nter an optional description to descri*e the la*el format. +.- In the 3isa*le 3ate field enter an optional date on which this la*el format can no longer *e used. +... Select the 3efault )a*el chec! *o6 to identify that this la*el format will *e used as the default la*el type if the system cannot find a rule that determines the la*el format. ,ote% >ou can specify only one la*el format as the default la*el. and you must disa*le printer assignments for la*el formats *efore you can delete indi"idual la*el formats.
:6 Clic! )a*el 2ields to open the 3efine )a*el 2ield Aaria*les window or clic! 3efine Sets to define sets to open the )a*el Sets window. -.& In the )a*el 2ields region 2ield ,ame field use the list of "alues to select the data element that represents the field on the la*el. The la*el type that you selected in the 3efine )a*el 2ormats window determines the list of "alues for this field. ,ote% Custom la*el fields that you created also appear in this list. < "alue of >es in the Custom SG) column indicates the field is a custom SG) field. -.+ In the 2ield Aaria*le ,ame field enter a uni4ue te6t string that will *e used as a "aria*le to represent the data field on the la*el format. @nter an optional description for the field "aria*le name. This field "aria*le name is used in la*el design application ()3<). ,ote% 2irst you create a la*el format in oracle WMS. <fter that you need to design the la*el in any )3< with the field "aria*le name defined in WMS. In case of direct QM) la*el printers you need to upload the la*el file to the printer so that it can map all the fields that come from oracle WMS. ;6 Adding a,el *ormats to a Set To add la*el formats to a set you select from pre"iously defined la*el formats. When you print the la*el set the system prints all of the la*els assigned to the set. >ou can add a la*el format to a set more than once. If
you do so the la*el prints more than once.
3efining Custom )a*el 2ields <ssociating )a*el Types to 5usiness 2lows )a*el 2ormat <ssignment #ules
8efining Custom a,el *ields

Su*mitted *y <nonymous on Sun B+?+B?+B&& ' B-%&C Tag%
>ou can create custom la*el fields and associate them with la*el formats. This ena*les you to ha"e additional control o"er the "alues that are listed on a la*el. >ou can write a custom SG) statement to create the custom la*el field. 2or e6ample if you ha"e a re4uirement to show the carrier $#O num*er and the system does not seed this field then you can write a custom SG) statement that creates this field. The custom la*el field that you create appears in the 3efine )a*el 2ields window along with the seeded "alues. >ou should restrict this window from certain responsi*ilitiesH only users with !nowledge of SG) should ha"e access to this window. >ou can use any field that you create on this window in a la*el. To define custom la*el fields% &. ,a"igate to the 3efine Custom )a*els window. +. Select the la*el type. This associates the fields with the appropriate la*el type. -. @nter the field name description and SG) 4uery statement. .. Sa"e your wor!.
Associating a,el "ypes to /usiness *lows

Submitted by Anonymous on Sun, 02/20/2011 - 03:38 Tag:
Wa e!ouse "anagement
<fter you set up la*el formats you must associate them with the specific warehouse *usiness flow where you want to use them. This association ena*les the la*el type to *e printed automatically as part of that *usiness flow. >ou can also print the same la*el type from different *usiness flows with a different format used at each flow. 2or e6ample many times a pac!age is la*eled with a carton la*el when it is pic!ed (Shipping Contents la*el type at $ic! )oad *usiness flow) *ut is then la*eled with a shipping la*el when it is shipped (Shipping Contents la*el type at Ship Confirm 5usiness flow.) This ena*les you to set up a la*el format selection rule that is *ased on the *usiness flow that the la*el print re4uest was generated from. The following ta*le pro"ides a list of the "arious *usiness flows and the types of la*els that you can associate with each flow. The hori/ontal header row of the ta*le lists the "arious la*el types that are a"aila*le. The far left "ertical column lists the warehouse'related *usiness flow. The num*er in parentheses ( ) indicates the *usiness flow code num*er that is needed when you are defining #ules @ngine format *ased rules. >es indicates that the system can generate the la*el type for that *usiness flow. ,o means that the system does not generate that la*el type for the *usiness flow.
, -e$ining .ustom /abe' 0ie'ds u% /abe' 0o mat Assignment 1u'es 2
Comments
a,el *ormat Assignment Rules

Submitted by Anonymous on Sun, 02/20/2011 - 04:19 Tag:
Wa e!ouse "anagement /
)a*el format assignment rules associate a la*el to a *usiness o*=ect *ased on parameters and restrictions you specify. <fter you define la*el formats and associate them to the appropriate *usiness flows you can define la*el format assignment rules. The figure in the slide pro"ides an e6ample of the type of rule you could create to generate an )$, Content la*el for ha/ardous items. If the material meets all of the restrictions when the rules engine e6ecutes the rule then Warehouse Management generates the ha/ardous item )$, Contents la*el. Creating la*el format rules is an optional step. Some implementations re4uire only a single la*el format for each la*el type. In this case the Warehouse Management uses the default la*el format for each type. It also uses the default if there are no applica*le rules. If the implementation re4uires more than one la*el format for a la*el type you must create la*el format rules.
, Asso&iating /abe' Ty%es to 3usiness 0'o+s u% -e$ining and Assigning 4 inte s 2
Comments
8efining and Assigning Printers

Su*mitted *y <nonymous on Sun B+?+B?+B&& ' B.%.0
>ou must define printers and assign them to the appropriate la*el types *efore you can print la*els. >ou define printers in the System <dministrator responsi*ility and assign printers in the Choose 3ocument and )a*el $rinters window. 8efining Printers System <dministrator (,) Install L $rinter L #egister
Assign Printers to documents (,) Setup L Warehouse Configuration L $rinters 1 3e"ices L <ssign $rinters to documents
>ou can assign shipping documents and selected reports to specific printers for multiple le"els. The le"els are% 7ser #esponsi*ility <pplication Site 8one?Su*in"entory 2ormat and Organi/ation
Oracle Shipping will loo! for a printer at the 7ser le"el first. If one e6ists then it is selected if one does not e6ist at the 7ser le"el then the system will loo! for a printer at the #esponsi*ility le"el. This pattern will continue until a printer is found at one of the le"els. If more than one printer is setup at a le"el then you must use the 3efault chec! *o6 to specify the preferred printer at that le"el. >ou should only ha"e one default printer at each le"el. If the document to *e printed is a $ic! Slip report the system will loo! at the Su*in"entory le"el first. If a printer e6ists at the Su*in"entory le"el then it will select that printer *ut if a printer does not e6ist then the system will loo! at the Organi/ation le"el and then through the rest of the le"els. 2or e6ample you can assign pic! slips and pac! slips to your warehouse tractor feed printer your mailing la*els to a tractor feed printer stoc!ed with *lan! la*els and other documents to a laser printer in your order entry office. The window consists of a 3ocument and a $rinter ta*% the 3ocuments ta* displays all the documents assigned to a printer while the $rinters ta* displays all printers assigned to a document. If a user or responsi*ility is not specified Shipping @6ecution uses the printer assigned to the application. ,ote% The document can *e anything a normal report li!e pic! slip or a la*el type li!e )$, or )$, content.
Printing Modes
Su*mitted *y <nonymous on Sun B+?+B?+B&& ' &&%0C Tag%
Oracle WMS pro"ides - different ways to integrate third party printing software with WMS. &. <synchronous mode +. Synchronous Mode ' (eneric
-. Synchronous Mode K TC$?I$ The profile option WMS% )a*el $rint Mode determines the printing mode. Asynchronous Mode In <synchronous Mode Warehouse Management creates an @6tensi*le Mar!up )anguage (QM)) file and transfers it to a directory the third party software monitors. >ou cannot use Warehouse Management to monitor the status of the print re4uest after creation of the QM) file. ,ote% The profile option WMS% )a*el output directory determines the output directory. <synchronous mode of architecture is simplest to set up and de*ug as there is a clear e6ternal record of the la*el re4uest. 3isad"antages of asynchronous printing include latency possi*le security issues to 2T$ files across ser"ers if print ser"er running on different platform and no possi*ility for response. &. Oracle WMS places the QM) file in a specified 3irectory. +. $rint Ser"er ? Other tool monitors the specified directory and pic!s up the QM). -. $rint ser"er ? Other tool modifies the QM). .. $rint ser"er maps the QM) to the la*el format and generates print stream in printers proprietary language. 0. $rinter prints the la*el Synchronous Mode A .eneric
In Synchronous mode of integration Oracle WMS generates a la*el QM) and sends it directly to the partner "ia one of two synchronous methods. In the first method the integration is "ia an <$I implemented *y the third party application that replaces an empty stu* pro"ided *y Oracle. Third party software processes this QM) and prints the QM). >ou need to set the profiles ' RWMS )a*el $rint Mode to RSynchronous K (eneric. &. Oracle WMS calls Synchronous <$I and pushes the QM) to print ser"er ? other tool. +. $rint ser"er ? Other tool modifies the QM). -. $rint ser"er maps the QM) to the la*el format and generates print stream in printers proprietary language. .. $rint Ser"er prints the la*el at the specified printer. Synchronous Mode "CP@1P
Synchronous Mode TC$?I$ is a real'time integration mode *etween Warehouse Management and third party software that is handled through a standard ethernet TC$?I$ connection. Warehouse Management ensures the printer or print ser"er is listening to the I$ and port and successfully recei"es the QM) string *ut does not recei"e the status the detailed status of the print re4uest.

Warehouse Management

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Warehouse Management

Încărcat de

Drepturi de autor:

Formate disponibile

Warehouse Management

Comparison of the modules

-.&. Cost (roup -.+ )a*el $rinting 1 #2I3

Warehouse Management Setup

"ask Setup Steps

WMS &' Set up &' Resources &' #$uipment

WMS Rules #ngine

The #ules Wor!*ench is comprised of two regions%

$ic!ing $utaway Cost group $lanned crossdoc! Opportunistic crossdoc!

#ules Wor!*ench Matri6

icense Plate 0um,ers 3 P0s4

.enerating icense Plate 0um,ers

>ou can generate )$,s using one of the following methods%

9sing a Mo,ile 8evice to .enerate P0s

1nventory "ransactions with P0s

ot and Serial Attri,utes

Set up +peration Plans

+ut,ound operation plans

Setup "ask *ilters

D Wor! Orders D Cycle Counting 9.Sa"e your wor!.

ask 8ispatch and Assignment

Warehouse Control /oard

WMS 1n,ound *eatures

Assign strategy to item

Receiving +ptions 3Mo,ile % 8esktop4

@6pense items 3irect receipts

Standard Receipt *low

P0 Put Away Process

9. @nter 3emand Sources

Planned Crossdocking Setup

Ma6imi/e Crossdoc! (2I2O) Minimi/e Wait ()I2O)

76 Crossdock criteria assignment

+pportunistic Crossdock #(ample

Plan Cross8ocking #(ample

Ma6imi/e Crossdoc! (2I2O) Minimi/e Wait ()I2O) Custom

76 Crossdock criteria assignment

S+ to Pick Confirm & Complete Process

&. Create a sales order

7se an )$, controlled su* in"entory as pic! from su* in"entory.

Aerify the tas! status

ask oading and 8ropping

Cartoni?ation> Consolidation and Packing

setup in the item?container relationship window.

Single evel Cartoni?ation

Multi evel Cartoni?ation

Container oad Relationships

Containers and Contained 1tems

8efining Contained 1tem

8efine Cartoni?ation .roups

a,el Printing Strategies

you do so the la*el prints more than once.

8efining Custom a,el *ields

Associating a,el "ypes to /usiness *lows

, -e$ining .ustom /abe' 0ie'ds u% /abe' 0o mat Assignment 1u'es 2

a,el *ormat Assignment Rules

, Asso&iating /abe' Ty%es to 3usiness 0'o+s u% -e$ining and Assigning 4 inte s 2

8efining and Assigning Printers

S-ar putea să vă placă și