Reputation: 2582
Currently we are running software from Seeburger company to transform e.g Edifact to iDoc. Therefore a lot of mapping files exist to describe this transformation in a proprietary language SEEXML. It has a file ending xml but it has just a bunch of XML tags (name, NewMapping,sourceMessages, destinationMessage) and it's own language in this textline tags:
Now the goal is to:
This is how a SEEXML mapping file looks like:
...
</textline>
<textline>//Variables part start
</textline>
<textline>
</textline>
<textline>global UNB_TIME$;
</textline>
<textline>global UNB_DATE$;
</textline>
<textline>global SNDPOR$;
...
</textline>
<textline>IF IsWorkFlowActive() = true
</textline>
<textline> Copy getInputValue("OWN.USER.ARCHIVE.SOURCE.FILE.IDENT") to ARCKEY$;
...
<recordMapping>
<fullname>UNB#1.UNH#1.G01#1.NAD#1</fullname>
<textline>// fill buyer details
</textline>
<textline>IF Trim(UNB.UNH.G01.NAD:3035) = "PE"
</textline>
<textline> Copy Trim(UNB.UNH.G01.NAD:C082.3039) to PE_PARTNER$;
...
<destinationMessages>
<destinationMessage kind="3">
<name>EXAMPLE_DEST</name>
</destinationMessage>
</destinationMessages>
</mapping>
I have also a reference for this language (BIC Mapping Designer Command
Reference) describing the commands like copy
, trim
and the path syntax (´UNB.UNH.G01.NAD:3035´)
Upvotes: 1
Views: 142