In the version 2.8.3 of the Sybase Adapter for EDI, ECMap can export a schema to the repository for e-Biz Integrator, e-Biz 2000 or MQSI. ECRTP (the runtime program that executes the maps developed in ECMap) is able to Put serialized NDO onto a queue and Read serialized NDO from a queue via calls to the ADK version 3.3. A map must be created manually in ECMap, to define the “application” record layout, map the data, and create the flow specifying the Read NDO or Write NDO and Put NDO commands. The NDO is then mapped in e-Biz Integrator, e-Biz 2000 or MQSI to the destination NDO format. In this version, you had to do mapping in two products (for example, ECMap and either MQSI, e-Biz Integrator or e-Biz 2000) with two different GUIs.
To resolve this double-mapping issue, ECMap 2.9 can automatically generate a map to either read or write serialized NDO from/to a queue and export the schema to the repository. In this case, mapping in ECMap consists of a set of “configuration” activities versus mapping activities. ECMap now automatically generates the mapping, create the Write NDO and Put NDO or Read NDO commands and exports the schema. To use ECMap in this manner, the schema must be exported from ECMap to the repository regardless whether the data is going into or coming out of the Queue.
This mapping solution should work automatically for most transactions. In the cases where the HL (Hierarchical Level) segment is present:
If the native X12 transaction is used, then the map that automatically created has to be modified manually because the structure of the transaction is not defined in the transaction set.
If an Implementation Guide (rather than the generic standard) is used to create the standard definition for these transactions, then this solution correctly handles the HL segments 100 percent automatically.
Options are provided for controlling the automatic message mapping utility:
The default is to put data on the queue one transaction at a time. Only the data between an ST and SE, inclusive, is placed on the queue. A transaction is considered a unit of work.
There is an option to include the Outer Envelopes with each transaction. Since there can be multiple transactions in an interchange and the largest unit of work the PUT NDO command can handle is a single transaction, the beginning outer envelopes is repeated on every transaction and the trailing outer envelopes does not appear in any serialized NDO data.
There is an option for breaking out a single transaction into multiple units of work. This option is used in situations where the size of the transaction could exceed the maximum queue size for a transaction.
This option slows down performance in ECRTP.
When ECRTP is creating EDI data, each transaction placed on the queue corresponds to a single EDI transaction as defined in the standards. There are no merge or combine functionality to create a single EDI transaction for multiple transactions on the queue. The current functionality in ECRTP group transactions that are destined to the same trading partner in a single interchange providing the data is placed on the queue ordered in this manner.
This design assumes that both the inbound and outbound inbound EDI data are processed through a compliance map to validate that the EDI data complies with the appropriate standard definition.
This section uses X12 terminology but you can automatically map EDIFACT and HL7.
The automatically generated map can be imported into:
e-Biz Integrator 3.1.1,3.2.2
MQSI 2, 2.0.1, 2.0.2, 2.1
e-Biz 2000
The automatically generated map is compatible with HIPAA Toolkit 4.1 or later.
Automatically creating a map
Install ECMap.
Run ECMap. In ECMap(AV) the default first window is in “Adapter View” with a limited toolbar as shown below.
The limited toolbar is all that you need to generate a map automatically. Later, you will learn how to display the “Full View” if you need to make changes to the map.
Create a project.
If you do not remember how create a project follow the steps in Chapter 3, “Projects”.
Create a map.
Fill out the Map Properties window. The Properties window is filled out for an inbound 997 Map.
The Map definition specifies type of map – X12, EDIFACT and HL7, transaction, version/release, direction (EDI into or out of ECMap/ECRTP), Y2K windowing logic and Description. In the Map DSN tab, the database version of the Trading Partner File and Log can be specified (This does not affect the production options). If the direction is IN, the source is EDI and the destination is NDO. If the direction is OUT, the source is NDO and the destination is EDI.
Select the Map Directories tab.
If your Standards are in a different directory than the default value, then change this path. Otherwise, no changes need to be made to this window.
No changes need to be made to the Map DSN windows.
Select OK to close this window.
From the View menu, select Transaction Tree.
The EDI segments for the transaction set must be selected. The default view appears with only the mandatory segments selected (checked). To select additional segments, left-click on the segment. In a typical EDI implementation only a subset of the segments defined in the transaction set are needed.
If the standard database was created from an implementation guide then all the segments are checked, since an implementation guide is a specific definition of the transaction subset that is to be used.
In ECMap, there are two views for the transaction set, the Table view and the Tree View. Below is a sample of the Tree view.
After the segments are selected, close this window.
From the Build menu, select the Generate Map option. The Generate Integration Broker Map window appears. The Generate Map option automatically creates the ECMap map with the appropriate I/O commands and the schema is stored in the storage.mdb database for the schema export process. When you create an automatic map for an inbound map, you are converting EDI to an Integration Broker Map. When you create an automatic map for an outbound map, you are converting an Integration Broker Map to EDI.
If the Create Full EDI Envelope Structure check box is selected, then the header EDI Outer Envelopes are included in the NDO schema, otherwise only the transaction header appears in the schema. For example:
If Create Full EDI Envelope Structure is checked, then the following appears at the beginning of the schema and data.
ISA
GS
ST
Otherwise only the ST appears at the beginning of the schema and data.
Select on Run.
During the Generate Process the status is displayed and upon completion, a Generate Complete message appears.
When you select Run, and this is the First generation of the map, a confirmation message appears.
This message describes what the default option is for the placement of the PUT NDO command. The default placement of the PUT NDO command is at the end of every transaction, which for X12 is the SE segment.
If Yes is selected, then the generate process continues to create the map and saves the schema for export.
If No, is selected, then the following window is displayed so that a segment can be selected to place the PUT NDO command. This is so large transactions like, Health Care Claims (837), Consolidated Service Invoice/Statement (811), Advanced Ship Notice (856), etc., can be broken out into smaller units of work so that the size limitation of MQ Series is not exceeded. The following window is displayed to select the segment that when the map either returns to or is about to process data at a lower numbered level.
To highlight a segment, left-click on the desired segment, and then select the OK button to continue. Only one segment can be selected in this window. If the Cancel button is selected, the generate process is stopped and the user is returned to the ECMap Desktop.
If this is not the first time you generated a map, a confirmation message appears to overwrite the information or not.
If Yes is selected, then the map is regenerated from scratch.
If No is selected, then the changes made are incorporated into the new version of the map being generated.
After you select Run, ECRTP begins processing the application data. If you do not receive a message on the window telling that your map has run successfully, you can select View Trace at the bottom of the window to verify the outcome. Usually the Auto-Mapping features generates the map automatically. Otherwise you receive errors. If you receive errors, select the View Trace button and see the Informational Messages chapter in the ECMap Reference Guide for steps on how to remove the error.
From the Utilities Menu, select Export Schema and select the formatter you use: e-Biz 2000, e-Biz Integrator, or MQSI.
Once the repository type is selected, then the user is queried to use an exiting configuration file or create a new configuration file.
If Yes is selected, the configuration selection window appears and an existing configuration must be selected.
If No is selected,:
Create a new configuration file, then select OK for the next window.
Select OK and the Configuration File Options window appears.
If With MQSI or e-Biz Integrator Options is selected and OK is selected, then the Prefix keeps the schemas unique in the repository. Clicking Next populates the configuration file and displays it in the Create Configuration File window so it can be edited.
If the Manually option is selected, then the Create Configuration File window is open for the configuration file to be manually keyed in.
If at any time you select Cancel, the schema export process is exited and nothing is saved. When Save is selected, a confirmation prompt appears.
If you select No, control is returned to the Create Configuration File window. If Yes is selected, the configuration file is automatically saved into the ECMap installation directory, for example: c:\program files\sybase\ecmap\. For the next step, go to step 15 below.
If you select Yes on step 7, then the configuration selection window appears and an existing configuration must be selected.
Once a configuration file is selected, then the Schema Name Selection window is displayed:
At this point, a schema name is displayed. You can override it by selecting on the Add button or select the Finish button. The Finish button causes the schema to be generated and exported into the repository. A file definition is automatically created so the map can be tested before data is written to the repository.
After you select Finish, the Add Schema Name dialog appears. Fill out the Schema Name and a description.
After the information has been added, select OK and you are returned back to the Schema Name Selection window.
