Integration Advisor: Overview of components for building B2B integration content and further reading

This is an update of the blog integration content advisor: Overview of components and further reading from March 12, 2019. It was necessary, because of the name changes, significant updates of the content such as blogs, training courses, and the strategic shift of the Integration Advisor. The Integrastion Advisor is now primarily focused on B2B integration content building. The names changes are in detail:

  • SAP Integration Advisor capability of Integration Suite (short Integration Advisor) instead of integration content advisor
  • SAP Cloud Integration instead of Cloud Platform Integration
  • SAP Business Technology Platfrom instead of Cloud Platform

All the integration components at the SAP Business Technology Platform are embraced into the SAP Integration Suite as its capabilities. You’ll find more about Integration Suite at SAP Integration Suite on the SAP Community

The Integration Advisor isn’t just a mapping tool. It’s a cloud- and crowd-based toll for writing functional specifications for especially B2B integration scenarios, which can be directly pushed and deployed on runtime. The main purpose of the Integration Advisor is to provide intelligent and efficient content creation and maintenance at business domain level to support experts and citizen integrators without writing technical code based on a programming language. Artificial intelligence (AI) supports the entire approach for reaching the aim much faster, more flexibly, and with significantly higher quality.

As shown in Figure 1, the Integration Advisor unifies all the necessary components with a strong focus on usability, flexibility, transparency, and speed. The Integration Advisor supports all kinds of integration content building and maintenance, with currently a strong focus on business-to-business (B2B).


Figure 1: Components of Integration Content Advisor

This post includes a short overview for each of the five components and provides the most current links to more detailed blogs and further information.Quite important is that the Integration Advisor can’t be just compared with the classic and technical oriented integration content building tools like the message mapping tool that you find in SAP Cloud Integration or SAP Process Orchestration.

The Integration Advisor is a paradigm shift with the strong focus on, as I mentioned, the writing of functional specification on business oriented level. Therefore, in order to understand this paradigm shift, it is worth to have a closer look to the training courses and the mentioned list of blogs.

The library of type systems is a centrally located collection of B2B, B2G, or A2A type systems. A type system has two main aspects:

  • The rules and the methodology for defining the syntax, structure, and naming of message interfaces, APIs, and data types, and
  • The library of message interfaces, data types, and codelists that are based on these rules and maintained by a responsible agency.

These listed interfaces (message types) in a library of a type systems provide all the required information for specifying a Message Implementation Guideline (MIG), if this must be based on a B2B standard or de-facto standard provided by SAP.

Related information:

Discover B2B/A2A standard libraries (to be updated)

List of provided type systems

Integration Advisor – Latest B2B/A2A Libraries for creating and maintaining your customized interfaces and APIs

SAP S/4 HANA and Ariba’s cXML type system/type system libraries now available at Integration Content Advisor

Integration Advisor – new versions for B2B Libraries ASC X12 and UN/EDIFACT

Integration Advisor – Odette Message Standard

Integration Advisor – Now GS1 EANCOM Library available

Integration Advisor – Automotive EDIFACT Subsets (JAIF, Odette, VDA) now available

The component “Custom Messages” is a library of proprietary defined schemas and interfaces, which are not provided by the “Library of Type Systems”.

It can be build by just uploading existing XML schemas. Remark: These XML schemas have some limitations.

A custom message could be also used for specifying a message implementation guideline (MIG)

Related information:


The runtime artefacts do not just cover the mapping from a source to a target scheme. It is a set of automatic generated processable schemes (XSD) and transformation scripts (XSLTs) for

  • Syntax conversion such as from EDI to XML or vice very
  • Validation such as the declared nodes and supported codes, which are allowed in a payload
  • Pre-/post-processing such as for adding or removing information in front or after a mapping
  • Mapping, which is the mapping from values in source nodes to the corresponding (mapped) target nodes

Related information:

Integration Advisor – The Mapping Runtime Artifacts and their purpose

This post completes, for now, the series of blogs and information that explains the power of SAP Integration Content so you can use it for your own purposes. But there are still brilliant, game-changing approaches for accelerating integration content development in our backlog. Once they’re released, you’ll find an update here. So, stay tuned.