Over the last 6 months, our IRT application has expanded from just being an application that facilitates SAP PI/PO testing to deal with more of the full development process for SAP Integration. We have added the following capabilities.
Filter your SAP PI/PO alerts so you can see new errors and document how old errors can be resolved
Enable you to test SAP Cloud Platform Integration(CPI)
That you don’t need to install anything at the PI system to use the tool
Create Ticket to log which objects you have changed for any specific use cases, so you can document what you have done to solve a ticket.
Download the Figaf IRT white paper now
Test all the ICOs where an object is used like a message mapping
We have had some challenging trying to communicate all of the functions that we are supporting in the process and how it worked. So now I finally was able to create a document that tries to explain all the capabilities we have in an easy to read manner.
We have tried to make it as appealing to the business but also explain what we are doing to make the life easier for integration developers.
https://figaf.com/wp-content/uploads/2018/08/IRT-whitepaper.png400700dgraversenhttp://figaf.com/wp-content/uploads/2016/05/160510_FigafLogo_final_35cm_KW.pngdgraversen2018-08-23 14:06:592018-08-23 14:51:53Whitepaper of what Figaf IRT can do for your SAP PI/PO or CPI integrations
We have lately seen a large interest in the Seeburger to B2B Migration because SAP PI/PO customers are seeing as a way to bring down cost and optimize. There is a number of factors that allow users to achieve this
The new solution from SAP has a lot of advantages making it a lot more flexible and supports the newest schemas. It includes all EDIFACT, X12, Tradacom and EANCOM messages that you want to be using, so you don’t need to pay for each message.
It is also simpler to transport since they don’t require the use of the BIC to make the one to one mappings
It contains all the same adapters with some new features
The price of the solution is also included in your standard SAP PI price so you don’t need extra licenses to make sure you can communicate with EDI for your partners. So you can save money on the maintenance of the Seeburger solution.
You have the option to use the Trading Partner Management solution making it a lot easier to maintain many partners and the information from them.
When facing the migration there are some challenges that you must figure out how to solve.
Schemas are different so everything needs to be remapped
Test nothing happens with the output messages.
Budget and planing
1) Schema changes update from Seeburger
One of the issues is the schema structure between the Seeburger and the SAP PI B2B Add-on is different on some different levels. The root element is different but there is also some different naming of groups and fields. In the Swing tool you have the option to remap some fields, but then you need to take manually account of all the fields in all mappings. And if it is not done consistently then you can end up with problems.
I always want to optimize as much manual labor as possible as that is what we are doing with our Seebuger Migration Tool. Simply select the message mapping and the new target XSD and it will convert it for you.
We currently have the free introduction package that contains 10 mappings for free. It is normally 100 USD pr mapping. So it is a really good way of getting started with the migration. That way you can prepare your self for the migration project and understand the complexity and what you otherwise need to move.
In the video below you can see how to get started, requesting licenses that you get to select 10 off for free. Then run the migration. Running the migration for a message mapping takes a few seconds.
For any migration, it makes sense to test that nothing vital has changed. It is really crucial for EDI because the importance for the business, you cannot afford to be down for a period of time.
Even if the mappings are validated there is still a lot of components that you need to ensure is not messing up the flow. We recommend using the Figaf IRT SAP PI/PO test tool. You can use it for free for up to 10 Interfaces, so you can use it to validate the migration tool work. The Figaf Testing tool is build to make it really easy to fetch test messages from your production system, and then be able to use them on your development system for testing with. If there is any difference you know there could be something wrong. IRT has support comparing XML, EDIFACT, X12 and other formats.
If you purchase the migration tool for your full conversion we can find a good offer on the test tool.
3) Budget and planning
It is pretty difficult to get any budget for a migration project. In most cases, you will halt development for a period of time to perform the migration. It is more fun to spend the money o new development that helps the business. The biggest reasons for a Seeburger to B2B add-on from a financial perspective is that you can avoid the maintenance of the Seeburger application and use the license you already have. The support and maintenance of the new system may also be faster but it will not likely be something that will make it selling criteria.
I have created some blog post that covers more details on how to perform migrations in and make it easiest. They are focused on general migration but it will be the same concepts that are required for the other migration.
https://figaf.com/wp-content/uploads/2018/07/Seeburger-migration-1.png400700dgraversenhttp://figaf.com/wp-content/uploads/2016/05/160510_FigafLogo_final_35cm_KW.pngdgraversen2018-07-05 15:31:232018-08-01 10:52:50Migrating Seeburger to SAP B2B Add-on the fast way
With the newest release of Figaf IRT tool, we have been adding a lot of new functionality.
In this presentation, you will see how to test SAP PI/PO and SAP Cloud Integration.
The testing of SAP PI/PO is stable for collecting and getting test messages. It is fast to record messages for testing and running them is also fast.
Testing SAP Cloud Platform Integration is possible
Development Supporting is now in the system that allows you to create tickets and assign any object version to it.
Change Tracking now have a deep comparison of Repository Objects so you can see what is changed with a message mapping and contains a link so you can see the affected ICO, that should be tested.
Support tool to monitor errors in the SAP PI CMBA and setup triggers for it.
In the current roadmap, we have the ability to fetch test data on SAP PI/PO without installing a module. And to perform object change and the support on Cloud Integration.
Everything has been build into one application that allows users to develop faster and have better tracking of what will happen.
Yesterday I hosted a webinar where we covered how to migrate from Seeburger on SAP PI to B2B Addon on SAP PO.
In the webinar, I covered some of the biggest challenges with migration.
How to create a business case for it. This is one of the challenges that I cannot help that much with, the main reason would be to the Seeburger Licensing. I’m unclear what it would mean.
How to convert the mappings. The message structures have changed, so you will need to update the schemas. It is not much but you need to do it correctly to ensure nothing is changed.
How to get rid of the seeburger User-Defined functions. The B2B Add-on have some different approaches to variables and counters, you probably need to upgrade the mappings to ensure that it works smoothly.
How to ensure everything is tested correctly. You don’t want to coordinate a migration with your partners more than necessary. So you just want to move the mappings and then ensure you have tested enough in the process.
I have two products that work to improve such a migration
Seeburger Migration Tool to migrate your mappings from the old format to the new. https://figaf.com/SMT
https://figaf.com/wp-content/uploads/2018/04/Seeburger-Migration-to-B2B-Add-on.png400700dgraversenhttp://figaf.com/wp-content/uploads/2016/05/160510_FigafLogo_final_35cm_KW.pngdgraversen2018-04-20 10:46:292018-04-20 10:47:16Migrate from Seeburger to SAP PI B2B Addon webinar
Proud of the team to deliver the IRT 2.1 release today for SAP PI. We have now added some features to make it easier to testing SAP PI/PO.
Testing normally requires a lot of manual work it is also the case when you want to test SAP PI/PO. I wanted to make it faster and easier for users to perform testing because I hate testing but it is one thing that you must ensure is performed.
View the video below hear about the different functions and learn what they mean to you. Or read the overview under the video.
The main things for users are the following:
CTT (Change Tracking Too) is a tool that allows you to see how made which changes to directory objects/trading partner management objects and assign it to an issue/ticket number. So you get a better visibility to when something has been changed. This will be something we will expand to the repository to automatic test what has been changed.
Manual Test upload allows you to create a zip file with payloads that you can use to upload your test cases. This is really useful if you have migration from dual to a single stack or from another tool to PI.
Audit log to see how made changes to objects and see what is going on on the system.
Transfering from 1.4/1.5 for existing customers
Included a global splitter configuration if you are testing the EDISeperator file.
https://figaf.com/wp-content/uploads/2018/04/irt-21-release.png7321293dgraversenhttp://figaf.com/wp-content/uploads/2016/05/160510_FigafLogo_final_35cm_KW.pngdgraversen2018-04-05 14:19:212018-04-05 14:19:21IRT 2.1 released for SAP PI/PO including Change Tracking and Manual Upload
