Wednesday, November 5 th
Wireless Network
Login: guest
Password: welcome11

Welcome and Thank You!
Meet the Board
• Mike Kean – Co-Chair
• Stephen Enfield – VP and Co-Chair
• Charlene Doherty – Speaker Chair
• Mike Tarentino – Membership Chair
• Cara Foley – Co-Chair
Meet the Sponsors
• ERP Guru
• Piracle
• SPS Commerce
Corporate Sponsor
• Altico Advisors
Speakers
• Ken Phu, Hub Pen Company
• Olivier Simard, ERP Guru
Non-Board Assistance
• Jaynelle Bellemore

Boston NetSuite User Group
Approach
• ½ Day Morning Meeting
• 2 Technical Sessions
• Networking and sharing
Event paid for by Sponsors
• ERP Guru
• Piracle
• SPS Commerce
* Covers cost of room rental, food and drinks
* Sponsors introduce sessions- commercials

Agenda
8:00 – 8:30 a.m.
8:30 – 8:45 a.m.
8:45 – 10:15 a.m.
10:30 - 11:30 a.m.
11:30 a.m. - 12:00 p.m.
Registration and Networking
Welcome
Technical Session I: Enhancing NetSuite Dependent Dropdown Fields and Custom Records
Technical Session II: NetSuite Integration Concepts
Closing Remarks

Presented By: Ken Phu

Agenda
• Dependent Dropdown Fields
• Definition
• How They Work
• Steps to create a Dependent Dropdown Field
• Custom Records
• Overview
• Create One on the Fly
• Example: Custom Field w/Custom List

Dependent Dropdown Field
A field’s list values are dependent on the value selected in a different field.

How They Work
Data Relationship

Steps to Create Dependent Drop Down Fields
1.
Determine your Trigger Field
A.
Existing NE Field (List)
B.
Custom Field Using Existing List
C.
Custom Field w/Custom List
2.
Create Components of the Trigger Field
A.
Existing NS Field (List) – No work jump 3.
B.
Custom Field (Using Existing List) – Create custom field and reference the list.
C.
Custom Field w/ Custom List – custom list first then the custom field referencing the custom list.
3.
Create the list values using a custom record for the Dependent Field
4.
Create the Dependent Field
1.
Where do you create the custom field?
2.
Reference the list value
3.
Apply Filtering/Data Relationship

NetSuite Custom Records
NS Custom Record = Table in a Relational Database = Custom Table in NS
Table Name
Field Names
Relationship

Example: Trigger Field is a Custom Field With Custom List
1.
Custom List (For Trigger Field)
2.
Create Custom Field (Manufacturer) and apply Custom List From Step 1
Determine where to create the custom field?
3.
Create a list value for the dependent field
• Create Custom Record First
• Add the fields to the custom record
• Add records to the custom record that represents the list value
4.
Create dependent field (Car Models)
Where do you create this?
Apply Filtering/Data Relationship to Car Model (dependent) field

Questions?

Break Until 10:00 am
Use this time to:
• Visit with our sponsors
• ERP Guru
• Piracle
• SPS Commerce
• Network with your NetSuite peers

Presented By: Olivier Simard

Agenda
What is integration and why consider integration
Examples:
Integration of ERP & CRM
Integration of ERP & 3PL
Integration of ERP & ecommerce
Conclusion
Questions

What is integration and why consider integration
The goal of integration is to connect multiple systems with heterogeneous data formats to support business use cases.
Each integration project is done for different reasons, depending on the needs of the company.
Examples:
Linking an e-Commerce Web Site with an ERP solution
Linking a new CRM tool with an ERP solution

Example 1: Integration NetSuite with SugarCRM
Description
The client is a software company. The client was already using SugarCRM and had decided to move forward with NetSuite for their ERP
Main needs
Sync: leads / contacts, activities (phone calls, tasks and events), campaigns / campaign responses
Challenges (issues with Flow)
Definitions of a lead and a contact differ in NetSuite vs. SugarCRM
Data mapping: example Country, State, activities from different time zones, other
What activities should be synched
More…

Example 1: Integration NetSuite with SugarCRM cont’d
Potential solutions
Daily manual import
Connector between the 2 systems to allow sync every 30 min.
Connector between the 2 systems to allow sync in real-time
Development of the connector (sync every 30 min)
Maintaining close communications with the customer at all times / reduce time for decision making
Most discussions touched on data mapping / NetSuite has more restrictions that SugarCRM
Connector required a lot of custom rules
Result: An automated process

Example 2: 3PL Integration with DotCom (Distribution Case)
Description
The client primarily drives business through an online store selling office supplies.
They already had NetSuite and they decided to acquire a new 3PL system
(DotCom Distribution)
Main needs
Provide order to DotCom so it can be fulfilled
Receive fulfillments from DotCom, support drop ship items & sync inventory between systems
Challenges
Supporting partial fulfillments from DotCom to NetSuite
Shipping code discrepancy
Inventory count and packages

Example 2: 3PL Integration with DotCom (Distribution Case) cont’d
Potential solutions
Sync of orders (without supporting partial fulfillment)
Connector between the 2 systems to allow sync of orders every 15 min.
Connector between the 2 systems to allow sync of orders and inventory
Development of the connector to allow sync every 15 min
Result
In this specific Integration, originally the requirements were without specifying Partial Fulfillment. It changed overtime because the client realized that for the big office furniture, it couldn’t package them together. After the connector was released, they chose to implement the Inventory Check and automating the creation of Inventory Adjustments.

Example 3: E-Commerce Business Case
Description
The client is a high quality wine distributor with an online web store. The client decided to purchase
NetSuite and integrate it with their online web store and their current in-house management system.
Main needs
Get real-time information from online store
Keep the in-house management system populated with some information from the web
Be able to do bi-directional synchronization for customer records, unidirectional for sync of inventory, orders, items and custom records
Challenges
Supporting the existing records from the in-house system and incorporate new records from NetSuite
Support real-time updates and search the web store/NetSuite while continuing to support the in-house database

E-Commerce : Solution

Example 3: E-Commerce Business Case cont’d
Potential solutions
Use of a connector & the NetSuite scripting solution for real-time processing
Use NetSuite only (NetSuite scripting solution)/eliminate in-house system
The connector only to sync data between NetSuite and the in-house system
Result
Integration of real-time processing of info between Netsuite, In-House
System and Web Store!
NOTE: Design based on current processes and third-party company involved for other parts of the Integrations . The Web Store was made by the third-party company and was in development during integration (posed issues for final testing)

Conclusion
Today’s presentation provided specific business profiles and examples of integration but so much more is possible with NetSuite and other systems:
• Shipping Integration
• Payment Integration
• Ticket Management System
• Project Management System
• More….

Closing Remarks
• Recap of event
• Initial Feedback and Suggestions
• Next Meetings (tentative dates)
• Wednesday, March 18 th
• SuiteWorld
• Wednesday, June 10 th