Table of Contents

Introduction

Maintain user

Application control preferences

Configure Transactional Apps

Configure Dashboard Apps

Introduction

The administrator can control the behaviour of the Simplified Loader mobile app by centrally managing its setup. Changes documented in this guide immediately reflect in the app.

Maintain user

This control applies only when the Mobile app’s Environments are set up using the Company Code and Passcode.

Simplified Loader mobile app is linked to a Lookup Type in Oracle Fusion. Using Lookup Type, the administrator assigns access to the users authorized to use the mobile app.

1. Get the right Lookup Type linked to the mobile app. The Lookup Type is listed under the App Details section on the Settings page.

2. In Oracle Fusion, navigate to Setup and Maintenance and select the “Search” option from the Task menu. Search for “Manage Common Lookups”.

3. Search for Lookup Type displayed in the mobile app

4. Add a new Lookup Code: Enter the username of the user to be authorized in Lookup Code and Meaning fields

5. Save the record.

6. The registered user can now access the mobile application

Application control preferences

This control applies only when the Mobile app’s Environments are set up using the Company Code and Passcode.

When a user logs in to Oracle Fusion using the Simplified Loader app, their login is validated using Lookup Type in Oracle Fusion. At the time of login, the Simplified Loader mobile app reads the text entered in the Description field of the Lookups setup. The app uses values entered in Description fields to control the app behaviour.

The Description fields can be set up with the following pre-defined preferences that control the mobile app’s behaviour. The administrator can choose to use one or more preferences. When using multiple preferences, enter pipe (|) delimiter between preferences.

DisableDataShare

The default behaviour of all Simplified Loader apps is to allow data sharing from the Transaction Details page in CSV format. To stop data sharing, use DisableDataShare preference. The default value of DisableDataShare preference is N. Set the value of this preference to Y to remove the data share feature from the app.

Usage: DisableDataShare[Y] or DisableDataShare[N]

Screenshot of Transaction Details page containing data share button (default behaviour).

Screenshot of Transaction Details page with disabled data share functionality ( DisableDataShare[Y] ).

AllowedDays

The default behaviour of all Simplified Loader apps is to allow users to log in to the app every day. Admin can restrict the days on which the app can be used with the AllowedDays preference.

Usage: AllowedDays[1,2,3,4,5,6,7] where numbers 1 to 7 represent days of a week. 1= Monday and 7=Sunday. Example: AllowedDays[1,2,3,4,5] will allow users to make use of this app only on weekdays.

The following error message is displayed whenever a user attempts to access the app outside the allowed days.

AllowedHours

The default behaviour of all Simplified Loader apps allows users to log in to the app at any time. Admin can restrict the time at which the app can be used.

Usage: AllowedHours[HH:MM,HH:MM] example: AllowedHours[09:00,17:00] permits users to log in and use the mobile app between 09:00 and 17:00 only.

The following error message is displayed whenever a user attempts to access the app outside allowed hours.

AutoLogoutAfterExitingApp

The app’s default behaviour is to log out automatically when the app is not used for 15 minutes. The 15 minutes duration can be changed by setting up AutoLogoutAfterExitingApp preference and providing the number of minutes as a value.

Usage: AutoLogoutAfterExitingApp[10]

For example, AutoLogoutAfterExitingApp[10] will force the user back to the login page if the app has not been used for 10 mins. Setting AutoLogoutAfterExitingApp [-1] will end the session immediately as soon as the app is closed. In such a case, the user needs to log in again to use the app. NOTE: The time counter starts when the user leaves the app.

AllowedPastCalendarDays

The app’s default behaviour is to allow a data query of the entire history, i.e. from the first day of usage. This can be restricted to a defined number of days by using AllowedPastCalendarDays preference. AllowedPastCalendarDays preference accepts the number of days as preference.

Usage: AllowedPastCalendarDays[100]

For example, AllowedPastCalendarDays[100] will allow users to query data that is 100 days in past. In this example, if the user were to attempt a query for greater than 100 days, then they will receive the following message:

Your organization has chosen to restrict the query data for the past 100 days only. Please contact your support desk if you need to query data beyond 100 days.

Override application control preferences at the user level

Preferences can be set up at the Lookup Type level of Lookup Code (User) level. When the same preference is defined at Lookup Type level and Lookup Code level, then the Lookup Code level preference takes precedence.

For example, the following setup will disable data share functionality from all users using the app linked to the given lookup.

The following screenshot demonstrates setup with preference override at the user level.

Configure Transactional Apps

The transactional mobile app (SL Requisitioning and SL AP Invoices) gives administrator ability to define fields to display in the mobile app. The administrator controls field behaviour using Preferences. Click here to view detailed steps to configure transactional mobile app.

Configure Dashboard Apps

The administrator can set up the Tasks page, and the charts displayed.

Manage Tasks Page

After successful login, the Tasks page is displayed to the user. The Task Name and the behaviour of each Task are configurable and centrally controlled by the administrator. This section details how to add or remove options on the Tasks page.

The Task page is controlled by “TasksPage” Data Model locate in directory /custom/SL_Templates/<MobileApp>. The “TasksPage” Data Model refers to a specific Lookup Type a which should be created with options suitable for your organization. The associated Lookup Type is typically named as SL__TASK_OPTIONS. For example, for the Requisitioner Dashboard app, the associated Lookup Type is SL_REQ_DASH_TASK_OPTIONS. Refer to the Data Model of each Mobile app to get the Lookup Type associated with the Dashboard app.

 

The following details are defined in the Lookup Type setup:

a. Task Names displayed to the user. For example, ‘Requisitions created in past 7 days’

b. The sequence in which Task Names are displayed to the user

c. Days selection based on the number of days or calendar

d. Reference to Dara Model that retrieves charts data

 

Follow the steps below to configure the Lookup Type for Tasks page

1. Log in to Oracle Fusion with BI Administrator capabilities. In BI Catalog, review TasksPage Data Model located under folder: /custom/SL_Templates/

2. Get Lookup Type Code from the associated Data Model.

3. Navigate to Setup and Maintenance

4. Select the option “Search” from the Tasks menu

5. Search Task “Manage Common Lookups”

6. Click the Plus (+) icon in the Search section to define a new Lookup

7. Enter the following details:

Lookup Type : {value obtained from 'TasksPage' Data Model}
Meaning : Simplified Loader Tasks page detail for {App name}
Description : Leave blank
Module : Common Lookups
Lookup Configuration Level : User
REST Access Secured : Secure

 

8. Save the record

9. Add Task Names as lookup values. The Task Names will get displayed on the Tasks page when the user logins to the Mobile app.

Lookup Code : Enter a unique value
Display Sequence : Enter the sequence in which Task Name should appear on the Tasks page
Enabled : Ticked
Start Date : Start date of Task Name. The start date field can be left blank.
End Date : End date of Task Name. The end date field can be left blank.
Meaning : Enter Task Name that gets displayed to the user.
Description : Enter the report path responsible for retrieving chart data.
Tag :

Enter days using one of the following options. The days defined in the option are passed in the :DAYS parameter when calling the report responsible for retrieving charts data.

i. Days: Enter the number of days associated with the Task Name. Example, value '30'. In this case :DAYS parameter will receive the value 30.

ii. Calendar: Enter value ‘...’ (without single quotes) to display calendar when selecting the Task Name. Based on the date chosen by the user, the mobile app will calculate the days between today’s date and the selected date. The day’s difference is passed to the :DAYS parameter. When defining a calendar, the administrator can optionally define validation to check what date range can a user select from the calendar.

  • ...[<31]: This option indicates displaying the calendar and validating the selected date. The date difference from today’s date must be less than 31 days. In other words, the user will be able to choose any date in the past 30 days.
  • ...[>365]: This option indicates displaying the calendar and validating the selected date. The date difference from today’s date must be more than 365 days. In other words, the user will not be able to choose any date in the past 365 days.

 

10. Save the record

Manage Charts

Simplified Loader Dashboard apps allow creating charts based on the Task Name in the Task page. The report defined against Task retrieves chart data. The chart data is presented in graphs using “AllGraphsMetadataReport” report located under /custom/SL_Templates/. There are four different types of graph supported by Simplified Loader Dashboard apps.

a. Pie chart

b. Bar chart

c. Double Bar chart

d. Number

 

Define report to retrieve charts data

1. Duplicate an existing Data Model and Report.

2. Change SQL in duplicated Data Model. When defining the Data Modal SQL query, ensure

  • The graph name in Data Modal SQL must match TasksPage Data Modal
  • Not to changes column sequence
  • Do not add or remove columns
  • Add details of all graphs that should be displayed under the selected Task Name
  • The Data can utilize the following parameters:
    :SL_USER_NAME
    :SL_TARGET_ID
    :DAYS

 

Steps to define different type of graphs

1. Edit AllGraphsMetadataReport Data Model under /custom/SL_Templates/

2. The values needed to set up graphs differs based on the graph type. The graph definition need fields supported by the Dashboard app. Visit the related topic section under the Dashboard application page to get the complete list of the fields supported by the app.

 

a. Pie chart

GRAPH_NAME : Enter graph name same as the graph name entered to report used to retrieve data
DISPLAY_SEQUENCE : Enter the sequence in which the graph displays on the screen
GRAPH_TYPE : Enter value 'PIE'
DISPLAY_LABEL : Enter field name supported the Dashboard mobile app. The field value gets displayed in the graph as the label. For example, ‘STATUS’
GROUPING_FORMULA_1 : Enter SQLite grouping formula. SQLite grouping functions are found here. For example, ‘COUNT(STATUS)’
GROUPED_BY_FIELD_1 : Enter the field name based on the value entered in GROUPING_FORMULA_1. For example, ‘STATUS’

 

The information supplied in graph metadata gets translated to the following SQL

SELECT DISPLAY_LABEL, GROUPING_FORMULA
FROM DASHBOARD_DATA
WHERE filter by GRAPH_NAME
GROUP BY GROUPED_BY_FIELD;

 

Example,

SELECT STATUS, COUNT(STATUS)
FROM DASHBOARD_DATA
WHERE filter by GRAPH_NAME
GROUP BY STATUS;

 

b. Bar chart

GRAPH_NAME : Enter graph name same as the graph name entered to report used to retrieve data
DISPLAY_SEQUENCE : Enter the sequence in which the graph displays on the screen
GRAPH_TYPE : Enter value ‘BAR’
DISPLAY_LABEL : Enter field name displayed with each bar. For Example, ‘SUPPLIER’
GROUPING_FORMULA_1 : Enter SQLite grouping formula. SQLite grouping functions are found here. For example, ‘SUM(PO_AMOUNT)’
GROUPED_BY_FIELD_1 : Enter the field name based on the value entered in GROUPING_FORMULA_1. For example, ‘STATUS’
LEGEND_TEXT_1 : Enter static text to appear in the graph legend. Example, '''PO Amount: '''
LEGEND_UOM_1 : Enter the field name to appear in the graph legend. For example, ‘FUNCTIONAL_CURRENCY’

 

The information supplied in graph metadata gets translated to the following SQL

SELECT DISPLAY_LABEL, GROUPING_FORMULA
FROM DASHBOARD_DATA
WHERE filter by GRAPH_NAME
GROUP BY GROUPED_BY_FIELD;

 

Example,

SELECT SUPPLIER, SUM(PO_AMOUNT)
FROM DASHBOARD_DATA
WHERE filter by GRAPH_NAME
GROUP BY SUPPLIER;

 

c. Double-Bar chart

GRAPH_NAME : Enter graph name same as the graph name entered to report used to retrieve data
DISPLAY_SEQUENCE : Enter the sequence in which the graph displays on the screen
GRAPH_TYPE : Enter value ‘DOUBLE BAR’
DISPLAY_LABEL : Enter field name displayed with each bar. For Example, ‘SUPPLIER’
GROUPING_FORMULA_1 : Enter SQLite grouping formula. SQLite grouping functions are found here. For example, ‘SUM(UNRECEIVED)’
GROUPED_BY_FIELD_1 : Enter the field name based on the value entered in GROUPING_FORMULA_1. For Example, ‘SUPPLIER’
LEGEND_TEXT_1 : Enter static text to appear in the graph legend. Example, '''Unreceived: '''
LEGEND_UOM_1 : Enter the field name to appear in the graph legend. For example, ‘FUNCTIONAL_CURRENCY’
GROUPING_FORMULA_2 : Enter SQLite grouping formula. SQLite grouping functions are found here. For example, ‘SUM(GRNI)’
GROUPED_BY_FIELD_2 : Enter the field name based on the value entered in GROUPING_FORMULA_1. For Example, ‘SUPPLIER’
LEGEND_TEXT_2 : Enter static text to appear in the graph legend. Example, '''GRNI: '''
LEGEND_UOM_2 : Enter the field name to appear in the graph legend. For example, ‘FUNCTIONAL_CURRENCY’

 

d. Number

GRAPH_NAME : Enter graph name same as the graph name entered to report used to retrieve data
DISPLAY_SEQUENCE : Enter the sequence in which the graph displays on the screen
GRAPH_TYPE : Enter value ‘NUMBER’
DISPLAY_LABEL : Enter label to be displayed in the graph area. For example, '''Total Unreceived'''
GROUPING_FORMULA_1 : Enter SQLite grouping formula. SQLite grouping functions are found here. For example, 'FUNCTIONAL_CURRENCY || ” ” || SUM(UNRECEIVED)'
GROUPED_BY_FIELD_1 : Enter the field name based on the value entered in GROUPING_FORMULA_1. For example, ‘FUNCTIONAL_CURRENCY’

 

The information supplied in graph metadata gets translated to the following SQL

SELECT DISPLAY_LABEL, GROUPING_FORMULA
FROM DASHBOARD_DATA
WHERE filter by GRAPH_NAME
GROUP BY GROUPED_BY_FIELD;

 

Example,

SELECT 'Total Unreceived', FUNCTIONAL_CURRENCY || ' ' || SUM(UNRECEIVED)
FROM DASHBOARD_DATA
WHERE filter by GRAPH_NAME
GROUP BY FUNCTIONAL_CURRENCY;