The Figaf Seeburger Migration Tool (SMT) allows you to migrate your existing Seeburger BIC solution to a native B2B Add-on solution. It helps to update your message mappings to use the new schemas created with the B2B Add-on. It makes your migration process a lot faster and has reduced risk. Some of the benefits of using the tool look as follow:
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
So, on January 15. 2018 I held a webinar I webinar about SAP PI Migration. In the webinar, I talked about my 7 step plan for migration of SAP PI to a single stack. The 7 steps look as following:
Goals
Current integrations
Pattern mappings
Resource consumption
Migration phases
Development
Testing
The plan covers an initial assessment on your landscape and an idea of where you want to move your landscape.
Here you can watch the replay on the webinar:
If you want to know more you can also take a look at the blog post 7 steps PI PO migration, which was published on September 25., 2017.
You can also take a look at the slideshow: SAP PI/PO migrations – How to save time and lower risk on your projects:
Lastly, when you are interested in migration, you might want to take a look at this:
Seeburger Migration Tool The Figaf Seeburger Migration Tool (SMT) allows you to migrate your existing Seeburger BIC solution to a native B2B Add-on solution.
It helps update your message mappings to use the new schemas created with the B2B Add-on. It makes your migration process a lot
faster and have a reduced risk
https://figaf.com/wp-content/uploads/2019/01/SAP-PI_PO-migrations.png400700Taushttp://figaf.com/wp-content/uploads/2016/05/160510_FigafLogo_final_35cm_KW.pngTaus2019-01-18 12:50:242019-01-18 12:50:24SAP PI Migration webinar
One thing that I have been helping with is to help to understand, which mapping is used at the customer location. For instance in a migration project or upgrade project where they need to get away from using the Seeburger Message mapping to the B2B Add-on from SAP.
With the Figaf IRT tool, we already have a link from Message Mapping to ICO, so it would make a lot of sense to use that information to create a report. Then we only needed to understand what was used on your system and join the data.
What does a report look like? Check out the link below.
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:232019-02-26 17:33:41Migrating Seeburger to SAP B2B Add-on the fast way
Some time ago I created a webinar about SAP PI to PO migrations. I wanted to use the content and share it because it is quite useful for everybody working on a migration. I can see that it is some of the questions that I got on my latest webinar was also about the process. I do hope that this gives a better understanding of what is happening.
As with all things, there are 7 steps to make a good SAP Migration. So if you are in the process this is the steps that I would recommend that you take. It is assumed that you will migrate to a new system because it will make it easier to migrate a single interface at the time. If things does not work you will always have a backup plan.
The 7 steps are the following:
Goals
Current integrations
Pattern mappings
Resource consumption
Migration phases
Development
Testing
The process should be very iterative because you learn a lot in the process that you can use to migrate other interfaces. I the current integration you are going to map out all your existing interfaces together with what types of pattern they are using. This information will then be used in the migration phase and how it is going you may get input on how the next interfaces can be migrated.
You can view this in two different ways. Either you can watch my Screen recording video of it.
Or view the slides here and download them if you want to be using them.
I have also created a longer article about some of the SAPs you need to consider more in details in the blog SAP XI/PI to PO migration. It is not the same and the two have a lot in common.
https://figaf.com/wp-content/uploads/2017/09/7-Steps-to-SAP-PO-migration-1.png400700dgraversenhttp://figaf.com/wp-content/uploads/2016/05/160510_FigafLogo_final_35cm_KW.pngdgraversen2017-09-25 22:46:072019-02-26 17:33:437 steps to a SAP PI to PO migration
