{"id":128247,"date":"2023-05-25T11:30:00","date_gmt":"2023-05-25T09:30:00","guid":{"rendered":"https:\/\/e3magpmp.greatsolution.dev\/?p=128247"},"modified":"2023-05-25T11:43:14","modified_gmt":"2023-05-25T09:43:14","slug":"s4-coding","status":"publish","type":"post","link":"https:\/\/e3magpmp.greatsolution.dev\/en\/s4-coding\/","title":{"rendered":"S\/4 coding"},"content":{"rendered":"

SAP Build or Clean Core<\/h2>\n\n\n\n

It's not easy for existing SAP customers to find their way through SAP's numerous offerings, roadmaps, software products and recommendations. With the advent of the cloud computing era, the call for immutable standards and Clean Core quickly became loud. But SAP also offers the Business Technology Platform with Embedded Abap, Steampunk, as a solution for individual tasks. Both, of course, have their justification. However, existing SAP customers must find their own way through the jungle of offerings.<\/p>\n\n\n\n

Clean Public Cloud<\/h3>\n\n\n\n

SAP's public cloud has to get by with almost no modifications because it is a standardized offering that thrives on being unchanging and the same everywhere. This naturally results in the advantages of automated testing and relatively low operating costs.<\/p>

\"\"<\/a><\/div>
\"\"<\/a><\/div>
\"\"<\/a><\/div>\n\n\n\n

Build and steampunk<\/h3>\n\n\n\n

But because sustainable added value is often only created through modifications, Abap programming naturally has a long tradition in the SAP community. For a long time, customization in the Z namespace was a real competitive advantage. However, in the transition to S\/4, the many Abap modifications present themselves as a stumbling block. Nevertheless, SAP will continue to promote custom problem solving with the Build program and the new Embedded Abap, or Steampunk. Abap RESTful Application Programming (RAP), Cloud Application Programming (CAP), Low-Code\/No-Code with SAP Build and Steampunk as Embedded Abap are just a small selection of the possibilities for how an existing SAP customer will be able to modify his ERP system in the future.<\/p>\n\n\n\n

Documentation and processes<\/h3>\n\n\n\n

Well-written Abap code does not need to be documented, is a statement of the E-3 Round Table<\/a> at YouTube<\/a> on the subject of coding. But what absolutely needs to be documented is the function of the modifications. Florian Schnitzhofer, CEO at Sysparency and a speaker at the SAP Competence Center Summit 2023<\/a> at June 1 and 2 in Salzburg<\/strong>emphasized in the E-3 Round Table that the knowledge of what the algorithm is supposed to do is often lost due to poor or missing documentation. He thus calls for stringent documentation of algorithms from the user's point of view.<\/p>\n\n\n\n

\n
\"YouTube\"

By loading the video, you accept YouTube's privacy policy.
Learn more<\/a><\/p>

Load video<\/a><\/p>