Concepts

NEHANET has been integrated with your back end system/ERP. The integration process is not complex; and customers typically automate the flow of Parts, Accounts and Sales History data from ERP to NEHANET.

Integration yields immediate benefits to your operational processes. Making Backlog and Shipment data visible in NEHANET helps drive Annual plan and Forecast accuracy. Giving access to order and backlog information to your reps is often a useful goal as well. For an overview of the integration please download the Integration Framework document https://www.nehanet.com/pdf/Information_Integration_Framework.pdf

Considerations

There are several approaches you can follow in integrating NEHANET with your ERP system.

  • The simplest and most cost-effective integration methodology is for you to publish data from your ERP system to an intermediate staging database; and for us to pick it from there and load it into the NEHANET system. The data sync is usually incremental, and the frequency of sync can be adjusted to your business needs.
  • The second method of integration is to directly and programmatically (API, web services etc) interface with your ERP system. This assumes the ERP system has a web service API that can be invoked remotely to get the requested data. We do not, however, recommend this approach since a version change in either software has the potential of breaking the integration link between the two systems.

As a first step, please identify your requirements as to what entities you need to sync between ERP and NEHANET. Typically, Parts, Customers and Sales Orders flow from the ERP to NEHANET. Forecasted Production plan flows from NEHANET to ERP. Approved Quotes can flow as conditional Orders to ERP and Approved Sample Requests can flow as zero cost orders to ERP. NEHANET Services team can work with you to implement the exact flow of information as needed by your business needs.

The next section below lists the common fields that flows between ERP and NEHANET.

Parts Master

The following is a typical set of Parts data that flows from ERP to NEHANET. Please note that this is just a recommended list. We can work with you to finalize the exact set of fields for your deployment.

  • Part Number
  • Part Family
  • Product Line or Business Unit
  • Part Description
  • Date Created
  • Date Last Modified
  • Status (‘Active’ or ‘Inactive’)
  • Additional Product Attributes as needed
  • Unique Record Id

Customer Master

The following is a typical set of Customer data that flows from ERP to NEHANET. Please note that this is just a recommended list. We can work with you to finalize the exact set of fields for your deployment.

  • Customer Name
  • Customer Id
  • Customer Type
  • Customer Sub Type
  • Street Address
  • City
  • State or Province
  • Zip or Postal Code
  • Country
  • Customer Region
  • Date Created
  • Date Last Modified
  • Status (“Active’ or ‘Inactive’)
  • Additional fields as needed

Sales Backlog

  • Unique Id
  • Order Number
  • Order Date
  • Sold To Customer
  • End Customer
  • Part Number
  • Unit Price
  • Quantity
  • Amount
  • Customer Requested Date
  • Date Created
  • Date Last Modified
  • Additional fields as needed

Sales Shipments

  • Unique Id
  • Invoice Number
  • Invoice Date
  • Sold To Customer
  • End Customer
  • Part Number
  • Unit Price
  • Quantity
  • Amount
  • Customer Ship Date
  • Date Created
  • Date Last Modified
  • Additional fields as needed

Forecasted Monthly Production Plan

  • Part Number
  • Part Family
  • Current Month Quantity
  • Next Month Quantity
  • and so on…