RikData OneApp 4+

Build a standardized User Interface for all business systems: EBS R12, Cloud, HANA S/4, Salesforce, ServiceNow, Dynamics 365, inoERP, etc

OneApp is a no-code, low-code platform to create a standardized User Interface for all business systems: EBS R12, Cloud, HANA S/4, Salesforce, ServiceNow, Dynamics 365, inoERP, etc. It allows organizations to create custom applications that integrate with standard ERP systems without writing any code.
You can use the application to create custom applications for all platforms: iOS, macOS, Android, Windows, and Web.

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, 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. You can use Rikdata REST builder to create REST APIs quickly without writing any custom code for old legacy systems.



The user interface is also available in Windows & macOS to configure various business processes and create navigation menus, forms, queries, reports, and charts.

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.

RikData REST builder is a GO-based application that makes building REST APIs simple and fast for legacy applications such as Oracle EBS. The builder is very flexible and provides well-defined REST APIs based on existing tables/data structures without writing any code. Currently, RikData REST builder is available for applications that use Oracle, MySQL/MariaDB, MsSql, PostgreSQL, Sqlite databases.



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