Major differences in WMS and non WMS enabled organization

• To transact a move order in WMS enable inventory org we can transact only via hand held devices having MSCA application or we can transact via desktop simulator of MSCA application.The reason is quite simple. When org is WMS enabled we will not find the "Transact" button on "transact move order" Form.

• Rule based picking and dropping (put away) is not possible without WMS.

• Selective lable printing could be made possible only with the help of rules of WMS.

WMS Custom Hook

wms_re_custom_pub

WMS Rule used in picking?

select Transaction_temp_id,Put_away_rule_id,pick_strategy_id,pick_rule_id,move_order_line_id,organization_id,subinventory_code,Locator_id from apps.mtl_material_transactions_temp;

and Rule name:

select * from apps.wms_rules where rule_id = RULE_ID_OF_ABOVE_QUERY

and Stratigy Name:

select * from apps.wms_strategies where strategy_id = STRATEGI_ID_OF_ABOVE_QUERY

Cycle Count : Reinitialize versus Update

----------------------------
Do not reinitialize everyday as this is the incorrect usage of the application. Re-initialize deletes all and re-loads. Update will update the items. Re-initialize is not the way to add new items, end users should be using update instead. Everytime re-(initialization) is run on the cycle count, all historical counts are erased and the system assumes it has the total number of counts to perform. This could cause an increase of items selected for count on any given day.

Auto-scheduling for cycle count logic

Auto-scheduling for cycle count logic works like this:
Within a given class - the system first tries to find out how many items needs to be scheduled for count. (Cycle count Scheduler) Formula to compute the number of items to schedule within a given class is as follows:

Max items to schedule = [(Total items in class * Nworkdays) / (ClasscountInterval) ] + 1
where ClasscountInterval = Number of working days in a year / (Number of counts / year for that class).

Next when you auto-generate cycle count requests based upon the number of items to be scheduled within a given class - the program tries to find the item with the lowest schedule order within that class. (see the respective table &  MTL_CYCLE_COUNT_ITEMS ). Suppose there are two items so the program will pick the items with the lowest schedule order ( in a series of 1,2,3,4,5 the system will schedule items with schedule order 1 and 2).

Once the counting is done - it will update the schedule order to 6 , 7 respectively. So next time you count - the system does not schedule the same items but picks up items with lowest schedule number again within that class (in the second case the series available is 3,4,5,6,7 so it will pick items with schedule order 3,4).

Best Note : 416149.1