1 Introduction to JD Edwards EnterpriseOne Mobile Enterprise Applications
This chapter discusses these topics:
-
Section 1.2, "Understanding Mobile Enterprise Application Basics"
-
Section 1.3, "Understanding Mobile Enterprise Application User Interfaces"
1.1 Prerequisite
Before using any JD Edwards EnterpriseOne mobile enterprise applications, you must first complete the required system configuration tasks.
|
See:
|
|
Note: The documentation for each mobile application includes a list of all the base applications in the EnterpriseOne system. To be able to use a mobile application, you must have permission to access all of the base applications listed for the mobile application. |
1.2 Understanding Mobile Enterprise Application Basics
JD Edwards EnterpriseOne mobile enterprise applications offer users the ability to access and update important business data directly from a mobile tablet or smartphone device. Using Oracle's MAF (Mobile Application Framework) Mobile technology, JD Edwards EnterpriseOne has developed the following mobile applications:
Asset Lifecycle Management (ALM)
| Application | Phone App | Tablet App |
|---|---|---|
| Condition-Based Maintenance | Yes | Yes |
| Create Equipment Work Orders | Yes | |
| Equipment Work Order Time Entry | Yes | Yes |
| Manage Equipment | Yes | Yes |
| Manage My Work Orders | Yes | Yes |
| Manage My Work Orders Disconnected | Yes | Yes |
| Meter Reading | Yes | |
| Review Team Work Orders | Yes | Yes |
Customer Relationship Management (CRM)
| Application | Phone App | Tablet App |
|---|---|---|
| Create Service Orders | Yes | |
| Manage Cases | Yes | |
| Manage Customer Equipment | Yes | Yes |
| Manage My Service Orders | Yes | Yes |
| Quick Case Entry | Yes | |
| Review Cases | Yes | |
| Review Team Service Orders | Yes | Yes |
| Service Order Time Entry | Yes | Yes |
Financial Management Solutions (FMS)
| Application | Phone App | Tablet App |
|---|---|---|
| Contact Customer | Yes | Yes |
| Contact Supplier | Yes | |
| Customer Account | Yes | Yes |
| Expense Approval | Yes | Yes |
| Expense Entry | Yes | Yes |
| G/L Batch Approvals | Yes | Yes |
| Invoice Batch Approvals | Yes | Yes |
| Payment Batch Approvals | Yes | Yes |
| Receipt Batch Approvals | Yes | Yes |
| Voucher Batch Approvals | Yes | Yes |
Health and Safety (HSE)
| Application | Phone App | Tablet App |
|---|---|---|
| Incident Scoreboard | Yes | Yes |
| Report an Incident | Yes | Yes |
Human Capital Management Fundamentals
| Application | Phone App | Tablet App |
|---|---|---|
| Contact Employee | Yes |
Project Management
| Application | Phone App | Tablet App |
|---|---|---|
| Change Request Approval | Yes | Yes |
| Change Request Entry | Yes | Yes |
| Field Progress Entry | Yes | Yes |
| Field Status Review | Yes | Yes |
| Job Progress Entry | Yes | |
| Manage Cost Code Schedule | Yes | |
| Project Status Review | Yes | Yes |
| Project Time Entry | Yes | Yes |
Supply Chain Management and Manufacturing
| Application | Phone App | Tablet App |
|---|---|---|
| Customer Order Overview | Yes | Yes |
| Inventory Availability | Yes | Yes |
| Product Price and Availability | Yes | Yes |
| Quote Review and Release | Yes | Yes |
| Sales Order Counts | Yes | Yes |
| Order Entry | Yes | |
| Sales Held Order Release | Yes | Yes |
| Search Sales Order | Yes | Yes |
| Warehouse Availability | Yes |
Supply Management
| Application | Phone App | Tablet App |
|---|---|---|
| Purchase Order Approval | Yes | Yes |
| Requisition Self Service Approval | Yes | Yes |
1.2.1 Supported Devices and Minimum Technical Requirements
Oracle supports the use of all JD Edwards EnterpriseOne mobile enterprise applications on several smartphone and tablet devices. For the latest list of supported devices, along with the most current MTR information, see this My Oracle Support document (sign on required):
https://support.oracle.com/epmos/faces/DocumentDisplay?id=1638204.1
|
Note: This documentation uses iPhone and iPad illustrations. Typically the functionality on the iOS and Android devices is the same. In cases where the functionality differs, the documentation will discuss the differences between the two operating systems. |
1.2.2 Languages in Mobile Applications
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 translated version of the application exists for that language, the mobile device displays the application using the user's preferred language. If no translated version 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 translated version of the application for that language. If there is no translated version in the selected language, the login page appears in English. |
Currently, translated versions 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.2.1 Language Support for Business Unit and Branch Plant Searches
Several Mobile Enterprise Applications use the Business Unit Search and Branch/Plant Search screens. The search behavior of these screens is dependent upon the language preferences of the logged-on user.
These screens search for data using the same method as the Business Unit Master Search program (P0006S) in the base EnterpriseOne system. If the language preference in the user's profile is set to blank, the mobile application uses the search description entered by the mobile user to search over the Business Unit Master table (F0006). If the language preference is populated, the mobile application uses the search description entered by the mobile user to search over the Business Unit Alternative Description Master table (F0006D).
1.3 Understanding Mobile Enterprise Application User Interfaces
JD Edwards EnterpriseOne mobile enterprise applications are developed using standards-based technology. This means that all of the applications share standard user interface elements and constructs. These elements behave in the same way through all of the EnterpriseOne mobile enterprise applications. This section discusses each of these user-interface elements in detail.
Oracle recommends that users review this section before using the applications.
| Mobile Application Object or Feature | Description and Usage |
|---|---|
| About Button | Tap this button to view the About This Application information associated with the applications. This information includes details such as the application name and version, the AIS server location, the application ID, and user login information. You access this button by tapping the Menu button.
|
| Action Buttons | Tap an action button to perform an action on the current screen. Actions can include Save, Add, Delete, and other actions you want to apply to a record in an application.
Action buttons typically appear in either the top navigation bar or the bottom bar of the application. This button illustrates an example of an Apply action button.
|
| Action Menu Button | Tap the Action Menu button at the top right of the screen to see a list of secondary actions that can be completed.
|
| Add Button | Tap the Add button to create a new record.
|
| Clear | There are two options that can be used to clear values. One, shown here, is used to clear the values from a specific field:
The other is a Clear action button, shown below, that clears the values from all fields on the screen.
|
| Credit Card | Tap this button to add credit card expenses to an expense report.
|
| Delete Button | Tap this button to delete a selected or associated entry.
|
| Edit Button | Tap this button to edit a selected or associated entry.
|
| Filter | Tap the Filter button, shown below, to access a form that enables you to enter search filter criteria to narrow your search results.
|
| Legal Terms | Tap this button to read the legal terms associated with using the mobile application. You access this button by tapping the Menu button.
|
| Logout | Tap this button to log out of the application. You access this button by tapping the menu button.
|
| Menu | The menu button, shown here, is displayed at the bottom of most screens, and enables users to log out of the application, view information about the application, or access legal terms.
|
| Next Field | The Next Field button appears when you are using the keyboard to enter data into fields on the screen. Tap this button to move to the next data-entry field on the screen.
|
| Previous Field | The Previous Field button appears when you are using the keyboard to enter data into fields on the screen. Tap this button to move to the previous data-entry field on the screen.
|
| Refresh | Many screens in the mobile applications use the standard device feature of swiping down on the screen to refresh the data.
Some screens include a refresh button, as shown here:
|
| Return To | 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 tapping this button returns the user to the Home screen, the button text is Home. If tapping the button returns the user to the Search screen, the button text is Search, as shown here:
|
| Tabs | Tabs are used within a detail screen to enable users to see different types of data related to the selected record. Tabs are typically organized horizontally near the top of the screen. When you tap on a tab, that tab is highlighted, and the data associated with that tab is displayed below. This is an example of two tabs, with the Equipment tab selected:
|
| Text | Tab this icon to use the texting application on your mobile device and send a message to the phone number displayed in the application.
|
| Visual Assist | Use the Visual Assist button, shown below, 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.
Note that in some cases, this button is used as a Find button. This typically occurs on the home screen of an application, where a user enters a value in the main header search field, and taps this button to find records that meet the search criteria. |
