47d1baffc5
This happens when a customer places identical orders and specifies that
they be shipped in different seasons. We end up with one order shipped
in 2023 and one open for 2024. Under our current operating procedures,
open orders are subtracted from shipped orders and are presented as
baseline for the next forecast. The zero that appears in the baseline in
this case was causing all kinds of issues in the SQL scripts for
inserting the adjustments, ranging from finding zero rows to adjust to
division by zero.
Another change required to correct this was updating the iter value of
the open orders from 'actuals' to 'copy':
UPDATE rlarp.osm_pool
SET iter = 'copy'
WHERE tag = 'open-orders'
|
||
|---|---|---|
| .. | ||
| addmonth_vupd.sql | ||
| adj_totals.sql | ||
| get_pool.sql | ||
| list_changes.sql | ||
| new_basket.sql | ||
| scale_pd.sql | ||
| scale_vd.sql | ||
| scale_vupd_sales.sql | ||
| scale_vupd.sql | ||
| scenario_package.sql | ||
| swap_cust.sql | ||
| swap_fit.sql | ||
| swap_post.sql | ||
| undo.sql | ||