Proposal for Customer portal customization

Proposal Summary 

This proposal describes the process of customizing the customer portal by automating the Sales Effective/ Shipping Date in the Sales order and by sending the list of Sales orders to the corresponding Sales Rep for the approval. 

Requirement-1 

Graph Tech needs to customize the customer portal by automating the field named Sales Effective/ Shipping Date in the Sales Order. 

When the Sales Rep must approve the SO, the Sales Effective/Shipping Date shall be applied. Depending on the Customer Price Level (e.g. OEM, Distributor, Dealer, Builder) there would be specific number of working days added to the date of SO release. 

Number of Working Days to be added for each customer channel 

OEM +45 working days : April 11th plus 45 w/d = June 13th 

Distributor +15 working days : April 11th plus 15 w/d = May 02nd 

Dealer +5 working days : April 11th plus 5 w/d = April 18th 

Builder +5 working days : April 11th plus 5 w/d = April 18th 

Retail +2 working days : April 11th plus 2 w/d = April 13th 

Artist +2 working days : April 11th plus 2 w/d = April 13th 

Our Solution 

We need to set the value of the field “Sales Effective/Shipping Date” (Field ID: ‘saleseffectivedate’) based on the Sales Order creation date (Field ID: ‘trandate’) and the channel (Field ID: custbody_eb_channel)  using a User Event Script in the create mode. 

The “Sales Effective/Shipping Date” field value is calculated from transaction date. According to the channel, the number of working days associated with each of the customer channel will be added to the transaction date for obtaining corresponding sales effective date. 

Sales Effective/Shipping Date = Date + Number of working days corresponds to the channel  

The table below displays the number of working days associated with each channel. 

               CHANNEL                       WORING DAYS 
    OEM     45 
    Distributor     15 
    Dealer       5 
    Builder       5 
    Retailer       2 
    Artist       2 

Assumptions 

  • We will update the Sales Effective/ Shipping Date at the time of creation. 
  • If channel field is empty, then we will not do any change in the Sales Effective Date. 
  • This update will not make any change in the existing Sales Orders 
  • The Sales Effective/Shipping Date field will be editable (Not locked) 
  • The script will be restricted to the orders creating in the customer portal and not applicable to other orders creating in the NetSuite 

Questions 

  • There are many other customer channels in the list. Could you please specify the corresponding working days associated with the following 
  1.     DEALERA 
  1.     DISDOM 
  1.     DISINT     
  1.     OEM-2 
  1.     OEMDOM 
  1.     OEMINT 
  1.     WEBSTORE                

Requirement- 2 

The Sales orders creating in the customer portal will be approved by 3 Sales Persons. Graph Tech need to create a flow where every Sales rep gets an email with the list of new SO posted during the previous day with the link to that particular record so that they can easily find out the Sales Orders which needs to be approved.  

Every Sales Rep will get the list of SO with they are assigned. 

Our Solution 

This requirement can be achieved using a Scheduled Map Reduce Script which will send Emails to the corresponding Sales Rep every day with a list of Sales Orders for the approval process. 

We will attach the list of Sales Orders in the “Pending Approval” status in a table format in the Email body with the link to the corresponding SO.  

For example, we have attached a sample table format. 

Date of SO release SO Internal ID Link to SO Record 
12/04/2022 123456 SO-123456 
   
   

The sender of the Email is Administrator and the receiver will be the corresponding Sales Rep in each Sales Order. 

We will schedule the script to work in every day so that the Sales rep get the newly created Sales Orders daily. 

Questions 

  • Could you specify the name of the other 2 sales reps who needs the Sales order list by email? (Assuming that one is AlexG) 

Time Hours –Requirement 1 

Task (Sandbox & Production)                            Time  
 
User Event Script                                4H 
Testing                               2H 
Production Deployment                               1H 

Time Hours –Requirement 2 

Task (Sandbox & Production)                            Time  
 
Map Reduce Script                                10H 
Testing                               2H 
Production Deployment                               2H 

Leave a comment

Your email address will not be published. Required fields are marked *