HOME

    EDI Resources Centre

 

 

  Inovis Catalyst:Map

  • The 2-way EDI Translator that automates your e-Business

Catalyst:Map is an optional module of the TrustedLink for Windows (TLW) software suite, providing a tightly integrated solution for all your EDI requirements. While TLW provides communications, message processing, and system administration functions, Catalyst:Map furnishes the link between your business applications and EDI-formatted data. It converts data from your user applications (such as accounting, inventory system, database, or spreadsheet software) into outgoing EDI documents (such as EDI purchase orders, invoices, or shipping notices etc.)

That information is then ready for transmission via TLW to your desired trading partner or EDI network. Similarly, Catalyst:Map converts incoming EDI-formatted data into files that are formatted specifically for your business applications.

The 2-way EDI Translator that automates your e-Business

INPUT PROCESS OUTPUT
Your Data Files Outbound Maps EDI Messages ready for exchange
EDI Message received from your Trading Partners Inbound 
Maps
Data input automated for your applications

A powerful development tool for EDI system developer !


 What is Data Mapping?

  Mapping

The integration of EDI documents with your applications is known as mapping. To facilitate these data mapping functions, Inovis Catalyst:Map and Harbinger STMAP also provides online dictionaries of EDI standards (both ANSI ASC X.12 and UN/EDIFACT). Each version and release of a standard document (such as version 4010 of the X.12 840 transaction set) contains all possible segments and data elements defined for that transaction set.  Catalyst:Map/STMAP enables your EDI systems programmers and administrators can do the following:

  • Codify information about your applications and trading partners
  • Create maps that define the relationship of this codified information
  • Maintain the maps whenever requirements change

  Maps

A map defines the relationship between two types of data files:

  1. Text files containing data in an EDI format
  2. Data files containing data in a format that can be accessed by your business applications

The map provides detailed instructions to the translator software on how to extract information from one file and where to place it in the other.

  Map Direction

Catalyst:Map / STMAP can convert data in two directions:

  • Outbound - from your application file to an EDI file ready for exchange
  • Inbound - from an EDI file to your application file

Maps are mono-directional. For example, if you transmit purchase orders and also receive purchase orders, you will require two maps for an X.12 850 transaction set: one for transmitting (outbound), and one for receiving (inbound).

  Map Definition

Map definition is the process by which you specify the relationship between a given field in the application data and its corresponding field in an EDI file. For example, your accounting software can create a file containing information for a purchase order: the purchase order number, date, the products being ordered, etc. Each data item must appear in a specific location within the EDI document that will be transmitted.

  Map Execution

Map execution (or running) is the process by which Catalyst:Map translates data files to or from EDI format, using the rules and instructions embedded within the map. You can also test your map by running it within Catalyst:Map before transmission.

 


 More Capabilities

Other impressive capabilities built into the Catalyst:Map / STMAP application mapping tool include:

  • Rapid EDI and application data conversion and processing
  • Reading dBase, FoxPro, Paradox, or Cobol data structure from your application for inclusion in a Map
  • Concatenation or substring of fields in the EDI transaction or applications database
  • Table and file cross-referencing

e.g., EACH from your application can be translated in EA for X.12 standard

  • Conditional testing, including loop processing

e.g., if/then/else statements

  • Arithmetic operations on user selected fields

e.g., utilizing LINECOUNT for your IT101 in your invoice (810)

  • Accessing of system information for inclusion in certain fields

e.g., bringing in the system date and time

  • Data definition, mapping logic, and rule sharing between Maps
  • Single map maintenance for all trading partners for each transaction type
  • Processing "HL" loops and other similar data structures

 


 Resource:

 


Catalyst:Map / STMAP presents a graphical user interface comprising many different tools for developing any maps. You will use these tools repeatedly, as needed, during a cyclical process of defining, testing, and refining your work.  When these maps are ready to be moved into the production environment, you will integrate them with TrustedLink Windows.

  Who can use Catalyst:Map? 

The processing of data through a completed Map using TLW is quite easy. Developing a Map requires a working knowledge of EDI data structure, and familiarity with the logical structure of the application file that will be used. Programming experience of any sort will also help.

 

Catalyst:Map and TLW used together provide seamless unattended operations, extensive status reporting, minimal trading partner maintenance, access to any network, Data entry and printing capabilities, and support for any industry participating in standards-based EDI (UN/EDIFACT, ANSI X12, Odette, to name just a few).

 

See it and you'll believe it! Please contact our Business Solution department on +852 27713533 for demonstration and EDI consultation.

 


EDI City - A city of Life !

 


Phone: +852 27713839    Fax: +852 81480125    email: service @ edicity.com

© 1994-2010 EDI Resources Centre. All rights reserved. See disclaimer & Privay Policy