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 an EDI 850 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 EDI 850 document with 10 fields in less than 10 minutes. Just for this example, the target document values are hard coded. In areal 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 EDI tags or EDI syntax.

Sample Java Code:

[java]

mondEngine.setTargetHeaderValue(“MessageIdentification”,”ABC100”);

mondEngine.setTargetHeaderValue(“MessageCreationDateTime”,”2013-01-01”); //actual time shouldbe stored here

mondEngine.setTargetHeaderValue(“BuyerPurchaseOrderNumber”,”123000001”);

mondEngine..setTargetHeaderValue(“PurchaseOrderDate”,”2013-01-01”);

mondEngine.setTargetHeaderValue(“BuyerName”,”Acme Buyer”);

mondEngine.setTargetHeaderValue(“VendorName”,”MONDCloud”);

mondEngine.setTargetLevel1Value(“BuyerLineItemNumber”,1,”1”);

mondEngine.setTargetLevel1Value(“StandardPartNumber”,1,”1190011236”);

mondEngine.setTargetLevel1Value(“ItemOrderQuantity”,1,”100”);

mondEngine.setTargetLevel1Value(“ItemOrderUnitOfMeasure”,1,”EA”);

mondEngine.setTargetLevel1Value(“ItemUnitPrice”,1,”750”);

mondEngine.setTargetLevel1Value(“ItemTotalAmount”,1,”75000”);

[/java]

Sample MOND Map:

Transformed EDI 850 Document:

ISA*00* *00* *01*114747764 *08*925485US00*130716*0139*U*00501*000001032*0*T*~

GS*PO*114747764*925485US00*20130716*0139*1032*X*005010

ST*850*1032

BEG*00*SA*123000001**20130101

CUR*BY*INR

N1*BY*Acme Buyer

N1*VN*MOND Cloud

PO1*1*100.0*EA*750.0******************UK*1190011236

AMT*1*75000.0

SE*8*1032

GE*1*1032

IEA*1*000001032

You may note that in both in the MOND Java based transformation and in the MOND GUI based 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 thetarget 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 EDI 850 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 onboard new trading partners.