VbzCart/packages - Revision history

Woozle at 13:01, 14 October 2022

2022-10-14T13:01:23Z

← Older revision		Revision as of 13:01, 14 October 2022
Line 1:		Line 1:
			==About==
	A package is either "outgoing" (i.e. part of a {{l/same\|shipment}}) or "incoming" (i.e. a customer return).		A package is either "outgoing" (i.e. part of a {{l/same\|shipment}}) or "incoming" (i.e. a customer return).
			==Process==
	~~See [[VbzCart/code/VBA/Form frmPackage]] and [[VbzCart/code/VBA/clsPackage]] for how this used to work in Access.~~		Whenever package lines are altered, the package should be told to recalculate its totals based on the line values.
	==~~General~~==
	Whenever package lines are altered, it should be told to recalculate its totals based on the line values.
	==Outgoing==		==Outgoing==
	Outgoing packages can take items from stock or return items to stock, where the package data mainly reflects the final contents of the package as shipped.		Outgoing packages can take items from stock or return items to stock, where the package data mainly reflects the final contents of the package as shipped.
Line 33:		Line 32:

	When units are moved back into stock, '''QtyShipped''' should be decremented but '''QtyReturned''' should remain unaltered.		When units are moved back into stock, '''QtyShipped''' should be decremented but '''QtyReturned''' should remain unaltered.
			==Historical==
			See [[VbzCart/archive/code/VBA/Form frmPackage]] and [[VbzCart/archive/code/VBA/clsPackage]] for how this used to work in Access.

Woozle: rule revision & expansion

2014-06-15T15:43:41Z

rule revision & expansion

← Older revision		Revision as of 15:43, 15 June 2014
Line 1:		Line 1:
			A package is either "outgoing" (i.e. part of a {{l/same\|shipment}}) or "incoming" (i.e. a customer return).

	See [[VbzCart/code/VBA/Form frmPackage]] and [[VbzCart/code/VBA/clsPackage]] for how this used to work in Access.		See [[VbzCart/code/VBA/Form frmPackage]] and [[VbzCart/code/VBA/clsPackage]] for how this used to work in Access.
	==Fetching Items==		==General==
			Whenever package lines are altered, it should be told to recalculate its totals based on the line values.
			==Outgoing==
			Outgoing packages can take items from stock or return items to stock, where the package data mainly reflects the final contents of the package as shipped.
			===Fetching Items===
	This is where items are added to the package.		This is where items are added to the package.
	* The web form indicates the locations of stock that might be used to fill the order.		* The web form indicates the locations of stock that might be used to fill the order.
Line 7:		Line 13:
	* If the current package is "new", then a package record is created.		* If the current package is "new", then a package record is created.
	* The code then creates or updates package line records as necessary to accommodate the stock being added to the package.		* The code then creates or updates package line records as necessary to accommodate the stock being added to the package.
	* ~~The code recalculates:~~		** For each unit moved from stock, '''QtyShipped''' should be incremented.
	** item sale amount(s)		** item sale amount(s)
	** per-item shipping (total)		** per-item shipping (total)
	** per-package shipping (max)		** per-package shipping (max)
			===Finalizing===
	==Finalizing==
	This is where we sort of make the package "official": statuses are updated, totals computed, etc.		This is where we sort of make the package "official": statuses are updated, totals computed, etc.
	* ''(We used to increment a "QtyDone" field in [[VbzCart/tables/ord lines\|ord_lines]] for each line in the package, but now we recalculate that dynamically (as needed) by summing up the package quantities.)''		* ''(We used to increment a "QtyDone" field in [[VbzCart/tables/ord lines\|ord_lines]] for each line in the package, but now we recalculate that dynamically (as needed) by summing up the package quantities.)''
Line 18:		Line 23:
	* Add a transaction record to the order for the amount owed for this package.		* Add a transaction record to the order for the amount owed for this package.
	* Time-stamp package as "finished".		* Time-stamp package as "finished".
			===Returning Items===
			It is sometimes necessary to return items to stock from an outgoing package, typically when the shipping user has made an error of some kind. It is also useful when testing or demonstrating the shipping process, so items removed from stock in the database but not ''actually'' removed from stock can be "put back" where they were (in the database).

			For each unit in a package line that is returned to stock, '''QtyShipped''' should be decremented.
			* If '''QtyNotAvail''' is greater than zero, it should also be decremented
			** ...although there may be other things that should happen. It may be that we should just zero out QtyNotAvail and QtyCancelled when items are taken out of a package.
			==Incoming==
			Incoming packages can only return items to stock, where the package data mainly reflects the contents of the package as received (before returning items to stock).

			When units are moved back into stock, '''QtyShipped''' should be decremented but '''QtyReturned''' should remain unaltered.

Woozle: update/simplification

2014-05-13T18:42:48Z

update/simplification

← Older revision		Revision as of 18:42, 13 May 2014
Line 3:		Line 3:
	This is where items are added to the package.		This is where items are added to the package.
	* The web form indicates the locations of stock that might be used to fill the order.		* The web form indicates the locations of stock that might be used to fill the order.
	* User enters the quantity to use (remove) from each location, and presses ~~one of the following buttons:~~		* User enters the quantity to use (remove) from each location, and presses "Fetch Stock" button.
	* "~~add to package~~" ~~if the package has already been created~~		** If "do it for real" box is not checked, subsequent data changes are displayed as hypothetical rather than actually being done.
	* "~~create package~~" ~~if the package has~~ not ~~yet been created~~		* If the current package is "new", then a package record is created.
	* "~~simulate~~" ~~to confirm what actions would be taken~~		* The code then creates or updates package line records as necessary to accommodate the stock being added to the package.
	** it's not clear if this has any use besides debugging		* The code recalculates:
	* The code then creates package line records as necessary to accommodate the stock being added to the package.
	* ~~After any modification of the package's contents, the~~ code recalculates:
	** item sale amount(s)		** item sale amount(s)
	** per-item shipping (total)		** per-item shipping (total)

Woozle: Created page with "See VbzCart/code/VBA/Form frmPackage and VbzCart/code/VBA/clsPackage for how this used to work in Access. ==Fetching Items== This is where items are added to the packa..."

2014-05-08T15:35:59Z

Created page with "See VbzCart/code/VBA/Form frmPackage and VbzCart/code/VBA/clsPackage for how this used to work in Access. ==Fetching Items== This is where items are added to the packa..."

New page

See [[VbzCart/code/VBA/Form frmPackage]] and [[VbzCart/code/VBA/clsPackage]] for how this used to work in Access.
==Fetching Items==
This is where items are added to the package.
* The web form indicates the locations of stock that might be used to fill the order.
* User enters the quantity to use (remove) from each location, and presses one of the following buttons:
* "add to package" if the package has already been created
* "create package" if the package has not yet been created
* "simulate" to confirm what actions would be taken
** it's not clear if this has any use besides debugging
* The code then creates package line records as necessary to accommodate the stock being added to the package.
* After any modification of the package's contents, the code recalculates:
** item sale amount(s)
** per-item shipping (total)
** per-package shipping (max)

==Finalizing==
This is where we sort of make the package "official": statuses are updated, totals computed, etc.
* ''(We used to increment a "QtyDone" field in [[VbzCart/tables/ord lines|ord_lines]] for each line in the package, but now we recalculate that dynamically (as needed) by summing up the package quantities.)''
* ''(We used to calculate totals at this stage, but that is now done whenever the package contents are modified.)''
* Add a transaction record to the order for the amount owed for this package.
* Time-stamp package as "finished".