Continuing from last post where I explained the basics of EDI and EDI X12 standards , let’s  see how we can enable EDI communication with Logic Apps Logic Apps and EDI together Earlier it was BizTalk from Microsoft which has all capabilities around Enterprise Application Integration(EAI) and Electronic Data Interchange (EDI)(which is server product) but with the cloud shift where everything is desired as service, Microsoft provided Logic Apps to cater the integration needs for cloud users and it is continuously getting matured (most of BizTalk capabilities already added). Read more about  Logic App Fundamentals To enable the logic apps to be leveraged in Business to Business EDI communication Microsoft introduced Enterprise Integration Pack,  which adds B2B capabilities like AS2 and X12, EDI standards support , XML capabilities like XML Validation, XSLT Transformation, Flat file to XML encode/decode etc.(Available as actions in Logic app e.g., AS2 De...

In07oduction It is very common scenario to map values from a loop in the applications where EDI X12 schemas are used and one of them is N1 Loop. Loops are nothing but blocks of repeating data. And N1 loop is such block which has address related data (Party Identification).   It is not mandatory and in the schema which ships with BizTalk, allows it to repeat up-to 200 times (EDI schema  are shipped in as a self-ex07acting executable and when ex07acted, schemas can be found at drive:\Program Files\Microsoft BizTalk Server 2010\XSD_Schema\EDI.) But it can vary and totally depends upon the requirement.  And from the multiple data, specific data is to be mapped to a particular node. In this article, BillTo and ShipTo nodes are used as an example to which data is to be mapped from repeating data (N1Loop). Input file ST*850*0001~ BEG*00*DS*45000007**20131002~ CUR*BY*USD~ REF*KK*STANDARD~ REF*BAI*8000~ REF*AAT*80206234~ REF*BLT*INVOICE~ REF*...