• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1402
  • Last Modified:

Purchase Requisition Project using Sharepoint 3.0

I'm starting on a project to convert our out-of-date paper Purchase Requisition system to an electronic one. Our MRP system doesn't include support for it, so would like to start simply by using Sharepoint.

We have only WSS 3.0 in house and an upgrade to MOSS2007+ isn't on the cards right now so I can't take full advantage of the Infopath features which I think would be the easiest option and due to the amount of users that would need to be part of the workflow, upgrading Office licences to Pro just for Infopath isn't viable.

Please take a look at our current req in the image.

I need to get this into some kind of workable document, such as Excel or even PDF but I don't want to go off creating something that might not be workable down the line. I don't believe I can use forms for this.

My idea is for the user to fill out the form and start a workflow manually, entering specific information about the document, including who needs to authorise the req, when the workflow is initiated. This owuld then route the docment off to the various other steps which I will develop further when I come to them.

What I'm asking for is some guidance and advice on what I am doing, whether it is is the right way to go, or if there is another way to do this.
2 Solutions
Without InfoPath or InfoPath Forms Services your options are limited. The only solutions I can think of is a SharePoint List which isn't very dynamic and customizable or a ASP.NET custom app. The ASP.NET is probably the more flexible solution.

The ideal solution is InfoPath with Event Handles/Workflows.

If you want backend integration to MRP, such as after the document is approved to move the amounts and accounts to accounting, even SharePoint is limited, since all of your data is locked up in individual files.

I would suggest www.qdabra.com and their SQL webservices.  It was made for this specific purpose and then all data, even though it runs through SharePoint is in a database in SQL for aggregation, reporting, and interfacing to another system.

So you would be able to lookup and query data from MRP, such as items, or accounts, etc and then the data could drop right into MRP for payment at the very end.  You can use InfoPath in the middle to provide rich forms, customized to your organization and needs.

InfoPath and webservices are the ultimate gap filler for any ERP/MRP environment since you can create your own UI quickly and easily and interface it back into the database.
ultra-itAuthor Commented:
Looks like we are putting this project on hold at the moment, but thankyou for your advice.

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now