VbzCart/queries/qryRstkItms expected: Difference between revisions
from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
fixed SQL syntax, I hope |
QtyOrd->QtyExp |
||
| Line 2: | Line 2: | ||
* '''Returns''': Restock items requested (ordered), not yet received, but possibly expected because the restock request hasn't been terminated (closed, orphaned, or killed). | * '''Returns''': Restock items requested (ordered), not yet received, but possibly expected because the restock request hasn't been terminated (closed, orphaned, or killed). | ||
* '''Requires''': {{vbzcart/table|rstk_rcd_line}}, {{vbzcart/table|rstk_rcd}}, {{vbzcart/query|qryRstkItms_active}} | * '''Requires''': {{vbzcart/table|rstk_rcd_line}}, {{vbzcart/table|rstk_rcd}}, {{vbzcart/query|qryRstkItms_active}} | ||
* '''Used by''': | * '''Used by''': admin listing of needed items | ||
* '''Algorithm''': any positive quantities in '''<'''{{vbzcart/query|qryRstkItms_active|<all items in <active restock requests>>}} - <{{vbzcart|table|rstk_rcd_line|items received}} on those item requests>'''>''' | |||
* '''History''': | * '''History''': | ||
** '''2008-11-19''' Created for new restock process | ** '''2008-11-19''' Created for new restock process | ||
| Line 8: | Line 9: | ||
** '''2008-12-04''' renamed: qryRstkItms_en_route → qryRstkItms_expected | ** '''2008-12-04''' renamed: qryRstkItms_en_route → qryRstkItms_expected | ||
** '''2010-01-03''' fixed syntax: have to recalculate aggregate functions to use them in a HAVING clause (bleh) | ** '''2010-01-03''' fixed syntax: have to recalculate aggregate functions to use them in a HAVING clause (bleh) | ||
** '''2010-01-04''' updated to use QtyExp instead of QtyOrd (field renamed/changed in {{vbzcart/query|qryRstkItms_active}}) | |||
==SQL== | ==SQL== | ||
<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryRstkItms_expected AS | <section begin=sql /><mysql>CREATE OR REPLACE VIEW qryRstkItms_expected AS | ||
| Line 13: | Line 15: | ||
rqi.ID_Restock, | rqi.ID_Restock, | ||
rqi.ID_Item, | rqi.ID_Item, | ||
SUM(rqi. | SUM(rqi.QtyExp) AS QtyExp, | ||
SUM(IFNULL(rcl.QtyRecd,rcl.QtyFiled)) AS QtyRecd | SUM(IFNULL(rcl.QtyRecd,rcl.QtyFiled)) AS QtyRecd | ||
FROM | FROM | ||
| Line 20: | Line 22: | ||
LEFT JOIN qryRstkItms_active AS rqi ON (rc.ID_Restock=rqi.ID_Restock) AND (rcl.ID_Item=rqi.ID_Item) | LEFT JOIN qryRstkItms_active AS rqi ON (rc.ID_Restock=rqi.ID_Restock) AND (rcl.ID_Item=rqi.ID_Item) | ||
GROUP BY rqi.ID_Restock, rqi.ID_Item | GROUP BY rqi.ID_Restock, rqi.ID_Item | ||
HAVING (SUM(rqi. | HAVING (SUM(rqi.QtyExp)-SUM(IFNULL(rcl.QtyRecd,rcl.QtyFiled)))>0;</mysql> | ||
<section end=sql /> | <section end=sql /> | ||
Revision as of 00:47, 5 January 2010
About
- Returns: Restock items requested (ordered), not yet received, but possibly expected because the restock request hasn't been terminated (closed, orphaned, or killed).
- Requires: rstk_rcd_line, rstk_rcd, qryRstkItms_active
- Used by: admin listing of needed items
- Algorithm: any positive quantities in <<all items in <active restock requests>> - <items received on those item requests>>
- History:
- 2008-11-19 Created for new restock process
- 2008-11-24 QtyRecd falls back on QtyFiled if null
- 2008-12-04 renamed: qryRstkItms_en_route → qryRstkItms_expected
- 2010-01-03 fixed syntax: have to recalculate aggregate functions to use them in a HAVING clause (bleh)
- 2010-01-04 updated to use QtyExp instead of QtyOrd (field renamed/changed in qryRstkItms_active)
SQL
<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryRstkItms_expected AS SELECT
rqi.ID_Restock, rqi.ID_Item, SUM(rqi.QtyExp) AS QtyExp, SUM(IFNULL(rcl.QtyRecd,rcl.QtyFiled)) AS QtyRecd
FROM
(rstk_rcd_line AS rcl LEFT JOIN rstk_rcd AS rc ON rcl.ID_RstkRcd=rc.ID) LEFT JOIN qryRstkItms_active AS rqi ON (rc.ID_Restock=rqi.ID_Restock) AND (rcl.ID_Item=rqi.ID_Item)
GROUP BY rqi.ID_Restock, rqi.ID_Item HAVING (SUM(rqi.QtyExp)-SUM(IFNULL(rcl.QtyRecd,rcl.QtyFiled)))>0;</mysql> <section end=sql />
