After the arrival of S/4HANA Cloud, many module consultants are worried that the standardization of functions and the reduction of configuration will affect their careers. The consultant will not go bad this way?
I don't worry about it at all.
The system configuration was originally only a small part of the work of SAP module consultants. Usually a SAP ERP project, designated as "system configuration", can be a good week. The greater value of consultants is to analyze business operations and design solutions.
The bigger challenge is actually SAP development consultants. Yes, ABAPers, you guys.
In addition to SAP's original factory, I estimate that more than 90% of SAP development consultants in domestic consulting companies are busy with their daily work and are still different from what they were 10 years ago. Regular development of reports, forms, system enhancements for complex points, cross-system RFCs or IDocs.
However, the immutable days will not be too long. When S/4HANA Cloud arrives, ABAPers will find that the skills they had already mastered will soon become insufficient.
Development model changes
In the article titled "Left and Right of SAP," I mentioned that the goal of SAP is to "Let SAP Leonardo and SAP S/4HANA together form the flagship product portfolio of the digital era."
You may not understand what this sentence means. I explained it ruthlessly according to my understanding: Starting from S/4HANA Cloud, it is not allowed to do development directly on the ERP platform. If you want to develop, please use SAP Leonardo. The foundation platform that Leonardo relies on is SAP Cloud Platform.
Do not talk nonsense, take a look at this picture.
See the bright English API in the upper left corner of the box? The future development of S/4HANA Cloud will be based on the API.
The new development model is called Side-by-Side. You can still develop SAP S/4HANA Cloud, but I'm sorry, the custom development program must be placed in the SAP Cloud Platform. To interact with S/4, please use API.
Obviously, this structure is complicated. What could have been done in one ERP system has become a cross-ERP and SCP system.
Can not help but want to chat a few technical details inside. The blue line in the figure above refers to the setting of "single sign-on SSO" between S/4HANA Cloud and SCP. In other words, let the two systems trust each other.
The Green Line is talking about how they establish data communication links. On the S/4HANA Cloud side, configure Communication Senario. On the SCP side, the HTTP Destination is set so that the self-developed programs on the SCP can access and operate the business data in the S/4HANA Cloud.
â–ŽAPI
What are the changes brought about by this side-by-side model?
The original OP version of SAP ERP, development is almost unlimited, if ABAPer is willing to modify the SAP source code can also be. The new model is completely different. On the ERP side, SAP has only opened a certain number of APIs for developers to call. The BAPI, BADI, BDC, and friends are familiar with bye bye.
On the SAP API Hub, you can see the API list for SAP S/4HANA Cloud, which is currently 138.
At the same time, SAP also provided documentation explaining how to call these APIs.
This means that, on the S/4HANA Cloud, it is impossible to change the source code.
Developers in the Leonardo era
Does the new model only add complexity and no good?
of course not.
"Three bodies" brought a concept of red, called "reduce the dimension." To put it simply, if two dimensions are different, it is basically difficult for them to compete with each other. The high dimension plays low dimension and the low dimension has no chance of winning.
The SAP Cloud Platform, or the SAP Leonardo concept introduced by the Side-by-Side model, in my view, actually adds a dimension to the original SAP development perspective.
The traditional ABAP development, whether Report, Form or enhancement, is mainly focused on the ERP system. The era of Leonardo weakened the absolute core of ERP. ERP became System of Records. The enterprise data hub is transformed into SAP Cloud Platform. Data from various platforms such as ERP, CRM, Concur, Ariba, etc., can be invoked by the SCP and further innovative development can be made.
Do you think this is nothing remarkable? Hey, I also forgot that the big functions of machine learning such as SAP Leonardo, big data, etc. can all be used in development. If this is not enough, companies assume that the use of Internet of Things, blockchain and other technologies, can also be integrated development of data from the ERP.
Here is another screenshot of the API Hub. This includes APIs from relevant platforms such as ERP, blockchain, and Internet of Things, released by SAP. The richness of the entire technology ecosystem is evident.
There are so many changes for the time being. Is it a bit tempting for developers?
Don't be impulsive. Let me quickly tidy up what knowledge and skills are to be learned in the cloud era.
S/4HANA Cloud: API, OData, Gateway, Communication Setting, Fiori, etc.;
SAP Cloud Platform: SSO, Destination Settings, WebIDE, UI5, Java, etc.
SAP Leonardo related: Machine Learning, IoT, Big data, etc.
Wait, is the traditional ABAP technology useless? Fortunately, SAP is already brewing ABAP on Cloud.
The tide of Cloud has arrived unavoidably, whether it's standing still or moving forward. Everyone has their own choice.
Ram Memory,Laptop Ram,Ram Computer,Computer Memory
MICROBITS TECHNOLOGY LIMITED , https://www.hkmicrobits.com