PROPOSAL FOR PRICE LEVEL & ALLOCATION STRATEGY PER ORDER

This proposal covers the scope for sourcing the customer’s price level and allocation strategy to the sales order’s 2 custom body fields and based on these fields the value for item line level will be sourced. This proposal also covers the engagement scope of Jobin & Jismi, as the Official Implementation Partner of Oracle NetSuite.

Proposal Summary 

This proposal outlines a comprehensive solution to source the price level and allocation strategy from the customer record to the sales order’s custom body fields. The values selected in these custom fields will then be propagated to the corresponding item lines in the sales order. This behavior will occur only during the creation of the sales order. Edits to the header fields after the sales order creation will not affect the item lines, except for cases where special pricing is applied to certain items. 

Requirement 

Astro Hospitality requires the implementation of two custom body fields on their sales order forms (ASTRO Sales Order and Astro Proforma Invoice) to reflect the price level and allocation strategy from the customer’s record. These values should be: 

  • Sourced from the customer record to the sales order upon selecting the customer. 
  • Propagated from the sales order body to the item lines when the sales order is created. 
  • Unaffected in the item lines by subsequent changes to the header fields during sales order edits. 
  • Not propagated to items that have special pricing (such as item pricing or group pricing). 

 

Deliverables 

  1. Custom Fields Creation: 
  • Two custom body fields on the sales order forms: “Price Level” and “Allocation Strategy”. 
  • These fields will be dropped down. 
  1. Value Sourcing from Customer Record: 
  • Source the values of “Price Level” and “Allocation Strategy” from the customer’s record to the sales order. 
  • Upon selecting the customer in the sales order, these values should be populated in the newly created custom fields. 
  1. Propagation to Item Lines: 
  • During the creation of a sales order, the values selected in the header fields should propagate to the corresponding fields in each item line. 
  • Ensure that if the customer’s record has these fields empty, the header fields in the sales order will also be empty, and item lines will follow the standard flow for these values. In other words, the script will not update the null value 
  1. Editing Sales Orders: 
  • Changes to the header fields during sales order edits do not override the values in the item lines. 
  • If the customer has special pricing for items, these items will not source values from the custom header field. 

 

Assumptions 

 

  • The customization will only apply to the below forms: 
  • 100-Astro Sales Order 
  • 128-Astro Proforma Invoice 
  • The two custom fields created will be dropdowns and sourcing from price level list and allocation strategy. 
  • The value in the item line is replaced by the header value only during the creation context. 
  • Special pricing (item pricing and group pricing) items will not source values from the header fields. 
  • After adding item lines, any updates to the customer or customer-level fields will not change the values in the existing item lines. For example, if one line is added and then the price level in the header is changed, the existing lines will not be updated. However, any new lines added will default to the updated header value. 
  • The context considered will be actions performed through the UI. 

 

Risks 

 

  1. Orders created from the website won’t be considered: This is because the customization applies only to orders created through the NetSuite UI, not external systems. 
  2. Orders created using CSV import are not considered: CSV imports bypass the UI, so the customization logic will not be applied. 
  3. Add multiple will not be considered: The “Add Multiple” feature does not trigger the customization scripts, so it will not reflect the desired functionality. 
  4. If a user tries to edit the header after setting the values in the item line during creation, all values will be overridden: During creation, the customization script will propagate header values to item lines, which might overwrite any manual changes made to item lines. 

Leave a comment

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