VbzCart/docs/tables/rstk ord line: Difference between revisions

From Woozle Writes Code
< VbzCart‎ | docs‎ | tables
Jump to navigation Jump to search
imported>Woozle
(+ID_Order, ID_RstkLine -> ID_RstkReq, +ID_Item)
imported>Woozle
(→‎SQL: changed indexes - ID_RstkReq+ID_Order+ID_Item, since ID_OrdItem isn't always available)
Line 8: Line 8:
==SQL==
==SQL==
<section begin=sql /><mysql>CREATE TABLE `rstk_ord_line` (
<section begin=sql /><mysql>CREATE TABLE `rstk_ord_line` (
   `ID_RstkReq`     INT NOT NULL COMMENT "restock request (rstk_req.ID) which is being used to fulfill the customer's order",
   `ID_RstkReq` INT NOT NULL COMMENT "restock request (rstk_req.ID) which is being used to fulfill the customer's order",
   `ID_Order`       INT NOT NULL COMMENT "customer order (core_orders.ID) which is being fulfilled by this restock request line",
   `ID_Order`   INT NOT NULL COMMENT "customer order (core_orders.ID) which is being fulfilled by this restock request line",
   `ID_OrdLine`     INT NOT NULL COMMENT "specific order line (ord_lines.ID) being fulfilled",
   `ID_OrdLine` INT DEFAULT NULL COMMENT "specific order line (ord_lines.ID) being fulfilled",
   `ID_Item`         INT NOT NULL COMMENT "item which is being requested to fill the customer's order",
   `ID_Item`   INT NOT NULL COMMENT "item which is being requested to fill the customer's order",
   `QtyOrd`         INT NOT NULL COMMENT "Quantity allocated to this customer",
   `QtyOrd`     INT NOT NULL COMMENT "Quantity of item allocated to this order",
   `Notes`           VARCHAR(255) COMMENT "human-entered notes on this allocation item",
   `Notes`     VARCHAR(255) COMMENT "human-entered notes on this allocation item",
   PRIMARY KEY(`ID_RstkReq`,`ID_OrdLine`)
   PRIMARY KEY(`ID_RstkReq`,`ID_Order`, `ID_Item`)
  )
  )
  ENGINE = MYISAM;</mysql>
  ENGINE = MYISAM;</mysql>
<section end=sql />
<section end=sql />
==Notes==
* '''ID_OrdLine''' is sort of opportunistic &ndash; it isn't always available in legacy data. The functions using this new set of data schemas should always fill it in, however.

Revision as of 22:41, 9 November 2008

About

  • Created: 2008-11-07
  • Distribution of restock items to customer orders (planned). This is more of a historical-log-and-search kind of record than something which is actually part of the process. (Should we get rid of it at some point?)
    • Search for every time a particular item was restock-requested, and which orders we were trying to fill
    • Search for every time we tried to restock-request items for a particular order
    • Shows which items in a restock request are for customers; remainder are for stock

SQL

<section begin=sql /><mysql>CREATE TABLE `rstk_ord_line` (

  `ID_RstkReq` INT NOT NULL COMMENT "restock request (rstk_req.ID) which is being used to fulfill the customer's order",
  `ID_Order`   INT NOT NULL COMMENT "customer order (core_orders.ID) which is being fulfilled by this restock request line",
  `ID_OrdLine` INT DEFAULT NULL COMMENT "specific order line (ord_lines.ID) being fulfilled",
  `ID_Item`    INT NOT NULL COMMENT "item which is being requested to fill the customer's order",
  `QtyOrd`     INT NOT NULL COMMENT "Quantity of item allocated to this order",
  `Notes`      VARCHAR(255) COMMENT "human-entered notes on this allocation item",
  PRIMARY KEY(`ID_RstkReq`,`ID_Order`, `ID_Item`)
)
ENGINE = MYISAM;</mysql>

<section end=sql />

Notes

  • ID_OrdLine is sort of opportunistic – it isn't always available in legacy data. The functions using this new set of data schemas should always fill it in, however.