top of page
  • Writer's pictureAlex James

Unraveling Boomi EDI AS2 - Deep dive into AS2 Outbound Flow

Updated: 5 days ago

B2B EDI involves exchanging documents between trading partners. In the context of the seller, EDI 850 (Purchase Order) sent from the buyer is an Inbound document and EDI 856 (Advance Ship Notice), 810 (Invoice) returned from the seller to the buyer are outbound documents.


I recommend reading my prior blog post on AS2 Inbound Flow before reading this one to better understand the context. Let’s assume FF Foods needs to send an EDI 810 to Modern SM.


 

For FF Foods, a “My Trading Partner Component” with a Public + Private key Certificate component and a “Partner that I trade with” Trading Partner Component for “Modern SM” with just public cert component is already configured.


1)      Outbound processing typically involves retrieving the data from ERP and then translating it from ERP data format to EDI using a mapping process.


2)      The translated EDI document should be passed over a Trading Partner Shape configured for AS2.


3)      The Trading Partner shape wraps the EDI transaction set (ST-SE) with EDI envelopes (ISA-IEA, GS-GE) and sends over to the trading partner via AS2.


4)      Boomi AS2 client would encrypt the EDI document using the encryption algorithm and the public certificate configured in the “Modern SM” Trading Partner component. If signing is enabled, AS2 client will sign the document using the “Signature Secure Hash Algorithm” configured in “Modern SM” Trading Partner component and private key configured in “FF Foods” My Trading Partner Component


5)      If MDN is requested by the AS2 client, the receiving trading partner would return a MDN signed by its private key. In our use case, Modern SM would return a MDN signed by its private key which would then be verified by Boomi AS2 processor using the Modern SM public key configured in “Modern SM” Trading Partner component.


6)      The trading partners should agree on encryption and signing algorithms and any mismatch in settings would result in AS2 errors. Also, the trading partners should ensure they share the corresponding public certificate for the private key configured in their EDI AS2 software so that there are no cert mismatch errors.


Should you have anything more to add, please put in comments!

239 views0 comments

Comments


bottom of page