-New.gif)
Table of Contents
Getting Started - Introduction/Overview
Add Environments using Mobile App
Set Up BI Reports using Mobile App
Getting Started - Introduction/Overview
Simplified Loader offers two ranges of the mobile app: Transactional and Dashboard. The Transactional range includes apps that enable users to complete real-time transactions from their mobile, whereas the Dashboard app allows them to view and drill down on data stored in Oracle Fusion.
Simplified Loader offers two methods to set up a mobile app. These methods vary based on setup for a subscribed app vs trial mode.
1. Configuration steps for the subscribed app using the Company Code and Passcode: Setup performed using this method allows the user to control users and app behaviour centrally. To complete setup using Company Code and Passcode, you will need an Excel template corresponding to the mobile app Excel. Please follow the steps below to complete setup using Company Code and Passcode. It is recommended that the steps are carried out in the order presented.
Step 1. Unlock the Admin Panel (Step performed using corresponding Excel template)
Step 2. Complete Connection Setup (Step performed using corresponding Excel template)
Step 3. Set Up BI Reports using Excel (Step performed using corresponding Excel template)
Step 4. Set Up Roles and Privileges
Step 5. Complete User Registration
2. Configuration steps for the trial version using Oracle Fusion URL: Using this method, the user can perform all setup steps from within the mobile app. The pre-requite to set up the mobile app using this method are login credential with access to BI Administration role.
Step 1. Add Environments using Mobile App
Step 2. Set Up BI Reports using Mobile App
Step 3. Set Up Roles and Privileges
Unlock the Admin Panel
Step performed using corresponding Excel template.
The first step in setting up a Simplified Loader Template is to unlock the Admin Panel, located in the Setup section of the Simplified Loader toolbar.
The Admin Panel contains a number of the operations required to set up the Template. These operations are password protected as they need to be completed by the user responsible for the initial set up of the Template and therefore should not be available for modification by day-to-day users.
1. Navigate to the Simplified Loader Admin Panel button in the Setup section of the Simplified Loader toolbar.
2. By default, the Admin Panel is protected by a password.
The Admin Password is required to make any updates to either the Admin Panel or the About worksheet.
The default password is admin. To change the password, enter the current password and new password and then click the Change Password button.
3. To use the features available in the Admin Panel, unlock the Template by entering the Current Password and click the Unlock Template button.
After unlocking the Template, the user receives the following message
Clicking OK on this window will close the message and the Admin Panel.
4. Click on the Admin Panel menu option again to reopen. This will enable all options available to use. If required, changes can now be made to the About sheet. Once the Template is unlocked, it remains unlocked for the session.
5. Whenever the Admin Panel has been unlocked, closing the Template will result in the following message.
This is a reminder to the administrator that they need to save the file to ensure that the Admin Panel is locked before exiting the Template.
Click OK to make the window disappear. The following message will then appear.
6. Click on the Save button before exiting the Template.
Complete Connection Setup
Step performed using corresponding Excel template.
Simplified Loader templates exchange data with Oracle Fusion. The method used by Excel to do so can differ from one PC to another. The Simplified Loader Connection Wizard helps identify the appropriate configuration for the Simplified Loader template to ensure a seamless data exchange with the Oracle Fusion applications. Follow the steps below to locate and store the appropriate connection setting within the Simplified Loader template:
1. Click on User Preferences in the Setup section of the Simplified Loader toolbar to open the User Setup panel
2. In the Connection Setup section of the User Preferences panel, select an Oracle Fusion environment from the Environment URL drop-down list and click the Launch Connection Wizard button. This will start the connection wizard to identify the best connection method to connect to the selected environment.
3. To test connectivity, Connection Wizard will attempt to connect to the selected environment. The test is performed without a username and password. Therefore, it is likely that a pop-up message (screenshot below) will appear asking for a username and password. If this happens, it means that the Template received a successful response from Fusion. Acknowledge the message by clicking the Cancel button.
4. When Connection Wizard finds an appropriate connection type, it displays one of the following messages. Click OK to complete the Connection Setup step.
Set Up BI Reports using Excel
Step performed using corresponding Excel template.
Simplified Loader templates use BI Reports to retrieve data from Oracle Fusion. BI Reports need to be set up once for each mobile app for each environment. Only users that have been allocated the BI Administrator role can complete the BI Report setup.
1. Navigate to Admin Panel
2. Under the BI Report section, select the environment and enter the Username and login password of the user with BI Administrator Role access.
3. Click the “Create the BI report in the selected environment” button to create BI reports. The following message will appear after the successful creation of BI Reports.
4. After receiving the confirmation message, the BI Administrator can review the reports in the /Custom/SL_Template folder in Oracle Fusion.
5. The BI Administrator can optionally set the SL_Template folder property to Hidden (shown below). This will ensure that all users do not access the Simplified Loader reports. The user will not be executing the reports directly from BI.
Add Environments using Mobile App
This step is required when setting up a Mobile app using Oracle Fusion URL. Add the target Oracle Fusion environment to which you wish to connect using the Simplified Loader mobile app. Environment setup is a one-time configuration:
1. Navigate to the Settings page
2. Under the Environment setup section, enter the environment identifier in the Alias field and the environment URL in the URL field. Ensure to include https:// in the URL. The best source to obtain the environment URL is the Oracle Fusion login page.
3. Click the Add Environment button to save the environment Alias and URL. The following confirmation message will appear after the environment is successfully added.
4. More than one environment can be added if desired. To do so, repeat steps 1 to 3 above.
Set Up BI Reports using Mobile App
This step is required when setting up a Mobile app using Oracle Fusion URL. Simplified Loader Mobile App use BI Reports to retrieve data from Oracle Fusion. BI Reports need to be set up once for each mobile app for each environment. Only users that have been allocated the BI Administrator role can complete the BI Report setup.
1. Navigate to the Setting page
2. Under the Environment Setup section, click the Setup BI Report button.
3. Select the environment and enter the Username and password of the user with BI Administrator Role access.
4. Click the “Create BI Report” button to create BI reports in the selected environment. The following message will appear after the successful creation of BI Reports.
Set Up Roles and Privileges
This step is required when setting up transactional mobile apps only. Skip this step if you are setting up the Dashboard app and go directly to Step 5.
To transact using mobile app, the users require specific Privileges to be assigned to them in Oracle Fusion. Privileges can be assigned using an existing role or a new role. Below are the steps to assign privilege using a new role.
1. Log in to Oracle Fusion with the user having access to the IT Security Manager role.
2. From Oracle Fusion’s SpringBoard. Select Tools and then the Security Console.
3. In the Roles page, click Create Role.
NOTE: You can add Privileges to a new or existing Role. Based on your organization’s security policies, either create a new Role or use an existing Role to add required privileges.
4. Enter details of the new Role and click Next.
5. In the Function Security Policies page, click Add Function Security Policy.
6. Search for the required privilege, highlight the record and click Add Privilege to Role.
NOTE: Refer to the Template or App page to get the list of required privileges.
7. Review all security Policies in the “Function Security Policies” page and click Next.
8. On the Data Security Policies page, click Next.
9. In the Role Hierarchy page, click Next.
10. Add users to the Role and click Next. Alternatively, Roles can be assigned to the users in the Users page found within the Security Console.
11. Search and add users
12. Review users and click Next
13. In the Summary and Impact Report page, click Save and Close.
14. From Navigator, select Scheduled Processes within the Tools section.
15. Execute the following Please wait for the first process to complete successfully before submitting the next process:
- Retrieve Latest LDAP Changes
- Import User and Role Application Security Data
Complete User Registration
The user registration for Simplified Loader is administered using Oracle Lookups functionality. To set up Lookup codes, the System Administrator within your organization needs to define the app-specific Lookup Type in Oracle Fusion. Setting up Lookup Type is a two steps process:
Get User Registration Lookup Type
To complete this step, you need the Connection URL, Company Code, and Passcode.
1. Download the app from Google Play or iOS App store.
2. Launch the app and navigate to the Settings screen
3. Scroll to the Connection Setup section and enter Connection URL, Company Code and click Get Details.
4. Enter Passcode and click OK.
5. This will populate details in the Environment Details section and App Details section
6. Get Lookup Type name populated in the App Details section
Complete Users Registration
Complete these steps in all the environments to which you wish to connect.
1. Log in to Oracle Fusion from your PC or laptop and navigate to Setup and Maintenance
2. Select “Search” from the Tasks menu
3. Search Task “Manage Common Lookups”
4. Click the Plus (+) icon in the Search section to define a new Lookup
5. Enter the following details:
| Lookup Type | : | {Value obtained from App Details section of mobile app} |
| Meaning | : | Simplified Loader - User registration for {App Name} mobile app |
| Description | : | Leave blank. This field is used to support custom validations. |
| Module | : | Common Lookups |
| Lookup Configuration Level | : | User |
| REST Access Secured | : | Secure |
6. Save the record
7. Add user names, as lookup codes, of those users to which access to the Simplified Loader App is to be provided.
| Lookup Code | : | Enter the user name Example: James@Abc.com |
| Display Sequence | : | Leave blank |
| Enabled | : | Ticked |
| Start Date | : | Start date from which the user has access. The Start Date field can be left blank. |
| End Date | : | End date to which the user has access. The End Date field can be left blank. |
| Meaning | : | Enter user name. NOTE: The Template performs user validation using the value in the Meaning field. |
| Description | : | Leave blank. This field is used to support custom validations. |
| Tag | : | Leave blank |
8. Save the record
Transactional Mobile App Setup
To set up the Simplified Loader transactional mobile apps, perform the following two steps in addition to the steps mentioned above. These steps need executing for SL Requisitioning and SL AP Invoices app only.
Step 1. Configure fields displayed in the mobile app
The transactional mobile app gives administrator ability to define fields to display in the mobile app. The administrator controls field behaviour using Preferences. The fields displayed in the mobile app are defined in the following lookup types
| Lookup Type to control fields displayed in the app | ||
| App Name | Lookup Type | |
| SL Requisitioning | : | SL_REQUISITIONING_FIELDS_SETUP |
| SL AP Invoices | : | SL_AP_INVOICE_FIELDS_SETUP |
In the absence of the above lookup, the app will display the following fields.
| App Name | Display Sequence | Meaning (User Field Name) | Description (Preference) |
| SL Requisitioning | 5 | Requisition Number | ShowByDefault[Y] | UserOverride[N] | Mandatory[N] |
| SL Requisitioning | 10 | Requisition Business Unit | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 20 | Requisition Business Unit ID | ShowByDefault[N] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 30 | Description | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 40 | Preparer Email | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultFromSQL[PREPARER_EMAIL] |
| SL Requisitioning | 50 | Initiate Approval After Requisition Import | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultValue[Y] |
| SL Requisitioning | 60 | Document Status Code | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultValue[INCOMPLETE] |
| SL Requisitioning | 70 | Taxation Country Code | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 90 | Interface Source Code | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] | DefaultValue[Simplified Loader] |
| SL Requisitioning | 100 | Externally Managed Flag | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultValue[N] |
| SL Requisitioning | 110 | Product Type Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 120 | Requester Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] | DefaultFromSQL[PREPARER_NAME] |
| SL Requisitioning | 130 | Requester Email | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] | DefaultFromSQL[PREPARER_EMAIL] |
| SL Requisitioning | 140 | Deliver To Location Code | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] | DefaultFromSQL[DELIVER_TO_LOCATION_CODE] |
| SL Requisitioning | 150 | Line Type | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 160 | Category Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 170 | Supplier Number | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 180 | Supplier Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 190 | Supplier Site Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 200 | Supplier Contact Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| SL Requisitioning | 210 | Supplier Item Number | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| SL Requisitioning | 220 | Item Description | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| SL Requisitioning | 230 | Quantity | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| SL Requisitioning | 240 | Unit Of Measure | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| SL Requisitioning | 250 | Price | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| SL Requisitioning | 255 | Amount | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| SL Requisitioning | 260 | Destination Type Code | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 270 | Negotiation Required Flag | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultValue[N] |
| SL Requisitioning | 280 | Negotiated By Preparer Flag | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultValue[Y] |
| SL Requisitioning | 290 | Buyer Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| SL Requisitioning | 300 | Percent | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] | DefaultValue[100] |
| SL Requisitioning | 310 | Charge Account Segment1 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT1] |
| SL Requisitioning | 320 | Charge Account Segment2 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT2] |
| SL Requisitioning | 330 | Charge Account Segment3 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT3] |
| SL Requisitioning | 340 | Charge Account Segment4 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT4] |
| SL Requisitioning | 350 | Charge Account Segment5 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT5] |
| SL Requisitioning | 360 | Charge Account Segment6 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT6] |
Set up the lookup type to define default fields and controls field behaviour displayed in the app. These lookup type defines fields to display in the mobile app and Preferences against each field to control field behaviour.
1. Navigate to Setup and Maintenance and search task Manage Common Lookups.
2. Create a new Lookup Type
| Lookup Type | : | Lookup Type |
| Meaning | : | Simplified Loader {Mobile app} app fields setup |
| Description | : | Leave blank |
| Module | : | Common Lookups |
| Lookup Configuration Level | : | User |
| REST Access Secured | : | Secure |
3. Enter Requisition field details in the Lookup Code section:
| Lookup Code | : | Enter the same value as used in the Meaning field. In case the length of the Meaning field contains more than 30 characters, then use any value in the Lookup Code field |
| Display Sequence | : | The sequence in which field will display in the mobile app |
| Enabled | : | Indicate if a field is enabled for mobile app |
| Start Date | : | Leave blank |
| End Date | : | Leave blank |
| Meaning | : | Enter the field name that gets displayed to the user. Select the field name from the table of allowed field names |
| Description | : | Preferences related to Requisitioning fields |
| Tag | : | Leave blank |
Available fields in Transactional apps
Transactional mobile app support fields mentioned in the following table. To define a field for the transactional app, add the value from the User Field Name column to the Meaning field in the Lookup Code section of the Display Fields [link] Lookup Type. Other fields (Section Name, Data Type, and User Field Description) are for information purposes only.
| App Name | Section Name | User Field Name | Data Type | Field Description |
| SL Requisitioning | None | Requisition Title | Character | Title to identify Requisition in your mobile device. This is a reserved field and should not be used in SL_REQUISITIONING_FIELDS_SETUP Lookup Type. |
| SL Requisitioning | None | Load Status | Character | Requisition upload status. This is a reserved field and should not be used in SL_REQUISITIONING_FIELDS_SETUP Lookup Type. |
| SL Requisitioning | None | Error Message | Character | Requisition upload error message. This is a reserved field and should not be used in SL_REQUISITIONING_FIELDS_SETUP Lookup Type. |
| SL Requisitioning | Header | Interface Header Key | Character | The cloud interface alternate header key code, for integrating applications to be able to identify the requisition header data loaded in the interface table. |
| SL Requisitioning | Header | Requisition Number | Character | The display number used to identify a requisition. |
| SL Requisitioning | Header | Requisition Business Unit ID | Character | The unique identifier of a requisitioning business unit. |
| SL Requisitioning | Header | Requisition Business Unit | Character | The display name of a requisitioning business unit. |
| SL Requisitioning | Header | Interface Source Code | Character | A code indicating the outside source that the data was imported from. Reserved values for internal use include ORA_FUSION_DOO, ORA_FUSION_SCO, ORA_FUSION_INV. |
| SL Requisitioning | Header | Description | Character | A text description capturing the purpose of the requisition. |
| SL Requisitioning | Header | Document Status Code | Character | A code indicating the status of the requisition. Valid values include incomplete and approved. |
| SL Requisitioning | Header | Preparer ID | Character | The unique identifier of the requisition preparer that maps to the person ID within Oracle Fusion Applications. |
| SL Requisitioning | Header | Preparer Email | Character | The e-mail address for the requisition preparer. |
| SL Requisitioning | Header | Initiate Approval After Requisition Import | Character | Flag to indicate whether to Requisition for approval after a successful import. |
| SL Requisitioning | Header | Emergency PO Number | Character | The display number used to identify a purchase order number reserved in advanced for an emergency requisition. |
| SL Requisitioning | Header | Justification | Character | A text description capturing the reason for the requisition. |
| SL Requisitioning | Header | Taxation Country Code | Character | A code indicating the country where the transaction is deemed to have taken place for taxation purposes. |
| SL Requisitioning | Header | Taxation Territory | Character | A code indicating the territory where the transaction is deemed to have taken place for taxation purposes. |
| SL Requisitioning | Header | Document Fiscal Classification Code | Character | A classification used by a tax authority to categorize a document associated with a transaction for a tax. |
| SL Requisitioning | Header | Document Fiscal Classification | Character | A classification used by a tax authority to categorize a document associated with a transaction for a tax. |
| SL Requisitioning | Header | Sold To Legal Entity ID | Character | The unique identifier of the legal entity that is liable for the purchase order amount. |
| SL Requisitioning | Header | Sold To Legal Entity Name | Character | The name of the legal entity that is liable for the purchase order amount. |
| SL Requisitioning | Header | Approver Email | Character | The e-mail address of the requisition approver. |
| SL Requisitioning | Header | Approver ID | Character | The unique identifier of the requisition approver. |
| SL Requisitioning | Header | Interface Source Line ID | Character | The unique identifier of the source transaction. |
| SL Requisitioning | Header | Externally Managed Flag | Y / N | Indicates whether or not the requisition line is externally managed. |
| SL Requisitioning | Header | Header Attribute Category | Character | The user descriptive flexfield structure. |
| SL Requisitioning | Line | Interface Line Key | Character | The cloud interface alternate line key code, for integrating applications to be able to identify the requisition line data loaded in the interface table. |
| SL Requisitioning | Line | Line Type | Character | The display name of a line type that indicates whether a purchase is for goods or services. |
| SL Requisitioning | Line | Line Type ID | Character | The unique identifier of a type to indicate whether a purchasing document line is for goods or services, as well as to default some attributes associated with the line. |
| SL Requisitioning | Line | Category ID | Character | The unique identifier of the code used to group items with similar characteristics. |
| SL Requisitioning | Line | Category Name | Character | The display name of a category used to group items with similar characteristics. |
| SL Requisitioning | Line | Destination Type Code | Character | A code indicating if the item should be charged to an inventory or should be expensed. |
| SL Requisitioning | Line | Destination Subinventory | Character | The display name of a subinventory to which the requested item should be delivered. |
| SL Requisitioning | Line | Currency Code | Character | A code indicating the three-letter ISO code associated with a currency. |
| SL Requisitioning | Line | Amount | Character | The total amount according to the quantities and prices of the goods and service items specified on the requisition line. |
| SL Requisitioning | Line | Price | Character | The price of the item on the requisition line. |
| SL Requisitioning | Line | Quantity | Character | The quantity for the item to be added to the requisition. |
| SL Requisitioning | Line | Unit Of Measure Code | Character | A code indicating the division of quantity defined as a standard of measurement or exchange. |
| SL Requisitioning | Line | Unit Of Measure | Character | A division of quantity defined as a standard of measurement or exchange. |
| SL Requisitioning | Line | Secondary Quantity | Character | The quantity converted in the secondary unit of measure of a dual UOM controlled item. |
| SL Requisitioning | Line | Secondary UOM Code | Character | A code indicating the alternative unit of measure that is allowed to quantify a dual UOM controlled item. |
| SL Requisitioning | Line | Secondary UOM | Character | An alternative unit of measure that is allowed to quantify a dual UOM controlled item. |
| SL Requisitioning | Line | Procurement Business Unit ID | Character | The unique identifier of a procurement business unit. |
| SL Requisitioning | Line | Procurement Business Unit Name | Character | The display name of a procurement business unit. |
| SL Requisitioning | Line | Rate | Character | The ratio at which the principal unit of one currency can be converted into another currency. |
| SL Requisitioning | Line | Rate Date | Date | The date as of which a conversion rate is used to convert an amount into another currency. |
| SL Requisitioning | Line | Rate Type | Character | The source of a currency conversion rate, such as user defined, spot, or corporate. For user-defined rate, provide USER in the rate type. |
| SL Requisitioning | Line | Requester ID | Character | The unique identifier of a requester. |
| SL Requisitioning | Line | Requester Email | Character | The e-mail address for a requester. |
| SL Requisitioning | Line | Product Category | Character | A code indicating the type of product fiscal classification used to classify products. |
| SL Requisitioning | Line | Product Category Name | Character | The display name of a product fiscal classification type used to classify products. |
| SL Requisitioning | Line | Product Type | Character | A code indicating the type of product fiscal classification used to classify products. Related term(s) product fiscal classification. |
| SL Requisitioning | Line | Product Type Name | Character | The display name of a product fiscal classification type used to classify products. |
| SL Requisitioning | Line | Urgent Requisition Line Flag | Y / N | Indicates whether the requisition is urgent or not. |
| SL Requisitioning | Line | Note To Buyer | Character | A text description capturing the instructions to the buyer when processing the requisition line. |
| SL Requisitioning | Line | Note To Supplier | Character | A text description capturing the instructions to the supplier. |
| SL Requisitioning | Line | Note To Receiver | Character | A text description capturing the instructions to the receiver in the docking area to be reviewed while performing the receipt. |
| SL Requisitioning | Line | Buyer ID | Character | The unique identifier of the buyer specified on the document. A buyer is a person responsible for placing item resupply orders with suppliers and negotiating supplier contracts. |
| SL Requisitioning | Line | Buyer Name | Character | The display name of a buyer specified on the document. A buyer is a person responsible for placing item resupply orders with suppliers and negotiating supplier contracts. |
| SL Requisitioning | Line | Buyer Email | Character | The e-mail address of the buyer specified on the document. A buyer is a person responsible for placing item resupply orders with suppliers and negotiating supplier contracts. |
| SL Requisitioning | Line | New Supplier Flag | Y / N | Indicates whether or not the supplier is new. |
| SL Requisitioning | Line | Supplier Item Number | Character | The display name of a suppliers identification number or code for the goods ordered on your order line. |
| SL Requisitioning | Line | Supplier ID | Character | The unique identifier of an organization or individual that provides goods or services to the buying organization for payment, bound by a contractual obligation. |
| SL Requisitioning | Line | Supplier Name | Character | The display name of an organization or individual that provides goods or services to the buying organization for payment, bound by a contractual obligation. |
| SL Requisitioning | Line | Supplier Site ID | Character | The unique identifier of an entity that models how the buying organization conducts business with the supplier. |
| SL Requisitioning | Line | Supplier Site Name | Character | The display name of an entity that models how the buying organization conducts business with the supplier. |
| SL Requisitioning | Line | Supplier Contact ID | Character | The unique identifier of a supplier employee who represents the supplier in communications with the buying organization. |
| SL Requisitioning | Line | Supplier Contact Name | Character | The display name of a supplier employee who represents the supplier in communications with the buying organization. |
| SL Requisitioning | Line | Supplier Contact Email | Character | The e-mail address for a supplier employee who represents the supplier in communications with the buying organization. |
| SL Requisitioning | Line | Supplier Contact Fax | Character | The fax number for a supplier employee who represents the supplier in communications with the buying organization. |
| SL Requisitioning | Line | Supplier Contact Phone | Character | The phone number for a supplier employee who represents the supplier in communications with the buying organization. |
| SL Requisitioning | Line | Source Agreement ID | Character | The unique identifier of a purchase agreement against which this purchase order line is released. |
| SL Requisitioning | Line | Source Agreement Number | Character | The display number used to identify a purchase agreement against which this purchase order line is released. |
| SL Requisitioning | Line | Source Agreement Line ID | Character | The unique identifier of a purchase agreement line against which this purchase order line is released. |
| SL Requisitioning | Line | Source Agreement Line Number | Character | The display number used to identify a purchase agreement line against which this purchase order line is released. |
| SL Requisitioning | Line | Item ID | Character | The unique identifier of an item. |
| SL Requisitioning | Line | Item Description | Character | A text description capturing details about the item being purchased. |
| SL Requisitioning | Line | Item Number | Character | The display name of an item representing anything you make, purchase, or sell, including components, subassemblies, finished products, or supplies. |
| SL Requisitioning | Line | Item Revision | Character | Identifier that indicates version of inventory item being referenced on the order line. |
| SL Requisitioning | Line | Base Model ID | Character | The unique identifier of a model from which an ATO configuration was created. |
| SL Requisitioning | Line | Base Model Number | Character | The display name of a model from which an ATO configuration was created. |
| SL Requisitioning | Line | Base Model Price | Character | The model price from which an ATO configuration was created. |
| SL Requisitioning | Line | First Party Tax Registration ID | Character | The unique identifier of the tax registration record corresponding to the sold-to legal entity on the purchase order. |
| SL Requisitioning | Line | First Party Tax Registration Number | Character | The unique display number assigned to the sold-to legal entity by a tax authority in order to manage tax liabilities. |
| SL Requisitioning | Line | Line Intended Use ID | Character | The unique identifier of a tax classification that is based on the purpose for which a product is used. |
| SL Requisitioning | Line | Line Intended Use | Character | A code indicating the type of the tax classification that is based on the purpose for which a product is used. |
| SL Requisitioning | Line | Line Intended Use Name | Character | The display name of a tax classification that is based on the purpose for which a product is used. |
| SL Requisitioning | Line | Assessable Amount | Character | The price at which a product is valued, by a tax authority, for tax calculation purposes. The same product can have more than one assessable value, as given by different tax authorities. |
| SL Requisitioning | Line | Tax Classification Code | Character | A code indicating the group of taxes for reporting and processing purposes. |
| SL Requisitioning | Line | Tax Classification Name | Character | The display name of a group of taxes for reporting and processing purposes. |
| SL Requisitioning | Line | Third Party Tax Registration ID | Character | A unique identifier of the registration number assigned to the supplier or supplier site, when it is registered by a tax authority, and by which the party or party site registration will be identified. |
| SL Requisitioning | Line | Third Party Tax Registration Number | Character | A unique sequence of letters and/or numbers assigned to the supplier or supplier site, when it is registered by a tax authority, and by which the party or party site registration will be identified. |
| SL Requisitioning | Line | Product Fiscal Classification ID | Character | The unique identifier of a classification used by a tax authority to categorize a product for a tax. There could be more than one by tax. For example, for Brazil two classifications are required. |
| SL Requisitioning | Line | Product Fiscal Classification | Character | A code indicating the classification used by a tax authority to categorize a product for a tax. There could be more than one by tax. For example, for Brazil two classifications are required. |
| SL Requisitioning | Line | Product Fiscal Classification Name | Character | The display name of a classification used by a tax authority to categorize a product for a tax. There could be more than one by tax. For example, for Brazil two classifications are required. |
| SL Requisitioning | Line | User Defined Fiscal Classification | Character | A coding indicating the classification for any tax requirement that you cannot define using the existing fiscal classification types. |
| SL Requisitioning | Line | User Defined Fiscal Classification Name | Character | The display name of a classification for any tax requirement that you cannot define using the existing fiscal classification types. |
| SL Requisitioning | Line | Transaction Business Category | Character | A code indicating the business classification used by Oracle Fusion Tax to identify and categorize an external transaction into an Oracle Fusion Tax transaction. |
| SL Requisitioning | Line | Transaction Business Category Name | Character | The display name of a business classification used by Oracle Fusion Tax to identify and categorize an external transaction into an Oracle Fusion Tax transaction. |
| SL Requisitioning | Line | Negotiated By Preparer Flag | Y / N | Indicates whether or not the requested item is negotiated with the supplier. |
| SL Requisitioning | Line | Negotiation Required Flag | Y / N | Indicates whether or not a negotiation is required for the requested item. |
| SL Requisitioning | Line | Service Level Code | Character | A code indicating the priority of transportation that affects how quickly goods are transported. Applicable values are all codes of the lookup Carrier Service Levels. |
| SL Requisitioning | Line | Hazard Class ID | Character | The unique identifier of a classification of hazardous materials, to facilitate safety regulations compliance. |
| SL Requisitioning | Line | Hazard Class | Character | The display name of a classification of hazardous materials, to facilitate safety regulations compliance. |
| SL Requisitioning | Line | UN Number ID | Character | The unique identifier of a United Nations identification number for the hazardous material. |
| SL Requisitioning | Line | UN Number | Character | The display name of a United Nations identification number for the hazardous material. |
| SL Requisitioning | Line | Customer Item Number | Character | The display name of a customers identification number or code for the goods ordered on your order line. |
| SL Requisitioning | Line | Customer Item Description | Character | A text description capturing a customers identification number or code for the goods ordered on your order line. |
| SL Requisitioning | Line | Customer PO Line Number | Character | The display number used to identify a purchase order line from the customer that originated the sales order, which is being fulfilled by the material being procured in a drop ship arrangement. |
| SL Requisitioning | Line | Customer PO Number | Character | The display number used to identify a purchase order from the customer that originated the sales order, which is being fulfilled by the material being procured in a drop ship arrangement. |
| SL Requisitioning | Line | Customer PO Schedule Number | Character | The display number used to identify a purchase order schedule from the customer that originated the sales order, which is being fulfilled by the material being procured in a drop ship arrangement. |
| SL Requisitioning | Line | Deliver To Customer Contact ID | Character | The unique identifier of a customer contact to which materials, being procured in a drop ship arrangement, need to be delivered. |
| SL Requisitioning | Line | Deliver To Customer Contact Name | Character | The display name of a customer contact to which materials, being procured in a drop ship arrangement, need to be delivered. |
| SL Requisitioning | Line | Deliver To Customer Contact Number | Character | The display number used to identify a customer contact to which materials, being procured in a drop ship arrangement, need to be delivered. |
| SL Requisitioning | Line | Deliver To Customer Contact Email | Character | The e-mail for a customer contact to which materials, being procured in a drop ship arrangement, need to be delivered. |
| SL Requisitioning | Line | Deliver To Customer ID | Character | The unique identifier of a customer to which materials, being procured in a drop ship or back to back arrangement, need to be delivered. |
| SL Requisitioning | Line | Deliver To Customer Name | Character | The display name of a customer to which materials, being procured in a drop ship or back to back arrangement, need to be delivered. |
| SL Requisitioning | Line | Deliver To Customer Number | Character | The display number used to identify a customer to which materials, being procured in a drop ship or a back to back arrangement, need to be delivered. |
| SL Requisitioning | Line | Deliver To Customer Location CLLI Code | Character | The CLLI code for the customer location to which materials, being procured in a drop ship arrangement, need to be delivered. |
| SL Requisitioning | Line | Deliver To Customer Location Original System Reference | Character | The original system reference for the customer location to which materials, being procured in a drop ship arrangement, need to be delivered. |
| SL Requisitioning | Line | Deliver To Customer Location ID | Character | The unique identifier of a customer location to which materials, being procured in a drop ship arrangement, need to be delivered. |
| SL Requisitioning | Line | Deliver To Location Code | Character | A code indicating the final delivery location for goods previously received from a supplier. |
| SL Requisitioning | Line | Deliver To Location ID | Character | The unique identifier of a final delivery location for goods previously received from a supplier. |
| SL Requisitioning | Line | Deliver To Organization Code | Character | A code indicating the organization to which the requested item should be delivered. |
| SL Requisitioning | Line | Deliver To Organization ID | Character | The unique identifier of a organization to which the requested item should be delivered. |
| SL Requisitioning | Line | Ship To Customer Contact ID | Character | The unique identifier of a customer contact to whom materials, being procured in a drop ship arrangement, need to be shipped. |
| SL Requisitioning | Line | Ship To Customer Contact Name | Character | The display name of a customer contact to whom materials, being procured in a drop ship arrangement, need to be shipped. |
| SL Requisitioning | Line | Ship To Customer Contact Number | Character | The display number used to identify a customer contact to whom materials, being procured in a drop ship arrangement, need to be shipped. |
| SL Requisitioning | Line | Ship To Customer Contact Email | Character | The e-mail address of a customer contact to whom materials, being procured in a drop ship arrangement, need to be shipped. |
| SL Requisitioning | Line | Ship To Customer ID | Character | The unique identifier of a customer to whom materials, being procured in a drop ship or a back to back arrangement need to be shipped. |
| SL Requisitioning | Line | Ship To Customer Name | Character | The display name of a customer to whom materials, being procured in a drop ship or a back to back arrangement, need to be shipped. |
| SL Requisitioning | Line | Ship To Customer Number | Character | The display number used to identify a customer to whom materials, being procured in a drop ship or a back to back arrangement, need to be shipped. |
| SL Requisitioning | Line | Ship To Customer Location CLLI Code | Character | The CLLI Code for the customer location where materials, being procured in a drop ship arrangement, need to be shipped. |
| SL Requisitioning | Line | Ship To Customer Location Original System Reference | Character | The original system reference for the customer location where materials, being procured in a drop ship arrangement, need to be shipped. |
| SL Requisitioning | Line | Ship To Customer Location ID | Character | The unique identifier of a customer location where materials, being procured in a drop ship arrangement, need to be shipped. |
| SL Requisitioning | Line | Sales Order Number | Character | The display number used to identify a backing customer sales order number. |
| SL Requisitioning | Line | Sales Order Line Number | Character | The display number used to identify a backing customer sales order line number. |
| SL Requisitioning | Line | Sales Order Schedule Number | Character | The display number used to identify a backing customer sales order schedule number. |
| SL Requisitioning | Line | Work Order ID | Character | The unique identifier of a contract manufacturing work order. |
| SL Requisitioning | Line | Work Order Number | Character | The display number used to identify the finished goods product of a contract manufacturing work order. |
| SL Requisitioning | Line | Work Order Product | Character | The display name of the finished goods product of the contract manufacturing work order. |
| SL Requisitioning | Line | Work Order Operation ID | Character | The unique identifier of a contract manufacturing work order operation. |
| SL Requisitioning | Line | Work Order Operation Sequence | Character | The sequence number of work order operation. |
| SL Requisitioning | Line | Work Order Sub Type Code | Character | The code of the work order sub type. |
| SL Requisitioning | Line | Location Of Final Discharge ID | Character | The unique identifier of a final destination location for the purchases made by the customer. The location of the final customer or where the goods would be used is not necessarily the same as the initial ship-to location. |
| SL Requisitioning | Line | Location Of Final Discharge Code | Character | A code indicating the final destination location for the purchases made by the customer. The location of the final customer, or where the goods would be used, is not necessarily the same as the initial ship-to location. |
| SL Requisitioning | Line | Mode Of Transport Code | Character | The display name of a mode of transportation used to describe the movement of goods. |
| SL Requisitioning | Line | Carrier ID | Character | The unique identifier of the company that transports goods from one point to another by land, sea, or air. |
| SL Requisitioning | Line | Carrier | Character | The display name of the company that transports goods from one point to another by land, sea, or air. |
| SL Requisitioning | Line | Requested Ship Date | Date | The date when the buying company has requested the ordered item is ready to be shipped. |
| SL Requisitioning | Line | Requested Delivery Date | Date | The date when the buying company has requested the ordered item or service to be delivered. |
| SL Requisitioning | Line | Days Early Receipt Allowed | Character | The maximum acceptable number of days early for receipts. |
| SL Requisitioning | Line | Days Late Receipt Allowed | Character | The maximum acceptable number of days late for receipts. |
| SL Requisitioning | Line | Configured Item Flag | Y / N | Indicates whether the requisition line is for a configured item and configuration details might exist. |
| SL Requisitioning | Line | Orchestration Code | Character | A code indicating if the integrating application is synchronizing changes between their application and Oracle Fusion Procurement. Example values include DOO_TRACKED and SCO_TRACKED. |
| SL Requisitioning | Line | Group Code | Character | A code indicating the option by which the requisition lines are grouped when they are being processed by the import program. Requisition lines that are grouped together will be put on the same requisition header. Valid values include none, buyer, category, item, location, and supplier. |
| SL Requisitioning | Line | Over Receipt Tolerance Percent | Character | The tolerance that allows a purchase order schedule to receive more than ordered quantity or amount without triggering the over-receipt action. |
| SL Requisitioning | Line | Back To Back Flag | Y / N | Indicates whether the purchase order schedule has a backing sales order that is fulfilled using a back to back order. |
| SL Requisitioning | Line | Autosource Flag | Y / N | Indicates whether supplier and price information is derived from source purchase agreements. |
| SL Requisitioning | Line | Line Attribute Category | Character | The user descriptive flexfield structure. |
| SL Requisitioning | Distribution | Interface Distribution Key | Character | The cloud interface alternate distribution key code, for integrating applications to be able to identify the requisition distribution data loaded in the interface table. |
| SL Requisitioning | Distribution | Percent | Character | The percentage of the requisition distribution. |
| SL Requisitioning | Distribution | Distribution Amount | Character | The total amount of the distribution according to the distribution quantity and requisition line price. |
| SL Requisitioning | Distribution | Distribution Quantity | Character | The quantity for the requisition distribution. |
| SL Requisitioning | Distribution | Budget Date | Date | The date used to derive the budget period from which budget is consumed. |
| SL Requisitioning | Distribution | Charge Account ID | Character | The unique identifier of the General Ledger charge account. |
| SL Requisitioning | Distribution | Charge Account Segment1 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment2 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment3 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment4 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment5 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment6 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment7 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment8 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment9 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment10 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment11 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment12 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment13 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment14 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment15 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment16 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment17 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment18 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment19 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment20 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment21 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment22 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment23 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment24 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment25 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment26 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment27 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment28 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment29 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Charge Account Segment30 | Character | The charge account key flexfield segment. |
| SL Requisitioning | Distribution | Project ID | Character | The unique identifier of a project. |
| SL Requisitioning | Distribution | Project Number | Character | The number assigned to a project. A project is a finite endeavor (having specific start and finish dates) undertaken to create a product or provide a service. |
| SL Requisitioning | Distribution | Project Name | Character | The display name of a project. A project is a finite endeavor (having specific start and finish dates) undertaken to create a product or provide a service. |
| SL Requisitioning | Distribution | Project Task ID | Character | The unique identifier of the number of a task which is a subdivision of project work. |
| SL Requisitioning | Distribution | Project Task Name | Character | The display name of a task which is a subdivision of project work. |
| SL Requisitioning | Distribution | Project Organization ID | Character | The unique identifier of the organization that incurred the cost on the expenditure item. |
| SL Requisitioning | Distribution | Project Organization Name | Character | The display name of the organization that incurred the cost on the expenditure item. |
| SL Requisitioning | Distribution | Project Expenditure Item Date | Date | The specified day when the expenditure item was incurred. |
| SL Requisitioning | Distribution | Project Expenditure Type ID | Character | The unique identifier of a classification of cost that is assigned to each expenditure item. Expenditure types are grouped into cost groups (expenditure categories) and revenue groups (revenue categories). |
| SL Requisitioning | Distribution | Project Expenditure Type Name | Character | The display name of a classification of cost that you assign to each expenditure item. Expenditure types are grouped into cost groups and revenue groups. |
| SL Requisitioning | Distribution | Project Capitalizable Flag | Y / N | Indicates whether or not the expenditure item is capitalizable after it is fully processed. The debit amount for a capitalizable transaction is generally made to a construction in progress account. |
| SL Requisitioning | Distribution | Project Work Type ID | Character | The unique identifier of a classification of the work associated with a task. |
| SL Requisitioning | Distribution | Project Work Type Name | Character | The display name of a classification of the work associated with a task. |
| SL Requisitioning | Distribution | Project Billable Flag | Y / N | Indicates whether or not the expenditure item is billable after it is fully processed. |
| SL Requisitioning | Distribution | Project Funding Allocation ID | Character | The unique identifier of the project funding override. This attribute is used when Oracle Fusion Project Billing or Oracle Fusion Grants Management is installed. |
| SL Requisitioning | Distribution | Project Funding Source Name | Character | The display name used to identify the funding source associated with a sponsored project. |
| SL Requisitioning | Distribution | Project Context Category | Character | An attribute that determines which contextual segments of a descriptive flexfield to display for a transaction. For example, an expense report transaction may have different descriptive flexfield segments defined as compared to a time card transaction. |
| SL Requisitioning | Distribution | Project Contract ID | Character | The unique identifier of the contract. This attribute is used when Oracle Fusion Project Billing or Oracle Fusion Grants Management is installed. |
| SL Requisitioning | Distribution | Project Contract Name | Character | Name of the contract. This attribute is used when Oracle Fusion Project Billing or Oracle Fusion Grants Management is installed. |
| SL Requisitioning | Distribution | Project Contract Number | Character | Number of the contract. This attribute is used when Oracle Fusion Project Billing or Oracle Fusion Grants Management is installed. |
| SL Requisitioning | Distribution | Project Contract Line ID | Character | The unique identifier of the contract line. This attribute is used when Oracle Fusion Project Billing or Oracle Fusion Grants Management is installed. |
| SL Requisitioning | Distribution | Project Reserved Attribute1 | Character | The reserved descriptive flexfield segment for future project related functionality. |
| SL Requisitioning | Distribution | Distribution Attribute Category | Character | The user descriptive flexfield structure. |
Preferences
The transactional mobile app allows defining the following preferences to control the field behaviour. Preferences are entered in the Description field of the Lookup Code section. The format to enter Preference and its value is
PreferenceName[PreferenceValue]
The preference value is specified within the square brackets. The administrator can choose to use one or more preferences. When using multiple preferences, enter pipe (|) delimiter between preferences.
Mandatory
The Mandatory Preference is used to specify a field as mandatory. Mandatory Preference allows Y or N value. Enter Mandatory[Y] to indicate a field required in the mobile app. By default, all fields are set as non-mandatory.
The Mandatory field validation is performed when the user tries to submit the transaction for creation.
UserOverride
The administrator can set up fields such that the user cannot override the administrator’s default values. UserOverride Preference allows Y or N value. When using UserOverride[N] preference, the administrator must specify a default value using DefaultValue or DefaultFromSQL preferences. By default, all fields are set as UserOverride[Y].
ShowByDefault
The ShowByDefault preference defines whether a field gets displayed while entering a transaction in the mobile app. ShowByDefault Preference allows Y or N value. Using ShowByDefault preference, the administrator can determine fields that the user should see when entering a transaction. When using ShowByDefault[N] preference, the administrator must specify a default value using DefaultValue or DefaultFromSQL preferences. By default, all fields are set as ShowByDefault[Y].
The user can override ShowByDefault Preference using the Field Setup section in the mobile app.
The usage of this Preference is to define fields like Business Unit, which should not be displayed to the user when they enter a transaction.
DefaultValue
The DefaultValue Preference defines a static default value of a field. The default value is specified within the square brackets. For example, to default the value “INCOMPLETE” in the Document Status Code field, set DefaultValue[INCOMPLETE] as Preference.
To define a default value for fields having Y / N data type, specify value true or false in the Preference.
By default, the user can override the default value in the mobile app. To stop the users from the overriding default value, use preference UserOverride.
DefaultFromSQL
The DefaultFromSQL Preference defines a default value based on the SQL select statement. Configuring DefaultFromSQL is a two-step process
a. Define the SQL to fetch data based on user:
- Navigate to BI Report /custom/SL_Templates/Mobile{app name}/UserSQLDefaultsReport
- Add an SQL statement that must return a single row with two columns, SQL_OUTPUT and FIELD_VALUE. Specify the field name in the SQL_OUTPUT column. The field name specified as SQL_OUTPUT is used as DefaultFromSQL preference value. FIELD_VALUE column contains the value that gets defaulted in the app.
- If required, use parameter SL_USER_NAME to filter records using username accessing the mobile app.
- NOTE: The SQL query specified in /custom/SL_Templates/Mobile{app name}/UserSQLDefaultsReport gets executed when the user logs in to the app.
b. Specify Preference using DefaultFromSQL: Enter the value of SQL_OUTPUT field in the DefaultFromSQL Preference. For example, if the value of the SQL_OUTPUT field is PREPARER_NAME, enter DefaultFromSQL[PREPARER_NAME] as the field Preference.
In the Fields Setup section of the mobile app, the value in DefaultFromSQL Preference appears with “SQL:” prefix. For example, the user sees SQL:PREPARER_NAME as the field value. When the user creates a Requisition, they see the actual value fetched from the SQL statement.
By default, the user can override the default value in the mobile app. To stop the users from the overriding default value, use preference UserOverride.
Defaulting field values
The following data flow demonstrates how field values gets defaulted in the mobile app.
Step 2. Setup FieldsSetupVersion preference
After configuring Lookup Type linked with the mobile app for user validation, it is mandatory to set up FieldsSetupVersion preference in the lookup. FieldsSetupVersion preference value is used to control if Requisition fields setup should refresh in the mobile app using the latest configuration in Display Fields Lookup Type. The following flow highlights how FieldsSetupVersion preference triggers the operation to refresh fields from Display Fields Lookup Type in the mobile app.
You are now ready to use the Mobile app!
After completing the above setup steps, the user can use the mobile app. You will find more information on how to use the app in the User Guide.