Introduction When we work with B2B using EDI standards in logic apps we use Decode component which does work of validation and decodes the EDI(flat file) and b ased on the settings we specify in Agreement, the Transaction sets are splitted ( one edi document comprise of segments contained in ST to SE) and is available in Payload of Decode component   for further use.  EDI X12 messages are wrapped with envelope, at header it has ISA segment (Interchange control header), GS (Functional group) and ST (Transaction Set) and at the trailer it has IEA, GE and SE. Enveloping segments work in pairs. ISA-IEA represents an interchange. GS-GE is a functional group inside of the interchange and ST-SE is a transaction inside the group. Most of the time, we need to map the individual edi documents( ST-SE)  to destination system's expected format. Read example about it -  Getting Started with Logic Apps - EDI X12 to XML   where following map was used ...

Introduction Any organisation which needs to do Business to Business communication using EDI Standards (EDI X12, EDIFACT, TRADACOMS etc) need to have some EDI System/Tool/Processor/Translator which does understand EDI standards and capable of receiving and sending the EDI messages. In following post I  have explained the basics o f EDI and EDI X12 standards   And before starting the communication the business partners decide on how communication will be (transport protocol), what data format will be used , whether Acknowledgement is required etc etc and a ll this becomes the part of Agreement between them . Following is high level picture of B2B EDI communication When a EDI document is to be sent the Partner 1 EDI system refers to Agreement and creates the documents as per the instructions in it. When a EDI document is to be received by the Partner 2, it's EDI system refers to Agreement to Validate the incoming document and to check if Acknowledgement - Techni...