Skip to main content

Oracle E-Business Suite Mobile Applications

 
Oracle E-Business Suite mobile apps enable users to perform needed tasks or take action on Oracle E-Business Suite transactions from mobile devices including iOS and Android smartphones Using EBS mobile apps, users can perform activities such as:
  • Approving workflow requests.
  • Entering and submitting time-cards.
  • Creating and managing purchase orders.
  • Executing warehouse stock movements.
  • Performing inventory counts.
These capabilities allow employees to remain productive while working remotely or travelling.
Oracle E-Business Suite mobile applications can be found by searching “Oracle America EBS” in the Apple App Store or Google Play Store.


 
Technical Overview
Oracle EBS mobile applications are developed using the Oracle Mobile Application Framework (MAF). This framework is also available to customers for building custom mobile applications when standard offerings do not fully meet business requirements.
However, Oracle does not support direct customization of the source code for standard mobile applications, except for:
  • Corporate branding configurations
  • Supported flexfield extensions
The mobile applications communicate with Oracle EBS through REST web services. These REST services are delivered as part of the standard Mobile Framework within EBS. For environments running versions earlier than Release 12.2.10, certain server-side patches may be required before the services are fully operational.
From a security perspective, users authenticate using their existing EBS credentials, eliminating the need for separate account management. The default authentication model is username and password–based, with additional options available, including Single Sign-On (SSO). Advanced security configurations can be implemented as needed.

Version Compatibility
Oracle EBS mobile apps are compatible with both Release 12.1.3 and Release 12.2.3 and onwards, as well as iOS 12.3 or later and Android 6.0 or later. EBS mobile apps are available only on the Apple iOS and Google Android platforms.
It is worth noting that there are some minor differences in behaviour when comparing the apps on iOS and Android. When developing these applications Oracle will test the iOS versions on iPhones, iPod Touches and iPads which gives very good device coverage. On the Android platform, Oracle will test on Samsung Galaxy and Google Nexus devices only. Due to the huge variety of Android handsets available, Oracle does not provide device-specific certifications on this platform.

References

Oracle E-Business Suite Mobile Apps, Release 12.1 and 12.2 Documentation (Note 1641772.1)

Oracle E-Business Suite Mobile Apps Administrator’s Guide, Release 12.1 and 12.2 (Note 1642431.1)
 



Comments

Popular posts from this blog

Oracle R12 Inventory Configuration: Key points to Avoid Mistakes

Most Oracle ERP R12 inventory problems are not system failures they are process and configuration failures. The same categories of mistakes surface repeatedly across implementations: Focusing on master data control, disciplined transactions, proper OU setup, and strong internal controls prevents operational and financial discrepancies.   This article walks through the four most critical areas where Oracle R12 inventory implementations go wrong, explains why each mistake is costly, and provides recommendations to prevent them. Each section includes the relevant navigation path and configuration screenshots for hands-on reference   1.       Improper Item Master Configuration in Oracle R12   Oracle E‑Business Suite R12 , the Item Master Configuration serves as the foundation of the Inventory module. Two critical components under this configuration umbrella are: Define Master Item Setup Define Item Status Both setups control how items ...

Monitoring and Troubleshooting Oracle APEX Performance with Real-World SQL Queries

    Introduction Oracle Application Express (APEX) is one of the most widely adopted low-code development platforms in the Oracle ecosystem. As organizations scale their APEX deployments, the need for robust monitoring and troubleshooting capabilities becomes critical. This article provides SQL queries that DBAs and developers can use to monitor, diagnose, and optimize their APEX environments.   What makes monitoring APEX unique is the three-tier architecture it operates on: the Oracle Database at the data layer, APEX at the application layer, and Oracle REST Data Services (ORDS) as the middleware. Understanding how sessions flow through these three layers is the key to effective monitoring.     Architecture Overview   Layer Component Version Role Database Oracle DB 19.28 Stores data, executes SQL, manages sessions Application Oracle AP...
SQL Query Performance Tuning: A Practical Approach for Oracle DBAs Inefficient queries in Oracle Database can significantly impact system performance, resulting in higher response times and decreased user productivity. By closely monitoring memory usage and CPU consumption, database administrators can identify performance bottlenecks and determine the root causes of inefficient query execution. Oracle Query Performance Tuning Checklist 1.          Monitor Memory Usage:                Purpose: Ensure optimal memory allocation to prevent excessive disk I/O and performance degradation.             Actions: * Track memory consumption using Oracle Enterprise Manager *Automatic Workload Repository (AWR) reports to review SGA and PGA utilization, and identify abnormal memory usage patterns. Analyze AWR reports for: a.   ...