Oracle E-Business Suite Reviews

The processes, for example, how you can procure to pay, are well implemented in the software.

The solution has other core processes that can be implemented with customers according to their needs.

It's the whole package of ERP which is so appealing in terms of really enjoying the product.

It's difficult for some customers to understand in the beginning. A user really has to understand the processes.

They are still developing out the E-Business Suite. I would like some things about contract management and the other parts of the procure to pay process to be able to standardize more for the public sector. That's the feedback I've encountered from clients. They've all chosen to go for custom made solutions now mostly due to this.

The solution could offer more integration with other toolsets. That's why NetSuite does better in that market. It's in the cloud completely and you can integrate with other software more easily. With E-Business Suite you have to use database links or something of that nature to establish better connections. 

Oracle E-business is not a cloud product.

I've been using the solution for 15 years at this point. It's been a long time.

The level of technical support you receive really depends on if you know who to reach out to. If you do, it's fine. For consultants like us, it's sometimes a little bit frustrating, because we know how to solve the problems ourselves for the most part. Yet, when we need Oracle, we have to fill in all these questions about standard things that we must deliver and query results and standard programs. 

We always provide enough information to be able to understand the problem. For us, we immediately get 5000 questions back when we log an issue and we've already passed that part of the process because we understand what is going on and what is going wrong. That can be a little bit frustrating. However, I understand why they do it. Oracle wants to know exactly what the issue is. For consultants, on the other hand, who recognize the issues, we would prefer not to have to go through the first line of support and rather be directed to someone we can talk to immediately. Right now, there's something like five steps before you can do that.

I can not say much about the price, because that's more of a question for management, and who deals with that directly. However, I am aware that the licenses are sometimes difficult for customers to understand. The pricing is a little bit expensive sometimes and how they come to the pricing is complex.

I'm a consultant. Our company has partnered with Oracle.

I'd rate the solution seven out of ten.

Based on my technical background on Oracle EBS, I can tell that the primary use case of this solution is having a sophisticated software, an ERP, in the environment. It is to have a software system that consists of global business applications with built-in integrity. Generally, my customers use it for their business applications: CRM, Financials, Human Capital Management, Procurement, Supply Chain and more. There are also some seperate applications outside these ERP systems, but mostly, they are also tightly integrated with EBS.

EBS is a software as a whole. It includes its own database (Oracle Database), an application server (Oracle Weblogic), and software. It has cross-industry capabilities and makes customers operate in cost-efficient way.  As an ERP system, EBS offers lots of applications built in. So it helps the customer to automate their back office processes and let them make correct, fast, and reliable decisions. In Human Capital Management implementations, customers benefit from having a complete HR system and do all the HR work using the EBS screens. By customizing the product, customers can make the application processes be compatible with their special needs. Localization and translation options are also available with the product. Although the software is built by an American company (Oracle), other languages can be enabled and localization can be deployed without touching any code. With these features that support having a global software environment, customers who are working worldwide also gain an advantage. 

Using EBS features like Oracle workflow, lots of the processes are automated and made easier. Mobile Web Applications can be used to make the relevant users be able to use the applications directly. Successful implementations, success stories, big install base, know-how and continuous support of the community (Oracle itself and EBS consultants), make the customers feel safe. With the integrated service oriented architecture gateway (SOA Gateway) of EBS, EBS APIs can be triggered outside (from Cloud or from other applications).. This feature lets customers be able to integrate their application with EBS easily. When core business needs something from the back office, it just uses SOA Gateway to retrieve the meaningful data from EBS. All the technology and software is from Oracle. This is also very important to be able to get single vendor support when required. The technology stack is built on Oracle Technologies. It is not hard to find an expert when needed both for development and administration.

When I put these aside, EBS saves time and increases the efficiency for the customers.  By using the tightly integrated application of EBS, customers, provide the solutions for their business from a single source. The ultimate application design, high-level software engineering and power of the Oracle technologies delivered with the product are felt at any moment.

EBS has lots of application families and lots of features. It is modular in deployment and flexible enough to let the customer increase the built-in capabilities and enable new applications when needed. These are very important things at hand in case there will be a need to expand the product capabilities and/or implement new projects.

EBS has a certain history. There is a certain know-how with documentation for almost all its use cases.

The product relies on Oracle technologies, the world's leading Oracle Database and Oracle application tier. This is valuable because, while it satisfies lots of customer requirements and standards, it also means that the technology layer gets continuous improvements and updates, as Oracle keeps the components on this layer always up-to-date.

EBS 12.2, the newest release also provides an Online Patching option for supplying near zero downtime both for applications (functional side) and the technology stack. This is valuable in mission-critical environments. Online patching removes the barriers for an upgrade because it is online. It gives the customers the ability to make downtime negotiations easier. Using online patching, they have planned downtime and it is measured in minutes.

For customers who are using a virutalized environment, Oracle delivers VM templates (for Oracle VM Server). This feature also provides easy enablement for applications.

High availability and disaster recovery architectures make the product continuously operate by any means. Continuity can be guaranteed with these architectures. 

Oracle gives high importance to this product and following a "Continuous Innovation" release model for Oracle E-Business Suite 12.2. EBS 12.2 will be supported at least until 2030.

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.

I have been using and administrating this ERP system (Oracle EBS 12.2) almost since it was released. I have used Oracle EBS for human resources and financials in one my ex-companies and I have worked in the implementation of several EBS 12.2 projects in different customer environments with different product families. It has been more than five years now. I have also used the earlier releases of this product, such as Oracle EBS 11i and R12).  Oracle continued to enhance the product over the years, so this is a review for the latest release, version 12.2.

It is quite stable. It has been in the market for a long time. It is a product of the Oracle Corporation and was created in late 1980s and Oracle continued to enhance the product over the years. The latest release (release 12.2) was created in 2013. Before that, we released R12 (12.1 and 12.). Even release 11i which is quite old, is still used by customers.

The architecture, code, and support are by Oracle. The product is stable and behaves as expected, according to the documentation. Customers can get the benefit from business continuity, recovery, load balancing, fault tolerance, consistency, and scale-out architecture when the implementation is done accordingly.  

It is highly scalable. It supports scale-out architecture with both load balancing and high availability. Applications can run on multiple nodes and database can run Active-Active on Oracle RAC (Real Application Clusters). This increases the computational resources. Note that, this is not only for increasing the throughput, but the high availability as well.

As EBS can leverage Oracle Real Application clusters techonology in the database tier, EBS databases can scale-out by adding database nodes to the configuration.. Thus, EBS database workload can be distributed to multiple Oracle database instances and EBS database throughput can be increased almost linearly. 

Similarly, in the application tier, we can have multiple application nodes working together to increase the application tthrougput.. In this context, we can have multiple application nodes, each have their own application servers (Weblogic), their own runtime and batch proccesses. By having this ability, we can increase application performance and make Oracle EBS handle several concurrent user connections.  Batch processing (which is called Concurrent Processing) can also work in the parallel mode (parallel across multiple application nodes) and can also leverage multiple Oracle database instances to provide better and guaranteed throughput.

When needed, more application and database nodes can also be added to the configuratio. We can also declare the role of these nodes according to our needs.. For instance, we can have one application node for serving the requests of internal users and we can have another application node for serving the requests of external users.. Similary, we can have a application node for serving all the web requests, and we can have another application node only for batch processing.

Having a multi-node application tier also provides high availability. That is, if we use a load balancer and configure our EBS well, application contiunity is guaranteed in case of a application node failure.

Moreover, EBS application and database tiers can be replicated to the disaster recovery sites for disaster recovery.. Oracle Data Guard Technology is used for database replication. A replication tool (such as rsync), a filesystem replication feature or a storage replication feature can be used for replicating the application tier to the disaster recovery sites. 

This type of a configuration can provide application continuity in case of a site failure..  Morever, active dataguard can be used for offloading some production reporting to Oracle EBS disaster site database instances..

Customers get their support from the Oracle support portal (support.oracle.com). Customers can also get local support from the Oracle Partner companies, which are quite capable of both implementing and supporting the solution. Both functional and technical support is available. Additionally, there are lots of public documents available, such as, books and blogs about EBS. This is also advantageous for customers who want to learn the product on their own and keep their support and consultancy cost minimum.

My customers and my ex-companies have used several custom and packaged applications before switching to EBS. They were using different application for different purposes. The applications they were using weren't modular.. 

The decision for switching to EBS was to have a centralized software system for bringing all the required functionalities and applications together. For one of my customer, the decision was made by head quarters which was located in another country. It was a big, global holding company and the head quarters decided to use the same software for all the companies under its control. 

Technically, it is straightforward. However, there are challenges in the functional side. This is expected as implementing ERP is a complex subject. 

When managed with a proper project plan and right resources, projects are completed on time and with success.

In most cases, I was on the vendor team that implemented the projects. In my experience, Oracle partners who are specialized in this area can be classified as experts with knowledge and real life expertise.

By using EBS, and putting almost all the functionality and applications integrated together inside this ERP, maintenance and consultancy costs previously required for different applications and application vendors can be reduced.

The labor and time required for manual data entry is avoided.

A better integration across the divisions is provided with these ERP implementations. This also provides a better visibility and reporting. Also, lots of business processes can be automated.

Thanks to online patching, Customers gain an opportunity to decrease their downtime.

In order to minimize the implementation and consultancy costs, business lines should have proper definitions. They need to have a proper way of retrieving their data, which should be structured well.

Both the current projects and future projects should be defined well. Licensing should be done according to current and near future plans.

Customer should do their sizing and understand their computational resource needs. They need to start sales negotiations according to their actual needs.

Customers should evaluate the partner who is responsible for implementing the project. 
The better the partner, the higher the success rate of the project.

We did evaluate other options. Customers usually evaluate solutions from local software providers. However, most of the time, enterprise customers conclude that those solutions are less capable than EBS. Most of the vendors that supply those solutions are quite smaller when compared to Oracle.. 

According to my experience, enterprise customers also consider SAP. In these considerations, the conclusion usually depends on the costs and are indexed to the success in the sales and pre-sales activities.

Customers can run Oracle EBS on Oracle Cloud today.. If the client's needs and expectations are met and they are compatible with the regulations they are subject to, they can also think of running Oracle EBS on cloud.

EBS r12.2. can be used in many industry  like oil and gas, energy, construction,health and care industries to implement Purchasing,HR,Finance modules in it.

It was complex to follow HR processes, such as leave application, approvals, and job applications. Now, they are integrated and managed from only one screen.

Online patching, which lets administrators apply patches on the fly and with minimum downtime to make it active.

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.

No, but you have to apply latest technology patches after base installation.

Yes, while using Shared Appl_top, you have to use NFS or related technology. But if your admin apps node fails, the second node cannot continue without the primary node. Manual interaction is required.

A seven out of 10.

No.

It was easy.

Do not enable any module that you do not use. Check them and disable, if necessary.

No, decision was already made before the project.

If your requirement is not so complex, give a try. For smaller ERP solutions, Oracle EBS is a complex solution which has complex requirements.

Process costing.

Improved visibility into manufacturing.

Costing: very good, in-depth analysis.

Reporting.

Management of supply chain in the petroleum industry: from requesting quotes from suppliers to issuing LPO, managing credit; and selling in cash, credit, and discounts.

Generating reports is more efficient: generating financial reports, employee reports, volume reports, and time attendance reports.

Accessing vital information on the dashboard: I can customize summarized reports to be available on the dashboard.

Sending alerts through bulk SMS. With the growing use of mobile phones, we would appreciate sending notifications through SMS.

It has improved the way we worked. Everything is now on a very well-centered database. Before, we would have things saved on Excel, but it would be on different versions, or someone would have it saved on e-mail, and it would not be saved as an Excel file. It became frustrating. On Excel it is definitely harder to keep things. With so many people in the company, everybody had his own version. Definitely that created a big disconnect. The Oracle E-Business Suite was not able to get reports. It was not able to get the connectivity. Now, we can use this solution to streamline the documentation and products of our organization.

The database is feature rich, no doubt. It is also a a tool that can easily connect an entire company. From this, you can build any BI orders. The reporting solution is good and it has a good database that connects with everything.

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.

The product does not crash. It is stable. 

We have not experienced problems with the scalability of the product. The only problem I have noticed is that sometimes the scales are not available easily in the market. Maybe in the future we will move to Linux or Interface Servers that will provide a lower cost solution. We will have to evaluate this in the future.

We are currently using the technical support because we have a relationship with Oracle to be able to raise tickets. We generally have not had many challenges.

The cost is high for this product.

When deciding on a solution, I suggest looking at the vendor, the stabiliy of the product and the tech support provisions. A business has to run smoothly, and the solution has to help ease that process.

The primary use case for this solution is for Governmental Fiscal Management Information Systems (GFMIS). This is a complete solution to manage the whole country Financial System.

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.

It costs too much. 

We are using Oracle E-Business Suite as our back-office system for HRMS, financials, and projects. We first implemented in 2003 and we've been upgrading to the release 12.2.6 which is our current version. It has been integrated with other Oracle and non-Oracle products.

Since 2013, IT Convergence has been growing at a two-digit pace and Oracle E-Business Suite has been supporting the operations and every new subsidiary/country that we have expanded to, minimizing risks.

We were able to grow from 250 employees, as of our first HRMS implementation, to more than 800 employees. In terms of financials, a 4x growth in revenue since the first implementation was possible by having world-class business software like Oracle E-Business Suite.

The most important features are related to the Financials and Project Management suites. Flexibility in configurations and how it supports business globally in a single instance are definitely the most valuable aspects of the tool.

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.

I'd rate it an eight out of 10. It is very stable and has all the required functionality. It's very flexible and capable of integrations. I think the technology has some room for improvement and the lack of embedded reporting creates a need for external reporting.