Announcement: SAP Trading Partner Management and B2B Monitoring brand new capabilities of SAP Integration Suite is released!
The Integration Suite family extended it´s B2B offering with a new capability and features:
- SAP Trading Partner Management (TPM)
- B2B Monitoring of the designed scenarios deployed via TPM
This new capability provides a Trading Partner centered view of Business-to-Business integration scenarios. This new design time capability is tailored to meet the needs of your B2B data exchange such as the individual definition and configuration of specific electronic exchange of business data between you and your trading partners.
B2B users have different levels of requirements for data exchange starting from the different kind of communication protocols such as AS2, SFTP, etc. to the usage of different types of B2B standards such as ASC X12 or UN/EDIFACT or APIs. TPM helps you effectively manage B2B relationships with multiple trading partners. The easy-to-use user interface helps you cope with the complexity of B2B communication between trading partners.
Capabilities and key components of TPM
TPM, is a new capability of SAP Integration Suite. This application achieves the goal by using the entities and artifacts provided by the other capabilities of SAP Integration Suite such as
SAP Integration Advisor
- SAP Cloud Integration
The main idea is that you can quickly define and maintain individually agreed B2B scenarios between a user of the Integration Suite and the users trading partners. Individually means that there should be an efficient way to define the individual trading partner’s communication parameters, the kind of business transactions (business documents) should be exchanged back and force as well as how these business transactions have to be mapped so that these will fulfill the users and trading partners requirements. For this purpose the new TPM provides the following key components:
These components have roughly the following concepts and functionalities:
Company – The term company refers to the leading trading partner. The trading partner is usually the owner of the trading partner management system who covers the specific information and parameters that are necessary and reusable for setting up the B2B scenarios with trading partners.
Trading Partner – is a company, organization, or a subsidiary to which the owner has a business relation and where the electronic exchange of business data is required.
Trading Partner Profile – provides reusable information about a company, organization or subsidiary, which is relevant for setting up a B2B scenario. It includes eg. information about business identifiers (eg. DUNS number) used for setting up the communication with the trading partner to identify the trading partner in the B2B message payload and the type of B2B standard used.
Trading Partner Agreement Template – defines a B2B scenario from the company’s point of view, it is a partially configured trading partner agreement which can be used as a baseline to create several agreements with multiple trading partners. A B2B scenario describes the choreography of business transactions that explains which kind of interchange should be sent to a trading partner or received from this trading partner during each business transaction activity. An interchange is a payload which will be exchanged between trading partners in a business transaction activity.
Trading Partner Agreement – is an agreement of a bilaterally agreed contract between two trading partners for a given business scenario(s) whereas one trading partner is the “Initiator” and the other trading partner is the “Reactor”. An agreement is based on a template(s. above) and covers the aspects of a selected trading partner at the trading partner’s side of a B2B scenario such as the B2B standard, identifiers used in the business interchanges. It furthermore links to the individually defined Message Implementation Guidelines covering the customized interfaces and the individual Mapping Guidelines covering the mappings between these customized interfaces. These guidelines are provided by the Integration Advisor.
In our following blogs we will go into more details based on an example about the concrete steps and activities of a business expert how to onboard and create and manage a B2B scenario.
Once an agreement is created and activated the underlying generic integration flow at runtime will dynamically consume the configurations stored in the Partner Directory(s. also Fig. “Components of B2B capabilities” above). Remember, there could be several business transactions per agreement and you can have many trading partners with which you will have agreements. If you go for the current Integration Suite solution, you have to create per business transaction and trading partner at least one Integration Flow. You have to think about it, what does this mean from point of view of maintenance reasons. The new approach handles all these business transaction via one generic flow using the Partner Directory. The next chapter describes this generic flow in more detail, its behavior and how to get it running in your tenant.
How do the TPM related integration content gets deployed in the runtime?
At runtime, you will need to consume all those parameters to execute end-to-end scenarios from or to your business partners. In the following chapter you will see how to use the standard content delivered by SAP to execute your scenarios end-to-end in Cloud Integration.
For that we deliver you an integration package in the SAP API Business Hub. You can find it in the discover section of Cloud Integration.
Once you copy it to your workspace, you will see the 5 integration flows and the script collection that make up the package. The integration flows are divided in 3 steps.
The Step 1 (3 integration flows) gets the messages from sending party through AS2, IDoc or SOAP adapter. With information from the incoming message, it finds an xslt mapping in the Partner Directory and extracts with it the payload from envelope and other information needed to find the corresponding Trading Partner Agreement in Trading Partner Management.
The Step 2 uses the information extracted in Step 1 to find the applicable Trading Partner Agreement. With the information from the agreement the incoming message is transformed into the outgoing message and delivered to Step 3.
The Step 3 takes the final message and delivers it to the receiver party through AS2, IDoc or SOAP adapter using the communication parameters extracted from the agreement in Step 2.
The integration flows also uses the information maintained in the Trading Partner Agreement for other purposes if required:
- decrypt/verify incoming messages
- generate and send functional acknowledgements
- split bulk messages in individual messages
- validate incoming or outgoing messages
- generate the document number for the final message
The Business to Business (B2B) Monitoring view allows you to check the processing status of your B2B interchanges. An interchange is the incoming payload for B2B transactions. To start monitoring the results of the end-2-end process, you need to configure and deploy the integration flows as explained in the document “Trading Partner Management-Setting up generic integration flow” contained in the package.
Once configured and deploy you can start sending messages to your Cloud Integration tenant. The concrete endpoints for sending AS2, IDoc or SOAP can be checked in Manage Integration Content of Cloud Integration.
You or your business partners will use those endpoints to send messages. For testing purposes, you can use your preferred client, like Postman or Mendelson. The message will then appear in the B2B Monitor. There you will see the following areas:
- Red: filter
- Green: list of business documents
- Orange: status of business document
- Black: sender, receiver and agreement information
- Blue: events with link to the Message Processing Logs
SAP Integration Suite offers you with the latest release an accelerated and optimized approach to:
- onboard and manage your trading partners
- design your bilaterally agreed business scenarios
- operate & monitor your integration processes
whereas the focus area within TPM and the interconnected capabilities such as Integration Advisor for accelerated interface design and mapping is on Business-to-Business relevant content.
In trust we waked up your interest to try out our new offering you may start already with the Trial version or even consume this directly within your productive landscape. The guided steps described in our online guide.
To get a detailed overview of the Service plans, upgrade paths and regions availability of Trading Partner Management is described within the SAP Note 2903776
Within the next following blog we will guide you through how a concrete scenario should be configured and maintained so that you get the key assets and benefits of our offering.
Looking forward for your next Blog. I'm very interested on how to setup a concrete scenario.
A quick question? EXTENDED_PREPROC_XSLT, SOURCE_MIG_PRE_PROC, SOURCE_MIG_XSD, MAPPING_XSLT, TARGET_MIG_XSD, TARGET_MIG_POST_PROC & EXTENDED_POSTPROC_XSLT (have also seen references to EXTRACT_XSLT & ASSEMBLY_XSLT) are expected to live in the partner directory? So if we have 5 trading partners with the same source and target message we have to maintain five copies of each of those schemas and transformations? I am hoping that is a misunderstanding because that is awfully wasteful, and a lot of additional maintenance that shouldn't be required to onboard a partner, should it not be required.
Thank you for the overview.
Awaiting your next blog on how a concrete scenario should be configured/maintained & also for an example on how to onboard/create/manage a B2B scenario.
thank you for this great overview.
Did you already create a blog how a concrete scenario should be configured and maintained so that we get the key assets and benefits of the SAP offering?
Thanks in advance for your response.
thanks for your interest, on it, we keep you posted !
Is the B2B monitoring functionality tightly coupled with configuring iFlows using TPM?
Can we use this for our custom built B2B iFlows without any reference to TPM? If yes, how do we do it?
Please clarify and explain
yes it is tightly coupled with the TPM specific Iflows with the configuration params from TPM.
Open to exchange with you about your requirements in detail (eg. via a call) to understand your scope and requirements you require so that able to consume TPM.
"Within the next following blog we will guide you through how a concrete scenario should be configured and maintained so that you get the key assets and benefits of our offering."
Any updates on this? 😄
Thank you for the blog post, is there any information on the roadmap for extending features of TPM? It seems that the types of systems currently available to connect to are limited; either web based (AS2 or SOAP) external partners or SAP Based systems. Perhaps it is the case that these are only configure for the Integration Package as you mention in another comment.
I am very curious if Type Systems and Adapters can be defined and used in the current iteration of TPM.
Company and Trading Partner Type Systems