Apple iPads Certified with Oracle E-Business Suite 12.1

Apple iPad and iPad miniApple iPads are certified with Oracle E-Business Suite 12.1. 

This certification covers Safari with E-Business Suite OA Framework-based (HTML) applications.  These are sometimes also referred to as "Self-Service Web Applications" (SSWA).

This certification also covers the use of Apple's Mail app to approve E-Business Suite Workflow notification emails.

It is not possible to run Java-based applications on iOS devices, so Oracle Forms-based products requiring the Java Runtime Environment (JRE) plug-in are not available on iPads.


  • Oracle E-Business Suite 12.1.3 and higher
  • iOS 6.0 and higher

What about iPhones?

EBS OA Framework-based products are currently designed assuming that the client device has a desktop-class screen (e.g. 1024 x 768).  Safari on iPhones also works, but given the smaller screen size, the user experience is not ideal.  We recommend using iPads for the optimal user experience when accessing OA Framework-based EBS products.

The use of Apple's Mail app to approve EBS Workflow notification emails is certified for both iPads and iPhones.

Using standards-compliant mail clients to approve Workflow notifications

Oracle Workflow is a key part of the E-Business Suite's technology stack.  It can be configured to send emails (via SMTP) that notify E-Business Suite users that certain EBS transactions are awaiting their approval.  E-Business Suite end-users can respond to those notification emails by clicking on a link in those emails, or responding with an email containing certain keywords in the body of a reply.

We test Workflow and E-Business Suite notifications using Windows desktop based email clients such as Microsoft Outlook.  We have tested Apple's Mail app as part of this iOS certification.  We do not currently perform any tests of Workflow notification emails with other mobile devices (e.g. Android, BlackBerry Email).

We would expect standards-compliant email clients to be able to handle Workflow notification emails properly, including email clients on mobile devices.  Some mobile email clients are unable to handle standards-based emails, and other email clients may truncate long Workflow notification emails.  These issues may prevent certain email clients on mobile devices from handling Workflow notifications properly.

If you encounter issues with Workflow email notifications on smartphones or mobile devices that can't be reproduced on standards-compliant email client, our recommendation would be to process Workflow notifications on the latter.

On a side note: technically-inclined readers might be interested to hear that we're aware of at least one web-based email client that does not comply with RFC 2368 in its handling of new line characters in mailto URL encoding.  Web-based email clients with issues like that will be unable to handle Workflow notifications properly.  If you encounter issues with web-based email clients that cannot be reproduced on a conventional Windows desktop-based email client, our recommendation would be to process Workflow notifications on the latter.

What about other mobile devices?

Other mobile devices are not certified yet.  If you have deployment plans for Android-based devices as EBS clients in your organisation, please drop me a line with details.  We are working through complications around fragmentation in the Android space, and insights into your requirements would be helpful.


Related Articles


Great work Steven,

I am waiting for an official communication for all Smartphone whether its a Android, windows or a blackberry :):)

Please keep us posted for the further updates.

As far as my business requirement goes I am working on Requisition (Internal and Purchase) and PO approval via smartphones, hope this is possible as far as our ERP is sending emails to user through their Outlook email client, then they could also receive these on their smartphones.

Any thoughts or suggestions?


Posted by Gaurav on April 17, 2013 at 11:54 AM PDT #

Hello, Gaurav,

As stated in the article above, you can use any standards-compliant email client -- on ANY mobile device -- to approve Workflow notification emails.


Posted by Steven Chan on April 17, 2013 at 11:59 AM PDT #

It's well known that the default Android email client doesn't like the encoded characters in the mailto anchors (e.g., &body=Do%20you%20approve:%20%27Approved%27%0D%0A%0D%0AApprover%20 will be truncated altogether).

Posted by guest on July 09, 2013 at 11:02 AM PDT #

We are thinking about using a mobile Samsung SAFE tablet product with Oracle EBS Forms in the shop. There is an open question whether this platform works with Oracle EBS Forms? Has any Oracle EBS Forms testing has been done on this platform? Thanks.

Tano Maenza
VP IT & Quality
Emerson Process Management - Daniel Division

Posted by guest on August 14, 2013 at 01:43 PM PDT #

Hello, Tano,

We have not certified any Android-based or Samsung devices for the E-Business Suite. I don't have any a priori assessments of how well those devices would work with Forms-based EBS content.

We are still evaluating different options for defining our certification strategy for Android. Feel free to drop me a line privately with more details about minimum Android levels that you plan to deploy. I'd be very interested in learning more about your plans for specific devices.


Posted by Steven Chan on August 14, 2013 at 02:34 PM PDT #

Do we have an example of "standards-compliant email client" on android platform?

Posted by guest on January 13, 2014 at 08:23 AM PST #

Hello, Guest,

I'm afraid that we don't have much visibility into Android email clients. The degree of fragmentation on this platform makes it difficult for us to make any statements about compatibility that will apply to all devices from all vendors.

You might have better luck following up directly with the vendor of the specific Android device that you're evaluating for your enterprise rollout.


Posted by Steven Chan on January 13, 2014 at 09:19 AM PST #

Hi Steven ,

I have business requirement for running oracle applications R12.1.3 on Android Devices , Kindly let me know how i can run on Android ..

Posted by Arshad Ahmed on February 27, 2014 at 02:31 AM PST #

Hi, Arshad,

We're working on our Android certifications now. You can monitor this blog for updates.

Like all vendors, we're struggling with the challenge of Android fragmentation. What are your organizations policies or standards for Android devices? In particular, what standards are you setting for Android models, versions, and minimum hardware prerequisites?


Posted by Steven Chan on February 27, 2014 at 11:21 AM PST #

Hello Steven,

I'm posting here since our question is directly related to iPad / Safari browser certification for EBS.

We know that certifications are for browsers regardless of the OS platform where it's running. However, in this case our question pertains to the certified EBS 3rd party SSO integration with MS-AD which largely depends on the OS platform and browser combination.

We have implemented Zero login SSO for EBS 12.1.3 following the OAM 11g to MS-AD integration (using WNA and Kerberos / SPNego tokens) authentication for users running Win 7 / IE9 clients. However, a subset of those same users already authenticated on Windows and MS-AD network domain will also need to access EBS SSWA pages using iPad / Safari.

Would like to know if there are any certified or recommended methods for leveraging our live 3rd party SSO integration with OAM and extend it adding seamless authentication (i.e. WNA-style / zero sign-on without userame/password) for EBS users on iPad/Safari. This would greatly help with deployment plans for iPad devices as EBS clients.


Posted by BouMiro on May 07, 2014 at 08:22 PM PDT #

Hello, BM,

Thanks for the insight into your deployment.

We're examining options for providing some degree of Single Sign-On-like functionality for mobile devices. The challenge, naturally, is that a desktop-based security token from, say, Windows Kerberos, can be shared with a desktop browser to allow for chained security via Oracle Access Manager.

These types of locally-stored tokens on desktops cannot be easily shared with mobile devices. Complicating matters further are the sandboxed approaches that iOS and Android use for security.

This is technically very tricky, but not necessarily insoluble. I'll provide updates here as they become available.


Posted by Steven Chan on May 08, 2014 at 11:56 AM PDT #

Thanks Steven,

So I take it that, for the time being, there are no Oracle prescribed or certified methods to implement EBS WNA SSO for iPad mobile devices.

I missed to mention in my earlier post that we have raised a SR to OAM product support requesting support for iPAD /Safari SSO integration with OAM 11g and EBS AccessGate; support has filed the following ER on our behalf:


Posted by BouMiro on May 12, 2014 at 03:55 PM PDT #

I do not see any mention of support for Sales for Handhelds in the EBS 12.1 suite. Is the iPad support available for this module? iPad / iPhone are not listed in the supported devices in the implementation guides. It would be extremely useful to have this support. Would you be able to comment on whether this support is available or planned for in the near future?

Posted by Narayan on December 04, 2014 at 11:17 AM PST #

Hello, Narayan,

There are no immediate plans for this right now. I've passed your feedback onto the EBS Sales team for their review.


Posted by Steven Chan on December 16, 2014 at 09:19 AM PST #


Can you explain why email workflow approvals accepted from a Samsung Galaxy device cannot be read by Oracle? Below is the email encoding for the response from a galaxy device. The email is encoded correctly, and the NID number is complete and correct. To me, it seems the email is very simple to parse. When comparing a response from Samsung's email application with a response from desktop Outlook within Outlook, the emails appear identical, which means Outlook decodes the Samsung email the same as it's own email.

Samsung Email Encoding:

<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body> Action: 'Approve'<br><br>Note<br>Note: ''<br><br><br><br>NID[9688022/79920227939048985467652147795754861193@WFMAIL]</body></html>


Posted by guest on June 17, 2015 at 11:53 AM PDT #

Hi, Steve,

That seems like good reasoning. I can't explain this anomaly.

Back in the day, some mobile email clients (e.g. Blackberry) did something odd with their reply formatting, which ended up corrupting the response in a way that confused Workflow. We could never fully reproduce those issues.

Can you log a Service Request with the details on how to reproduce this issue? Please include the Samsung Galaxy model number as well as the Android version and code level. I can't promise that we can fix this, but it would be very interesting to investigate this further.


Posted by Steven Chan on June 17, 2015 at 12:32 PM PDT #

Hi Steve,
One question:
do you know whether ADF screens would run on the Ipad mini ?
i.e. EKanban pages (the only ADF screens I'm aware of) ?

We are currently planning a bigger customization using ADF technology.

Potentially we want to use iPad minis for the end-users .
Do you see any challenges here ?

best regards,

Posted by guest on June 24, 2015 at 01:46 AM PDT #

Hi, Enno,

ADF works on iPads.

Externally-integrated standalone products do not fall under the usual EBS client certifications. You'd have to check with the E-Kanban team specifically to verify whether they have certified with iPads.


Posted by Steven Chan on June 24, 2015 at 08:52 AM PDT #

Hello Steve,

My company has decided to adopt windows 8 smartphones (Nokia Lumia 830) as standard devices for corporate users. We are talking about more than 300 devices. Is there a roadmap to enable apps also for Windows Mobile?


Posted by Massimiliano on October 22, 2015 at 07:17 AM PDT #

Hello, Massimiliano,

No, we do not have any current plans to expand our mobile certifications to include Windows Phone devices.

That said, Microsoft's strategy is for Windows Phone to use the same core code as Windows 10-based laptops. If this is true, then it is possible that our Windows 10 certifications will also apply to Windows Phone-based devices. You may wish to run some trials to see whether your target devices can be upgraded to Windows 10, and then evaluate the compatibility afterwards.


Posted by Steven Chan on October 22, 2015 at 09:30 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed


« July 2016