ASP应用程序-采购订购系统 [英] ASP Application - Purchasing Ordering System

查看:102
本文介绍了ASP应用程序-采购订购系统的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

你好,

我想知道是否有人可以向我指出正确的方向.我将开始为我的最后一个项目整理一些想法,并且我正在考虑使用后端数据库来开发一个ASP应用程序.

我想创建一个采购申请系统,在该系统中,用户登录到系统上并下订单,并与应用程序一起经历不同的阶段.我正在考虑的一些事情,例如下订单,自动系统生成订单号,向供应商发送信息,匹配发票等等.

我只想知道我可以包含的内容以及任何非常有用的提示,请提前

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

推荐答案

不要包含超出完成要求的内容过程.这是应用程序和网站面临的最大问题之一-他们试图添加无用的铃铛/口哨声,除了引起"gee-whiz"响应模式外,这些铃铛/声响对基础流程没有任何影响.

听起来您拥有编写所需代码所需的一切.
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.


您可能想考虑诸如授权之类的事情.

是否所有用户都可以简单地放置大型PO?例如,您可能需要一个业务规则,即只有经理"角色的成员才能下达大于5,000英镑的订单.另一个业务规则可能是,如果您的订单超过50,000英镑,则必须由具有董事"角色的人签署!

您可能希望将授权限制"存储在每个用户帐户旁边,以使他们在特定时间范围内的支出不能超过特定数量.

请考虑一下项目"或组织代码",以便当用户放置可以随即分配给特定项目代码的采购订单时使用.这对于报告目的非常有用,例如

项目代码``S00152-服务器升级''
与该项目有关的所有采购订单均根据该代码分配.
现在,您可以根据代码S00152进行报告,以准确了解升级服务器所花的费用.

在这一领域,您有很多可能,我前段时间设计了类似的东西.
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应用程序-采购订购系统的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆