Page 1 of 7

Oracle WMS Personalization Framework [ID 469339.1]

Modified 29-NOV-2010 Type WHITE PAPER Status PUBLISHED

In this Document
Abstract
INTRODUCTION
Document History
Oracle WMS Personalization Framework
ARCHITECTURE
PERSONALIZATION FEATURES
PERSONALIZATION RESTRICTIONS
PROFILE OPTIONS USED BY MWA PERSONALIZATION FRAMEWORK

Applies to:

Oracle Warehouse Management - Version: 11.5.10.0 and later [Release: 11.5.10 and later ]
Information in this document applies to any platform.

Abstract

INTRODUCTION

Oracle Warehouse Management System is a real-time execution system that enables a majority of the transactions to be executed on the mobile devices and captures the related information.
While the product is growing feature rich by the release, the variety of its expanding customer base is increasing rapidly too. The number of customers that are interested in and demanding to
tailor the execution of these mobile transactions to their custom business processes and procedures is increasing.
The following are some of the variety of reasons why the user wants to customize the mobile pages at their facility.

· The management is confident that their mobile operators are well qualified and can be relied upon, hence would like to reduce the amount of information that needs to be verified and
confirmed through the mobile devices. This will reduce the number of scans and hence improve the speed and overall efficiency at which the mobile transactions can be executed.

· Default some of the fields based on the various business rules that are used at their facility and do not need the operators to input.

· Capture additional information to meet the requirements of the business processes and procedures using the LPN Descriptive flex field.

The project will eliminate the need to customize the WMS mobile UI pages and reduce the implementation time for the growing WMS customer base. Patch 6662606 provides the capability of
personalizing Oracle Warehouse Management pages.

Document History

Authors : Bhanu Vanjaku and Puneet Sood

Create Date: 30-NOV-2007

Oracle WMS Personalization Framework

ARCHITECTURE

The following diagram represents the architecture of MWA Personalization Framework.

Customers can use the MWA Personalization Framework menu option, which is available under the existing Warehouse Manager responsibility’s Setup menu option, to personalize the WMS
Mobile pages
Personalization can be done at three different levels. The levels in order of decreasing precedence are:

1. Responsibility
2. Organization
3. Function

PERSONALIZATION FEATURES

Customers can now achieve the following without making any code changes:

· Hide fields and buttons.

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=469339.1 18-Mar-11
 Page 2 of 7

· Change the prompts for the fields and buttons.

· Provide default values to the fields.

a. If there is no default value provided using personalization framework then system tries to get the default value from a custom java class as explained in appendix A.

· Copy the value of a field to the another field.

· Set editable fields as read-only.

· Set non-mandatory fields as mandatory.

· Enable/Disable the LPN Descriptive Flex Field. DFF can also be made as a read-only field

PERSONALIZATION RESTRICTIONS

Any given field on a page can be hidden provided any one of the following is true.

1. The field is not a required field.

2. The field is required but a valid default value is set through this personalization framework.

3. The field is a display only field.

An editable field can be made read-only when any one the following is true.

1. The field is not a required field.

2. The field is required but a valid default value is set through the personalization framework.

PROFILE OPTIONS USED BY MWA PERSONALIZATION FRAMEWORK

MWA: Enable Personalization

You should set this profile option to “Yes” for personalization to take effect. This profile option can be set at site, application, responsibility and user level.

MWA: Cache Personalized Metadata

This profile option should be set to “Yes” at site level on a production instance for faster performance. This profile option is specifically created for Personalization Administrator to quickly
review the personalization changes without having to bounce the mobile server by setting it to “No” at user level.

Personalization is supported for the following pages:

1. Pick Load Page

Pick Load Page can be accessed using accept any tasks menu (Mobile WMS Tasks Interleave Accept Function) or by using paper based picking menu (Mobile WMS Manual Picking
Function). Personalization done at the function Mobile WMS Manual Picking will be picked up irrespective of the current function if the current page is Pick Load Page.

2. Pick Drop Page

Pick Drop Page can be accessed using the Drop Loaded LPNs menu (Mobile WMS Drop Loaded LPNs Function).

3. Manual Load Page

Manual Load Page can be accessed using the menu Manual Load available under manual tasks (Mobile WMS Inbound Manual Load Function).

4. Item Load Page (Manual Load – Select Contents Page)

User can navigate to item load page if ‘Select Contents’ button is clicked on manual load page.

5. Move Any LPN page

6. Drop Page (Move Any LPN – Select Items page)

If the form function parameter SUGGESTION is set to LINES for the function Mobile WMS Move Any LPN then user will be able to navigate to Putaway Drop Page.

7. Update LPN Page

8. Mobile PO Receipt page

9. Mobile PO Receipt Information Page

User can navigate to PO Receipt Information page if Done button is clicked on PO Receipt page.

10. LPN Ship Page

11. Mobile Ship Confirm Page

User can navigate to mobile ship confirm page if ‘continue/ship’ button is clicked on LPN Ship page

PERSONALIZING MOBILE PAGES

Steps for Personalizing a Mobile Page

Step 1: Navigate to the self-service Warehouse Manager responsibility and choose MWA Personalization framework option under the Setup sub-menu. This option is also available in the
MWA Server Manager responsibility. This menu option takes the user to the Personalization Home page

Step 2: The List of values for the “Mobile page” field displays the function name and the mobile pages, which can be personalized. Select a page and click the “Personalize” button.

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=469339.1 18-Mar-11
 Page 3 of 7

Step 3: All the current fields and buttons for the page are displayed. Choose a field from the “Fields list” table and click the “Edit” icon to personalize the field.

Step 4: A new page is displayed which lists all the properties of the field that can be personalized. Make the required personalization and hit the “Apply” button to save your personalization for
the selected field. Repeat this step for all the fields you would like to personalize on this page.

Step 5: Navigate to the mobile page and review your personalization done for the page. Note: If the profile option “MWA: Cache Personalized Metadata” is set to “Yes” then, the personalization
made will come into effect only after bouncing the mobile server.

Default Update LPN Page Personalized Update LPN Page

The Personalized Update LPN Page displays the page name as “* Update LPN (W1)” The “ * ” indicates that the page involved has been personalized.

The above picture shows the before and after view of the “Update LPN” page with the following personalization:

· LPN field’s prompt changed to “Custom LPN”.

· Default value is set to weight field and is made read-only.

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=469339.1 18-Mar-11
 Page 4 of 7

· LPN Attributes LPN DFF is enabled/rendered for the LPN field.

· Content Vol. field is made hidden.

· Container field is made mandatory/required.

· Update LPN button’s prompt is changed to Custom Update.

Activate/Deactivate Personalization

Personalization created for a page can be Activated/Deactivate from the activate/deactivate personalization page.

Enabling Descriptive Flex Fields for a Mobile Page

A new Descriptive Flexfield (DFF) has been seeded for the WMS License Plate Number Table. Oracle has seeded the DFF on all the pages being enabled for personalization. The users
to enable the DFF for the pages they want to have the DFF displayed.

Update Allowed: When un-checked and at least one of the attribute columns have data, all the DFF Attributes will be rendered as read-only. If not, the user will be allowed to enter/update the
DFF attribute fields

Headers: Optionally choose one or more fields, from the page, to be displayed as headers on the DFF window. Header fields are ignored if they are not visible on the page at the time the DFF
window is invoked (Control-F) by the user. This header field definitions are ignored when the DFF attribute fields are displayed inline with the page.

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=469339.1 18-Mar-11
 Page 5 of 7

LPN DFF enabled on Update LPN page with’ Display After’ set to LPN.

The LPN DFF is enabled on the Update LPN page with ‘Display Inline’ set to False. The DFF window is invoked using (Control-F).

LPN DFF enabled on the Update LPN page with Display Inline set to True.

APPENDIX A: Providing default value from a custom class

If there is no default value provided through the MWA Personalization framework as shown in the following screenshot then the system will try to get the value from a custom class
FieldDefaultValueHandlerImpl.class that contains user defined logic.

Please make sure that this class is compiled with Oracle apps.zip in the classpath.

After compilation, make sure that a file FieldDefaultValueHandlerImpl.class is created. Please move this file to $CUSTOM_DIRECTORY/xxx/custom and add $CUSTOM_DIRECTORY to the
classpath of your mobile server. $CUSTOM_DIRECTORY, can be any directory on the file system.

// FieldDefaultValueHandlerImpl.java

package xxx.custom;

import oracle.apps.mwa.beans.FieldBean;

import oracle.apps.mwa.beans.PageBean;

import oracle.apps.mwa.container.Session;

import oracle.apps.mwa.presentation.telnet.personalization.*;

import oracle.apps.mwa.presentation.telnet.personalization.FieldDefaultValueHandler;

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=469339.1 18-Mar-11
 Page 6 of 7

// FieldDefaultValueHandlerImpl should extend the abstract class FieldDefaultValueHandler

public class FieldDefaultValueHandlerImpl extends FieldDefaultValueHandler

public FieldDefaultValueHandlerImpl()

public static String getCustomDefaultValue(Session session, PageBean pageBean, FieldBean fieldBean)

// User has access to the current session, current page and current field bean. Please refer to WMS/INV/MWA

// javadocs for getting more details on how to customize using the provided methods. User can place the needed custom

// logic in this method

String val;

if (fieldBean.getName().equals("LPN") &&

pageBean.getName().equals("oracle.apps.wms.pup.server.UpdateLPNPage"))

val = "Custom Default Value";

return val;

return null;

APPENDIX B: Scope Of Mobile Personalization Feature

APPENDIX C: Recommended Support/Bug Logging Process For Mobile Personalization Feature

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=469339.1 18-Mar-11
 Page 7 of 7

Copyright © 2008 Oracle. All rights reserved. Oracle is a registered trademark of Oracle. Various product and service names referenced herein may be trademarks of Oracle. All
other product and service names mentioned may be trademarks of their respective owners.

Disclaimer: This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle does not warrant that this document is
error-free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. Oracle specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by
this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the prior written permission
of Oracle.

Attachments

469339.1_1 (111.86 KB)

469339.1_2 (75.54 KB)
Activare Deactivate Personalization (14.56 KB)
CopyFrom (5.1 KB)
Headers (4.5 KB)
Icon (387 B)
Maintain DFF (15.05 KB)
Page Fields (22.45 KB)
Personalization Context (38.15 KB)
Personalization Home (5.94 KB)
Personalization LOVFieldBean LPN (27.35 KB)
Personalize DescriptiveFlexFieldBean LPNDFF (30.45 KB)
UpdateLPN2 (5.18 KB)
UpdateLPN (6.04 KB)
UpdateLPN Mobile GUI (18.7 KB)
WMS License Plate Numbers (4.82 KB)
architecture (42.33 KB)

Related

Products

Oracle E-Business Suite > Logistics > Logistics > Oracle Warehouse Management

Keywords

PERSONALIZE; CLASSPATH; PERSONALIZATION

Back to top

Rate this document

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=469339.1 18-Mar-11