Highlights *MAPGUI

Each Mapping is Unique

*EDIFACT

• All EDIFACT message types
• All subsets
• EDIFACT <> ANY conversion

*FLATFILE

• FLATFILE <> ANY conversion
• AllfFlatfiles
• ERP connection, e.g. SAP IDOC

*DB

• DB <> ANY conversion
• Connection to DB2, MySQL, MSSQL and Oracle databases
• Commitment control(Rollback) for unbroken transactions DB2 Tablesin event of aborted conversion

*XML

• XML <> ANY conversion

*CSV

• CSV <> ANY conversion

*IDOC

• IDOC <> ANY conversion

*X12

• ANSI X.12 <> ANY conversion

*TRADACOMS

• TRADACOMS <> ANY conversion

Conversion

• Any2Any conzept
• Choose any input or output file from the IFS or DB2 System
• Flexible Mappings and Directories
• Module-based expansion concept (EDIFACT, FLATFILE, XML, X.12, CSV, IDOC, TRADACOMS...)
• Content based interfaces
• Power Systems based RMI-Server
• Power Systems based JOB-Server
• Platform independent graphical Mapping-Client (eclipse)
• RUNMAP-command as the start basis for mapping processes
• Integration of the i-effect^® Logbook for optimal monitoring of mapping processes
• Error correction and expanded logging
• Integration of partner core data
• Own subsystem on the IBM Power Systems

Graphical Interface

• Any modules in the source and target view (Any2Any-Mapping)
• Mapping Conditions to control value assignments on the target page
• Mapping Tasks (System, Base, Module, User) for value processing, formatting, and variable assignment which allows the use of functions (Mathematical, Date, Time, String)
• Mapping Trigger for precise control of mapping processes
• Mapping Variables as clipboard for values
• Creation of Guidelines (Mapping as PDF print)
• Wizard control support within the mapping process
• Individual module configuration with the graphic front end

Communication and Control

• Any data volume, unlimited number of trading partners
• Constant monitoring of background processes with the integrated logbook
• Standardized message monitoring

Master Data

• Central master data maintenance
• Maintenance of sender and recipient information with the central partner core
• Any number of communications paths per partner
• Unlimited number of sender addresses for partner aliases
• EDIFACT- and Flatfile based partner setting
• IFS archiving of input and output files in separate directories

Mapping

• Unlimited number of mappings: conditionally, based on partner master data, XML based
• Unlimited number of database input and output objects (SQLTables, physical and log files)
• Dynamic reading and writing of database records
• All database field formats
• Output of constants