Oracle Mobile Field Service Implementation Guide

Implementing and Synchronizing Oracle Mobile Field Service Store and Forward Multiple Platform Support

This document contains details regarding implementing and using Mobile Field Service (MFS) Multiple Platform application. The application is available currently on iOS and Android platforms.

In addition to Implementation notes, this document provides an overview of getting started with installing the application on an iPhone and synchronizing with the enterprise server.

Implementation Process

The implementation process broadly involves the following steps:

1. Setting Profile Options for Mobile Field Service

2. Scheduling Concurrent Programs for Mobile Field Service

3. Creating a Mobile Field Service User

Setting Profile Options for Mobile Field Service

The following new profiles are applicable specifically for MFS Multiple Platform.

Profile OptionDescriptionAccess Level Default/ Recommended Values

CSF: Default Labor Debrief Date/Time

This profile is used to enable logic for automatically displaying information for Travel and Labor debrief. Accepted values are as follows:

Status Change: Automatic logic is implemented for displaying labor start and end date.

Scheduled Date: The labor start and end date is taken from the scheduled date.

System: The system date is used as the labor start and end date.

None: User must manually enter the labor start and end dates.

CSF: Google Map Client IDThis profile option is used to access Google Maps on your device. The Google Map Client ID must be downloaded on the client using this profile. Users must purchase Google license to get this ID. If the profile is set to the correct Google Map Client ID, this profile value is downloaded to the client device and the technician has unlimited access to Google Maps. If you do not purchase the Google license, you will have restricted access to Google Maps.ID = Alphanumeric; Recommended

No = Restricted Access

CSM: Default Task Status for Synchronous Update

This profile determines the task assignment status to be used for immediate update to server via mobile query framework. When the technician changes the status, for example, Accepted, a remote query is fired and task status at server side is updated. The profile values are as follows:

Task Assignment Status: Remote update is fired when the technician changes to this task assignment status.

Null: Remote query is not fired and the status updates are uploaded through regular sync process.

CSM: Enable Multiple PlatformThe profile enables, both Oracle Lite and multiple platform users to exist in the same instance. This enables implementers who want to upgrade existing MFS users to Multiple Platform users to do so in a phased mannerSite, Responsibility and UserNULL : Default

Yes : Recommended

Note: This profile must be set to Yes at the site level when not using Oracle Lite. A value must be specified at the responsibility and the user levels if Oracle Lite is also implemented.

CSM: Maximum Number of ItemsThe profile controls the number of items to be downloaded. ResponsibilityDefault: 500

CSM: Return Activity DurationThis profile sets the duration (in days) of the return activity.ResponsibilityDefault: 90

The following table lists the profiles and their relevance in MFS Multiple Platform application. The MFS Multiple Platform application does not use all the profile options listed in Mobile Field Service Implementation Guide. Refer the Mobile Field Service Implementation Guide for a description of the profile options mentioned below.

Profile OptionUsed in MFS Multiple Platform Application

ASG: Enable Mobile UserYes

ASG: Synchronous Data UploadYes

CSF: Allow Overlapping Debrief LinesYes

CSF: Business ProcessYes

CSF: Capture travel informationYes

CSF: Default Commit task statusYes

CSF: Default Debrief Business ProcessYes

CSF: Default Debrief Service Activity CodeYes

CSF: Default Distance UnitYes

CSF: Default Labor Debrief Date/TimeYes

CSF: Default Return Reason (For Material Debrief)Yes

CSF: Default Service Activity Code for LaborYes

CSF: Default Service Activity Code for TravelYes

CSF: Google Map Client IDYes

CSF: Mandatory Labor Debrief (Y/N)Yes

CSF: Mandatory Resolution Code (Y/N)Yes

CSF: Restrict Service Request Creation to Scheduled Sites Yes

CSM: Allow Free Form Installed Base IdentifierYes

CSM: Allow Free Form ItemYes

CSM: Labor Line Total CheckYes

CSM: Maximum Number of ItemsYes

CSM: Notify on Deferred RecordsYes

CSM: Purge Interval (Days)Yes

CSM: Restrict Number of Items to Search for in LOVYes

CSM: Return Activity DurationYes

JTM: Application Conflict RuleYes

JTM: Conccurrent Program History LevelYes

JTM: Mobile Applications EnabledYes

ASG: Auto Upgrade All Users

No

ASG: Disable Custom Flag

No

ASG: Disable Custom Object Synchronization

No

ASG: Dormancy Period

No

ASG: Enable Delivery Events

No

ASG: Enable Upload Events

No

ASG: JDBC URL for the APPS Database

No

ASG: List of the Application Id handled by ASG

No

ASG: Mobileadmin Schema Password

No

ASG: Purge User Count

No

ASG: SSO Authentication Enabled

No

ASG: Synch History Purge Period

No

CSF: Default In Planning Status

No

CSF: Default Task Status for Personal Tasks

No

CSF: Default Task Type for Personal Tasks

No

CSF: The unit of measure for hours

No

CSF: The unit of measure for minutes

No

CSF: Update Planned/Scheduled Times Allowed

No

CSFW: Planned Task Window

No

CSM : CSM : Synchronous History Collection

No

CSM : SR Create Responsibility

No

CSM : Search Result Set Size

No

CSM TOP DIRECTORY

No

CSM: Allow Counters Download for Parties

No

CSM: Allow Service Contract Download for Parties

No

CSM: Allow Service Request History Download for Parties

No

CSM: Automatic Synchronization Interval for Data Download

No

CSM: Automatic Synchronization Interval for Data Upload

No

CSM: Email Account name for message interception

No

CSM: Email IMAP Host Name

No

CSM: Email IMAP User Name

No

CSM: Email IMAP User Password

No

CSM: Email SMTP Host Name

No

CSM: Email SSL Enabled

No

CSM: Enable Auto Sync

No

CSM: Enable Auto sync Status Notification

No

CSM: Enable Online Access

No

CSM: Enable create SR

No

CSM: First Alert Timeout in minutes

No

CSM: High Availability Mode

No

CSM: Inbox for Email Interface

No

CSM: Item Category Filter

No

CSM: Item Category Set Filter

No

CSM: Mobile Field Service Wireless URL

No

CSM: Mobile Query Schema Name

No

CSM: Notification of Synchronization Errors

No

CSM: Notifications Scope

No

CSM: Notify on Email Interface exceptions

No

CSM: Number of IB items at location

No

CSM: Number of Previously Closed Service Requests

No

CSM: Restrict Debrief to Default Subinventory

No

CSM: Restrict Order to Default Subinventory

No

CSM: Restrict Transfer between Subinventories

No

CSM: SERVLET VIRTUALPATH

No

CSM: Second Alert Timeout in minutes

No

CSM: Select Task Owner through Territory Assignment

No

CSM: Third Alert Timeout in minutes

No

CSM: Time Reasonability Check Apply

No

CSM: UIX Preview Path Directory

No

CSM:Data Routed to Group Owner

No

CSM:Enable Create task

No

CSM:Enable Customer product

No

CSM:Enable update task assignment

No

CSM:Maximum attachment size

No

CSM:Maximum readings per counter

No

Client Timezone

No

HZ: Reference Territory

No

ICX: Date format mask

No

ICX: Numeric characters

No

JTM: TimePicker Format (HH24/HH12)

No

Server Timezone

No

Service: Inventory Validation Organization

No

Task Manager: Default assignee status

No

Task Manager: Owner type for a task

No

Scheduling Concurrent Programs for Mobile Field Service Multiple Platform

The following table lists the concurrent programs that are used in the MFS Multiple Platform application:

Concurrent Program NameDescriptionDefault/Recommended Schedule

JTM Master Concurrent ProgramThe JTM master concurrent program runs all concurrent jobs registered by mobile applications. The JTM Master concurrent program accepts the lookup, transaction, inventory, and customer categories as parameters.TRANSACTION:

Every five to fifteen minutes.

LOOKUP: once a week or on demand.

INVENTORY: once a day. Sub programs that must be run more frequently can be scheduled into a custom category.

PURGE: as often as required (once per month)

Manages Mobile UsersAutomatically creates, removes, or updates mobile users based on assigned mobile responsibilities.Every one hour or on demand.

Processes Uploaded Mobile DataProcesses uploaded mobile data and applies it to the enterprise system.Every one minute.

The JTM master concurrent program runs all concurrent jobs registered by Oracle Mobile Field Service Store and Forward applications. The JTM master concurrent program uses the following category types:

TRANSACTION

LOOKUP

INVENTORY

CUSTOMER

PURGE

For a complete description of these category types use the Mobile Field Service Administration responsibility. The Mobile Concurrent Program Summary page displays the JTM concurrent program details for all the concurrent programs related to Oracle Mobile Field Service Store and Forward. The mobile concurrent program displays how many times the program has currently ran, and the maximum and the minimum times taken to finish the program.

The concurrent program screens enable you to view the status of mobile logic (PL/SQL) modules, which process the various business events for the Oracle Mobile Field Service Store and Forward applications. The mobile logic modules are grouped in various categories and the frequency of their execution is based on the category. You can change the mobile logic modules from one category to another or add a new category and hence change the frequency of execution, based on the business requirements.

These screens can also be used to understand the resources used by mobile logic modules, identify and resolve any performance bottlenecks.Creating a Mobile Field UserBefore you can use the Mobile Field Service Store and Forward Multiple Platform Support application you must create a mobile field service user. The Manages Mobile Users (MMU) concurrent program creates Mobile Field Service users that are assigned the Oracle Mobile Field Service responsibility.

You must specify a value for the Create Multiple Platform User parameter in the Manages Mobile Users concurrent program. This program periodically allocates resources for users that have a mobile responsibility, so there will be a delay between when the responsibility is assigned and when the change will take effect.

The MMU program has several parameters that need to be specified. In case of multiple platform application users, you must specify Yes for the Create Multiple Platform User parameter.

Mobile Field Service leverages existing Field Service setup to configure a mobile user. Once an EBS user is created and assigned various sub inventories as per Field Service requirements, the next step is to provide mobile access to this user.

Use the following steps to create a user.

1. Select a FND user who is also a CRM resource of type Employee.

2. Add the Oracle Mobile Field Service responsibility to this user. You can also assign custom responsibilities. Refer Implementing Oracle Mobile Application Foundation of the 12.1.3 Mobile Field Service Implementation Guide for a description of the ASG: Enable Mobile User profile. 3. Run the "Manages Mobile Users" concurrent program. The following parameters must be set to Yes for creating users.

"Create Users" parameter must be set to Yes, and

"Create Multiple Platform User" must be set to Yes.

Note: The default value for the above-mentioned parameters is Yes.

The remaining parameters are optional as shown below.

Note: Select a user name from the User Name LOV in the Parameters window above, only if you want to create a specific user. By default, all users with a valid mobile responsibility are created.

4. The mobile user is created after the successful completion of the concurrent program. The user is now ready to synchronize and access the MFS Multiple Platform application.

Deploying the MFS Application

Deploy the MFS application using the Enterprise deployment model for iOS. Please work with the IT team to host the application (OMFS.ipa/OMFS.apk) in an internal web site and provide instructions for the users to download it to their devices.

Upgrading the MFS Application

When the MFS iOS application is changed, you will get a newer version of the OMFS.ipa//OMFS.apk file. Please publish it to the web site, and notify the users so they can download it.

In most cases, the local database synchronized will be preserved during an upgrade.

Synchronization with the Enterprise Server An Overview

To use the Mobile Field Service Store and Forward Multiple Platform Support application technicians and administrators will launch the application and then synchronize with the enterprise system to ensure that they have the most current information and that their most current information from the application is sent to the enterprise system.

Complete the following steps to launch and synchronize Oracle Mobile Field Service Store and Forward Multiple Platform Support application after the installation.

To receive new data that has been assigned to technicians such as new tasks, technicians must synchronize with the enterprise system. Likewise, to upload the changes that technicians make such as creating debrief lines and updating task statuses; they must synchronize the device with the enterprise system.

Installing Mobile Field Service on iOS

Install the iOS MFS application by synchronizing over iTunes or over the air depending on the deployment in your instance. The following figure shows the UI once the application is installed on an iPhone.

Tap the Field Service icon to launch the application. The login screen appears as shown below:

Enable SSL by tapping on the lock icon next to the Server text field. Once SSL is selected, the UI changes as shown above in the screen shot on the right.

Enter the username, password, and the server information to initiate synchronization. The server field must contain both the server name and port name in the following format:

ServerName:Port

The server name and port are the same as the server name and port of the Apache URL of the EBS instance.

The progress of synchronization process is as shown below:

The Task list screen displays after the synchronization process is complete.

Tap the Filter button on the top right to change the view from Todays Tasks (default) to Open Tasks, or any other view.

Tap the Home button on the top left to access other features of the application.

Tap the Sync icon to initiate subsequent synchronizations. You can change the default view in the Preferences screen.

Viewing Synchronization History

You can view the synchronization details from the Sync History screen. This screen displays the following details: Sync Type, Session ID, Start Date, End Date, Refreshed, and Status.

Additional Resources

For product information on My Oracle Support

http://support.oracle.com/For Release 12.2 information on My Oracle Support

http://support.oracle.com/ Note 1297457.1

For Oracle EBS product documentation Release 12.1.3

http://docs.oracle.com/cd/B53825_08/current/html/docset.html

For more information about Oracle Applications Strategy

http://www.oracle.com/applications/home.html

For more information about Education

http://www.oracle.com/education/index.html

For more information about Support

http://www.oracle.com/support/