Re: My StockManger Relational Model
Re: My StockManger Relational Model
- Subject: Re: My StockManger Relational Model
- From: Gustavo Pizano <email@hidden>
- Date: Mon, 17 Nov 2008 19:33:08 +0100
Exactly Im doing it to learn, I just can't imagine the Framweork
doing it all for me... hehe.. but its a great thing to know about
D2JC, I will take a look, anyway that's why I divided this projetc in
3 phases, the last one its UI.
Gus
On 17.11.2008, at 18:19, David Avendasora wrote:
On Nov 17, 2008, at 11:18 AM, Gustavo Pizano wrote:
Now all you need to do is create a D2JC project and you'll have a
working application! ;-)
I was thinking in a WonderAplication.
Pfft. Wonder?! Wonder's great for the server-side and if you are
going to go with a UI that you basically have to write from scratch
yourself. Direct To Java Client gives you a native UI out-of-the-box
so you can worry about the business-logic and not the UI.
I'm just kidding. I know you are making a Web application and using
it to learn AJAX and such. I just can't resist a plug for D2JC.
Dave
Gus
On 17.11.2008, at 17:08, David Avendasora wrote:
On Nov 17, 2008, at 10:58 AM, Gustavo Pizano wrote:
1) You're missing the relationship from PURCHASEORDERITEM TO
PRODUCT,
Big OOPS!
2) You'll want to track the quantity of PURCHASEORDERITEM being
received in POITEMRECEIVED
Fixed it.
3) For the sake of simplicity, I'll assume that the Unit of
Measure you stock things in is the same as the Unit of Measure
you Order them in (and receive them in for that matter). In the
real world this is not the case and is often the root of many
inventory/purchasing problems.
Completely LOST :S :(
Disregard this. It's not important since this is a learning
exercise for you.
The due date on the PO would be the date by which everything on
the PO should be received. It is _possible_ that you may want
the individual items at different times and their due dates
should reflect that. If you are trying to keep the system simple
for now,
I think is fine by now.
Now all you need to do is create a D2JC project and you'll have a
working application! ;-)
Dave
thx
Gus
On 17.11.2008, at 16:49, David Avendasora wrote:
On Nov 17, 2008, at 10:33 AM, Gustavo Pizano wrote:
Hello David, thanks for the advices, if I understood good,
then my initial phase RM shold looks like this.
<StockManagerRM.pdf>
A couple things:
1) You're missing the relationship from PURCHASEORDERITEM TO
PRODUCT,
2) You'll want to track the quantity of PURCHASEORDERITEM being
received in POITEMRECEIVED
3) For the sake of simplicity, I'll assume that the Unit of
Measure you stock things in is the same as the Unit of Measure
you Order them in (and receive them in for that matter). In the
real world this is not the case and is often the root of many
inventory/purchasing problems.
I have a doubt about the following:
you may want individual due dates for each PO Item so that you
can order multiple things on one PO that are due at different
times
So wha tyou are suggesting is to pass the dueDate attribute
from PURCHASEORDER to PURCHASEORDERITEM?
The due date on the PO would be the date by which everything on
the PO should be received. It is _possible_ that you may want
the individual items at different times and their due dates
should reflect that. If you are trying to keep the system simple
for now, I'd actually leave this whole concept off, along with
the receivings. I was bringing them up as other things to think
about in the future. This is the same for #3 above. Inventory
and Purchasing can get incredibly complicated, very quickly.
Dave
well let me know what you think, for me it looks fine, but
well thats for me... hehehe.. so I can continue to create the
EO and then use migrations.
regards
Gus
On 17.11.2008, at 13:28, David Avendasora wrote:
Hey Gus,
You'll probably need a "Purchase Order" entity with
information like vendor, order date, due date, user who placed
the order, etc. And a "PO Item" entity that has information
like Product, Quantity Ordered, Quantity Received, Price, etc.
Going beyond the basic, you may want individual due dates for
each PO Item so that you can order multiple things on one PO
that are due at different times. You may also want to have a
"PO Item Receiving" entity that keeps track of each time a
product is received for a given PO Item in case the Provider
makes more than one shipment.
Other than that, the Model looks sound from both a DB and a
EOF stand point.
Dave
On Nov 17, 2008, at 6:00 AM, Gustavo Pizano wrote:
Ok so here is an initial Model of the new app im making. The
main idea of this phase is to be able to implement the
operations of insert delete, update for the app, also I want
to implement some method who will tell me when one product is
getting close to be out of stock, and email the admin about
it so he can place an order. So far thats it, just place an
order, but do nothing else. So here is the model, I dunno
what Im missing, comments are welcome.
Gus
<StockManagerRM.pdf>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden
)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden