Overview

SnapLogic's B2B solution allows you to integrate the EDI gateway of 1EDISource with another EDI gateway or B2B solution to send and receive B2B data. You can integrate with multiple applications supported by SnapLogic, such as NetSuite, SAP, Oracle, etc.

Below is an overview of the B2B integrated solution:

Supported B2B Gateway Protocols

• File Transfer Protocol (FTP)
• SSH File Transfer Protocol (SFTP)
• File Transfer Protocol secure (FTPs) 
• Applicability Statement 2 (AS2)
• HTTPS Web Service

In addition to the above protocols, you can leverage a Value Added Network (VAN) through 1 EDI Source to support all common B2B protocol requirements.  

Prerequisites

• Working knowledge of the SnapLogic Intelligent Integration Platform (IIP).

• Appropriate level of access to the target endpoints to integrate.

• Access to the 1 EDI Source web visibility portal. 

Implementing a B2B Solution

To implement SnapLogic's B2B solution you must first integrate an EDI gateway with SnapLogic. While each EDI gateway will have its specifications and requirements, the general procedure to integrate it with SnapLogic is per the following:

1. Establish EDI requirements. Enter your EDI requirements in the SnapLogic EDI Discovery Questionnaire. This information is helpful in establishing your requirements from the SnapLogic B2B solution such as the trading partners to integrate and the transaction types. 
   
   
2. Setup and configure the EDI platform. Make a note of the account attributes (such as tenant URLs, passkeys, client IDs) and the file paths that you may need while configuring the accounts in SnapLogic. File Reader/Writer Snaps that read from or write to the EDI platform's account, require these account attributes and file paths. Additional requirements may be required based upon the specific account, Snaps available and client solution implementations. These will become apparent during the implementation phase with 1 EDI Source. 
   
   
3. The configuration of the EDI platform will be performed by 1 EDI Source using the EDI Discovery Questionnaire and follow up conversations throughout the implementation process. At the end of this configuration process, the three following components will be configured:
   1. The EDI Gateway
   2. The B2B transformation engine
   3. The customer-facing visibility and data insights web portal
      
      
4. Design and develop the SnapLogic Pipelines per your requirements. Use the account attributes that you stored earlier during this step. You need to build one Pipeline each for outbound and inbound transactions with the EDI platform per the following:
   1. Handling outbound transactions from the B2B Trading Partner to the Backend Application (Endpoint):
      
      
      
   2. Handling outbound transactions from the Backend Application (Endpoint) to the B2B Trading Partner: 
      
      
      
5. Monitor the EDI system to ensure that the associated processes are running as expected and status reports are created and sent. The 1 EDI Source Managed Services team will be notified of any errors or data exceptions from either the client's trading partner or backend application. Error resolution by either 1 EDI Source, the trading partner, or the customer will be passed upon the type of resulting error.
   
   

SnapLogic EDI Use Cases

The following use cases demonstrate how SnapLogic's Pipelines can handle transactions between an EDI gateway and an ERP:

• Create and send a sales order from 1 EDI Source to NetSuite 
• Create an invoice upon order fulfillment in NetSuite and send it to 1 EDI Source

See Also

• 1EDISource
• Value Added Network (VAN)
• SnapLogic Product Glossary
• Getting started with SnapLogic