Introduction
OneApp provides a standardized single user interface for all business systems used in an Organization.
OneApp is a mobile/desktop application for creating, viewing, and updating various business-related documents and transactions in a single user interface. The default configuration of OneApp supports different business systems such as Oracle Cloud Applications, SAP HANA S/4, Oracle E-Business Suite R12, Microsoft Dynamics 365 Business Central, Microsoft Dynamics 365 for Finance and Operations,Salesforce, ServiceNow, etc. You can also use the OneApp with any other ERP, PLM, Quality, MES business system that provides REST/ODATA APIs similar to any seeded applications.
The user interface is also available in Windows & macOS to configure various business processes and create navigation menus, forms, queries, reports, and charts.
info
You can check which functionalities are currently supported by these two products on their official documentation site.
- SAP: https://api.sap.com/ (Only ODATA APIs)
- Oracle: https://docs.oracle.com/en/cloud/saas/index.html (Only REST APIs)
You can use RikData EBS REST APIs for Oracle R12 or develop your own REST APIs. RikData EBS REST APIs are available for all EBS R12 modules and provide REST APIs similar to Oracle Cloud Application. The REST APIs don't use Oracle R12 responsibilities for security but use role-based & group-based data control.
Screenshots
| Dashboard | Menu |
|---|---|
 |  |
| Result | Search |
 |  |
| Custom Dashboard | Settings |
 |  |
| Qucik Menu | Configuration |
 |  |
| Reports | Charts |
 |  |
| Configurable Forms | Personalized Menus |
 |  |
Technology Stack
Key Features
OneApp allows users to configure all forms and fields:
- Form Visibility: Which form is visible to which user. (Ex: A technician can only issue materials to a work order but can not edit the work order)
- Field Visibility: Which fields of a form is visible to which user(Ex: Buyers can view and edit purchasing related fields on item master and Planners can view and edit only planning-related fields on item master)
- Field Sequence: The sequence of each field in a form (Ex: while doing a material transaction, the user will view item number before a unit of measure)
- Mandatory Fields: Users can't save a document or create a transaction without entering values in mandatory fields. (The field is not required to be mandatory in Oracle/SAP)
- Default values: Default values for documents and transaction to simplify data entry
It also allows users to
- Scan all fields
- Create own dashboards showing data/menus/charts important to a user
- Search documents with various parameters and save the query for future reference
- Create charts and reports as per business requirements