...
Reuseability is important when creating maps, so you don’t end up with one map per partner, but has the option of reusing the mapping for several partners when they need the same format. To accomplish this it is important to keep integration logic on the integration platform, and avoid hardcoding customer specific data or choises in the mapping. Read here how you can improve reuseability with Link: … Reuseability with mappings
Another great thing with the Link Xsl is you can easily define your own error codes with expected cause and solution for the error. This can be embedded directly in the Xslt as defined here: Embedding error code definitions in Xslt files
and it makes it very easy to direct errors to the correct recipient with the information for them to solve it. Often when doing a mapping some information in the source schema is optional while it is required in the destination. While this if often not considered an issue as he date is expected to be filled out, we all know this will not always be the case, and we would then like the errors to be directed directly to the persons who can solve it. One sample could be the GTIN number is optional in you ERP but the partner requires it to be filled out in the EDI file.
To create your mappings it is important with schemas. These help convert from/to xml, but can also be used to validate both in and outbut against the agreed upon schema using XsdValidate component. Read more about schemas here: Schemas to use for mappings
Reasons to Choose XSLT as a Mapping Language:
...