Better SAP EAM Through SAP Fiori and SAP S/4HANA

Better SAP EAM Through SAP Fiori and SAP S/4HANA

What’s the business case for SAP S/4HANA? That varies by company of course, but those with a vested interest in SAP Enterprise Asset Management (EAM), there are some clear benefits in making the leap from a legacy system to SAP’s latest ERP innovation.

From the user experience, to analytics and the ability to extend with SAP Cloud Platform, there are key differences in S/4HANA from its predecessors. There are challenges in moving to SAP S/4HANA, though. That’s why Martin Stenzig, Rizing CTO, took to the podium in front of a packed room at SAP-Centric EAM in Austin, Texas to discuss those key topics that SAP customers should keep in mind when considering the leap to S/4HANA.

Combining Mobility and Usability

EAM isn’t commonly something that happens on one laptop or in a single location. For many industries, maintenance is done by field employees, making the challenge of entering and accessing data a challenge—and one that requires mobile capabilities.

However, simply providing mobile capabilities to field maintenance workers does not guarantee adoption. Employees have to be encouraged to use mobile applications, and the best way to do that is by providing a simple user experience that makes work easier.

“The discussion is changing. It’s not anymore about mobility and usability—it is a combination of both,” says Stenzig.

For SAP customers, Stenzig points to the SAP Fiori user experience in SAP S/4HANA as way to take traditional SAP transactions that were tougher to access in SAP GUI and put them in a more user-friendly interface. Fiori is browser-based, which means it is can be accessed on many different operating systems, allowing a field employee conducting on a mobile phone or tablet to see the same screen as their colleague back in the office who may be scheduling the maintenance.

SAP itself point to the Fiori user experience as a key differentiator in asset management on S/4HANA versus asset management on legacy SAP ERP systems. However, Stenzig does warn that a key question to ask when considering Fiori Launchpad—it does require connectivity–as an access point for employees in the field is whether or not they will have access to WiFi or mobile internet.

Read more on how asset management differs in SAP S/4HANA.

SAP Cloud Platform Vision

An important piece of SAP’s plan for how customers deploy S/4HANA is utilizing the SAP Cloud Platform as a way to augment systems that would be considered vanilla by past SAP ERP standards.

“How SAP envisions SAP Cloud Platform is to keep core S/4HANA fairly static and with a sidecar approach transfer tables you need into the cloud,” says Stenzig. “If you want to build add-ons to SAP systems, do it out there (in SAP Cloud Platform).”

Stenzig explains while this strategy makes logical sense, it’s not necessarily easy to accomplish. It’s important to have a stakeholder drive the development on SAP Cloud Platform, because if so the time to innovate is reduced dramatically.

“If you don’t do anything with [SAP Cloud Platform] right now, that’s fine, but you need to get versed on it,” he adds.

Attend one of Vesta’s complimentary SAP Asset Management workshops.

The Basis Challenge

Stenzig said the biggest lesson that SAP EAM customers considering a transition to S/4HANA should consider is the importance of training SAP Basis teams for the move. Their tasks change with S/4HANA, going from not just working with the core SAP ERP system, but to previously optional components such as Enterprise Search. Basis teams must also consider working with SAP Fiori, which means different browsers and different security certificates. There’s also the integration with SAP Cloud Platform—these are all things that Basis teams need to know.

“The challenge we see is that Basis organizations simply aren’t trained—that’s not their fault, it’s normal while going to S/4HANA to underestimate that part,” says Stenzig. “Either contract somebody, train individual people, or make it part of the contract that you already have. As a partner, [Vesta Partners] is making it a contingency to make sure your Basis people can do what is required.”

Taking EAM ‘Out of the Stone Age’

Why make all this effort to move to S/4HANA? Well first, Vesta Partners EAM Codex can make the process easier and faster, but aside from that moving to S/4HANA is part of laying the technological footprint that can enable companies to take advantage of new technologies. That means SAP Leonardo and that entails—Internet of Things, blockchain, Big Data, advanced analytics and more.

“You want to get to the point where you can talk about predictive maintenance or digital twins, but you’ll never get out of the Stone Age until you change the foundation,” concludes Stenzig.

Learm more about building your S/4HANA and SAP Leonardo foundation with EAM Codex.

Search All Categories:

Better SAP EAM Through SAP Fiori and SAP S/4HANA2018-04-19T23:13:33+00:00

Asset Management Differences in SAP S/4HANA vs. SAP ECC

The Difference Between Asset Maintenance in SAP S/4HANA vs. SAP ECC

SAP S/4HANA® is SAP’s next-generation ERP, but here’s a little secret: Transactions in legacy SAP ERPs—such as SAP ECC—can be just the same in S/4HANA. Does that mean running asset management with S/4HANA is the same as running it in SAP ECC? Not quite, and the fact that S/4HANA is optimized to run on the SAP HANA database is a key differentiator.

“I hear comments that S/4HANA asset maintenance is the same as ECC, but SAP HANA is why certain things are only possible in S/4HANA,” says Karsten Hauschild, Solution Manager at SAP, who spoke at the SAP-Centric EAM conference this week in Austin, Texas.

The SAP Fiori Impact

Hauschild points to S/4HANA’s user experience, which is driven by SAP Fiori applications such as Request Maintenance and SAP GEO Framework. The former drives maintenance request notifications, while the latter taps into SAP ESRI to run SAP plant maintenance transactions via maps.

“The user experience from a workflow/work order perspective is vastly different from SAP GUI (SAP’s transaction code-driven user interface),” says Hauschild. “That’s from feedback we’ve gotten from current customers—that SAP GUI is ugly.”

There’s also a S/4HANA-specific maintenance scheduling application which is meant to replace SAP Multi Resource Scheduling (MRS) for scheduling individual technicians.

HANA-Driven Intelligence

The case for an improved user experience is about expanding the number of employees that can access the data in the SAP system, Hauschild adds. SAP GUI screens that aren’t part of Fiori apps have also been updated to look more like Fiori.

Beyond an interface that is prettier to look at, S/4HANA is also utilizing its in-memory database to drive embedded analytics and what SAP calls “Enterprise Search”—a keyword-based search function. The embedded analytics provide visualizations directly on S/4HANA transaction screens, while also providing automatically calculated KPIS.

Enterprise Search allows users to find transactions and information within the SAP system regarding a term—rather than looking up by transaction codes or work order numbers.

The Same, But Different

As an example of the similarities between the two ERPs, Hauschild says all plant maintenance transactions that exist in ECC are in S/4HANA, and have been since its launch. Overall, an SAP customer moving to S/4HANA from ECC doesn’t have to change business processes, it’s just the way SAP supports those processes from a user experience and analytics point of view—with Fiori, embedded analytics and enterprise search—that is different, he explains.

Now, that doesn’t mean that it will be a guaranteed breeze for customers to move old transactions onto S/4HANA—that process can still be arduous. Fortunately, that’s where Vesta’s EAM Codex solution comes into play, to speed up that transition to modernized SAP enterprise asset management.

Search All Categories:

Asset Management Differences in SAP S/4HANA vs. SAP ECC2018-04-19T23:10:34+00:00