Proposal For Automated Management of Main and Intercompany Purchase Orders in NetSuite

Proposal Summary 

 

This proposal outlines implementation of an automated system within NetSuite that streamlines the creation and management of Intercompany Purchase Orders (POs) based on a manually created Main Purchase Order.  

The estimated effort for implementing the customization in the Sandbox and Production is 46 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 BGGN 

 

BGGN want to automate the creation of intercompany purchase orders (POs) for item lines in a primary PO. When a main PO is created with an external supplier, it includes line-level allocations across various subsidiaries, with the location specified in the PO’s body. Upon saving the PO, intercompany POs are automatically generated according to these allocations. 

Statement of Work (SOW)   

We have reviewed the requirement thoroughly and please find below the deliverables we propose.  

• In the main PO, item lines will include columns for selecting the Subsidiary and Location. 
• For item lines with the different subsidiaries and locations, Intercompany POs will be created automatically. 
• A user event script will be implemented to automatically create Intercompany Purchase Orders (ICPOs) for a main Purchase Order (PO). 
• Each Intercompany PO will have a field linking it to the main PO. 
• Item lines in the main PO will include links to the created Intercompany POs. 
• A checkbox will be added to the main PO to indicate whether Intercompany POs have been created. After creating the Intercompany POs this will be checked. 
• For each created Intercompany PO, the Vendor will be set as the Intercompany Vendor whose primary subsidiary matches the subsidiary selected in the item lines and whose representing subsidiary corresponds to the subsidiary of the main PO. 
• The location for each Intercompany PO will be the location chosen in the respective item line. 
• A search saved report will be created to display the Main Purchase Orders and the linked Intercompany Purchase Orders. 
• The search result includes details on the Main Purchase Order (PO), the associated Intercompany POs, and the Intercompany Sales Orders created. It also captures the location and the receive date for both the Main PO and the Intercompany POs. 

Error Handling 

 

• A new column field will be added to the main Purchase Order (PO) to store any errors that occur during the creation of an Intercompany PO.  
• If no errors occur, this field will remain empty.  
• A Saved Search will be created to list all the main POs in which there are errors creating Intercompany POs.  
• Users can review the error details, resolve the issue, and then, upon editing and saving the main PO, the Intercompany POs will be generated for any previously errored lines.  

Assumptions 

 

• The user event script will be triggered during the creation and editing of purchase orders (POs). 
• Only purchase orders (POs) that are pending receipt will be considered for this customization. 
• If new items are added to the Main PO and there is no existing Intercompany PO associated with the subsidiary for the new line, a new Intercompany PO will be automatically generated. 
• Existing Intercompany PO: If an Intercompany PO already exists for the subsidiary of the newly added item line, the new line will be added to that existing Intercompany PO. 

Questions 

 

• Should this automation be applied to purchase orders for all subsidiaries or just one specific subsidiary? 

Scope Limitations 

 

• If existing item lines on the main purchase order (PO), for which intercompany POs have already been generated, are edited, the changes will not be reflected in the corresponding intercompany PO. 

 

 

 

Estimated Effort  

    

Completion of development in NetSuite Sandbox: 42 hours 

Production movement after UAT Signoff: 4 hours 

Total: 46 hours 

 

Estimate assumptions: 

1. The estimate includes Project management, risk analysis, system analysis, development, unit testing, regression testing, documentation, and deployment.   
2. The rate is calculated based on our master service agreement.   
3. The implementer expects the client to sign off or report bugs within 7 days of UAT submission in Sandbox. If no feedback is received, the work will be considered approved, and an invoice for 42 hours will be issued. 

Validity of this proposal 

7 days from the date of submission.