Learn how to communicate and exchange information with your partners, suppliers, and customers with SnapLogic’s EDI Snap Pack.
Learn more about the EDI Snap Pack in the blog post, “SnapLogic November 2018 Release: Revolutionize your business with intelligent integration.”
Hi! In this demo, I will walk you through SnapLogic’s B2B integration capabilities so you can integrate backend systems and move EDI documents into other applications such as ERP, CRM, and more. EDI or electronic data interchange is an electronic communication method with standardized formats and protocols for exchanging data via any electronic means between different trading partners. By using SnapLogic’s EDI Snap Pack, which includes the Create EDI Transaction Snap and Get EDI Transaction Snap, you can easily transact with your partners.
In this demo, I will show how buyers like Walmart and suppliers like Clover can use the SnapLogic EDI Snap Pack to achieve the use case order to cash. Walmart creates a purchase order and sends it to Clover to purchase grocery items. A purchase order X12 EDI file is dropped into an EDI folder.
In production this actually comes from an external trading partner via AS2, FTP or WAN. However, I will simulate this by dropping it directly into the EDI folder. The B2B Gateway transforms the X12 document into a JSON file and validates it.
SnapLogic then posts this transaction from the B2B Gateway using the Get EDI Transaction Snap. You can also select the Partner ID or list of transaction types. Here we are selecting Purchase Order but you can select different types of transactions.
If there are any inbound or outbound transactions, SnapLogic shows the business number and Transaction ID that comes with an associated transaction.
Then Clover receives the specific purchase order and stores it into their NetSuite ERP system.
Clover will then generate or create an invoice from the purchase order. The invoice enters into the Create EDI Transaction Snap that shows the Partner ID and transaction type. For this use case, I select invoice.
As we could see from the output, there is a Transaction ID that has been created.
The invoice is then mapped to a B2B gateway schema. The B2B gateway then validates, applies rules and transforms to X12. The invoice X12 shows up in this specific SFTP folder, but in production this can be sent to an ERP system where I can read the specific Transaction ID and we can see it as part of the output.
Thank you for watching this video. For more information, please visit docs-snaplogic.atlassian.net.