Day: December 21, 2017

As we know, Mule Batch always runs in an async manner. But sometimes, it is required to send batch reporting figures (i.e. number of successes/failed records etc.) to the flow back for further processing.

Objective

Our objective is to create a simple REST API which invokes a batch process and sends the batch statics in the api response. https://goo.gl/sWB7G8 #DataIntegration #ML

It was a big announcement at SAP TechEd Las Vegas: ABAP will be available in SAP Cloud Platform within the next years.

Looking forward to the SAP Cloud Platform, ABAP will meet there all the cool new kids on the block – Blockchain, Internet of Things, Machine Learning and Big Data. But in my opinion more significantly  it will join a highly agile development environment. Git support and one-click deployments are already standard when developing in Cloud Platform.

A Git-Support for ABAP is already there – if you do not know it already check out the openSource tool abapGit, initialized by Lars Hvam.

And there is more in the ABAP world – especially in the last years SAP introduced beside new technologies like Channels or Drafts a lot of tools and features to increase quality, robustness and efficiency of the ABAP custom code development. But it is still seems to be open which of this innovations are supported with the currently most used product – the Business Suite.

Within the huge amount of new ABAP features which were developed in the last years and presented at the TechEds, I want to point out one, which is the best test frameworks I have seen till now – well its some time ago since I switched from the Java world to the ABAP world and I may not be up-to-date, but anyway. Let me present you …

The OSQL test double framework.

There are already test double framworks available since Version 7.40, like the ABAP Test Double Framework. But this new one – the Open SQL test double framework comes with a very powerful attitude: With only four lines of code any DDIC table or view and also CDS View can be mocked. In other languages like JAVA or Javascript this has to be done usually with extra persistence frameworks and a lot of extra effort. DATA sales_order type table of sepm_i_salesOrder. “* DATA(environment) = cl_osql_test_environment=>create(i_dependency_list = VALUE #( ( ‘sepm_i_salesorder’) ). sales_order = VALUE #( ( customeruuid = ‘10000404’ SalesOrderBillingStatus = ‘P’ CreationDateTime = ‘20161010’ … environment->insert_test_data( sales_order ). ”* the first line was not shown on the presentation slides – so please do not judge me for any bugs here.

Presentation slide and sample code extracted from SAP TechEd Barcelona session S4H232 – Automated testing within the ABAP programming model for SAP S/4HANA by Thomas Ritter

A really cool feature – and with the perfectly applied “chain saw” approach its something that can fastly increase the code robustness and contribute to a smooth conversion from Business Suite to S/4HANA … if it would be available also for a lower release than 7.52.

Innovation needs two sides

A lot of cool new features of the last two years are currently only available for S/4HANA. Certainly for some of them the enablement for the Business Suite will be nearly impossible, especially when they depend highly on the S/4HANA data model. For others an inventive solution could be the best way, like the Central Check System approach for ATC. And for others its in my opinion worth going the extra mile and making the feature backward compatible.

Sure, first of all, developers have to adopt the “new” features, for example Unit testing or ATC checks which are there since the early 7 versions. But done that a lot of developers will have to stay on the Business Suite and there seem to be currently no definitiv decision which features of the last two years releases 7.51 and 7.52 will be availaible also in the Business Suite.

I think it is crucial that as many of the brand new tools or enhanced features are downported to the  Business Suite stack. Otherwise the majority of the ABAP developers will not be able to use this cool new ABAP tires for years due to the fact that a lot of customers are not able to start immediately with transfering all stones from the Business Suite cart to the brand new S/4HANA cart.

 

  http://bit.ly/2CRY6t0 #SAP #SAPCloud #AI

The SAP Activate: SAP Activate Methodology for SAP Ariba – Project Management Workstream is live and was released Tuesday, November 28th. We are excited to bring this new solution specific implementation roadmap to the SAP Roadmap Viewer for project teams, customers, and partners to use during their SAP deployments. The roadmap’s purpose is to guide teams through the SAP Ariba deployment Project Management Workstream which can be found in the Prepare through the Deploy Phases of the SAP Ariba Roadmap.

The SAP Activate Methodology innovative adoption framework is comprised of six phases taking the project team from Discover through Run in a detailed Agile project set up. The Project Management Workstream for the SAP Activate Methodology for SAP Ariba is only found in four of the six phases: Prepare, Explore, Realize, and Deploy.

The purpose of the Project Management Workstream is to formally recognize that a new project exists and to initiate the work on the project. During this time the project sponsor and project manager work to align stakeholders ­ such as clients, customers, and SAP management ­ around a project and its scope, provide updated information for planning, and obtain a commitment to proceed forward with the project.

As part of the initiation activities the project manager conducts a handover from pre-project phase, creates a project charter document, scope statement document and establishes the project governance that ensures proper management process for the project. This ensures alignment between the SAP System Integrator, the customer’s project team, the partner’s team, the company’s strategic direction, and the satisfaction of operational requirements.

Key topics for the SAP Activate: Implement and Configure SAP Ariba – Project Management Workstream roadmap include:

* Guided content for teams to use for a guided step-by-step approach for each of the four phases that the Product Management Workstream can be found
* A comprehensive description of deliverables and tasks by phase for SAP Ariba – Project Management Workstream
* Helpful accelerators associated with each one of the project deliverables

The breakdown of the Project Management Workstream deliverables per phase are as follows:

You can find past blog posts in the SAP Communities space with tag #sapactivate, as well as in the SAP Activate Methodology Jam group (request access here), a community of 21k members already actively engaged in SAP’s Implementation Roadmaps for Cloud, On Premise, and Hybrid environments.

If this topic series interests you, check out our e-book SAP S/4HANA Cloud: Implementation with SAP Activate which is available from SAP PRESS. Let us know your thoughts and feedback either in the comments or join our Jam Group. http://bit.ly/2BKhwAI #SAP #SAPCloud #AI