Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Stored Proc - Dealing with Orders and OrderDetails... Expand / Collapse
Author
Message
Posted Tuesday, January 26, 2010 8:56 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, August 5, 2014 2:44 PM
Points: 32, Visits: 92

In my database, I have 2 tables, Orders and OrderDetails. This may be obvious, but Orders holds information relevant (DateOrdered, OrderStatus, CustomerNumber) and the OrderDetails table contains information relevant to the details (ProductOrdered, ProductPrice, Shipped)

I want to know the best way to set it up so that when all of the Details of an Order are market Shipped, the order then gets an OrderStatus as Shipped. In addition, for example, if at some point in the process a all of the details get marked as shipped, the OrderStatus changes to Shipped - and someone goes and unmarks a detail as shipped for some reason - the order is then marked back to Pending.

I would think that this is a pretty common scenario - I am just looking for some direction.

Thanks in advance.
sb

Post #853723
Posted Tuesday, January 26, 2010 10:39 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 9:20 AM
Points: 12,916, Visits: 32,080
steve whenever i have an overall status that depends on the details, i do not store it in the parent/Orders table. I always try to calculate it based on the details, for example.

I create a view instead, and the view calculates the status, so it is automatically correct based on the details.
an example might be something like this: notice the case statement and the group by sub select to figure it all out:
CREATE TABLE Orders (
OrderID int identity(1,1) not null primary key,
DateOrdered,
CustomerNumber)

CREATE TABLE OrderDetails(
DetailsID int identity(1,1) not null primary key,
OrderID int references Orders(OrderID)
ProductOrdered varchar(30)
ProductPrice decimal(19,4)
Shipped char(1) default('N') )

CREATE VIEW VW_ORDERS AS
SELECT
Orders.OrderID,
Orders.DateOrdered,
Orders.CustomerNumber
CASE
WHEN DETAILS.SHIPPEDCOUNT = DETAILS.TOTALCOUNT
THEN 'Shipped'
WHEN DETAILS.SHIPPEDCOUNT =0
THEN 'Not Shipped'
WHEN DETAILS.SHIPPEDCOUNT < DETAILS.TOTALCOUNT
THEN 'Partial Shipment'
END As Status
FROM VW_ORDERS
LEFT OUTER JOIN
(SELECT OrderID,
SUM(CASE WHEN Shipped = 'Y' THEN 1 ELSE 0 END) AS SHIPPEDCOUNT,
COUNT(DetailsID) AS TOTALCOUNT
FROM OrderDetails
GROUP BY OrderID) DETAILS
ON OrderDetails.OrderId = DETAILS.OrderID



Lowell

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #853814
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse