1 Introduction to JD Edwards EnterpriseOne Mobile Applications

This chapter contains these topics:

1.1 Prerequisite

Before using any JD Edwards EnterpriseOne mobile applications, you must first complete the installation, configuration, and deployment tasks associated with mobile applications. This includes configuring the Authentication Provider, which is used to log into all JD Edwards EnterpriseOne mobile applications.


See:

  • JD Edwards EnterpriseOne Mobile Applications Installation and Configuration Guide.

1.2 Understanding Mobile Application Basics

JD Edwards EnterpriseOne offers users the ability to access and update important business data directly from a hand-held mobile device. Using Oracle's ADF (Application Development Framework) Mobile technology, JD Edwards EnterpriseOne has developed these mobile applications:

  • Mobile EnterpriseOne Menu (Release 9.1 Update)

    Use this application as a single sign-in and launch point for all available EnterpriseOne mobile applications. This application simplifies the log-in process when the user has multiple mobile applications available.

  • Download applications from the Google Play Store or Apple App Store. (Release 9.1 Update)


    Note:

    If you download the application from Google Play or the Apple Store, you must configure information during the initial log in on your mobile device.

  • Mobile Expense Management

    You use the Mobile Expense Management application to:

    • Review expense reports that are currently awaiting your approval.

    • Approve or reject expense reports for your employees.

    • Enter your own expense reports.

    • (Release 9.1 Update) Attach photographs of receipts or other documents to your expense report.

    • Search for expense reports that you, or your employees, have entered previously.

  • Mobile Purchase Order Approval

    You use the Mobile Purchase Order Approval application to review, approve, and reject purchase orders that are currently awaiting your approval.

  • Mobile Requisition Self Service (RSS) Approval.

    You use the Mobile RSS Approval application to review, approve, and reject requisitions that are currently awaiting your approval.

  • Mobile Sales

    You use the Mobile Sales application to:

    • Inquire on item base price information.

    • Inquire on item availability.

    • Search for and review open and historical sales orders.

1.2.1 Oracle's ADF Mobile Technology

Oracle's ADF Mobile technology enables the creation of mobile applications that:

  • Extend EnterpriseOne applications to mobile devices.

  • Can be developed once, and deployed to multiple mobile device platforms.

  • Are device native in their look and feel.

  • Support database synchronization, web services, and transaction replay for communication with the server.

  • Are secure, robust, and standards-based.

This graphic illustrates the ADF Mobile deployment model with JD Edwards EnterpriseOne mobile applications:

Figure 1-1 Mobile Application Deployment Model

Description of Figure 1-1 follows
Description of "Figure 1-1 Mobile Application Deployment Model"

For more information about Oracle's ADF Mobile, visit the Oracle Technology Network site, and search on ADF Mobile: http://www.oracle.com/technetwork

1.2.2 Supported Devices

Oracle supports the use of all JD Edwards EnterpriseOne mobile applications on these devices:

  • IOS-based devices, such as the iPhone and iPad.

  • Android devices.

  • Blackberry devices on operating system level 6 or above.

1.2.3 Supported Languages

By default, all Oracle mobile applications that are built with ADF technology are deployed using English as the language. When a user launches a mobile application and signs in, the login service retrieves the user's language preference from their JD Edwards EnterpriseOne user profile. Language preference codes are stored in UDC table 01/LP.

If a translation bundle for that language exists, the mobile device displays the application using the user's preferred language. If no translation bundle exists for the specified language, the mobile device displays the application in English.


Note:

The login page for the application will appear in the language that is set as the default language of the mobile device, provided that there is a translation bundle for that language. If no translation bundle exists for the language, the login page appears in English.

Currently, translation bundles for all EnterpriseOne mobile applications exist for these languages:

  • English

  • French

  • German

  • Arabic

  • Czech

  • Chinese Simplified

  • Chinese Traditional

  • Danish

  • Dutch

  • Finnish

  • Greek

  • Hungarian

  • Italian

  • Japanese

  • Korean

  • Norwegian

  • Portuguese

  • Polish

  • Russian

  • Spanish

  • Turkish

  • Swedish

1.2.4 Setting up Favorites and Shortcuts

After you deploy your mobile applications, users can configure their mobile devices with favorites, shortcuts, and icons. The EnterpriseOne mobile solutions have been delivered with Oracle graphics that are used when creating favorites and bookmarks.

Users can follow the instructions provided with their mobile device to set up their access points to the mobile applications.


Note:

When setting up favorites and shortcuts to EnterpriseOne mobile applications, you must set them up to point to the application's Home screen, and not the Log In screen.

1.3 Understanding the Mobile Application User Interface

JD Edwards EnterpriseOne mobile applications are developed using standards-based technology. This means that all of the applications share standard user interface objects. These objects behave in the same way through all of the EnterpriseOne mobile applications. This section discusses each of these user-interface objects in detail.

Oracle recommends that users review this section before using the mobile applications.

Mobile Application Object Description and Usage
Surrounding text describes add_button.gif. Click the Add button to add a selected value to a list or form. This object appears next to items that you can add to a list or form.
Surrounding text describes clear_button.gif. Click the Clear button to remove all values from the fields on the current form. The clear button is typically used on search or filter forms that are initially populated with default values. Clicking the Clear button clears the all user-entered and default values from all fields, and enables the user to enter new values.
Surrounding text describes expand_button.gif. Click the Expand button to see additional detail about the specified record. When you click this button, the arrow points downwards, and any additional detail that is available is displayed on the screen. To collapse or hide this additional detail, click the button again.
Surrounding text describes home_button.gif. Click the Home button to return to the Home screen of the mobile application you are using.
Surrounding text describes next_prev_buttons.gif. Use the Next and Previous arrow buttons to navigate up or down through a list of records. If you click the upward-facing arrow, the system brings you to the previous record in the list. If you click the downward-facing arrow, the system brings you to the next item in the list. If you are at the top of a list, the Previous button is disabled. If you are at the end of a list, the Next button is disabled.
Surrounding text describes remove_button.gif. Click the Remove button to delete an existing item from a list. The button appears next to items that can be individually removed from a list or form.
Surrounding text describes restore_button.gif. Click the Restore button to repopulate fields on a form with their pre-defined default values. When you click this button, the system removes any manually-entered values, and populates all fields with the default values (if available). If default values do not exist for a field, the system leaves the field blank.
Surrounding text describes return_to_button.gif. Use the Return To button to return to the previous screen within the application flow. The text on this button changes, depending on the name of the screen to which you will be redirected. For example, if clicking this button returns the user to the Home screen, the button text is Home. If clicking the button returns the user to a filter screen, the button text is Filter.

Note that this button typically returns the user to the previous screen. However, when using the Item Base Price and Item Availability features in the mobile sales application, the button behaves in a slightly different manner. When using these features, users can move between the item availability and item price application flows. Therefore, the Return To button might not always bring you to the previous screen, but might bring you to the filter screen associated with the application flow.

For example, if you jump from a pricing form to check item availability, you are moving from one application flow (item pricing) to another (item availability). Therefore, the Return To button on the item availability form will bring you to the item availability search form, which is the "previous" form within the item availability application flow. The button will not return you to the item price form.
Surrounding text describes save_button.gif. Click the Save button to save the data that you enter on a form.
Surrounding text describes sign_out.gif. Click the Sign Out link to sign out of the current mobile application. This link appears at the bottom right of all mobile application forms.
Surrounding text describes visual_assist.gif. Use the Visual Assist button to access forms that enable users to search for valid values for the selected field. For example, you might find a Visual Assist button next to a Branch/Plant field that enables users to search for a valid branch/plant or business unit.