PeopleSoft Reviews

Our end process is going through multiple procure-to-pay systems. So the most valuable feature of PeopleSoft is the collaboration that it provides between our procurement/purchasing and accounts payable.

Because it links our procurement/purchasing and accounts payable, we have a single way to track transactions.

PCM, the procurement side, is weak and is far from the strongest product. It leaves a lot to be desired with the integration of the contract management module along with the purchasing. There isn't really a strong way to allow folks within the organization view access to contracts without bringing that down to low-level security. It's just not flexible.

I've been with my current company for five years, and we implemented v9.2 in January 2014. Personally, I've used it for a number of years.

We've haven't had issues deploying it.

With our current implementation, we have some instability. But, I believe that that's something we'll overcome over time. Otherwise, it a mostly stable product, though there is still room for improvement in many areas.

As we've acquired companies, it's certainly been scalable for what we do with it. We've been able to integrate all of the pieces of the implementations back to new parts of our organization.

7/10 - Response time sometimes on what we consider critical issues to us isn't as fast as we'd like, especially with v9.2. We went in flat with 9.2.0, so there were a lot of bugs and things that we didn't realize were bugs until we called Oracle. Sometimes it was days waiting to find out if the issues we had had something to do to our system or whether it was with the product.

The most valuable feature is the continuous roll-out of bug fixes, new features, and functionalities. Oracle really listens to the customers and provides valuable content for when those PUMS come out.

It empowers users to perform ad hoc analyses themselves rather than having to go to IT or somewhere else. That makes it much more efficient for our users to do their jobs because they have access to data analysis in front of them instead of having to find that information elsewhere.

We struggle with release notes. There's a lot of information, and I would love to see release notes broken down into compartments. For example, here's security, this is what you need to do; or, here's the business side or the functional side, and it gives us the technical stuff. I would like to see the release notes deconstructed and then parsed out into, for example, I'm a technical developer or I'm a super user and I need to understand how this is going to change my business processes. I think that's where we've had some detailed workshops where we've had to dig that information out. Not that it's not there, but it's time consuming to do so. So it would be nice to have a bit more user-friendly release notes for the user community.

For HR, we've been using it for four years, and for finance, we've been on it for two-and-a-half years.

We've had no issues with deploying it.

I'd say it's stable because one of the things that we do is we separate all of our testing cycles. We do all of the initial testing in one environment, then we do integration, and then we do a brand new copy and production for our user acceptance. We have a few small defects that we have to resolve once we go live.

When we get to that part through Hypercare, which is usually where we keep project people on-site to help with defects, and we transition over to our support vendor, we don't see a dip or an increase in tickets. That helps. Because of our business people that have committed to doing that, it helps us keep the stabilization where it should be.

We are so excited about how this can scale. We know that everything is kind of hinging on version 8.5.5, so we're excited about it. I've had so many of my colleagues come up and say, "Anne, when can we do this and when can we go on 8.5.5?" I don't know that we can go this year, but we want fluidity and elasticity. We want all of this stuff. We love how they've taken the fluid pages and you can choose. If you're a super user and you need to get your hands on a keyboard, you can go classic. It's nice for our people that are out across the country. All they really want is to be able to use their mobile devices. We're all excited about it. They see the scalability and we feel like we're just getting our feet wet with it.

I love Oracle support. When we were going through our first set of PUMS last year, we did zero to 13, so it was a huge amount that we took on to do that many images all at once. We had probably half a dozen hot fixes that Oracle provided. I love that they were willing to help us. They knew that we were under some critical time frames and some of it was for the very user-facing applications, like travel and expense.

When you've got 3,000 people who are out there trying to approve expense reports and they're getting errors, technical support understood that and they responded very quickly. I am very happy with Oracle support.

We were on JD Edwards previously. We had been on it for 12 years. We had never upgraded so we're still going through a cultural shift in being on a product that is progressive, that is continually changing. We're trying to keep up with the usability side of it, which is a struggle for our users, but they're seeing the value in it and they're letting go of the old, comfortable JDE system. It's been a little difficult at first, but it's gotten much, much better in the last year-and-a-half.

You need to understand your core business processes. What are you really looking to get out of a software application? The application can do whatever you want it to do. Look at what your core processes are, look at what the application offers, and change your processes to fit that software.

Also, the more vanilla you can go, the easier it is, the better it is and the more value you're going to see when you go do PUMS, when you go to DBK, and you add all those bells and whistles.

Having a complete enterprise solution where all the reporting is in our own centralized system is great. Also, having capabilities for analytics and reporting needs is highly valuable for us.

It's improved or functioning as we went from a mainframe legacy system to an ERP solution, so it's just a whole different world. It's like comparing apples and oranges, as the benefits are all over the place because we didn't have the capabilities that we have now. It did take getting used to, but we're in a much better place.

It needs more reconciliation between the modules.

We've had no issues with deployment.

It is a stable product, and we have had no issues with instability.

It has scaled well for our needs.

We've opened tickets and the IT side handles that as I'm more on the functional side. We send the request to IT and they opened up the tickets, but the turnaround time is a little long.

It was a complex setup. There were a lot of man hours involved as it was a big project.

We implemented it with our in-house team.

No, we did a pilot program ten years ago and we already had the licenses and infrastructure in place for it.

Setup and configuration is key. It takes a lot. It depends on where you come from, though. If you're coming from another software that integrates, it's an easy implementation, but if you're coming from a thirty-year-old mainframe system, you're going to have some tough times ahead.

There are several new features in the PeopleSoft tool set that I've found particularly valuable, such as grid control and related actions.

It allows our business users to access information in a format that's easier for them to digest than just raw data.

The main area for improvement would be with performance in some cases, specifically with migrations. We've had to address some of those issues recently.

We've had no issues with deployment.

It's pretty stable, but it does depend on the release, like how early you are on the release that you are adopting. Stability on a particular version becomes better after a certain release of that version.

It has pretty good scaleability. We've had no issues scaling it for our needs.

The level of technical support varies, but we've been pleased with the ticket resolutions for the most part.

The implementation was done before I was at the company, but I haven't heard that it was particularly complex.

Get involved with the grassroots community, like conferences such as Collaborate and Alliance.

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.

The most valuable features most important to me are the web solution, the web interface, and the integration with other ECM products.

We've been able to customize it and add various modules to suit our suits. It's very flexible.

I know they have come up with some good analytical terms in the latest version, but I would like to see it improved further.

This is an area I would warn others about. I've worked on several implementations and there's a long period of time within which PeopleSoft needs to be implemented. It also comes at a high cost depend on how many modules that are implemented at one time.

It's been stable. We haven't had any issues of instability.

I think it scales pretty well. It's customizable so we can have all of our customer solutions which are most frequently used by our company and for PeopleSoft. We have been able to expand to different, new products and we're able to integrate them pretty easily.

I'd expect customer service to be better than they are. I give them a 6/10.

Most businesses that use PeopleSoft can easily make the system suit their business, so I think it's flexible, but it adds complexity to the setup.

Beware of the price as it adds up with additional modules.

With the way that my agency uses PeopleSoft, the most valuable feature of it is the ability it gives us to track our contracts and the release against those contracts.

The UI and appearance of People Soft needs a lot of upgrading and modernization. The current flow in the UI feel very clunky in comparison to the UI's of other sites.

I've used it for approximately two and a half years.

We upgraded to 9.2 last spring, so we've gone through that year-long cycle of challenges and getting it back up to running as smoothly as it was before.

Generally, it's stable. We haven't had any real issues with stability.

I think all the challenges in regards to scalability is getting more and more people to learn how to use PeopleSoft.

The company had been using the product for a long time before I started.

The initial setup was done before I started, but I haven't heard about it being particularly complex.

We've had a really excellent customer experience with it because of two main features -- it's easy to upgrade and it interfaces well with other systems. Ease-of-upgrade is important because we need to maintain the our workflow without the interruption of waiting for the system to upgrade. And we have other applications we run, so it's important that PeopleSoft can interface with them and everything works together.

There are a couple of areas for improvement, including better overall performance as well as an even quicker update process so that we have as minimal of downtime as possible. Again, it's very important that we maintain our workflow.

We've had no issues with deployment.

It's been stable. We haven't had any issues with instability.

It scales as we need and we haven't had any issues when it comes to not being able to scale.

We're in touch with Oracle support often. When we've created cases, the service has been very good. It's very consistent across all the Oracle products we use. Support is centralized in one location, so our service from them is consistently good.

The setup was easy and straightforward.