
Figure 1: Components of Integration Content Advisor
![]() | General Information |
In addition to the available set of blogs, and videos, there is now an OpenSAP training course available. All the listed content gives you a good overview on the paradigm shift and how to you the Integration Advisor in general and detail. | Training courses:Open SAP Course: Integration Advisor Capability of SAP Integration Suite Open SAP Course: Accelerate Enterprise Integrations with SAP Integration Suite Related information:SAP Help Portal – SAP Integration Advisor Integration Advisor – Integration game changer! integration content advisor for SAP Cloud Platform Integration (to be updated) Videos:Appetizer video for L1 Integration Advisor, the game changer Integration Advisor: Overview |
![]() | Library of Type Systems |
The library of type systems is a centrally located collection of B2B, B2G, or A2A type systems. A type system has two main aspects:
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 interfac... SAP S/4 HANA and Ariba’s cXML type system/type system libraries now available at Integration Content... 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 Integration Advisor – new versions for B2B Libraries cXML, ASC X12 and UN/EDIFACT |
![]() | Custom Messages |
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:TBD |
![]() | Message Implementation Guidelines (MIGs) |
The Message Implementation Guidelines (MIGs) are used to specify the customized interfaces on business oriented level covering just these nodes and their requirements on which and how the information of message such as purchase order, invoice or despatch advice should be sent or received. MIGs can be created for the messages, which should be sent or received by the user's company, or by the trading partners of this company. Each trading partner might have different requirements, therefore it is suggested to create one MIG per trading partner and message type. A MIG is the basis for the creation of mapping guidelines (MAGs). As more a MIG is precised on its requirements and properties, as simpler a MAG will be. | Related information:Integration Advisor – Key concepts of a Message Implementation Guideline Create a customized interface using MIG editor The importance of customized codelists in MIGs Integration Advisor – The precision of semantics – Use of qualifiers Integration Advisor – MIG Qualification based on multiple Qualifiers !!!NEW!!! Integration Advisor – Extended semantic validation options for MIG structures Integration Advisor – How can I customize and generate Message Implementation Guideline hard-copies Integration Advisor – How do I document my Message Implementation Guidelines? Integration Advisor – MIG Qualification based on multiple Qualifiers Integration Advisor – support for multi-value Qualification in MIGs |
![]() | Mapping Guidelines (MAGs) |
A mapping guideline (MAG) is used to specify the mapping between a source and a target message implementation guideline (MIG). The intention is that mapping guideline will be very simple without much coding on the mapping elements itself. In other words, we want to get rid of all the complicated coded functions and technical oriented functional expressions. This aim is not finished yet. Therefore, it is still necessary using functions for a number of requirements. But we will always let you know, when and how an improvement for reaching this aim is available. A mapping guideline also have an embedded simulation in order to reduce the debugging on runtime. The MAG is the basis for the generation of runtime artifacts. | Related information: Integration Content Advisor: Create a mapping using MAG editor integration content advisor – Quickly create your individual code value mappings in MAGs Integration Advisor – List of supported XSLT elements and XPath functions Integration Advisor – Mapping element functions, the use of xsl:copy, xsl:copy-of, xsl:sequence, or ... Integration Advisor – MAG: How to create If-Then-Else Statements in Mapping Elements? Integration Advisor: Conditional Mapping Feature Integration Advisor – Mapping element functions for comparing nodes and values |
![]() | Runtime Artefacts |
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
| Related information: Integration Advisor – The Mapping Runtime Artifacts and their purpose |
![]() | Runtime Support |
Currently, the Integration Advisor supports:
The generaed runtime artefacts can be directly injected into the prepared integratoin flow at SAP Cloud Integration. | Related information: Support SAP Process Integration/Process Orchestration with Integration Content Advisor Integration Advisor: Functions at target side – Ordinal number for line items and segment count |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
12 | |
7 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 |