How to decide when to move to SAP S/4HANA

Recommend This Post!Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+Pin on Pinterest

How to decide when to move to SAP S/4HANA

TAKE NOTE (Insights into SAP solutions and Emerging Technology)

In this Q&A, Shaun Syvertsen of Convergent IS says that SAP S/4HANA can be transformative — if your organization has the right mindset.

Why should organizations consider making a move to S/4HANA?

Shaun Syvertsen: If they’re looking at it as an opportunity not to replace their existing system in kind but to take a leap forward, then that’s a really exciting proposition. I think the folks aren’t ready to think about it that way should probably hold off until there is a broader community of people who have done an implementation. But for the folks are ready to make a leap like that, get in there, get a good partner, get a team from SAP Services and start prototyping.

So there are some organizations that should hold off on implementing S/4?

Syvertsen: Absolutely. If your organization comes out and says “We need to replicate all of our old stuff in the new system,” then they’re just replacing in kind and that’s a massively missed opportunity. So to those guys I would say hang off a little bit, not necessarily until it’s a more mature product, but until there’s a more mature ecosystem of organizations that are running it and can demonstrate why more modern business processes are leveraging that capability.

It’s also harder for an organization like a municipality to change some of its business processes. Some organizations aren’t as forward looking and they’re saying “It’s running OK so don’t bug me.” I’d say they are well served to sit back and watch a little bit. Also, I think for something [that is] legitimately new and that requires a different way of thinking about what it does and how to run a business on that, there’s a genuine shortage of organizations out there that can help with that kind of a transformation.

Read More.


UNDER DEVELOPMENT(Information for ABAP Developers)

Layer Aware Debugging (SLAD) in SAP Demystified

How many of us have had this happen during debugging? You need to analyze a bug, or you want to find out how an application works. And you don’t know where exactly to set a breakpoint. So you start the ABAP Debugger and start stepping through the code. And you keep on stepping through the code, endlessly, without reaching any of the application logic in which you are interested!
Well there is a solution and its called Software Layer Aware Debugging (SLAD), sometimes referred to as Profile Controlled Debugging. With NetWeaver 7.0 EHP2, which is delivered with Enhancement Package 5 of SAP ERP, ABAP brings you an elegant solution to the problem of reaching the code you want to debug with its software debugging tools.
The basic idea of layer aware debugging is simple: you separate the code in the system into the code that you want to debug and all the rest that you don’t want to see. You tell the New ABAP Debugger about this, and the debugger lets you jump right to the code you want to see, skipping over (optionally) all the rest of the code

Q&A(Post your questions to Facebook or Twitter and get the answers you need)

Q. I keep hearing that ABAP Development is moving to something called Eclipse. I use SE80, what does this mean to me?

A. Let’s start this discussion by defining what Eclipse is. Eclipse is an open-source development environment that started life in its current form around about 2001. It really started to gain momentum in about 2004, and since then a new version has been released near the end of June every year, each named after a planet or a satellite. Its mostly been used for JAVA development.

If you’ve been paying attention, you might notice that more recent features in the ABAP Workbench look suspiciously like features that you find in Eclipse (e.g., automatic code completion or coloring keywords differently from variables). Eventually, SAP decided to make the leap; in July 2012, SAP NetWeaver Development Tools for ABAP (ADT) was released. Everyone calls it “ABAP in Eclipse”. You download the ADT Package as well as Eclipse here at the SCN ABAP page
Eclipse is a step in the right direction, change isn’t always easy, and SAP quite rightly suspected that traditional ABAP developers would be horrified by the very thought of not performing development tasks in Transaction SE80 or its subset transactions, like SE24, SE37, or SE38. (This sound like you?)
So, there you have it… ABAP’s main development environment, the ABAP Workbench (Transaction SE80), has improved with each new release and has often added features found in another popular integrated development environment: Eclipse. Now, SAP has bitten the bullet and adopted Eclipse itself for ABAP programming. To install Eclipse, your backend system needs to be at least an SAP NetWeaver 7.31 SP 4 system. If you’re one of the SAP customers still on 7.02 or below, Eclipse is not for you.
Recommend This Post!Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+Pin on Pinterest

Pin It on Pinterest

Share This

If you enjoyed this post, why not share it with your friends!