Scenario
We would like you to look at the possibility of creating and new field at the sales order line level that would populate the quantity ordered as a default, but if we wanted to change the quantity we could. This would also change the committed quantity to what is in the new unique field.
See below example.
| SO | Item | Quantity | Ajanta Quantity to ship(new Field) | Committed Quantity | Backordered Qty | Comments |
| SO1234 | 12345 | 1000 | 200 | 200 | 800 | this ships on 1/25 |
| SO | Item | Quantity | Ajanta Quantity to ship(new Field) | Committed Quantity | Backordered Qty | Comments |
| SO1234 | 12345 | 1000 | 800 | 800 | 0 | this ships on 1/30 |
Solution
The mentioned requirement can’t be done by the NetSuite default process.
Reason: NetSuite always considers the item for commitment based on the on-hand – Available item. We can’t fetch the data from the proposed custom field for the commitment with the default process. Also, I have checked the possibility of the “ Inventory allocation preference and the default commitment option as Available, Do not commit, and the complete Quantity. With these features, we can’t maintain the items back ordered as zero when considering the required format ( Format same as like above )
NetSuite always considers the available quantity for the commitment and can’t change the same with NetSuite’s default functionality.
NetSuite will give the 800 back ordered in line 1 and 200 back ordered in line 2 if the available quantity is 1000 for the line item when we consider the data in the “Ajanta Quantity to ship needs “ as the exact quantity that we will commit in the system. NetSuite considers the available quantity for the commitment.
So as per the NetSuite process if 500 quantity is available then we will order 1000, 500 will be committed and the remaining will be back ordered and the back ordered will be 0 when this item is available in the system automatically. The same SO can use for the transactions and SO have the status as Pending Fulfillment/Pending Billing. We can use the feature if required for the Required scenario.