PeopleSoft Reviews

This is an ERP product and the best use case is to raise your query to the HR manager. There is functionality built-in for the staff to raise their queries direction to HR.

The PeopleSoft interface is very good.

The integration with Microsoft Exchange Server works well.

The whole systematic flow of any query raised to HR should be improved. For example, if I raise a query, I cannot see the status. I don't know if it's under review, or if someone is reviewing it or not. If it is taking quite a long time and you're worried about it, then you can't see if somebody has had the chance to review it or not.

In the future, I'm expecting to see a complete user flow. It should be a complete flow of the process for the end-user and it should connect with the line managers, as well as others in the same area.

I have been using PeopleSoft for the past seven years.

This is a stable product and I prefer to keep using it in the future.

PeopleSoft is quite scalable. We have more than 2,000 users in our organization.

The technical support is very robust and I am satisfied with it. They will solve any technical issues that you have with the REP.

I have heard about several other similar products but do not have any experience with them myself.

This product is quite easy to install, although I'm not sure how long it takes to complete. It integrates with LDAP services and with Microsoft Exchange Services, so I think that it takes between two and three days.

From a technical perspective, it is not a problem for the end-user to deploy it.

Our in-house team is responsible for the installation of products and integration with other services.

There are no additional costs for licensing.

I can recommend PeopleSoft to all institutions and companies.

I would rate this solution an eight out of ten.

My primary use is to keep track of clients.

The most valuable feature is that it's easy to use.

An area for improvement would be that it's quite difficult to learn how to use this product, and the documentation provided isn't helpful in giving you practical advice.

I've been using this solution for a few months.

I'd rate this solution as eight out of ten.

The most valuable feature is ERP application information.

Having applications which provide more enhanced features and user-friendly elements.

We have been using this solution for 10 years.

We did have issues with Push notification and Fluid options.

There were no scalability issues.

Customer service is good.

Technical support is good.

We did not use a solution before this one.

The setup was complex, as it has multiple configuration changes.

We implemented it ourselves.

Check all options before a decision is made.

The most valuable feature for us is the integration between the HR Payroll and Financials modules. We really like the way they link and work together because there are no duplicate entries and the information flows from HR Payroll to Financials, and from Financials back to HR Payroll.

There are several ways it's improved our organization. It's an all-encompassing suite of applications, and the GUI is very user-friendly. Also, PeopleSoft has a mobile app that's coming out soon, which, to me, is very cool. My client's not there yet, but they will be within the next year. Even the desktop application is user-friendly. Overall, it's a full suite of apps so that you don't have to but individual component parts.

My developers want to use more HTML instead of the specialized tool, PeopleTools because, they say, it's better from a user perspective. 

Also, making it more configurable would be an improvement, so that users can modify it the way they want so that we don't have to customize it. What my team has to do is make customizations because, let's say, if you have HCM work and a work list from HCM and FSEN, when the user sees that, it's all in one window so that they can see what application that was from. If you don't have to customize, your upgrades are easier. You don't have to retro-fit all of your customizations if they can use the delivered functionality. When they deliver PeopleSoft, they could make it so that it's just a flip of a switch, instead of an actual code change.

Performing an upgrade takes a long time. I know that when they're talking now about how the new version 9.2 has new PUM updates, you're supposed to be able to do them. Oracle will advertise, "hey, you can do this in 4 weeks. Just implement, put it right in. Boom! You're done." But they don't tell the customer, "well, if you have 10,000 customized objects, it's not going to be that easy."

The bugs are always in the latest release, so I always tell my client to be one release behind, let somebody else find all those bugs, and their response time in fixing those bugs sometimes take a little while. The customer can't wait up to two months for a fix.

We've had no issues scaling it.

It depends on where your customer is coming from and how willing they are to change. I've had clients that came from a PeopleSoft mixed mainframe, and they were really on board and really wanted that change. They did a lot of training and it went very well. I've also had clients who came from J.D. Edwards that was totally customized. They loved it. They didn't want to change, and it's been hard overcoming the resistance.

Get your users on board and engaged. That's the number one thing. Get them in their training, which, unfortunately, is the first thing people always cut from implementation, and that's the last thing they should cut. When you're implementing a new product, you don't want to cut training.

The allocation tool is probably the most valuable feature for us in PeopleSoft. With it, we can schedule it to run overnight and then find out what happened in the morning. Previously, everything had to be kicked off manually, and now we can just schedule a batch to run overnight. I don't have to actually run it because I just verify it.

There are definitely time savings and greater efficiency. We had a manual consolidation process, and when we updated to 9.1, we used that delivered process as well. I think over time, we're adopting more and more of what's delivered instead of the workarounds.

I know we're looking at the cloud, and I think we're tying to become more progressive, but I think that's just a cultural thing where it might be a little slower for a company like ours in that we're very concerned about security. Our company is in a paradigm switch where we were the quiet company, but now we're trying to become more outward-facing. We're doing more spots for, like, hosting the NCAA, advertising, and things like that. So I think they're pushing the solution out and trying to see how we feel, and I think culturally it's going to be a little slower for us. It's just a comfort level that we don't have yet have with PeopleSoft in cloud.

But as for specific features, I'd like to see integration of chart-fill requests so that I don't have to put it on a shared point and so it's readily available for a new account. I'd also like to see Financial Close Management sit on top of PeopleSoft instead of as a separate Oracle product.

We use the allocation tool and have pretty intense allocations, so that works pretty well for us. Previous to upgrading to 9.1, we had a lot of customization. When we did that upgrade, we took as much customization out of that process, and now we're just using the delivered solution.

We sell products, are there seems to be screen after screen after screen of data, such as attributes. We don't really mine the data, so there's no use for us to have all that information upon deployment.

We don't have stability issues with PeopleSoft itself but with the feeds coming into it. I don't know whether those stem from the source systems or not. Also, sometimes there are slow-downs, but that's generally due to server issues and not just PeopleSoft.

There have been no issues growing it, adding more users, more licenses, or more seats.

We had what I thought was a simply question about our consolidation process, but to ask Oracle support how to troubleshoot that was really difficult. They want you to build your whole system a demo environment; that's a lot of work just to answer what I think is a relatively simple question.

I usually Google issues and solutions, but to actually go to the support site, and I haven't had a lot of experience with that, but the back and forth seemed like they were asking a lot of really broad information and trying to scale it down.

I wasn't part of the team that originally implemented it, but I was involved in upgrades. I think it was extremely difficult. I wasn't on the project, but I was there when they needed me, and inserted me where they needed me. We hired IBM to help us do that upgrade, and I think there were a lot of pain points. It was kind of a two- or three-year process. I think there was good and bad, but not perfect, but it was difficult.

You have to be flexible and open to ideas and know that it's not going to be a perfect solution. This isn't a reflection, I think, of Oracle or, in our case, IBM, our contractor. They were just the experts we brought in to help us.

The SOAP and REST features are the most valuable features. What I like is that we can have multiple web services created and multiple consumers can use them together without any interruption or downtime. It helps us to have a very reusable kind of environment where we can have a single service that can be reused from multiple sources.

I'd like to have a dashboard on a mobile app where I can check the health of all the servers and middleware, where I can get alert notifications if there are any critical services going or not going up at all.

I also think it needs to be a little bit more robust as we have faced some issues such as thread counts with stuck threads. These issues came up basically because of the huge volume of data transactions, so if something could be enhanced so as to make it capable of handling more data, that would be good.

There are load also issues with OSB, and it doesn't provide logs. What this means is that I cannot go and check what happened to my incoming or outgoing transactions.

We've been using it for more than two years.

We haven't had issues with deployment.

It is a stable right now from what we have experienced so far.

It is good from a scalability perspective. It could have a different kind of feature such as OSB so that data can be consumed from it directly from the consumer or from an IPA gateway.

I have not experienced many issues requiring me to contact technical support.

Once you get the feel of it and learn how to use it, the ease of use and performance are the most valuable features. It processes everything very quickly.

Because it's so fast, we're able to work much more efficiently.

It needs a better interface on the financial side because there have been more improvements to the RMS interface than the financial one.

We've been using it at the organization since 1996.

We've had no issues with deployment.

It's been stable. We've had no issues with instability.

As far as I know, we haven't had issues with scalability.

I'm a test engineer, so I don't deal with Oracle technical support. If I find anything that's not working, I hand it over to our developers. But I haven't hear any issues they've had with technical support not providing answers.

It takes some time in order to set it up and to implement, make changes, and deploy it to our users.

How you use it will depend on the size of your organization and the number of transactions you do on your backend. If you have a small shop, there are other more suitable ERP solutions on the market that you can implement quicker.

The fact that it's an all-enterprise solution is the most valuable feature to me. It's fully integrated with our HR and finance departments and works well throughout our campus infrastructure.

We're able to get great support and the latest updates that are convenient. I know much larger shops running PeopleSoft, which is great because we're a small shop and we're able to handle the ERP system as well.

I think that Oracle is making a lot of improvements right now with fluid implementation, new tools in the release of 8.5.5 and version 9.2, and the fluid interface. We just need to upgrade to the latest version. But in terms of what I'd like to see, I think it needs better integration with other parties. Right now, it's limited only to partners and it needs to integrate other technologies.

I transferred to the college eight years ago, but they've been live for 15 years. However, I did have the opportunity to implement PeopleSoft from our previous job and it's been good.

We've had no issues with deployment.

We're pretty stable. Very seldom do we have production errors.

What we have scales pretty well.

Technical support is very responsive. It's pretty much how you create the ticket. If I contact them when I need immediate help, they pretty much respond right away.

The initial setup was straightforward for us.

The way they've been supporting us, the way they've been upgrading the technology, I think it's great. There's only a few ERP as far as campus solutions go out there, and they're probably the best one.