Jira Code: BLUEL:16
If the accounting preference in a NetSuite account is set to
-Commit available quantity
-commit orders based on Expected ship date
Then,
Consider two sales order with same line item(Test item A)
In Sales order #1
Test item A, 10(quantity via SO ), 6(committed), 4(back ordered), Expected Ship Date:20/05/2019 (manually given)
In Sales order #2
Test item A, 1(quantity via SO ), 0(committed), 1(back ordered), Expected Ship Date:17/05/2019 (manually given)
Then we place a Purchase order #1
Test item A, 1(quantity via purchase order)
Then due to this particular accounting settings, the item in the ‘Sales order #2’ will be committed because it has the earliest expected ship date.
After receiving the purchase order the changes in the sales order is mentioned below.
In Sales order #1
Test item A, 10(quantity via SO ), 6(committed), 4(back ordered), Expected Ship date:20/05/2019
In Sales order #2
Test item A, 1(quantity via SO ), 1(committed), 0(back ordered), Expected Ship Date:17/05/2019 (this item have been committed)
Note: The Expected Shipdate field in the line level of the sales order is only available if we enable the demand planning feature.