Data Integration as a concept is in existence for over two decades now. Inspite of its existence for such a long time, data integration has challenges that has rendered business organizations less agile due to time involved in making any changes to business messages exchanged with the trading partners and has also curtailed their ability to onboard new trading partners quickly. In a series of blogs we are showing a new approach to Data Integration that is followed in our MOND Platform. Creating a SEPA PACS.004 document is a trivial task or a difficult task depending on the tool used. In this example, I will show you how we can create an SEPA PACS.004 document with 10 fields in less than 10 minutes. Just for this example, the target document values are hard coded. In a real life map, the values will be fetched from a database or from source document or a combination of both. In the new data transformation approach we use the principle of separating the Business logic from the structure of the document. You may note that this map does not require any knowledge of SEPA message structures.Sample JavaCode: [java]_transformer.setTarget HeaderValue("MessageIdentification","ZVS1212170000667");_transformer.setTargetHeaderValue("CreationDateTime","2012-12-17T12:45:11");//actual time should be stored here_transformer.setTargetHeaderValue("NumberOfTransactions","2");_transformer.setTargetHeaderValue("Total ReturnedInterbankSettlementAmount","60.00");_transformer.setTargetHeaderValue("TotalReturnedInterbankSettlementAmountCurrency","EUR");_transformer.setTargetHeaderValue("InterbankSettlementDate",1,"2012-12-17");_transformer.setTargetLevel1Value("ReturnIdentification",1,"2352J0306732632SRAB");_transformer.setTargetLevel1Value("OriginalMessageIdentification",1,"121217101003019");_transformer.setTargetLevel1Value("OriginalMessageNameIdentification",1,"pacs.008.001.02");_transformer.setTargetLevel1Value("OriginalTransactionIdentification",1,"E034269393");_transformer.setTargetLevel1Value("OriginalInterbankSettlementAmount",1,"50.00");_transformer.setTargetLevel1Value("OriginalInterbankSettlementAmountCurrency",1,"EUR");_transformer.setTargetLevel1Value("ReturnedInterbankSettlementAmount",1,"50.00");_transformer.setTargetLevel1Value("ReturnedInterbankSettlementAmountCurrency",1,"EUR");[/java]Sample MOND Map:

Transformed PACS.004 Document:& lt;Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.004.001.02"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">  ZVS12121700006672012-12-17T12:45:112 60.002012-12-17  CLRG SUB    AXABBE22    2352J0306732632SRAB 121217101003019pacs.008.001.02 NOTPROVIDEDE034269393 50.00 50.00 You maynote that in both in the MOND Java based transformation and in the MOND GUIbased transformation the developer only builds the business logic for setting values to the commonly understood Business terms of the industry, which represents the various fields in the target document, without worrying about the structure of the target document. The all powerful and comprehensive'Create Output' method provides functionality of creating the target document based on the structure of the SEPA PACS.004 document as would be available in the MOND Semantic repository. This new data transformation approach reduces the time to build transformation, renders the transformation reusable to create target documents of different document standards of your trading partners and thereby reduces the time to on board new trading partners.

‍