This tab displays the following information. You can change it by just editing the fields and click on Save.

It displays informations about date and times where the channel was created or last updated.

You can also precisely see and control the informations about the deployment of this channel (fields Status, Next deployment and Enabled ? ). All the informations avout these 3 fields and the associated commands can be found in the deployment section.

The Delete action allows you to delete your channel.

The Duplicate action allows you to duplicate your channel.

The gateway in specifies the way incoming messages are communicated from the source external system to Babelway. Babelway supports a large variety of protocols, including FTP, AS2, HTTP, Email, OFTP, SFTP, X400 or web upload.

You can find all informations about how to define and configure gateways in the gateways chapter.

The message in precisely describes the structure of the incoming message.

You can find all informations about how to define and configure message definitions in the message definitions chapter.

The transformation tells Babelway how the incoming message should be translated to the outgoing message.

You can find all informations about how to define and configure transformations, including the behavior of the visual drag-and-drop editor, in the transformations chapter.

The message out precisely describes the structure of the outgoing message.

You can find all informations about how to define and configure message definitions in the message definitions chapter.

The gateway out specifies how the outgoing message should be communicated to the target external system.

You can find all informations about how to define and configure gateways in the gateways chapter.

For each individual channel, you may configure automatic notifications that send emails to specified addresses upon arrival of new messages. Notified users can be different if the message has been successfully processed or if an error has been generated.

You can find all informations about how to define and configure notifications in the notifications chapter.

The routing allows you to define which channel must process a message, when multiple channels use the same gateway in.

You can find all informations about how to define and configure gateways in the routing chapter.

The test cases are a great way to be sure that your channels are correctly configured, and produce the expected results.

You can find all informations about how to define and configure gateways in the test cases chapter.

Figure 4.4. Related Items

That tab gives you quick links to many other elements of the application that are related to this channel :

The general tab contains the signaletic information of the gateway, and offers actions that act on the whole gateway.

This tab contains the configuration of the gateway.

The parameters depend on the type of the gateway.

This tab contains quick links to many other elements related to this gateway.

This tabs shows you all the history of changes on this gateway, and allows you to revert to a past version. For more details, see the change log section.

Email gateway in allows to receive incoming messages sent to a specific Babelway email address, as attachments. The messages are processed as soon as they arrive.

The specific parameters are :

Figure 4.11. Email Gateway configuration

With a Ftp Client Input Gateway, incoming messages are transfered to an external Ftp server. Babelway platform polls this server at regular intervals and retrieves incoming files to process them.

The specific parameters are :

When a message is transfered to the ftp server, it is processed immediately then original file is removed from server.

With a Ftp Server Input Gateway, incoming messages are received on a Babelway specific ftp server and processed as soon as they arrive.

The specific parameters are :

After channel deployment, your ftp server will be available to send messages. You can access this ftp server using any ftp client software set up with the previous account parameters.

When a message is received by the ftp server, it is processed in the 90 seconds (default polling interval) max. After processing, the original file is removed from server.

If you are using an ftp server both as incoming and outgoing gateways, you cannot use the same login for both gateway servers.

With a SFTP Client Input Gateway, incoming messages are transfered to an external SFTP server. Babelway platform polls this server at regular intervals and retrieves incoming files to process them.

The specific parameters are:

After channel deployment, your ftp server will be available to send messages. You can access this ftp server using any ftp client software set up with the previous account parameters.

When a message is transfered to the sftp server, it is processed immediately then original file is removed from server.

Using the SFTP Server Input Gateway,incoming messages are received on a Babelway specific server and processed as soon as they arrive. The SFTP server gateway supports SFTP version 3 and password and/or publickey user authentication mechanisms.

The specific parameters are:

you can set both password and public key fields. In that case, you will be able to connect to your account either by using a password or by using your private key associated with the uploaded public key.

After channel deployment, your SFTP server will be available to send messages. You can access this SFTP server using any SFTP (version 3) client software set up with the previous account parameters.

When a message is received by the SFTP server, it is directly processed. After processing the file is removed from the server

The public key is expected to be in a RSA format (OpenSSH, Putty or DER). If you don’t already have a public/private key, you can generate one using ssh-keygen from OpenSSH :

C:\cygwin\bin>ssh-keygen.exe
Generating public/private rsa key pair.
Enter file in which to save the key (/.ssh/id_rsa): /tmp/identity
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /tmp/identity.
Your public key has been saved in /tmp/identity.pub.
The key fingerprint is:
f0:e4:2f:(...) user@computer
		

With an AS2 Gateway, incoming messages are received using an AS2 connection. Incoming files are processed as soon as they are received.

AS2 (Applicability Statement 2) is a specification about how to transport data securely and reliably over the Internet. Security is achieved by using digital certificates and encryption.

The specific parameters are:

After channel deployment, your AS2 connection will be available to receive messages.

To report AS2 parameters to the other party, click on GenericAS2Specifications.doc command to download a Word file including all parameters values required to establish AS2 communication. In this file, you should change Identity field to match the To field value (see above) as automatically attributed by Babelway interface, this value follows " BABELWAY_AS2_xxxxx " form.

Once this parameter has been changed to match your settings, you can send the file to the other party to give him all parameters he will require to establish a communication with your channel.

Figure 4.12. GenericAS2Specifications Word file example

With an OFtp server Gateway in, Incoming messages are received on a Babelway specific OFTP server and processed as soon as they arrive.

The specific parameters are:

After channel deployment, your Oftp server will be available to send messages. You can access this oftp server using any Oftp client software set up with the previous account parameters.

If you require a custom SSID / SFID / PASSWORD, please send a request to support@babelway.com .

When a message is transfered to the Oftp server, it is processed immediately then original file is removed from server.

With an OFTP Client Input Gateway, incoming messages are transferred from an external OFTP server. The Babelway platform polls this server at regular intervals and retrieves files to process them.

The specific parameters are:

After channel deployment, your Oftp server will be available to send messages. You can access this oftp server using any Oftp client software set up with the previous account parameters.

If you require a custom SSID / SFID / PASSWORD, please send a request to support@babelway.com .

When a message is transfered to the Oftp server, it is processed immediately then original file is removed from server.

With an Http In Gateway, incoming messages are received on a Babelway specific server and processed as soon as they arrive.

The specific parameters are:

After channel deployment, your connection will be available to send messages.

The HTTP Post can do the following:

With a X.400 Input Gateway,allows to receive message from X.400 networks. Your trading partners can reach you to your hub private X.400 address.

The specific parameters are:

After channel deployment, your connection will be available to send messages.

The first time X.400 is used in an account, it has to be enabled by Babelway support. The request is done automatically and you will be notified when the gateway is functional.

The Scheduler in Gateway allows to create a message based on a time trigger.

The specific parameters are:

If no values are provided, the scheduler will create an input message every 90 seconds. The input message will enter the channel and follow the processing steps as in any other channel

The message has the following structure:

<?xml version="1.0" encoding="UTF-8"?>
<simpleScheduler>
	<date>
		<time>1327871680013</time>
		<display>20120129-221440</display>
	</date>
	<gatewayIn>9999999</gatewayIn>
</simpleScheduler>
		

Where the time and display tags provide the current time and the gatewayIn tag provides the gateway Id

To create another message than the default message, you can specify and upload an Xslt transformation. For instance, the following xslt will use the built-in XPath function used to search for message and message record to retrieve message records for every message since yesterday midnight:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
	xmlns:date-util="java:com.babelway.messaging.transformation.xslt.function.DateUtil"
	xmlns:enrich="java:com.babelway.messaging.transformation.xslt.function.Enrich"
	xmlns:xs="http://www.w3.org/2001/XMLSchema">
	<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes" omit-xml-declaration="no"/>
		<xsl:template match="/">
			<xsl:variable name="start" select="date-util:formatDateLenient(concat(date-util:formatDateLenient(date-util:currentDate(), 'yyyy-MM-dd HH:mm:ss.SSS', 'yyyy', 'true'),number(date-util:formatDateLenient(date-util:currentDate(), 'yyyy-MM-dd HH:mm:ss.SSS', 'D', 'true'))-1), 'yyyyD', 'yyyy-MM-dd''T''HH:mm:ss', 'true')"/>
			<xsl:variable name="messages" select="enrich:searchMessage($start)"/>
			<xsl:copy-of select="$messages" />						
		</xsl:template>			
</xsl:stylesheet>
		

There is also the possibility to upload your own code to create a new timebase gateway In. Please contact the support if you need this kind of gateway.

The internal gateway in / out are used for internal transfer of messages between channels inside the same account environment.

There is no parameter to define in this template. The internal gateway will be automaticaly created using the gateway name you entered. You will then be able to select it as an Internal Gateway Out in another channel configuration.

As opposed to most other gateways, this internal one is immediately available as gateway out for other channels configuration without requiring a channel deployment.

With a Store Client Input Gateway, incoming messages are transfered to an external Store server, like FTP, S3, NFS... Babelway platform polls this server at regular intervals and retrieves incoming files to process them.

The specific parameters are :

When a message is transfered to the store server, it is processed immediately then original file is removed from server.

The SAP Gateways are based on the SAP RFC protocol and JCo technology. RFC is an SAP interface protocol allowing internal or external systems to communicate with the SAP system. JCo is the Java implementation of RFC distributed by SAP. Babelway leverage the built-in JCo redundancy mechanism to distribute the gateway on our different locations (data centers).

Figure 4.13. Solution overview

System boundaries, acknowledgment and error management

For Inbound IDoc, Babelway sends the IDoc to SAP. If the message cannot be delivered to SAP, the error will be managed using the traditional Babelway process. Error notifications will be delivered to registered users. When the message is delivered to SAP, Babelway fetches the detailed status and error messages of the IDoc. The messages are always set to 'acknowledged' when the transmission is successfully. However the status could be SUCCESS or ERROR depending the SAP IDOC status code.

For Outbound IDoc, SAP sends IDOC to Babelway. If the message cannot be delivered to Babelway, the IDoc is in error in SAP with a status = 20. Once the message is delivered to Babelway, SAP automatically change the status to 03. In addition of this, we provide a function to explicitly change the status by calling the RFC defined during the setup phase. This allow SAP that the remaining of the IDoc processing will entirely take place in Babelway.

Connectivity Setup

Babelway provides the gateways to communicate in both direction. SAP Gateway In allows to receive outbound IDoc and SAP Gateway Out allows to send inbound IDoc to SAP. The JCo RFC Provider service uses a TCP/IP connection type. In order to secure this connection, Babelway advices one of the following solutions:

The Port number used to contact the SAP system range from 3300 to 3399. The exact port number depends on the SAP system you want to reach. The exact port number must be given in the parameters (defined below). Firewall need to allow Babelway server to reach these ports.

SAP configuration

Here is the list of the SAP specific setup to perform in order to make the connector working. This is guide lines

Babelway configuration

Simply create a channel with the SAP gateway and XML IDoc message definition.

Figure 4.18. Sap Channel Details

The specific parameters are :

The e-conomic wizard is used to create a gateway that lets you query your e-conomic online account (http://www.e-conomic.com) and retrieve invoice documents based on a specified CVR reference.

The specific parameters are:

With an Email Gateway Out, Processed messages are attached to email messages and sent to a specific email address.

The specific parameters are:

With a Ftp Client Output Gateway, outgoing messages are transfered to an external Ftp server.

The following fields should be defined in order to configure access to your external ftp server:

With a Ftp Server Output Gateway, outgoing messages are transferred to a Babelway FTP server, where you'll be able to fetch them.

The specific parameters are:

After channel deployment, your ftp server will be available to receive messages. You can access this ftp server using any ftp client software set up with the previous account parameters.

If you are using an ftp server both as incoming and outgoing gateways, you cannot use the same login for both gateway servers.

With a SFTP Client Output Gateway, outgoing messages are transfered to an external SFTP server.

The specific parameters are:

With an OFTP Client out Gateway, outgoing messages are transferred to an external OFTP server as soon as they are processed by the Babelway engine.

The specific parameters are:

After channel deployment, your Oftp server will be available to send messages. You can access this oftp server using any Oftp client software set up with the previous account parameters.

If you require a custom SSID / SFID / PASSWORD, please send a request to support@babelway.com .

When a message is transfered to the Oftp server, it is processed immediately then original file is removed from server.

With an OFtp server Gateway out, Outgoing messages are transferred to an Babelway OFTP server.

The specific parameters are:

After channel deployment, your Oftp server will be available to send messages. You can access this oftp server using any Oftp client software set up with the previous account parameters.

If you require a custom SSID / SFID / PASSWORD, please send a request to support@babelway.com .

When a message is transfered to the Oftp server, it is processed immediately then original file is removed from server.

With an AS2 Gateway, outgoing messages are transmitted using an AS2 connection.

AS2 (Applicability Statement 2) is a specification about how to transport data securely and reliably over the Internet. Security is achieved by using digital certificates and encryption.

The following fields should be defined in order to configure your AS2 access:

To report AS2 parameters to the other party, click on GenericAS2Specifications.doc command to download a Word file including all parameters values required to establish AS2 communication. In this file, you should change Identity field to match the To field value (see above) as automatically attributed by Babelway interface, this value follows " BABELWAY_AS2_xxxxx " form.

Once this parameter has been changed to match your settings, you can send the file to the other party to give him all parameters he will require to establish a communication with your channel.

Figure 4.19. GenericAS2Specifications Word file example

With an HttpClientOut Gateway, outgoing messages are send using a Http connection.

you can select several http internal in

The specific parameters are:

After channel deployment, your connection will be available to send messages.

With a HTTP out Output Gateway, outgoing messages are transferred to a Babelway HTTP server.

The specific parameters are:

After channel deployment, your connection will be available to send messages.

With a X.400 out Gateway, allows to sends the message on the X.400 network. To specify the address from your trading partner.

The internal gateway in / out are used for internal transfer of messages between channels inside the same account environment.

The specific parameters are:

As opposed to most other gateways, this internal one is immediately available as gateway out for other channels configuration without requiring a channel deployment.

The null gateway is used for test and development purposes. The outgoing message will not be sent out of Babelway platform.

Outgoing messages will not be forwarded but they are nevertheless created and readable through Messages interface. You may use this gateway for testing your messages transformation and creation before going to production or for preventing a channel to send messages before deployment.

Create a splitter channel

Th specific parameters are:

The aggregator allows to merge messages into one larger file. The aggregation could simply append the messages, use a xslt to merge xml document or merge Edifact or X12 documents. The resulting messages is forwarded to an other channels in the same environment.

The specific parameters are:

As opposed to most other gateways, this internal one is immediately available as gateway out for other channels configuration without requiring a channel deployment.

With a Store Client Output Gateway, outgoing messages are transfered to an external Store server, like FTP, S3, NFS...

The specific parameters are :

With a SAP Output Gateway, outgoing messages are pushed from Babelway to a SAP server.

The specific parameters are :

The generic gateway is used to setup gateway out with features not available at other gateways like transfer of output message to more than one channel.

After importing generic gateway from Babelway templates, you should complete setup of gateway manually by entering class name and adding string and file properties under advanced properties.

The general tab contains the signaletic information of the gateway, and offers actions that act on the whole message definition.

The tree describes the structure of the message, with all its fields. It is displayed in graphical form.

For more details, see all informations about the message definition tree.

Don't forget to save when you're finished with your changes.

The properties are the parameters of the message definition, and allows to configure all the options of the message definition, depending of its type.

See message definitions types section for the description of every parameter, type by type.

The extra processings allows you to configure additional processings that must be applied on the messages. Some examples are extracting the file from a zip file, or signing the output file.

See extra processings section for the description of every available extra processing, and all their parameters.

This tab contains quick links to many other elements related to this message definition.

This tabs shows you all the history of changes on this message definition, and allows you to revert to a past version. For more details, see the change log section.

The message tree representing a hierarchical view of the message is based on three node types:

Figure 4.21. Node types

When you right click on message nodes, a context menu such as the one illustrated below will open. This menu displays a set of commands available for selected node. All possible commands are listed hereunder and described in details in referenced chapters.

Figure 4.22. Edit screen contextual menu

Edit Element enables you to modify node name, to add a node description, to define a static value and to tag node as required.

Duplicate makes a copy of selected node and all its children if any. You should modify duplicated nodes name according to your system to avoid any problem at message processing time.

Hide and Show makes node (and its children if any) visible or not in the transformation tab. This function is used to simplify transformation step by not displaying nodes that do not require mapping. Note that if a hidden node is already mapped, it remains mapped in the transformation tab but cannot be modified.

Delete removes selected node (and its children if any). A confirmation message box is displayed before deletion.

The Add Validations... submenu allows you to select one or more criteria that must be met by a node in order for the message to be properly processed by the system. If any of these criteria is not met, message will not be processed and an error will be raised. Refer to Message Validation for detailled informations.

Create Loop, Remove from Loop, Put in next/previous Loop enables you configure loops in your message. These loops are used to manage repetitive elements such as multiple items lines in a message. Refer to the Managing Loops chapter for detailled informations.

Create Choice, Remove from Choice, Put in next/previous Choice enables you configure choices and options in your message. These choices are used to manage different mutually exclusive message configurations. Refer to the Managing Choice chapter for detailled informations.

In Babelway interface, it is possible to set up validations at message definition level.

You can set up validation rules for incoming and/or outgoing messages. These validations will be performed at runtime on messages.

To add validation rules, right click on a node in message definition window and select Add Validations... submenu. There are 3 basic validation rules that you can set up directly. In addition, you can also define your own rules in Xpath language.

Several validation rules may be applied to a same node. For example, using together a Max Length and a Min Length rule makes it easy to check that a node value has a specific length.

Once a validation rule has been added to a field, it will appears under the Validations section of message node. It can be removed by right-clicking on the validation rule and selecting the Delete command.

Example of Xpath validation rule:

string-length()>4
	

matches(.,"\d+") to validate if this field is only numeric 

Example of cross field validation rule:

For XML like this

<item>
	<price>456</price>
	<tax>123</tax>
	</item>

You can write Cross field validation like

price > tax

You can create choice to manage conditional processing of your message definition.

To identify a node or a set of nodes that can have several alternatives in its structure and/or value, you need to enclose the set of related alternatives within a Choice node and each alternative branch into an Option node.

A Choice node is a virtual node identifying alternative branches. Each alternative branch is a possible option and is represented by an Option virtual node as illustrated in the following example:

Figure 4.23. Example of a choice

There are two Choice nodes, one for the buyer's information, that accepts either a company structure with a VAT number value, or a person structure with firstname, lastname and address values. The other Choice node is for the price of an Item, it can accept either a price with a 0% or a 21% VAT.

In this latter case, both alternative branches have the same structure, but they have different static values (0 or 21) for their VAT node (static value nodes are green).

It is mandatory that each Option of a Choice is uniquely identifiable compared to each others. They could be identified by having different structures (like the buyer's Choice example) or by having the same structure with different static values (like in the price Choice example).

Create loops to manage repetitive parts of your message definition.

Loops and grouping

A message is based on three node types as defined in the Message Definition chapter.

To specify that a value or a structural node can occur more than once, you need to enclose it in a Loop. A Loop is a virtual node representing the multiplicity of a node or a set of nodes. It is defined by its minOccurs and maxOccurs properties:

CSV Sample:

By definition a CSV message is composed of a header containing some header items followed by one or many lines containing line items. The number of line items correspond to the number of header items.

header1,header2,header3,header4
123,aaa,abc,000
456,bbb,def,111
789,ccc,ghi,222
...

Here is the message tree for this CSV:

Figure 4.24. Message tree

The headers and line nodes are structural nodes while header and line items are value nodes. To specify that the line can appear more than once, there is a virtual Loop node enclosing the line node.

Grouping

A Loop can define the multiplicity of a node sequence. To identify a node sequence in a Loop, you must manually group those relevant nodes using one of the following grouping type:

Loop parameters can be edited by right-clicking on the loop node in the message tree in the in or out message tab durint channel editing.

Figure 4.25. Loop parameters

The grouping value is an XPath expression identifying the grouping pattern.

By right clicking on any node, you can:

Regrouping a Loop

An existing loop can also be regrouped using one of the Grouping type. To do this you can use the Regroup this Loop in the loop contextual menu. This will create a new enclosing loop that requires specifying the Grouping type and the Grouping value.

Example with a DESADV message in a CSV format:

TruckId,PalletId,PacketId,Quantity,Item
 1,       1,       1,       5,Item 1
 1,       1,       1,      25,Item 2
 1,       1,       1,       1,Item 3
 1,       1,       2,       3,Item 4
 1,       1,       2,      15,Item 5
 1,       2,       1,     100,Item 6
 1,       2,       1,       2,Item 7
 1,       2,       3,      20,Item 8
 1,       2,       3,      11,Item 9
 1,       2,       3,       9,Item 10
 1,       2,       4,      72,Item 11
 2,       1,       1,      91,Item 12
 2,       2,       1,     423,Item 13
 2,       3,       1,      88,Item 14
 2,       4,       1,       3,Item 15
 3,       1,       1,      12,Item 16
 3,       1,       1,      21,Item 17
 3,       1,       1,     666,Item 18
 3,       1,       2,       3,Item 19
 3,       1,       2,      22,Item 20
 3,       1,       2,       2,Item 21
 3,       2,       1,     211,Item 22
 3,       2,       1,      64,Item 23
 4,       1,       1,      61,Item 24
 4,       1,       1,      17,Item 25
 4,       1,       2,       2,Item 26
 4,       1,       2,       9,Item 27
 4,       1,       2,      85,Item 28
 5,       1,       1,      57,Item 29

Figure 4.26. Default message tree

In this example, we have a loop of lines defining an item to dispatch, where each line has the truck id where the item is stored.

We could regroup this loop of lines by TruckId so we can loop on all trucks and then loop inside each truck on all items in that truck.

To do that we select the Regroup this Loop action on the loop, select the Group By value for Grouping type and set it to ' field[1] ' (as this is the XPath of the TruckId element).

Figure 4.27. Regroup this loop

We now have a loop on all trucks and a sub loop on all item in a truck.

Figure 4.28. Sub loop

We can even go further and decide to group by PalletId and PacketId, that would give us four nested loops, one for all trucks, the next one for all pallets in a truck, the next one for all packets in a pallet and the last one, for all items in a packet.

Figure 4.29. ...

A CSV or comma-separated values file is used for the digital storage of data organized in a table form. Each line in the CSV file corresponds to a row in the table, and within a line, fields are separated by commas (or semicolons, colons or tabs), each field belonging to one column of the source table.

As this is a very common and simple file format, CSV files are often used to move tabular data between different computer programs, such as between a database and a spreadsheet program.

File sample

Following is a sample CSV file.

NAV Date,ISIN,Fund Name,Share Typ,Fund Ccy,NAV in Fund Ccy,Bid Price in Fund Ccy,Offer Price in Fund Ccy,TNA,Outstanding,Publication Ccy,NAV in Publication Ccy,Bid Price in Publication Ccy,Offer Price in Publication Ccy,Equity Profit,WKN Code,Zwischengewinn,TIS,TID
06/13/2008,LU0223208157,HSBC GIF EMERGING EUROPE EQUITY,AC,EUR,15.088,15.088,15.924,12190498.17,807980.236,GBP,11.96,11.96,12.623,37.650,A0ER9A,0.001,,

The following properties are available :

United Nations / Electronic Data Interchange for Administration, Commerce and Transport (UN/EDIFACT) is the international EDI standard developed under the United Nations impulse. This standard is maintained and further developed by a UN body. EDIFACT has now been adopted by the International Organization for Standardization (ISO) as the ISO standard ISO 9735.

The EDIFACT standard provides a set of syntax rules to structure data, an interactive exchange protocol (I-EDI), and standard messages which allow multi-country and multi-industry exchange.

As Babelway supports all EDI transaction sets of the EDIFACT standard, you can use any of them in your own gateway setup.

Babelway supports all following EDIFACT documents:

APERAK, AUTHOR, AVLREQ, AVLRSP, BALANC, BANSTA, BAPLIE, BERMAN, BMISRM, BOPBNK, BOPCUS, BOPDIR, BOPINF, BUSCRD, CALINF, CASINT, CASRES, CHACCO, CLASET, CNTCND, COACSU, COARRI, CODECO, CODENO, COEDOR, COHAOR, COLREQ, COMDIS, CONAPW, CONDPV, CONDRA, CONDRO, CONEST, CONITT, CONPVA, CONQVA, CONRPW, CONTEN, CONWQD, COPARN, COPAYM, COPINO, COPRAR, COREOR, COSTCO, COSTOR, CREADV, CREEXT, CREMUL, CUSCAR, CUSDEC, CUSEXP, CUSPED, CUSREP, CUSRES, DAPLOS, DEBADV, DEBMUL, DEBREC, DELFOR, DELJIT, DESADV, DESTIM, DGRECA, DIRDEB, DIRDEF, DMRDEF, DMSTAT, DOCADV, DOCAMA, DOCAMI, DOCAMR, DOCAPP, DOCARE, DOCINF, ENTREC, FINCAN, FINPAY, FINSTA, GENRAL, GESMES, HANMOV, ICASRP, ICSOLI, IFCSUM, IFTCCA, IFTDGN, IFTFCC, IFTICL, IFTMAN, IFTMBC, IFTMBF, IFTMBP, IFTMCA, IFTMCS, IFTMIN, IFTRIN, IFTSAI, IFTSTA, IFTSTQ, IHCEBI, IHCLME, IMPDEF, INFCON, INFENT, INSDES, INSPRE, INSREQ, INSRPT, INVOIC, INVRPT, IPPOAD, IPPOMO, ISENDS, ITRRPT, JAPRES, JINFDE, JOBAPP, JOBCON, JOBMOD, JOBOFF, JUPREQ, LEDGER, LREACT, LRECLM, MEDPID, MEDPRE, MEDREQ, MEDRPT, MEDRUC, MEQPOS, MOVINS, MSCONS, ORDCHG, ORDERS, ORDRSP, OSTENQ, OSTRPT, PARTIN, PASREQ, PASRSP, PAXLST, PAYDUC, PAYEXT, PAYMUL, PAYORD, PRICAT, PRIHIS, PROCST, PRODAT, PRODEX, PROINQ, PROSRV, PROTAP, PRPAID, QALITY, QUOTES, RDRMES, REBORD, RECADV, RECALC, RECECO, RECLAM, RECORD, REGENT, RELIST, REMADV, REPREM, REQDOC, REQOTE, RESETT, RESMSG, RESREQ, RESRSP, RETACC, RETANN, RETINS, RPCALL, SAFHAZ, SANCRT, SKDREQ, SKDUPD, SLSFCT, SLSRPT, SOCADE, SSIMOD, SSRECH, SSREGW, STATAC, STLRPT, SUPCOT, SUPMAN, SUPRES, TANSTA, TAXCON, TIQREQ, TIQRSP, TPFREP, TSDUPD, TUPREQ, TUPRSP, UTILMD, UTILTS, VATDEC, VESDEP, WASDIS, WKGRDC, WKGRRE

File sample

Following is a sample EDIFACT file.

UNA:+.? '
UNB+UNOC:3+000eanpimgest:14+000eanatelier:14+2009-05-26 10:41:34.524 +0200:2009-05-26 10:41:34.524 +0200+1518'
UNH+1+DESADV:D:01B:UN:EAN007'
BGM+351+0000090027+9'
DTM+137:200905190938:203'
DTM+17:200905150000:203'
DTM+2:200905150000:203'
DTM+171:20090519:102'
NAD+BY+000eanatelier::9++LATELIER+Chausse de Lige 477+JAMBES++5100+BE'
NAD+SU+000eanpimgest::9++PmiGest+Parc Scientifique Cralys+LES ISNES++5032+BE'
TDT+1++30'
CPS+1'
PAC+2+:52+201::9'
CPS+2+1'
PAC+1+:52+201::9'
MEA+PD+AAC+KGM:0'
MEA+PD+T+KGM:0'
PCI+33E'
GIN+BJ+p00001'
PCI+34E'
GIN+SRV+05400111005652'

ASC X12 (also known as ANSI ASC X12) is the official designation of the U.S. national standards body for the development and maintenance of Electronic Data Interchange (EDI) standards. ASC X12 has sponsored more than 315 X12-based EDI standards for health care, insurance, government, transportation, finance, and many other industries.

Babelway supports all following X12 documents:

Order Series (ORD), Materials Handling Series (MAT), Tax Services Series (TAX), Warehousing Series (WAR), Financial Series (FIN), Government Series (GOV), Manufacturing Series (MAN), Delivery Series (DEL), Engineering Management and Contract Series (ENG), Insurance/Health Series (INS), Miscellaneous ANSI X12 Transactions Series (MIS), Mortgage Series (MOR), Product Services Series (PSS), Quality and Safety Series (QSS), Student Information Series (STU), Transportation (Air and Motor Series (TAM) - Ocean Series (TOS), Rail Series (TRS),Automotive Series (TAS)

File sample

Following is a sample X12 file.

ISA*00*          *00*          *ZZ*SENDERISA      *ZZ*RECEIVERISA    *960807*1548*U*00401*000000020*0*T*>~
GS*IN*SENDERDEPT*007326879*19960807*1548*000001*X*004010~
ST*810*000000001~
BIG*20090927*00027**A00027-01~
N1*ST*CHOCOLATE IMPORT*9*1234567890~
N3*1000 N. NORTH HIGHWAY~
N4*NEW YORK*NY*10310~
N1*BT*RETAILER INC.*9*1098765432~
N3*P.O. BOX 0000~
N4*LAKE*VA*20120~
N1*RE*FOODSELLER*9*12345QQQQ~
N3*P.O. BOX 222222~
N4*FAIRFAX*VA*94978~
ITD*01*3*1**15**16~
FOB*PP~
IT1**16*CA*12.34**UA*006540022222~
PID*F****BELGIUM CHOCOLATE~
IT1**13*CA*12.34**UA*006540033333~
PID*F****SWISS CHOCOLATE~
TDS*35786~
CAD*****FREEFORM~
ISS*29*CA~
CTT*2~
SE*22*000000001~
GE*1*000001~
IEA*1*000000020~
		

XML stands for eXtensible Markup Language and is a very common type of files.

File sample

Following is a sample XML file.

<?xml version="1.0"?>
<Document>
<SenderID>5420008199981</SenderID>
<ReceiverID>5400102000086</ReceiverID>
<DocumentDate>20080531170538</DocumentDate>
<DocumentNumber>VK20084010</DocumentNumber>
<TestIndicator>P</TestIndicator>
<DocumentLanguage>NL</DocumentLanguage>
<Version>1.1/Food</Version>
<Invoice>
<MessageReferenceNumber>VK20084010</MessageReferenceNumber>
<InvoiceHeader>
<MessageType>INV</MessageType>
<MessageNumber>VK20084010</MessageNumber>
<MessageFunction>ORI</MessageFunction>
<InvoiceCurrency>EUR</InvoiceCurrency>
<Dates>
<InvoiceDate>20080531170538</InvoiceDate>
<AccountingValueDate>20080531170538</AccountingValueDate>
<DeliveryDate>20080530170738</DeliveryDate>
<OrderDate>20080530170538</OrderDate>
</Dates>
</InvoiceHeader>
<InvoiceDetail>
<InvoiceItem>
<ItemType>GDS</ItemType>
<LineItemNumber>1</LineItemNumber>
<EANArticleNumber>95400102057205</EANArticleNumber>
</InvoiceItem>
</InvoiceDetail>
</Invoice>
</Document>

File sample

Following is a sample Excel file having headers at the first row of the Excel sheet.

Figure 4.30. Excel Sample file

PDF Wizard screen allows you to define your PDF message format based on your XHTML template file.

To define a message in PDF format, select an existing template or make a copy of the generic PDF template in the catalogue and following screen will be displayed.

Wizard screen

When you create a new message format, you must first configure it using the following wizard.

Figure 4.31. PDF Wizard screen

An PDF messsage can only be set up using a template file in XHTML format. Select your template file using the Browse... button next to the XHTML file, then click on the Upload command.

File sample

Following is a sample PDF file.

		
<?xml version="1.0" encoding="UTF-8"?>
<html xmlns="http://www.w3.org/1999/xhtml">
   <head>
      <title>PDF output</title>
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
     
<style>
 @page { size: A4; margin: 3cm 1.5cm 2cm 1.5cm; border: none; padding: 1em; }
 @page { @top-left{content: ""; }}
 @page { @top-right{content: "Page " counter(page) " on " counter(pages);}}
 @page { @bottom-left{content: element(footer);border-top: solid 0.01mm #000; }}

 #footer{display: block; position: running(footer); }
</style>
	 
   </head>
   <body style="font-size: 12pt; font-family: 'Nobile'"> 

      <center>
         <h1 >PDF output example</h1>
      </center>
      <br/>
      <div style="font-size: small">
         <span>Date :</span>
         <span id="invoiceDate">25-08-2009</span>
      </div>
      <br/>
      <center style="font-size: large">Example</center>
      <br/>
      <table style="width: 100%" >
         <tr>
            <td rowspan="1" style="width: 200px; height: 20px;">
               <span>Invoice number :</span>
               <span id="invoiceNumber">field1</span>
            </td>
            <td style="width: 300px; height: 20px;">
               <span>Contact Name :</span>
               <span id="firstName">field2</span>
               <span id="lastName">field3</span>
            </td>
         </tr>
      </table>
      <br/>
      <center>
         <span>Some static info</span>
      </center>
		<table style="width: 100%" dir="ltr" frame="box">
		  <tbody>
			<tr>
			  <td bgcolor="#cdd5cb" rowspan="1"
				style="width: 120px; height: 30px;">Description</td>
			  <td bgcolor="#cdd5cb" style="width: 80px; height: 30px;">Unit price</td>
			  <td bgcolor="#cdd5cb" style="width: 40px; height: 30px;">Qty</td>
			  <td bgcolor="#cdd5cb" style="width: 80px; height: 30px;">Vat rate</td>
			  <td bgcolor="#cdd5cb" style="width: 100px; height: 30px;">Tax free
			  price</td>
			  <td bgcolor="#cdd5cb" style="width: 80px; height: 30px;">Tax</td>
			  <td bgcolor="#cdd5cb" style="width: 80px; height: 30px;">Total price</td>
			</tr>
			<tr id="product-loop">
			  <td style="width: 120px; height: 20px;" rowspan="0"><span
				id="itemDescription">Support pack 5h</span> </td>
			  <td style="width: 80px; height: 20px" align="right"><span
				id="itemUnitPrice">425.00</span> </td>
			  <td style="width: 40px; height: 20px" align="right"><span
				id="itemQuantity">1</span> </td>
			  <td style="width: 80px; height: 20px" align="right"><span
				id="itemVatRate">21.00</span> </td>
			  <td style="width: 100px; height: 20px" align="right"><span
				id="itemTaxFreePrice">425.00</span> </td>
			  <td style="width: 80px; height: 20px" align="right"><span
				id="itemTax">89.25</span> </td>
			  <td style="width: 80px; height: 20px" align="right"><span
				id="itemTotalPrice">514.25</span> </td>
			</tr>
		  </tbody>
		</table>
		<br />	  
      <center style="page-break-before:always">
         <span>second page</span>
      </center> 
      <br/>
      You can upload images or css sheets as file properties and use a simple relative url in your xhtml.
      <br/>  
      <br/>    
      For specific print css options, see http://www.w3schools.com/css/css_reference.asp for all css options 
      <br/>  
      <br/>  	  
      <h2>Barcode Integration</h2>
        <br/> 
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="EAN13">123456789012345675</barcode>
        <br/>
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="EAN8">123456789012345675</barcode>
        <br/>
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="UPCA">123456789012345675</barcode>
        <br/>
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="UPCE">01234133</barcode>
        <br/>
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="CODABAR">A123456789A</barcode>
        <br/>
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="CODE39">123456789012345675</barcode>
        <br/>
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="CODE39_EXTENDED">123456789012345675</barcode>
        <br/>
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="CODE128">123456789012345675</barcode>
        <br/>
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="CODE128_UCC">123456789012345675</barcode>
        <br/>
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="CODE128_RAW">123456789012345675</barcode>
        <br/>
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="EAN8">123456789012345675</barcode>
        <br/>
        <barcode style="display: inline-block; width: 300px; height: 200px;" type="POSTNET">123456789012345675</barcode>
        <br/>
	  <div id="footer">
		Footer line#1<br/>Footer line#2
	  </div>

   </body>
</html>		
		
		

Edit screen

Once the message format template has been uploaded, or when it is used or copied from a saved format, you have the possibility to go on the created element. If you want to edit the properties of that message definition, switch to "Properties".

Figure 4.32. PDF Edit screen

In order to ease the navigation, the xhtml attribute id is used as the name in the resulting message definition. These elements are visible by default. Mapping to these elements will be preserve if you upload a other template containing the element with the same id.

If you need to add a loop to your xhtml, you can simply name the element with a suffix -loop like in the example above. The system will create a loop and a corresponding element. Mapping to these elements will also be preserved if you upload a other template.

All elements without id in the xhtml will be hidden by default. If you cannot add an id to your element, you have to manually show any element you need in the transformation step. Additionaly, you should edit and rename the element label for easier management during transformation step.

To ease the search of the fields you need, the values uploaded from your example file are displayed in the field tooltip descriptions.

See Message Definition to change show/hide parameter and edit the element label.

Multirecord Wizard screen allows you to define your Multirecord message format (delimited or a fixed-length) according to your own file format.

What is mr file?

The mr file is a multirecord definition file which is used by the Self-Service MultiRecord wizard to generate the corresponding message definition and also to build the corresponding servingxml resource file.

How to build mr file?

For fixed-length messages, the mr file header will look like this:

<multirecord name="mymultirecord" type="fixed-length" lineDelimited="true" recordDelimiter="\r\n" quoteSymbol-character="&quot;" quoteSymbol-escapeSequence="\&quot;" xmlns="http://xmlns.babelway.com/2007/multi-record">

For the delimited messages the mr file header will look like this:

<multirecord name="mymultirecord" type="delimited" fieldDelimiter="," recordDelimiter="\r\n" quoteSymbol-character="&quot;" quoteSymbol-escapeSequence="\&quot;" xmlns="http://xmlns.babelway.com/2007/multi-record">

* recordDelimiter defines the delimiter between each record, it is usually the ending line character represented on windows by \r\n, on Unix/Linux by \n and on Macintosh by \r.

* lineDelimited specify if the system use a record delimiter. If set to false, record will be based on the sum of the fields lenght for fixed length or the number of fields for delimited multirecords.

* trim specify if the white spaces in the begining and the end of the fields should be removed.

* fieldDelimiter, only used whith a delimited message, defines the field delimiter.

* quoteSymbol-character is the character used to quote a field (often ")

* quoteSymbol-escapeSequence is the sequence that will display the quote symbol character in a quoted field (often \")

Hint:

For multirecord as message in, do not specify recordDelimiter. The system will catch the \r or \n or \r\n. For multirecord as message out, DO specify recordDelimiter as being for instance "\r\n"; this will generate windows compliant file and let you change the delimiter from the advanced properties later on.

You should specify the name for the record and for each of its field. Each record should have at least one field with a static value which will be used to identify the record.

<record name="Record1">
	    <field name="recordType" value="R1" width="2"/>
	    <field name="field1" width="5"/>
	    <field name="field2" width="3"/>
	</record>

* the width is only mandatory for fixed-length messages

* value is used to specify that the field has a static value that will never change

By default all first fields with a static value are used to identify a record. But, you can also manually defines which fields must be used to identify a record using the identifier paramter.

<record name="Record1">
	    <field name="recordType" value="R1" width="2" />
	    <field name="fieldA" width="5"/>
	    <field name="fieldB" width="3" value="BBB" identifier="true"/>
	    <field name="fieldC" width="7" />
	    <field name="fieldD" width="2" value="DD" identifier="true"/>
	</record>

In this case, only the third and fifth fields (fieldB & fieldD), with identifier equals to true, will be used to identify the record. The default (without identifier=true) would only use recordType field as the identifier.

Remark:

For fixed-length messages, the fields used to identify a record should have the same position and length in each record. No overlap between identifiers is allowed between records.

If a fixed-length message have variable length identifier per records, the only way to define it in the mr files is to first define the smallest common length identifier for all records and then for each records that have longer identifier, add as many as smaller field needed to unambiguously identify each record.

For example if we have a message where AAAAA, 111 and 2222 are identifier like in the following:

AAAAA contentcontent   anothercontent
	1112222  this and that

The following definition is not valid since the fieldA is bigger than field1 and moreover, fieldA also overlaps with field2

<record name="Record1">
	    <field name="fieldA" width="5" value="AAAAA" identifier="true"/>
	    <field name="fieldB" width="15" />
	    <field name="fieldC" width="17" />
	</record>
	
	<record name="Record2">
	    <field name="field1" width="3" value="111" identifier="true"/>
	    <field name="field2" width="4" value="2222" identifier="true"/>
	    <field name="field3" width="20" />
	</record>
	

It should be replaced by:

<record name="Record1">
	    <field name="fieldA" width="3" value="AAA" identifier="true"/>
	    <field name="fieldA" width="2" value="AA" identifier="true"/>
	    <field name="fieldB" width="15" />
	    <field name="fieldC" width="17" />
	</record>
	<record name="Record2">
	     <field name="field1" width="3" value="111" identifier="true"/>
	    <field name="field2" width="2" value="22" identifier="true"/>
	    <field name="field2" width="2" value="22" identifier="true"/>
	    <field name="field3" width="20" />
	</record>

We had to split the fieldA in two in order to have one fieldA with the length 3 (the same as field1) with another fieldA with the remaining length 2.

Then the field2 (length 4) was also bigger than the second fieldA (length 2) so we also need to split it in two field2 of length 2.

All corresponding identifier have now the same length (3 and 2) and there is no overlap between them.

It is also possible to add 4 extra parameters label, description, justify & padCharacters to each field

<field name="myField" label="My Field" description="My field description" justify="right" padCharacter="x" width="10"/>

* label and description are used to display the message tree

* justify can be center, left or right

* padCharacter is the character used to fill empty space in the field width

 <xml>
	    <group name="Transaction" maxOccurs="unbounded">
	          <group name="headers">
	             <record name="header" minOccurs="1" maxOccurs="unbounded"/>
	          </group>
	          <record name="record1" maxOccurs="unbounded"/>
	          <group name="footers">
	             <record name="footer" />
	          </group>
	     </group>
	  </xml>

* Each element can define the minOccurs and the maxOccurs parameter with either a 0, a positive number or 'unbounded'.

* Records defined in the records simplesect can only appear once in the message structure.

* Records can be grouped using the group element. The name of the group is mandatory.

* Records in a group should be ordered in the same way they appeared at the message.

Sample multirecord fixed-length message

HH00123  AB
HH00045 CDE
R1one  100
R1two  101
R1four 103
FF3

Sample multirecord definition file

<?xml version="1.0" encoding="UTF-8"?>
<multirecord name="mymultirecord" type="fixed-length" recordDelimiter="\r\n" quoteSymbol-character="&quot;" quoteSymbol-escapeSequence="\&quot;" xmlns="http://xmlns.babelway.com/2007/multi-record">
<records>
<record name="header">
<field name="recordType" value="HH" width="2"/>
<field name="header1" width="5" justify="right" padCharacter="0" />
<field name="header2" width="4" justify="right" padCharacter=" " />
</record>
<record name="record1">
   <field name="recordType" value="R1" width="2"/>
   <field name="field1" width="5" label="My field" description="My field Descritpion" />
   <field name="field2" width="3"/>
</record>
<record name="footer">
<field name="recordType" value="FF" width="2" />
<field name="footer1" width="1"/>
</record>
</records>
<xml>
       <group name="Transaction" maxOccurs="unbounded">
          <group name="headers">
             <record name="header" minOccurs="1" maxOccurs="unbounded"/>
          </group>
          <record name="record1" maxOccurs="unbounded"/>
          <group name="footers">
             <record name="footer" />
          </group>
       </group>
    </xml>
</multirecord>

File sample

Following is a sample Flat file.

EE54001340000093012918100700000000000147521
DD0000018713906060109 6011                               3005330101
DD0000028713906061106 6111                               3005250201

Tradacoms is an early standard for EDI (Electronic Data Interchange) primarily used in the UK retail sector. It was introduced in 1982 as an implementation of the UN/GTDI syntax, one of the precursors of EDIFACT, and was maintained and extended by the UK Article Numbering Association (now called GS1 UK).

As Babelway supports all TRADACOM transaction sets of the TRADACOM standard, you can use any of them in your own gateway setup.

Babelway supports all following TRADACOM documents:

1.ACKHDR, ACKMNT, ACKTLR, AVLDET, AVLHDR, AVLTLR, CORDER, CORHDR, CORTLR, CRAHDR, CRAINF, CRATLR, CREDIT, CREHDR, CRETLR, CUSHDR, CUSINF, CUSTLR, DELHDR, DELIVR, DELTLR, DLCDET, DLCHDR, DLCTLR, DRAHDR, DRAINF, DRATLR, EXCHDR, EXCINF, EXCTLR, GENHDR, GENRAL, GENTLR, INVFIL, INVOIC, INVTLR, LPRDET, LPRHDR, LPRTLR, ORDERS, ORDHDR, ORDTLR, PAYHDR, PAYINF, PAYTLR, PICHDR, PICKER, PICTLR, PPRDET, PPRHDR, PPRTLR, PRIHDR, PRIINF, PRITLR, PROHDR, PROINF, PROINF, PROTLR, RSGRSG, SADDET, SADHDR, SADTLR, SNPHDR, SNPHDR, SNPSTS, SNPTLR, SRMHDR, SRMINF, SRMTLR, UCNDET, UCNHDR, UCNTLR, UCNTLR, UPLHDR, UPLIFT, UPLTLR, UTLBIL, UTLHDR, UTLTLR, UVATLR, VATTLR

File sample

Following is a sample TRADACOM invoice file.

STX=ANAA:1+501xxxxxxxxxx:name+501xxxxxxxxxx:NAME SERVICES (U.K.)LTD.+040316:184411+00001++INVTES'
MHD=1+INVFIL:9'
TYP=0700+INVOICES'
SDT=501xxxxxxxxxx:053752CF01STDD+Tenprl Fnsrjnl Sbbqfreivpr+221 UvyyunyyRoad:Yvfohea:Co. Antrim:N.Ireland:OG27 5WQ+412557175'
CDT=501xxxxxxxxx+NAMESERVICES (U.K.) LTD.+Cnexynaqf Pbheg:OvezvatunzTerng Cnex:Ehorel:Birmingham:OG45 9CM'
FIL=1+1+040316'
FDT=040302+040302'
MTR=7'
MHD=2+INVOIC:9'
CLO=0000000100007: ++PNEEVPX GOLF CLUB:ABEGU ROAD:PNEEVPX SRETHF::OG388YC'
IRF=01000589M+040302+040302'
ODD=1+::040302+:040302'
ILD=1+1+:8408++:31266+0+2:2500:KG+54300+135800+Z+0+++SILVERSIDE 1-5 KG'
STL=1+Z+0+0+1358+++++1358++0+0++1358'
TLR=1+1358+++++1358++1358+0++1358'
MTR=8'
MHD=3+VATTLR:9'
VRS=1+Z+0+1358+1358+0+1358+1358'
MTR=3'
MHD=4+INVTLR:9'
TOT=1358+1358+0+1358+1358+1'
MTR=3'
MHD=5+RSGRSG:2'
RSG=00001+501xxxxxxxxxx'
MTR=3'
END=5'

JSON Wizard screen allows you to define your JSON message format according to your own file format.

JSON (JavaScript Object Notation) is a lightweight text-based open standard designed for human-readable data interchange. It is derived from the JavaScript scripting language for representing simple data structures and associative arrays, called objects. Despite its relationship to JavaScript, it is language-independent, with parsers available for many languages. The JSON format is often used for serializing and transmitting structured data for web applications.

To define a message in JSON format, select an existing template or make a copy of the generic JSON wizard in the catalogue and following screen will be displayed.

File sample

Following is a sample JSON file.

	{
	"id": "0001",
	"type": "donut",
	"name": "Cake",
	"ppu": 0.55,
	"batters":
		{
			"batter":
				[
					{ "id": "1001", "type": "Regular" },
					{ "id": "1002", "type": "Chocolate" },
					{ "id": "1003", "type": "Blueberry" },
					{ "id": "1004", "type": "Devil's Food" }
				]
		},
	"topping":
		[
			{ "id": "5001", "type": "None" },
			{ "id": "5002", "type": "Glazed" },
			{ "id": "5005", "type": "Sugar" },
			{ "id": "5007", "type": "Powdered Sugar" },
			{ "id": "5006", "type": "Chocolate with Sprinkles" },
			{ "id": "5003", "type": "Chocolate" },
			{ "id": "5004", "type": "Maple" }
		]
	}
	

SAP IDOC are the well-known SAP interchange formats. You can obtain the definition parser directly from SAP. In order to do this, select the transaction WE63. Select Basic type or Extended Type according IDoc extensions usage.

IDOC parser sample

Following is a sample SAP IDOC file.

BEGIN_RECORD_SECTION
   BEGIN_CONTROL_RECORD
     BEGIN_FIELDS
       NAME                TABNAM
       TEXT                Name of external structure
       TYPE                CHARACTER
       LENGTH              000010
       FIELD_POS           0001
       CHARACTER_FIRST     000001
       CHARACTER_LAST      000010

       NAME                MANDT
       TEXT                Client
       TYPE                CHARACTER
       LENGTH              000003
       FIELD_POS           0002
       CHARACTER_FIRST     000011
       CHARACTER_LAST      000013

       NAME                DOCNUM
       TEXT                IDoc number
       TYPE                CHARACTER
       LENGTH              000016
       FIELD_POS           0003
       CHARACTER_FIRST     000014
       CHARACTER_LAST      000029

       NAME                DOCREL
	   ...
	

Not Defined message format is used when in and out message format does not need to be defined because no processing will be performed on it and no change is required.

(for format not natively supported by Babelway): advanced users have the option to upload programmatic code that provides support to proprietary messages formats, such as specific binary ERP format (for example idoc of SAP...)

If message in format is "Not defined", so should be out message otherwise output may return unexpected results or empty message.

Usually, this setting is used in combination with No Transformation in a channel that simply transfers an unchanged and unprocessed message from one gateway to another different one.

Generic Wizard screen allows you to define your generic message format according to your own file format.

The general tab contains the signaletic information of the gateway, and offers actions that act on the whole transformation.

Following of the type of the transformation, these tabs define all the rules that must be applied to convert the message in to the message out.

See Drag and Drop Transformation for defining transformation with the visual editor.

See Xslt Transformation for defining the transformation by writing an xslt.

This tab contains quick links to many other elements related to this gateway.

This tabs shows you all the history of changes on this gateway, and allows you to revert to a past version. For more details, see the change log section.