I had the great pleasure of talking with Paw Sandal Pedersen, who is
We did have a talk about BizTalk. It have been evolving much like SAP PI for the last long time. Microsoft have not wanted to say a lot about the future of the product, as they wanted more cloud usage. Now they have released plans of a 2019 version to give customers support for longer duration and the ability to integrate more with the cloud.
Logic Apps can be used by anyone
We talk about Logic Apps. It is Microsoft Serverless technology that
“Logic apps is this new way of creating integration, so as a developer you don’t have to think about which servers, you just pay pr. action, there is a lot of connectors, that helps you to connect to a system“, paw says and continue: “There are 300 connectors at the moment that Microsoft supplies, and you also have the possibility to create
It is fairly simple to start creating the Logic Apps, but you will need to know how to process documents in
There is also the Flow service, which allow business users to create Logic Apps without much knowledge on the background processing. So a Citizen integration approach.
One of the products that
I can see it gives a number of features in a more user friendly way, like partner management, documents tracking and easy creation of new EDI agreements. Often this is more or less only for developers or It Admins. It is possible to integrate with SAP using BizTalk SAP Adapter or Logic App SAP Connector, but there is currently no possibility to use SAP PI/PO as an engine for transformation and transport of the documents. If more customers ask then it could be relevant.
Many customers talk about API is the way to go but if you have 300 partners it can be a lot easier if you can follow one common approach for handling your partner integration.
We also talk about the Peppol a new standard for exchanging e-Invoices with European governments and also businesses. It contains the option to lookup partner information and then uses it for sending the data to providers. It will be interesting to see how the adoption of it will be.
We discussed that and other topics during the Integration Podcast. It was interesting to see how much Microsoft and SAP is looking when viewing their approach for integration.
In this podcast about Figaf´s Integration Regression Tool I take a look at some of the challenges, that SAP is facing with integration.
As an independent developer of both tools and courses regarding SAP I get to talk to quite a few customers when presenting my tool. And I can see how the tool can help them in the process of planning their workflow.
Some of the most common challenges I see are as follow:
- How the change in integration
- Cloud means
- S4 also impacts the way most will be doing integration
Key question: Where is your architecture?
Many people working with SAP are struggling with understanding CPI and how it should fit into their organization. There seems to be a spike in the number of requests for projects, and the developers have to skilled in both CPI and PI. It is of course very important to ensure that the developers do not break anything. The key question is where your architecture should be.
Automize your testing
Figaf´s IRT is a tool made for testing. It will automize many of the things you do manuale, and it will lower your number of errors. It will help you test:
- What kind of impact it will have.
- Will be more widly used
- Hope that we will be the place of choise for customers wanting a better testing framework
- Will see how we can integrate with it, when customers are there
IRT also offers Monitoring:
- CPI is quite a different way to monitor than PI.
- Need some external tool for it
The best way to implement
Finally, IRT gives you great input when you have to find out, when is the best way to implement:
- If you have the data in the delivery but
- Can see how the tool fits your organisation
- Regression when making changes.
I had the pleasure of having Luke Marson as a guest in the Integration Podcast who is a solution architect at Ixerv. He is an experienced solution architect and widely-recognized expert in SuccessFactors and SAP ERP HCM. He Provides end-to-end HR and HR technology strategy, advisory, assessments, roadmaps, transformation, optimization, and implementation services for large, global enterprise customers.
Luke Marson has been around the SAP space for a decade, more than half of that is within the SAP SuccessFactors space. He has been solution architect, integration architect, a lead consultant, a project director and also different roles over the years, working with customers on SAP SuccessFactors transformations.
A proven, powerful integration platform
There are a few different options, you can look at it from a perspective of middleware technology, from API´s and then from functionality within SuccessFactors itself. So, from a middleware perspective when you subscribe to employ central, as part of the subscription customers will get a subscription for SAP Cloud platform integration, and that essentially provides you with an unlimited amount of integration connections as long as one end of the integration, either the inbound or outbound, is touching the employee central system. Now it is a proven, powerful integration platform, previously SAP had up in the atmosphere into the employee central subscription. That´s still available for customers on request, most costumes are getting the news in the SAP cloud platform integration as their middleware employee central.
There are two core foundational API´s, there is the SuccessFactor API, that’s the original SOAP-based API and now the OData V2 and V4 that are taking over. There is also the Integration Center that allows business users to perform integration and developing reports them self. There is some collaboration between the two sides.
After doing a SuccessFactors project I do understand some of the complexity of the suite and what needs to be integrated. We cover some of the pre-packaged content where a lot of the modifications is because of customization on the backend SAP systems. Here some of your customizations will cause the integration to be more difficult.