6.8.28. How to Integrate with Transplace?

This "How to" should provide you with the necessary steps to implement a working integration with Transplace from scratch using Babelway.

Figure 6.160. 


Preferred Protocols and Message Formats. When integrating with Transplace, you will be expected to send X12 (version 4010) messages through FTP.

Setting up your connection

Transplace uses FTP. Your channel will look something like this:

Figure 6.161. 


For FTP, create an "FTP Client" gateway IN as follows. Note that Transplace needs to share with you the information required to complete the highlighted section.

Figure 6.162. 


In order to send content to Transplace, you will need to complete the matching FTP client outgoing gateway:

Figure 6.163. 


Once again, you will need Transplace to share the highlighted information with you. Most likely, only the directory will differ between the two gateways and you will use the same credentials to log in to their FTP server.

Whether you begin with the incoming or outgoing flow, you can test your connection by creating a dummy channel using your newly created gateway, "Not defined" message definitions and a "no transform" transformation to just ensure that you can exchange content with Transplace correctly. Next, you will want to validate that you can correctly convert your format to theirs in a way that matches their requirements.

Configuring your messages

You will find samples for their messages in the resources bundle.

Transplace doesn't seem adamant that you use 997 functional acknowledgements when exchanging content with them. However, if you wish to correlate the acknowledgements they send you, or if you decide to send acknowledgements yourself, you can have a look at Babelway's 997 implementation:

Figure 6.164. 


This documentation is based on our integration projects but we'd love to enhance and update it with your own feedback and experience: support@babelway.com.

Last update: Jan 10 2018