Proposal Summary
This proposal outlines a solution for integrating AMP orders and quotes with NetSuite on a scheduled basis. The objective is to facilitate the synchronization of AMP Quotes into NetSuite as Opportunity records and AMP Orders as Quote records.
The estimated effort for implementing the customization in the Sandbox and Production is 32 hours.
The scope and the provided estimate are based on the anticipation, expectation, and understanding through our discussions and email. If the scope change/additional feature development identified during actual development, they will be treated as change request.
Requirement From Classy Art Wholesalers.
Currently, NetSuite integrates with AMP to retrieve orders from AMP and create corresponding sales orders in NetSuite. The client would like to:
- Development of a new Map/Reduce script to convert AMP Quotes to NetSuite Opportunity records.
- Modification of the existing integration script to convert AMP Orders into Quote records.
Statement of Work (SOW)
Solution Approach
The integration process will follow these steps:
- Modification of Existing Integration:
- The existing Map/Reduce script that currently syncs AMP orders to NetSuite as sales orders will be modified. The new functionality will allow it to create Quote records instead of sales orders. This involves changing the logic in the script to accommodate the new requirements while ensuring that the existing functionality remains intact. Additionally, any custom fields that are not already present will be applied to the Quote records.
- Development of New Map/Reduce Script:
- A new Map/Reduce script will be developed to handle the synchronization of AMP Quotes into NetSuite as Opportunity records. This script will fetch the relevant data from AMP, transform it as per the defined field mappings, and create Opportunity records in NetSuite.
Error Handling Records:
An integration logs record will be created to capture any errors that occur during the synchronization process. This record will store details about the error, allowing for easy identification and resolution. The errors will be reprocessed in subsequent scheduled runs, ensuring that no quotes or opportunities are missed.
Once the error is solved and created the corresponding record, the custom record instance can be inactivated.
Notification System:
To ensure timely resolution of errors, a saved search will be created to generate daily email notifications for designated users. The notification schedule can be adjusted based on client preferences.
Field Mapping
Quote record
Salesorder Field ID
Quote Field ID
Not in Quote
entity
entity
billaddress
billaddress
shipaddress
shipaddress
otherrefnum
otherrefnum
custbody_special_instructions
custbody_special_instructions
custcol_list_price
custcol_list_price
shipdate
shipdate
custbody_shipping_method
custbody_shipping_method
shipmethod
shipmethod
custbody_jj_amp_order_id
Need to apply to Quote
externalid
externalid
createdTime
createdTime
item
item
custcol_item_display_name
Need to apply to Quote
quantity
quantity
custcol_jj_amp_order_line_id
Need to apply to Quote
price
price
rate
rate
amount
amount
Assumptions
- The current authentication mechanism used for AMP and NetSuite can be reused for this development.
- Currently, AMP quotes are not coming into NetSuite at all.
- There will be no link between Synced quote and opportunity as they will be created individually.
- Opportunities are going to be primarily used to manage internal deals – if the opportunity is created from an AMP quote, the NetSuite quote will be generated off of the NetSuite opportunity – not by converting the AMP quote. The less frequent instance is where a sales rep generates an AMP quote and then converts that AMP quote to an order. In that case, client will be managing that – it’s just giving them more insight into the sales reps’ activities. In this instance client would like these transactions to connect, but they can always tie the quote back to the existing opportunity.
Scope Limitations
- We will strictly follow the Field mappings provided in this proposal. Any of the changes in the solution will be considered as change request.
- Processing time depends on the number of records retrieved.
Estimated Effort
Total Estimated Hours – 32 Hours