VbzCart/tables/ord pkg lines - Revision history

Woozle: +CostShPkg

2014-06-16T02:24:14Z

+CostShPkg

← Older revision		Revision as of 02:24, 16 June 2014
Line 20:		Line 20:
	*** '''QtyFromStock''' All units now must be entered into stock before they can be shipped.		*** '''QtyFromStock''' All units now must be entered into stock before they can be shipped.
	*** '''WhenVoided''' - This was not really ever used, and I can't think of a reason it should exist.		*** '''WhenVoided''' - This was not really ever used, and I can't think of a reason it should exist.
			* '''2014-06-15''' Adding '''CostShPkg''' so totals can be recalculated solely from package line data.
	==SQL==		==SQL==
	<mysql>CREATE TABLE `ord_pkg_lines` (		<mysql>CREATE TABLE `ord_pkg_lines` (
Line 32:		Line 33:
	`CostSale` DECIMAL(9,2) DEFAULT NULL COMMENT "price charged for this item",		`CostSale` DECIMAL(9,2) DEFAULT NULL COMMENT "price charged for this item",
	`CostShItm` DECIMAL(9,2) DEFAULT NULL COMMENT "per-item shipping cost charged",		`CostShItm` DECIMAL(9,2) DEFAULT NULL COMMENT "per-item shipping cost charged",
			`CostShPkg` DECIMAL(9,2) DEFAULT NULL COMMENT "per-package shipping cost minimum for this item",
	`Notes` VARCHAR(255),		`Notes` VARCHAR(255),
	PRIMARY KEY(`ID`)		PRIMARY KEY(`ID`)
	)		)
	ENGINE = MYISAM;</mysql>		ENGINE = MYISAM;</mysql>

Woozle: rule for voiding lines

2014-06-15T11:39:05Z

rule for voiding lines

← Older revision		Revision as of 11:39, 15 June 2014
Line 8:		Line 8:
	** quantity ordered - (QtyShipped + QtyNotAvail + QtyKilled) + QtyReturned = quantity we still need to ship		** quantity ordered - (QtyShipped + QtyNotAvail + QtyKilled) + QtyReturned = quantity we still need to ship
	* When a return package is first created, QtyShipped and QtyReturned will be the same. When the items are returned to stock, QtyShipped will be zero but QtyReturned will be unchanged.		* When a return package is first created, QtyShipped and QtyReturned will be the same. When the items are returned to stock, QtyShipped will be zero but QtyReturned will be unchanged.
			* If QtyShipped and QtyReturned are both zero, then the line is void and may be reused.
	==History==		==History==
	* '''2010-10-19''' Adding CostShItm and CostSale fields to record prices charged (parallels ChgShipItm and ChgShipPkg in {{vbzcart/table\|ord_pkgs}})		* '''2010-10-19''' Adding CostShItm and CostSale fields to record prices charged (parallels ChgShipItm and ChgShipPkg in {{vbzcart/table\|ord_pkgs}})

Woozle: major simplifying; QtyReturned to handle returns

2014-06-15T01:52:21Z

major simplifying; QtyReturned to handle returns

← Older revision		Revision as of 01:52, 15 June 2014
Line 4:		Line 4:
	* '''Fields''':		* '''Fields''':
	** '''QtyFromStock''' may be an obsolete field, as ''all'' package quantities should now come from stock.		** '''QtyFromStock''' may be an obsolete field, as ''all'' package quantities should now come from stock.
	* ~~'''History'''~~:		==Rules==
	** '''2010-10-19''' Adding CostShItm and CostSale fields to record prices charged (parallels ChgShipItm and ChgShipPkg in {{vbzcart/table\|ord_pkgs}})		* across all packages, for a given item:
	*** Those fields didn't exist until I created them just now (because I thought certain other fields were serving that function), but it's better to have too much data than too little for critical things like packages.		** quantity ordered - (QtyShipped + QtyNotAvail + QtyKilled) + QtyReturned = quantity we still need to ship
	** '''2011-10-08''' Added '''WhenVoided''' field so we have a quick way of removing lines from the package to put them back into stock (while still keeping a record of what was there).		* When a return package is first created, QtyShipped and QtyReturned will be the same. When the items are returned to stock, QtyShipped will be zero but QtyReturned will be unchanged.
			==History==
			* '''2010-10-19''' Adding CostShItm and CostSale fields to record prices charged (parallels ChgShipItm and ChgShipPkg in {{vbzcart/table\|ord_pkgs}})
			** Those fields didn't exist until I created them just now (because I thought certain other fields were serving that function), but it's better to have too much data than too little for critical things like packages.
			* '''2011-10-08''' Added '''WhenVoided''' field so we have a quick way of removing lines from the package to put them back into stock (while still keeping a record of what was there).
			* '''2014-06-14'''
			** Added '''QtyReturned''' so we can keep track of what ''was'' in a return-package.
			** Doing away with:
			*** '''QtyExtra''': This should be indicated by setting '''CostSale''' and '''CostShItm''' to zero.
			**** If a given item has some units that are freebies and some that are not, then create separate lines.
			*** '''QtyFromStock''' All units now must be entered into stock before they can be shipped.
			*** '''WhenVoided''' - This was not really ever used, and I can't think of a reason it should exist.
	==SQL==		==SQL==
	<mysql>CREATE TABLE `ord_pkg_lines` (		<mysql>CREATE TABLE `ord_pkg_lines` (
	`ID` INT NOT NULL AUTO_INCREMENT,		`ID` INT NOT NULL AUTO_INCREMENT,
	`ID_Pkg` INT NOT NULL COMMENT "ord_pkgs.ID",		`ID_Pkg` INT NOT NULL COMMENT "ord_pkgs.ID",
			`ID_Item` INT NOT NULL COMMENT "cat_items.ID",
	`ID_OrdLine` INT COMMENT "ord_lines.ID",		`ID_OrdLine` INT COMMENT "ord_lines.ID",
	~~`ID_Item` INT NOT NULL COMMENT "cat_items.ID",~~		`QtyShipped` INT COMMENT "quantity included in this package",
	`QtyShipped` INT COMMENT "quantity ~~shipped/charged~~ in this package",		`QtyNotAvail` INT COMMENT "quantity which can't be filled",
	`~~QtyExtra~~` INT COMMENT "quantity ~~tossed in as freebies in this pkg~~",
	`QtyKilled` INT COMMENT "quantity fulfilled by being cancelled",		`QtyKilled` INT COMMENT "quantity fulfilled by being cancelled",
	`~~QtyNotAvail~~` INT COMMENT "quantity ~~which can't be filled",~~		`QtyReturned` INT COMMENT "quantity returned by customer",
	~~`QtyFromStock` INT COMMENT "quantity which was moved from stock",~~
	~~`WhenVoided` DATETIME DEFAULT NULL COMMENT "when this line was voided~~",
	`CostSale` DECIMAL(9,2) DEFAULT NULL COMMENT "price charged for this item",		`CostSale` DECIMAL(9,2) DEFAULT NULL COMMENT "price charged for this item",
	`CostShItm` DECIMAL(9,2) DEFAULT NULL COMMENT "per-item shipping cost charged",		`CostShItm` DECIMAL(9,2) DEFAULT NULL COMMENT "per-item shipping cost charged",

Woozle: removed obsolete tags

2014-04-27T14:49:11Z

removed obsolete tags

← Older revision		Revision as of 14:49, 27 April 2014
Line 9:		Line 9:
	** '''2011-10-08''' Added '''WhenVoided''' field so we have a quick way of removing lines from the package to put them back into stock (while still keeping a record of what was there).		** '''2011-10-08''' Added '''WhenVoided''' field so we have a quick way of removing lines from the package to put them back into stock (while still keeping a record of what was there).
	==SQL==		==SQL==
	~~<section begin=sql />~~<mysql>CREATE TABLE `ord_pkg_lines` (		<mysql>CREATE TABLE `ord_pkg_lines` (
	`ID` INT NOT NULL AUTO_INCREMENT,		`ID` INT NOT NULL AUTO_INCREMENT,
	`ID_Pkg` INT NOT NULL COMMENT "ord_pkgs.ID",		`ID_Pkg` INT NOT NULL COMMENT "ord_pkgs.ID",
Line 26:		Line 26:
	)		)
	ENGINE = MYISAM;</mysql>		ENGINE = MYISAM;</mysql>
	~~<section end=sql />~~

Woozle: WhenVoided

2011-10-08T20:23:27Z

WhenVoided

← Older revision		Revision as of 20:23, 8 October 2011
Line 7:		Line 7:
	** '''2010-10-19''' Adding CostShItm and CostSale fields to record prices charged (parallels ChgShipItm and ChgShipPkg in {{vbzcart/table\|ord_pkgs}})		** '''2010-10-19''' Adding CostShItm and CostSale fields to record prices charged (parallels ChgShipItm and ChgShipPkg in {{vbzcart/table\|ord_pkgs}})
	*** Those fields didn't exist until I created them just now (because I thought certain other fields were serving that function), but it's better to have too much data than too little for critical things like packages.		*** Those fields didn't exist until I created them just now (because I thought certain other fields were serving that function), but it's better to have too much data than too little for critical things like packages.
			** '''2011-10-08''' Added '''WhenVoided''' field so we have a quick way of removing lines from the package to put them back into stock (while still keeping a record of what was there).
	==SQL==		==SQL==
	<section begin=sql /><mysql>CREATE TABLE `ord_pkg_lines` (		<section begin=sql /><mysql>CREATE TABLE `ord_pkg_lines` (
Line 18:		Line 19:
	`QtyNotAvail` INT COMMENT "quantity which can't be filled",		`QtyNotAvail` INT COMMENT "quantity which can't be filled",
	`QtyFromStock` INT COMMENT "quantity which was moved from stock",		`QtyFromStock` INT COMMENT "quantity which was moved from stock",
			`WhenVoided` DATETIME DEFAULT NULL COMMENT "when this line was voided",
	`CostSale` DECIMAL(9,2) DEFAULT NULL COMMENT "price charged for this item",		`CostSale` DECIMAL(9,2) DEFAULT NULL COMMENT "price charged for this item",
	`CostShItm` DECIMAL(9,2) DEFAULT NULL COMMENT "per-item shipping cost charged",		`CostShItm` DECIMAL(9,2) DEFAULT NULL COMMENT "per-item shipping cost charged",

Woozle: correction... those fields weren't what I thought they were

2010-10-19T22:42:27Z

correction... those fields weren't what I thought they were

← Older revision		Revision as of 22:42, 19 October 2010
Line 5:		Line 5:
	** '''QtyFromStock''' may be an obsolete field, as ''all'' package quantities should now come from stock.		** '''QtyFromStock''' may be an obsolete field, as ''all'' package quantities should now come from stock.
	* '''History''':		* '''History''':
	** '''2010-10-19''' Adding CostShItm and CostSale fields to record prices charged (parallels ~~ShipCost~~ and ~~PkgCost~~ in {{vbzcart/table\|ord_pkgs}}		** '''2010-10-19''' Adding CostShItm and CostSale fields to record prices charged (parallels ChgShipItm and ChgShipPkg in {{vbzcart/table\|ord_pkgs}})
			*** Those fields didn't exist until I created them just now (because I thought certain other fields were serving that function), but it's better to have too much data than too little for critical things like packages.
	==SQL==		==SQL==
	<section begin=sql /><mysql>CREATE TABLE `ord_pkg_lines` (		<section begin=sql /><mysql>CREATE TABLE `ord_pkg_lines` (

Woozle: added 2 fields for recording what was charged

2010-10-19T20:35:10Z

added 2 fields for recording what was charged

← Older revision		Revision as of 20:35, 19 October 2010
Line 4:		Line 4:
	* '''Fields''':		* '''Fields''':
	** '''QtyFromStock''' may be an obsolete field, as ''all'' package quantities should now come from stock.		** '''QtyFromStock''' may be an obsolete field, as ''all'' package quantities should now come from stock.
			* '''History''':
			** '''2010-10-19''' Adding CostShItm and CostSale fields to record prices charged (parallels ShipCost and PkgCost in {{vbzcart/table\|ord_pkgs}}
	==SQL==		==SQL==
	<section begin=sql /><mysql>CREATE TABLE `ord_pkg_lines` (		<section begin=sql /><mysql>CREATE TABLE `ord_pkg_lines` (
Line 15:		Line 17:
	`QtyNotAvail` INT COMMENT "quantity which can't be filled",		`QtyNotAvail` INT COMMENT "quantity which can't be filled",
	`QtyFromStock` INT COMMENT "quantity which was moved from stock",		`QtyFromStock` INT COMMENT "quantity which was moved from stock",
			`CostSale` DECIMAL(9,2) DEFAULT NULL COMMENT "price charged for this item",
			`CostShItm` DECIMAL(9,2) DEFAULT NULL COMMENT "per-item shipping cost charged",
	`Notes` VARCHAR(255),		`Notes` VARCHAR(255),
	PRIMARY KEY(`ID`)		PRIMARY KEY(`ID`)

Woozle: extracted from VbzCart/tables

2008-12-27T15:25:28Z

extracted from VbzCart/tables

New page

==About==
* '''Purpose''': What's in an order package ({{vbzcart/table|ord_pkgs}})
* '''Refers to''': {{vbzcart/table|ord_pkgs}} (parent), {{vbzcart/table|ord_lines}}, {{vbzcart/table|cat_items}}
* '''Fields''':
** '''QtyFromStock''' may be an obsolete field, as ''all'' package quantities should now come from stock.
==SQL==
<section begin=sql /><mysql>CREATE TABLE `ord_pkg_lines` (
`ID` INT NOT NULL AUTO_INCREMENT,
`ID_Pkg` INT NOT NULL COMMENT "ord_pkgs.ID",
`ID_OrdLine` INT COMMENT "ord_lines.ID",
`ID_Item` INT NOT NULL COMMENT "cat_items.ID",
`QtyShipped` INT COMMENT "quantity shipped/charged in this package",
`QtyExtra` INT COMMENT "quantity tossed in as freebies in this pkg",
`QtyKilled` INT COMMENT "quantity fulfilled by being cancelled",
`QtyNotAvail` INT COMMENT "quantity which can't be filled",
`QtyFromStock` INT COMMENT "quantity which was moved from stock",
`Notes` VARCHAR(255),
PRIMARY KEY(`ID`)
)
ENGINE = MYISAM;</mysql>
<section end=sql />