Many of you have been looking forward to Mobile Personalization feature that we demoed at various user events and most notably at Oracle Open World. I am excited to note that this feature is now available for download on Metalink. This is great news for anyone who wishes to modify WMS mobile transaction pages without pounding any Java code.
This feature is currently available for most commonly used mobile transactions e.g. Receipt, Putaway Load, Putaway Drop, Pick Load, Pick Drop and ship confirm. Here is a quick rundown of what you can do with this feature:
Change field and button prompts: Field and button prompts can be modified using a simple setup.
Default value to a field: The value can be either a fixed value or copied from another field. You can also default a field value based on your own logic.
Capture additional attributes (DFF) for LPN: Additional LPN attributes can be entered or viewed using this feature.
Hide a field or button: Buttons that are not needed for your business can be hidden completely.
Make a field read only: You can make certain fields read only to make transactions more accurate and efficient e.g. UOM field if you only have one UOM for transactions.
Make a field mandatory: You can make certain fields mandatory for superior control e.g. LPN field for Receipt Transactions with Direct Receipt routing.
The following screenshot displays a "Before" and "After" comparison of a personalized mobile page.
Comments (2)
Hi,
Could someone help me find the answer to the following question, or point me in the right direction?
Does anyone know if the MTL Transaction Reason Workflow can be setup to classify the new tasks (from N-Step) as a different task other than a replenishment move order task? And if that task (from N-Step) could be started by any users by simply scanning or performing a 'Load' on the LPN?
**********DETAIL INFORMATION***********
We are using Oralce WMS mobile application that is setup for standard Oracle Multi Step Put Away, where the user can choose to drop an LPN/Skid into a temporary staging locator (different from system directed loc.) by selecting reason option N-step putaway.
Once the user select the N-Step Put Away override option, a workflow (MTL Transaction Reason workflow) creates a replenishment move order task for the LPN that will allow another user to complete the task. However the new task then has the same restrictions as replenishment move order tasks, which is a problem for us.
We would like for any user to be able to continue the task by simply scanning or performing a 'Load' on the LPN again without having to follow the sequential order of the replenishment move order tasks.
Thanks!
Posted by Montez | July 17, 2008 10:52 AM
Posted on July 17, 2008 10:52
hi Montez, can you please share u r solution on N-step putaway. Thank you
Posted by lokesh | May 4, 2009 3:25 PM
Posted on May 4, 2009 15:25