Difference between revisions of "VbzCart/tables/rstk rcd"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
(+InvcEntry)
(future terminology changes; link to req table)
Line 1: Line 1:
 
==About==
 
==About==
[[category:VbzCart/tables]]
+
* '''Purpose''': Master record for a restock shipment received; contents are in {{vbzcart|table|rstk_rcd_line}}
* '''Purpose''': Master record for a restock shipment received; contents are in {{vbzcart/table|rstk_rcd_line}}
+
* '''Related''': {{vbzcart|table|rstk_req}} contains restock requests, each of which may have one or more restock shipments received against it
 
* '''History''':
 
* '''History''':
 
** '''2008-11-07''' Created
 
** '''2008-11-07''' Created
 
** '''2008-12-17''' Added '''InvcEntry''' field
 
** '''2008-12-17''' Added '''InvcEntry''' field
 +
* '''Future''':
 +
** '''ID_Restock''' should be named '''ID_Request''' or '''ID_Req'''.
 +
** Should this table be named '''rstk_shp''', and terminology changed from "restock received" to "restock shipment"?
 
==SQL==
 
==SQL==
 
<section begin=sql /><mysql>CREATE TABLE `rstk_rcd` (
 
<section begin=sql /><mysql>CREATE TABLE `rstk_rcd` (

Revision as of 03:11, 26 November 2010

About

  • Purpose: Master record for a restock shipment received; contents are in rstk_rcd_line
  • Related: rstk_req contains restock requests, each of which may have one or more restock shipments received against it
  • History:
    • 2008-11-07 Created
    • 2008-12-17 Added InvcEntry field
  • Future:
    • ID_Restock should be named ID_Request or ID_Req.
    • Should this table be named rstk_shp, and terminology changed from "restock received" to "restock shipment"?

SQL

<mysql>CREATE TABLE `rstk_rcd` (

  `ID`             INT NOT NULL AUTO_INCREMENT,
  `ID_Restock`     INT COMMENT "rstk_req.ID of restock this shipment fulfills",
  `SuppInvcNum`    VARCHAR(63)  COMMENT "supplier's invoice number",
  `CarrierDescr`   VARCHAR(63)  COMMENT "shipping carrier (UPS, USPS...)",
  `InvcEntry`      TEXT DEFAULT NULL COMMENT "invoice lines as parseable text",
  `WhenShipped`    DATETIME DEFAULT NULL COMMENT "when supplier shipped the package",
  `WhenReceived`   DATETIME DEFAULT NULL COMMENT "when package was received from supplier",
  `WhenDebited`    DATETIME DEFAULT NULL COMMENT "when charge for order was debited",
  `TrackingCode`   VARCHAR(63)  COMMENT "carrier's tracking number",
  `TotalCalcMerch` DECIMAL(9,2) COMMENT "total cost of merchandise calculated from contents of received restock",

/* from supplier invoice */

  `TotalInvMerch`  DECIMAL(9,2) COMMENT "total cost of merchandise invoiced",
  `TotalInvShip`   DECIMAL(9,2) COMMENT "total shipping cost invoiced",
  `TotalInvAdj`    DECIMAL(9,2) COMMENT "total invoice adjustments",
  `TotalInvFinal`  DECIMAL(9,2) COMMENT "final total on invoice (must match amt paid)",
  `InvcCondition`  INT DEFAULT NULL COMMENT "do we have all the paperwork for this invoice?",
  `PayMethod`      VARCHAR(63)  COMMENT "how payment was made, if not same as restock request",
  `Notes`          TEXT DEFAULT NULL COMMENT "human-entered notes",
  PRIMARY KEY(`ID`)
)
ENGINE = MYISAM;</mysql>

  • TrackingCode: eventually there will be a table of carriers so we can retrieve tracking info or at least pull it up from the web
  • TotalInvFinal: Final = Merch + Ship + Adj
  • InvcCondition: 0 = absent, 1 = partial, 2 = complete