ASP Application - Purchasing Ordering System

Question

0.00/5 (No votes)

See more:

SQL-Server-2005

, +

Hi there,

I wonder if anyone could point me out in the right directions. I am about to start putting some ideas together for my final year project and i was thinking of doing an asp application with a backend database.

I want to create purchasing requisition system where by a user logs onto a system and places and order and goes through different stages withing the application. Some of the things i was thinking about like placing an order, automatically system generates an order number, sending informtation to supplier, invoice matching so on and so forth.

I just want some ideas of what i could include and any tips that would be great thanks in advance

Posted 28-Jul-11 3:13am

Geofferz

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

#realJSOP · Answer 1 · 2011-07-28T03:19:00

Don't include anything more than what is required to accomplish the process. That's one of the biggest problems with apps and web sites - they try to add useless bells/whistles that have no impact on the underlying process other than to elicit the "gee-whiz" response pattern.

It sounds like you have everything you need to write the code that's required.

Dylan Morley · Answer 2 · 2011-07-28T03:20:00

You might want to think about things like authorisation.

Should all users simply be able to place large POs? For example, you might want a business rule that only members of the 'Managers' role can place orders larger than £5,000. Another business rule could be that your PO's must be signed off by someone in the 'Directors' role if larger than £50,000!

You might want to store 'authorisation limits' next to each user account, so they can't spend more than a certain amount in a certain time frame.

Have a think about 'Project' or 'Organisation Code' so when users place POs that can assign then against a particular project code. This is very useful for reporting purposes, e.g.

Project Code 'S00152 - Server Upgrades'
All POs regarding this project are assigned against this code.
You can now report against code S00152 to see exactly how much was spent upgrading your servers.

There are lots of possibilities for you in this area, I designed something like this a while ago.

ASP Application - Purchasing Ordering System

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0