Top EDIConnect Features: EDIConnect EDI Transaction Process

Many businesses use Electronic Data Interchange (EDI) to send and receive messages. Last week we covered EDI source files and parsing. This week, we reach our number one feature for Centerprise’s EDIConnect connector: the EDIConnect Transaction Process.

  1. EDI Builder and Destination File

To build an EDI document, use the EDI Builder feature. There are two steps in this process. First, build the EDI message using EDIConnect Visual Designer. Next, validate it against Partner Standards and send it out.

EDI Builder

Select File > New > Dataflow.

To create an EDI file, select the EDI Message Serializer from the Toolbox on the left as shown in the screenshot below. Drag and drop the EDI Message Serializer to the Dataflow.


Setting EDI Builder Properties

Right-click on the EDIBuilder message and select Properties. A dialog box opens as seen below. First, point this file to a Trade Partner Profile: this automatically selects the transaction type for the outgoing EDI message.


EDI Builder Structure

The EDI builder now has a structure for the selected transaction type in the previous step. Any problems and errors that occur during a preview are shown in the Errors section.


EDI Destination file

EDI destination files can also be selected from the toolbox and dragged and dropped into the Dataflow. Use the file properties to specify the location of the output file and the Trade Partner Profile data.



Finally, map the EDI Builder file to the EDI Destination file as seen in the screenshot below. This Destination file will contain the final EDI message.


EDIConnect can be used to handle entire EDI transaction process. It supports all EDI message standards and customizes transaction documents: EDI transactions have never been easier.

That concludes our top 4 EDIConnect features! We hope that you’ve enjoyed this series and that you’ll check back next week for more exciting new information.

Top EDIConnect Features: EDI Source Files and Parsing

Businesses across the globe send and receive messages via Electronic Data Interchange (EDI). Last week we covered our Centerprise connector, EDIConnect’s, Custom Repository feature. Our focus this week are our number two features for EDIConnect: EDI Source Files and Parsing.

Once an EDI file has been received, validated, and once the acknowledge process is complete, it goes to a dataflow to be parsed and translated. After that, it can be transformed, mapped, and written to destination.

EDI Source File

This reads the incoming EDI messages.  First, create a new Dataflow by selecting File > New > Dataflow. Once a new dataflow opens up, drag and drop the EDI Source File option from the toolbox on the left to the dataflow.

Now, specify source file location information and Trade Partner Profile settings. These contain all information about processing incoming data using EDI Source file properties.


To preview EDI source file data, right-click on the EDI Source File box in the dataflow and select Preview Output.


The output is in hierarchical format as seen below.


EDI Parser

This generates the transaction structure that can be mapped to any destination. The Parser also includes the Trade Partner Profile file: all information required to parse a transaction is in one place. From here, users can specify all transaction sets expected from a partner.

The EDI Parser can be dragged and dropped in to the dataflow using the Toolbox on the left. To set its properties, right-click on it and select Properties. The screenshots below demonstrate the EDI Parser process.




To map the EDI Parser to the EDI Source file, drag the Transaction Node of the EDI Source file onto the EDI Parser file.


Destination file

Once the EDI message has been parsed, it’s ready to be mapped to a destination file, such as an XML file as shown in the example below.  Drag and drop the XML/JSON File Destination option from the Toolbox on the left under the Destinations category to the dataflow.


Make sure you specify the output file location and provide an XML Schema file that matches the EDI Parser transaction structure to the XML Destination File Properties.


Now, map your EDI Parser to your XML Destination File. Your output file is ready to view.

Want to know more about EDIConnect? We’ve been covering our top four EDIConnect features over the past several weeks. Be sure to check back for the final installment in this series!

Top EDIConnect Features: EDI Custom Repository

Many businesses use Electronic Data Interchange (EDI) to send and receive messages. Last week we covered our Centerprise connector, EDIConnect’s, Trade Partner Management features. Our focus this week is our number three feature for EDIConnect: the EDI Custom Repository.

EDI Custom Repository

With EDIConnect, users can customize transaction sets, segments, composite elements, and elements, and store them in a custom repository.

Create a new Custom Repository

To create a new Custom Repository, Select File > New > Edi Custom Repository.

This will create an empty custom repo that contains all the standard definitions for transaction sets, segments, elements and composite elements.


Customize a Transaction Set

In the screenshot below, all the standard EDI Transaction sets are listed on the right and each transaction set’s details can be seen and modified once clicked.


Custom segments can also be added or deleted.

3 4

Customize Segments/Composite Elements/Elements

As with the transaction sets, every segment, composite element, and element can also be customized: EDIConnect is robust and powerful enough to handle various EDI transaction documents with ease. The screenshots below demonstrate the numerous possibilities to customize EDI documents.

5 6 7

All artifacts that come with standard EDI messages can be modified using EDIConnect and can be stored in an EDI Custom Repository.

Want to know more about EDIConnect? We’re covering our top four EDIConnect features over the next several weeks. Be sure to check back for the third installment!

Top EDIConnect Features: Trade Partner Management

Many businesses use Electronic Data Interchange (EDI) to send and receive messages. Last week we covered what EDI is and two specific use cases. This week, we take a closer look at how to get started with Astera’s  Centerprise connector, EDIConnect. Below is our number four feature.

Trade Partner Management

The Trade Partner Management feature in EDIConnect allows users to set up trading partners, manage all aspects of trading partner relationships (such as inbound and outbound transaction maps definition and  separators for segments,) and has ways to customize EDI message standards and use them within trade partner definition.

Create new Trade Partner Profile

To create a new Trade partner profile, select File>New> Edi Trade Partner Profile. From there, specify the Trading partner profile name and settings, Inbound/Outbound Maps, and Sequences.

X12 Settings lets the user define acknowledgement information, functional groups, Validation settings, etc. The screenshot below shows the options available.

Specify Inbound Maps and Outbound Maps

Use this option to detail how transactions from the partner will be treated and the number of transactions expected from said partner. Choose from standard or customized versions of EDI messages, as well as standard or customized transaction processes.

Outbound maps are where the user can establish and customize which maps will be sent out to this partner. 


All sequence generations for a particular EDI partner are controlled by the properties specified in the Sequences tab (see screenshot below.) Options such as Database Information, Functional Group Control numbers, etc., can be set via the Sequences tab.


Want to know more about EDIConnect? We’re covering our top four EDIConnect features over the next several weeks. Be sure to check back for the second installment!

Handling Benefit Enrollment and Claims EDI Data using Centerprise

One of Astera’s Centerprise connectors, EDIConnect, offers a user friendly and intuitive user interface to accurately and efficiently handle bi-directional EDI data integration. It is scalable and powerful enough to fulfill entire EDI transaction processes. In this blog we are going to focus on how to handle benefit enrollment and healthcare claims data.

EDI 834 – Benefit Enrollment and Maintenance:

The EDI 834 transaction set represents a Benefit Enrollment and Maintenance document. It is a standard format for enrolling members in healthcare benefit plans. It helps electronically exchange health plan enrollment data between employers and health insurance carriers. The Health Insurance Portability and Accountability Act (HIPAA) requires all health plans or health insurance carriers to accept 834A Version 5010 which is a standard enrollment format.

The 834 document is submitted to transfer the enrollment information typically by the employer, to healthcare payer organizations who are responsible for payment of health claims and insurance/benefits. The recipient of an 834 transaction responds with a 999 Implementation Acknowledgement. This confirms whether the file was received and provides feedback on the acceptance of the document.


EDI 837 – Healthcare Claim:

The EDI 837 document is required for electronic submission of healthcare claims. It has a standard format established to meet HIPAA requirement for healthcare claim information. This document is used to submit health care claim billing information from healthcare service providers to sponsors.

Healthcare providers must be compliant with version 5010 of the HIPAA EDI standards. The 837 EDI transactions may be sent either directly or indirectly via clearinghouses.



EDIConnect offers data mapping, validation, incoming file translation and information extraction as well as outgoing file construction and acknowledgement generation. EDIConnect also provides automation, process orchestration and job scheduling for automated translation and parsing of EDI documents. It is a complete solution for accurate and efficient bi-directional EDI data integration. It offers EDI capability in an intuitive user interface with visual tools to build bi-directional integration. With built-in transaction sets for incoming file translation and ingestion, advanced data mapping, validation, and correction capabilities to better manage data ingestion, fast and easy outgoing transaction construction, acknowledgement generation, and automation, process orchestration, and scheduling, EDIConnect delivers the power and scalability to meet the most demanding EDI needs within Centerprise.

Want to know more about EDIConnect? We’re covering our top four EDIConnect features over the next several weeks. Be sure to check back for the first installment!

Optical Character Recognition Support

Welcome to The Highlight Reel, Astera Software’s blog series on ReportMiner 7’s newest features.

ReportMiner 7 now offers built-in Optical Character Recognition (OCR). Combined with our sophisticated pattern based text extraction functionality, ReportMiner can be used to unlock data trapped in scanned documents seamlessly.

How does it work in ReportMiner?

ReportMiner uses OCR as a preprocessing step to get the text equivalent of the image found in the scanned pdf documents. Once the equivalent text is available, rest of the process is exactly same as other text based documents. Let’s review the OCR process for PDF documents containing textual information as images:

  1. Once we select File > New > Report Model, we can go ahead and set the path to the PDF document containing textual information that we would like to run OCR on.

Make sure that the “Run OCR” option is checked, so that ReportMiner will run OCR on the document.

An important thing to be noted here is the option of zoom level and its default value being set to 100%.

Selecting an appropriate zoom level results in both speed and accuracy. If the image containing text is very small, increasing the image size can result in better text recognition with improved accuracy. Hence, you can adjust this zoom level until you get the desired results.

  1. Below is a screenshot of the PDF document we are trying to read using ReportMiner.

  2. As soon as you select “Ok”, ReportMiner will start running OCR on the document.



  1. As shown below, Report Miner grabs the textual information from the PDF document and displays it on the screen.

Now that you have your document digitized, it can be processed by ReportMiner. It can be used to create report models to create data regions and identify matching patterns, grab data and then export it to your desired destination.

Be sure to check back every Thursday for more highlights. If you’d like to see the current list of featured features, click here.

Microsoft Word and Rich Text Format Support

Welcome to The Highlight Reel, Astera Software’s blog series on ReportMiner 7’s newest features.

ReportMiner 7 now includes support for Microsoft Word (Doc and Docx) and RTF formats: enjoy efficient and easy information extraction from more source files than ever before. Now you can process invoices, purchase orders, receipts, forms and other Word/RTF-formatted files with ReportMiner 7.

The screenshots below illustrate .docx extension support in ReportMiner.

Select File > New > Report Model and choose your source document.

As seen in the screenshot below, the .docx file opens and is ready for processing.

You can now continue to create your report model.

We at Astera Software are proud to take every step towards making our products the best that they can be. Be sure to check back every Thursday for more highlights.

Astera Introduces ReportMiner 7


Astera is excited to announce that ReportMiner 7 is now available.  New innovative features make it one of the most powerful software solutions for document content extraction and integration on the market.

Astera’s ReportMiner enables users to extract data from non-tabular data documents. Users define pattern-based extraction models to extract desired data, transform, and send it to a variety of destination formats, such as spreadsheets, relational databases, and XML files. ReportMiner comes with advanced integration features such as workflow orchestration and scheduling with batch and real-time modes, making it a complete solution for end-to-end unstructured data integration.

This latest release builds on our software’s signature ease of use and intuitiveness with features intended to capture a multitude of new source types and structures.

Key new features in ReportMiner 7 include:

  • OCR for PDFs: This feature is introduced to handle documents containing images. With built-in OCR feature, ReportMiner can read data from scanned PDFs directly within the software.
  • Microsoft Word and RTF support: ReportMiner can now extract data from Microsoft Word and RTF documents.
  • Multi-column layouts: Multi-column (newspaper-style) layouts are now supported for extraction. Visually mark the columns and ReportMiner will automatically apply the extraction logic to each of the columns.
  • Action functions: These context-based functions give control of the raw text while creating formula fields.
  • Forward and backward append: “Append” data regions can work in both directions. User can append data to all preceding records or all succeeding records.
  • Flat Preview: Where applicable, ReportMiner now offers a flattening of the preview grid so users can envision how their data will look when exported to a flat structure such as an Excel spreadsheet.
  • User interface enhancements: With a sleek new interface, brand new visual themes, and many user interface enhancements, ReportMiner 7 offers an entirely custom experience in data extraction.


ReportMiner 7 is available immediately. For those interested in giving ReportMiner 7 a test drive, a free trial can be requested here. If you’re a current customer and want to upgrade, contact your account manager for more details on how.

Trade Partner Management in EDIConnect

EDIConnect is a complete solution for accurate and efficient bi-directional EDI data integration. It offers EDI data integration capability in an intuitive user interface with visual tools to build bi-directional integration. This blog will discuss how to set up a trade partner relationship in EDIConnect, including how to define incoming and outbound condition maps, how to define separators for the segment elements, and how to customize standards and use them inside the trade partner definition.

First, let’s review the EDIConnect process for receiving and sending messages.


You define your trade partner and specify the settings to receive incoming messages.

Once you receive the message, it goes into the system, where you can validate it and generate acknowledgements such as X12, 997, and 999 or Tier One.

Now let’s take a closer look at the process for defining a trade partner and specifying the settings to receive incoming messages.

Begin by creating a new trade partner. Go to file/new and click on EDI Trade Partner Profile.


In the screen, you can specify the partner name and also specify your settings, inbound maps, outbound maps, and sequences.


Let’s look at these options one by one.

First, select the dialect for the partner, in this case X12.


Within the X12 settings, you can specify information for the interchange headers, functional groups, validation settings, and acknowledgement.


Within the Functional Group you can specify GS properties as shown below.


Similarly, for Interchange Header you can specify all ISA properties, as well as separators for your data elements, as shown below.


For the validation settings, you can specify what should be validated when a message is received for the partner.


You can specify acknowledgements such as what kind of acknowledgement you want to convey when the messages arrive, such as FunctionalAckTransactionSet, GenerateAk2ForAcceptedTransactionSet, or SendTechnicalAcknowledgement.


Now we’ll move on to how to specify inbound maps. This is where you specify how specific transactions from the partner are treated and how many you are expecting from that partner. For example, from this partner I am expecting only 850 transactions.


So I’m going to add one 850 as an incoming transaction set and specify how I want it to be processed in the system. You can have a standard 850 or you can have a customized version of it. In the case of a customized version, you will pick your customized 850 version as a mapping so that when the messages arrive the customized information is used to process that message.


Similarly, for outbound messages you specify what maps you are going to send out to this partner and if there is any customization, in which case you map the standard message to the customized message in the customization window as shown below.


Now we’ll move on to sequences. All the sequence generation for this EDI partner is controlled by the properties specified in this tab.


Here you specify where your sequence object resides, your database information, and your functional group control numbers, interchange control numbers, and conditions of control numbers.

Now that you know how to set up a trade partner relationship, our next blog will show you how to use the EDI builder and EDI destination file in EDIConnect.

Creating a Complex Dataflow in Centerprise – Part 2

Part 2 – Routing Data to Multiple Destinations

In Part 1 we have learned how to use the Join transformation and different types of maps such as the Expression map and Function map. Now we will use the Router to send data into two different tables depending on the routing information.

We want to decide the destination of the loan depending on its origin state. Take the State field from the transformation window and drag and drop it into the Route, which maps it to the State field in the Route.


Open the router properties and go to the next page, here you can add the rules to decide the different routes. For example, for the California loans we can write a simple rule such as “State equals CA.”


Click on the new rule icon in the left top of the rule window and the next rule we will write is “State does not equal CA.”


The result in the Router window is that there are two different outgoing nodes available for mapping, CA and Out_Of_State. This enables us to put each set of data in a different table.


Now we can go ahead and create the destination tables for the routed loans. We need to create one for California loans and one for Out_Of_State loans.  You can drag and drop the database table destination from the toolbox onto the designer, however, you can also use a shortcut for creating a database table source or destination using the database browser. You simply select the database browser underneath the toolbox and point to one of the existing connections.


The browser will then show you all the existing databases, including tables and views.


Select the tables folder, which shows all the tables in the database and we can see the California loans table.


Select the California loans table, press shift, and drag and drop it onto the designer to create the destination.


Follow the same steps to create the Out_Of_State Loans destination.


If we expand the CA_Loans designation, we can see that we have all the fields and we can do our map from the Route to each destination. Drag the CA field from the router to the destination, and do the same for the Out_Of_State_Loans.


So with these few clicks we have created the scenario we started with in the very first image. We have the Loans and Taxes sources, we did the join, we did the calculation for the Address and Name Parse function, and, finally, we did the routing to send the loans to two different destination tables.


However, as you can see if you compare this to the first image at the beginning of the blog, there are a couple of lookups along with the address calculation and name parsing, as well as a data quality rule to check the data coming from the tax source.


If we open the preview window for the tax data, we can see that for some loans the tax is showing zero.


We need to check whether the source data is correct or not, so we add a data quality rule, which can be found in the toolbox transformations. Drag and drop it onto the designer and do the mapping as with any other transformation. Open the properties window and a rule can be written to specify that the property tax cannot be zero.


Now do a preview on the loan tax join. Since the data is passing through the data quality rule you can see that the data quality rule has flagged all the errors.


Another thing that has been done is to add a profile of the tax data. If you do a preview you can see that for the LoanID and the PropertyTax fields the information about the all the values has been collected.


Since the profile is like any other source, it can be mapped to an Excel spreadsheet destination and when the dataflow is run, it puts the information in the Excel sheet, which becomes our report. So along with doing the data transfer, a report on the tax data is provided as well.

This is a quick overview has demonstrated how to create a complex dataflow in Centerprise. In Part 1 we learned how to combine data from two sources using a join, send the data for transformation and mapping, and create a function.  In Part 2 we learned how to route our data to two different destination tables. For more information on creating workflows and subflows, visit our Astera TV Workflows and Subflows playlist.