cleanFiles/bookmap_SAP_Integration_Suite_in_a_Nutshell_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2024-08-27T13:32:13.000Z

Connecting Seamlessly with Your Business Partners

Modernizing Integration with SAP Integration Suite

SAP_MOOC_btp5_Lesson_10_CSBP_Video.mp4

My topic is B2B and my name is Marco Ertel and I'm working in the product management of the Integration Suite. So let me show you how to connect seamlessly with your business partner. In the Integration Suite we have several capabilities and here you see highlighted the capabilities which are needed for business-to-business integrations as these are slightly different from A2A integrations. We are using cloud integration as the runtime capability for the integrations and for the design time we're using the integration advisor and the trading partner management. The B2B integration or business to business integration is slightly different from the A2A integration because of several things. The complexity is most often much higher in B2B integrations compared to A2A or B2G integrations because a lot of different communication protocols are needed like AS2, AS4, SFTP and others. But also a lot of different standards are used. Standards might be Adafact, X12, TraderComps, GS1 or others and very often, each trading partner is using a different of these standards. Then, each of the trading partners want to exchange not only one but several documents and these documents are differently and have to set up differently and therefore more than 10 documents per trading partner is very common. And the part which increases the complexity at its most is the pure number of trading partners. So we are very often see integration projects where not only 100 trading partners are there but very often more than thousand trading partners are used and therefore if you want to set up an integration there the complexity increases a lot. This was the reason to develop two different capabilities the Integration Advisor and the Trading Partner Management. The Integration Advisor has several parts in it, kind of pillars, the type systems, where we store all these different standards, then the editors for the mix, the message implementation guidelines, the editor for the max, the mapping guidelines. And out of this knowledge, we are then generating runtime artifacts, which will then be used in the cloud integration. But we also generate documentation out of this. You also see here an external database, the so-called knowledge graph. Here we are using machine learning algorithms to improve the MIGs and MAGs. So this means, you start by defining your message implementation guideline and get help by this knowledge graph. So you get a kind of proposal how a message implementation guideline, how your interface is structured in your system. You do this for source and target structure. And then you also get a kind of proposal for the mapping. This means, how mapping can look like in your business process and in your area. This really helps saving a lot of time, because here you already get a kind of finished mapping. You refine it. You add documentation. And out of this, you can then generate the runtime artifacts for the Cloud Integration, but also for the SAP Process Orchestration, and documentation in different formats like PDF, but also for Excel. The next part is the Trading Partner Management. You have now used the Integration Advisor to create message implementation guidelines and mapping guidelines. In the Trading Partner Management, you store now data about your own company, but also about your trading partners, and you define your B2B scenarios, where you reference the message implementation guidelines and the mapping guidelines, and push this via an activation step down to the runtime, to the cloud integration, where the partner directory is storing all the data and the generic integration flow can then use this data to really run your B2B integrations. On top of that, there's also a B2B monitor with which you'll get more insights after your interchanges have been finished. And with the use of the integration suite, you see now that you save a lot of time because you do not have to change between different systems. So all the phases of the project, starting from the requirements collection to the message implementation guidelines to the mapping guidelines, over to the implementation, testing and correction and deployment takes place in the SAP Integration Suite. And therefore, you save a lot of time and a lot of media breaks. And with this, let me jump to the system, to show you how this really works in systems. Now, let's have a look in the system how B2B, business-to-business integrations, look like. For this, we have added under Design the B2B scenarios. Here you see different parts. The company profiles, the partner profiles, the agreement templates, and the agreements. In the company profile and in the partner profile, you see information around the company or your trading partners, like names, addresses, contacts, but also identifiers, how this company identifies in the interchange, but also in the backend system. Under systems, you see then, how the system is connected, what kind of type systems the system supports, and also how to reach that system with more technical information. Also for security reasons, certificates, and other security parameters. Under the agreement templates, you define your B2B scenarios. This means of course you know your own company and which kind of type system is supported there, and also the version and the identifiers, but also the scenarios are defined here. This means we have several transactions in this scenario and let's have a look in the first one, the purchase order request response. This means your trading partner will send in a message via this adapter, but at the moment we do not know which trading partner really will use that, but we know you have an S4 system and the system can be reached via that channel. The system will then send back an order response, and we also know the structure of this order response. Now, let me show you how to onboard a new trading partner. For this, I've already prepared one. And you now see that this trading partner is visible here to Markus Tullius Grocery with all the needed information. And in our scenario, we now see also the exact communication details of this company. We also have access to the structure which this company uses, which is defined in the integration advisor, where we also have the possibility directly to jump in the structure of the integration advisor. The mapping, which is also referenced from the integration advisor. And with this, our process can run and we can have a look how this looks in the monitoring section. Our trading partner has now sent a message and we want to see how this looks. We have added here on the monitor an entry B2B scenarios where we get more insights than only from the technical monitoring of cloud integration. We see here the messages, in this case, from the last 24 hours, which have been coming in or also sent out. Let me open one and you see this was done with Markus Tullius Grocery, it was completed. And we get here more insights, complete status is green, it is completed, everything has worked. And we can see here, what this partner has used for protocols, the identifiers of sender and receiver. And we also have access to the payload which had been sent in by this company, and also how it was mapped to the format our system needs for this. And with this, you have seen how B2B integrations in the Integration Suite using different capabilities is working. Now, after you have seen how this works in the system, and you heard the theory, you get now an understanding of the required capabilities. You have an idea of the advantages of the Integration Advisor and also of the benefits of the Trading Partner Management. Thanks a lot.