Today I discuss B2B migration with Kishore Enumula. Kishore works with the Salling Group (Dansk Supermarket Group) one of the biggest retailers in Denmark. He has just been leading a migration from Seeburger BIC to B2B Add-on from SAP. I see that many consumers are moving away from Seeburger and starting to use SAP B2B Add-on. Salling Group decided to migrate because they were their database had limited future support. They had no choice but to stop using the Seeburger tools. They had around 60-70 different message mapping they needed to migrate. The entire process took about six months to complete.
Salling had 2000 partners listed in the Trading Partner Management (TPM) tool. They used the API to re-create all the partners because it would have been too difficult to manually enter all that information. There were some performance problems and they needed to improve the CPA object cache to have all the partners defined. TPM also gave a good visibility to how was the active partners.
They created completely new mappings to the new structure, which gave the option to remove some of the old bad habits and use the new B2B functions.
In this podcast we also discuss:
- Reasons why migration
- Project time span and planning
- They build a tool for EDI team to manage the partners.
- TPM performance was good once they enhanced the cache
- Longtime archiving of EDI Messages.
Figaf notes on the project
If you are considering a migration project do listen to the podcast and get the takeaways from it.
We have two offerings that will help in the process.
- Seeburger migration tool. This will take the Seeburger Mapping and convert the structure of B2B Add-on. This will allow you to save many hours on the structure conversions. Read more on how it works on your SAP PI/PO system.
- The other is Figaf IRT a test tool that makes it easier to set up tests and run them. It supports EDIFACT/X12 comparison and the B2B Splitter. It have a lot of features and can be used for more than just the b2b migration. So it supports the full development lifecycle of SAP PI. Check it out at https://figaf.com/IRT.
I got a chance to get a conversation with Udo Paltzer, product manager on many integration tools from SAP, about the future roadmap of SAP PI Integration at the SAPSA/IFG conference. There has been a lot of discussion going on what it was and where customers should doing with their SAP PI/PO systems. It was really nice to get a chat with the Expert on the topic of what is the SAP direction.
A big topic is the use of SAP PI/PO where it will take us. So we do talk about it together with the SAP roadmap for it. What will the next release of SAP PI be and how you can influence it. What is happening to the BPM/BRM and ABAP stack. I had thought that the dual-stack option was complete of the table for the next release, but it may be possible that even it will be in the release. Though it is not a recommended option, and have not been for a long time.
Udo recommended that every user of SAP PI-systems upgrade to 7.5 (newest version), and he also mentioned that users are very welcome to write about any kinds of problems regarding to SAP Pi in the cloud. By doing so it is possible for SAP to react or respond quickly if necessary.
The new thing and useful is the option to run CPI on-prem to use for BPM processes, where you have some technical requirement. It is a pretty good way for SAP to be able to leverage dual delivery strategy, to have a rock solid PI for all the “standard” messages. Then they can deliver new innovation on the CPI part.
We also cover the new Cloud Integration Suite, which is the iPaaS offering from SAP around all cloud development and tools. It is pretty good to get your hands on to understand what to do and the model allow you to pay for the services that you use.
You can read more about the Impuls18 and IFG Integration conference here.
We did have some sound problems, so it is not an ideal sound. But the content is pretty good, I hope.
If you liked it please share it with your friends.
In this show I’m thrilled to have Harsh Jegadeesan, who is a product manager from SAP. He is responsible to for quite a few of the integration product as SAP and has a strong presence in SAP progress to API. It was a really interesting conversation where we covered a lot about what was going on with integration at SAPTeched and SAP in general.
This is the first time I do a live interview and in a bit noisy setting, but it should be possible to hear what we are talking about.
We do cover quite a few interesting things on the show.
- Using API as a way to remove the complexity of your landscape, as the bedsheet you use to throw over your bed to cover the mesh.
- Why is the API different than the Enterprise SOA. One of the differences Harsh mentioned was that E-SOA was a waterfall approach whereas the API is a lot more agile. SAP is using the same API for UI so they will do a better job understanding them.
- We talk about API and how to implement them in a customer landscape and how SAP is thinking about API.
- Open connectors: One interesting point I took away from it was that it was more a hub model. So you could have to multiply ie. CRM system and then you would just all the Open Connector with one standard interface, then Open Connector would ensure it is delivered to the correct CRM system if organizations use different settings.
- We talk about the Cloud Integration Suite and where it fits into the customer’s journey.
If you found it interesting please share it.