Please share with the community what you think needs improvement with Oracle E-Business Suite.
What are its weaknesses? What would you like to see changed in a future version?
Administration takes some effort. Administrating the technology stack is not so complex but application aware database administration and following the new methodologies like online patching can be a little complex and time consuming. Oracle should ease the administrators jobs and do some innovation on this administration area as well. Oracle Autonomous Database is Oracle's leading technology these days. Using a similar approach, application stack may become a little more self-managing. EBS still leverages Oracle Forms technology. Oracle Forms might be considered as an old technology when it puts the client machine into the picture. Clients are using their web browser to connect to the EBS and use several functionality and applications using the web browser only. However, some applications automatically runs Oracle Forms through a Java applet on the client. Of course, this creates a fast, easy-to-use client experience, but it has disadvantages as well, such as, the requirement to manage the client side java.
Sending alerts through bulk SMS. With the growing use of mobile phones, we would appreciate sending notifications through SMS.
Its user interface is not completely a web interface. It uses a lot of traffic which costs too much for a large number of users scattered throughout the country as they connect from their terminals to do their tasks.
The UI interface is not good. In addition, there is a constant challenge that new things are evolving and people are looking at new ways of connecting. They do not want to log into web interfaces. And, the standard UI does not give you flexibility. You need to have a specialist who will work on the workflow. If changes are made, alerts are required. This provides challenges. Additionally, if inventory gets linked with our OEM portals, you enter some number, order number, find the OEM number and then an inventory which you have ordered. You receive the GRN updates your inventory also, links with OEM, and we really good because then you'll know the third party hardware or whatever solution you're purchasing, what is the end of life, where is the end of support, when is the warranty ending, what is the new product coming? All things can be related. Right now it is a stand alone system that is not integrated, whereas today you're talking about global solutions things can be in database. Even if it is not loud, even then things can be dated because you have only given purchase order to your OEM, you're under warranty. We have the right to get the information. OEM has the right to push information but then ERP is not supporting us. None of the effort goes into that.
Reporting is a big area for improvement. It needs to provide the ability to extract data from the suite. Oracle has also been making a great effort to make E-Business Suite more user-friendly but there are still areas where a focus on User Experience would help.
Standard reporting needs to be changed. Many of the standard reports look the same as they did 20 years ago in version 10.7.
The iStore could be better.
I would like to see more integration with other systems.
Currently, Oracle is focusing on their Cloud ERP. Since Cloud ERP is being rebuilt from scratch using a different technology, it seems that their on-premise support is slow and unresponsive. This differs with SAP Strategy, whose cloud solution is moving to their on-premise solution.
* New hire on-boarding, employee off-boarding, etc. * More user-friendly fast formulas for all HRMS modules. * HRMS analyzers should be automatically updated to be the most recent because Oracle support always asks for the latest version of the analyzer output.
One issue with the product is because it build on a lot of older technologies, there is a substantial technical debt in the system. For example, the use of Oracle forms which are a much older technology, and are basically a two-tier client server setup shoehorned into a three-tier architecture, it might create issues over a wide area network. It would be good if the EBS team enables multitenant fatures beyond the current single pdb cdb architecture allowing for pdb snap clones in the same oracle cdb database.
Deployment of customization is complex, thus nobody is using it. Instead, we are deploying the same code on both filesystems (fs1, fs2). In order to follow standards, the deployment process should be as easy as before, in R12.1.