Proposal summary

This proposal describes the CA form updates in Netsuite.

Requirement 

The requirement is to make the CA Sales Order, CA Item Fulfillment, CA Invoice look, feel and work the EXACT same as how the USA forms work – even down to the field names. This will involve adding additional lists in the background, adjusting mapping, and changing processes

Our Solution

The Requirement can be achieved by Updating the CA forms similar to the US form.

CA Form	US form
CA Sales Confirmation	US Sales Confirmation
Orvato CA Sales Confirmation	Orvato US Sales Confirmation
CA Item Fulfillment	US Item Fulfillment
CA Invoice Form	USA Invoice Form
Orvato CA Invoice Form	Orvato US Invoice Form

There may be processes done specially for the CA subsidiary. So if we remove the fields from CA forms, it may affect that process. So we will create a new tab in CA form, and move the fields to that tab instead of removing fields from the form.  

We will add mappings in fields in the CA form from the US form. And will not remove the existing mapping from the CA form as it causes issues in the CA processes.

We have reviewed the NetSuite account and noticed some processes not used in CA and used in the US. 

Following are the processes used in the US subsidiary.

1. Bulk Print Page.
2. Script used to update custom fields in Item Fulfillment on a real-time and scheduled basis in the US subsidiary.
3. {fb} Customer Reorder Card process restricted for subsidiary AU and US

Workflows :

1. Load and Submit Open orders: Load and Submit Open orders For Checking the split condition
2. OX USA – Invoice Orders: Create the invoice from sales order having Pending billing status for subsidiary OX Tools USA.
3. OverDue Invoice Reminder: Used to send invoice overdue email to the customer for subsidiary OX Tools USA
4. Billing Email: Set customer’s billing email in the email field in the invoice
5. SalesRep field-inline set: Set the display type of Sales Rep field as Inline when a US Sales Person or AU Sales Person loads a sales order.

Assumption

We have noticed the Numeric integration development is already deployed in both US and CA subsidiaries. The script was done to push code to different Numeric accounts. We assumed that the working of the Numeric Process is okay now. So we are not considering the Numeric integration in this proposal.

Risk

1. We will update only the CA form to look the same as the US Form. We will not update or change the related PDF in the CA form.
2. We only noticed the processes mentioned above for US subsidiaries. Therefore, we considered only these processes in the current scope. If any other process is underway for a U.S. subsidiary, that will be considered as additional scope.
3. Will not remove the existing field/mapping from the CA form as it causes issues in the processes defined for CA.