More Details

Basically in SAP-Terms it is an “ALE Message Handling System”  capable to Send IDocs and Receive IDocs with Unicode communication enabled.

That’s exactly what is shown in our SAP Certificate .
As CA-AMS, this tool partly competes with more complex “LE Converter” Tools usually sold for much higher prices. We don’t provide easy drag-and-drop field mapping like the before mentioned products. Our Tools are designed for automated background usage in a more “fire-and-forget” manner with a fixed configuration prepared in well-commented .ini-files.

Anyway, our products offer a wide variety of _enhanced_ file format
conversions during consumption of input-files and also on creation of target-file formats.
Enhanced Data Conversion includes the option to create csv, xml
or any other customer specific output format (json, yaml, …) through a flexible “template filling” feature. There we allow to compose a Target-File Structure using IDOC Fieldnames as variables. Target-File then is created by “filling out” that template structure with each IDOC Segement data. The structure and formatting of the Template is fully conserved including all Blanks, Line Breaks, .etc.

Instead of working field by field it’s also possible to operate format conversions on a per-character level. It’s literally possible to define complex conversion schemes by telling which character-position from IDOC-Structure should be placed on which character position in the Target-File.
Input- and Target-File always are flat “text” files, codepage is ISO8859-1 if SAP is a non-unicode System. If SAP is on Unicode the communication between SAP and us is UTF-16(LE), input/output codepage then can be any 8-bit or Unicode Codepage which can be derived from UTF16LE or also UTF16LE directly.
Some of the above conversion options for obvious reasons won’t work with output codepages with variable character length like for example UTF-8 using a 8-bit in-/output file codepage is strongly recommended for maximum flexibility in Enhanced Data Conversion scenarios.
The SAP Communication itself always is asynchronous transactional RFC.

Technically the product consists of two or more background daemons (on
Windows implemented as Windows Services) running unattended and completely maintenance free in the background of your Servers.
Supported OS Platforms are most SAP supported Linux Flavours and actual MS Windows versions (minimum 64-bit 2008r2). Versions forAIX, SUN Solaris and HPUX on Itanium could be build on request.
32-bit Windows below 2008r2 might also be supported on request.