Jump to content

General structure of Inventory and Assets management

Dimitrios Fkiaras

This topic is 2237 days old. Please don't post here. Open a new topic instead.

Recommended Posts


In an  Asset managment solution, do I absolutely need these tables:

Asset (e.g. HP Photosmart 102b)------< Individual Assets (e.g. HP Photosmart 102b | s/n:1234567890)---------< Transaction Items >------------Transactions   ?


Currently I don't have an Individual Assets table and all Individual Assets are created in Transaction Items table and a Serial number is assigned to them there.

When I sign out an Asset, I create a new Transaction and when it is returned, I flag the Transaction as VOID.

I know I have that Asset at hand if it appears only ONCE in my CURRENT Transactions. (VOID Transactions are excluded via self join)

If it appears only once it means that I have only one relative Transaction  the one that I created when I first received the item).

If I have two, it means that I reveived it and then made another Transaction (signed it out).


Is that a correct approach? What are possible pitfalls?


I know for sure that this approach is used when handling Inventory, I don't know about assets

but if feels a bit odd having this structure of mine...


I am a bit confused about it....








Edited by Dimitrios Fkiaras
clarification of problem
Link to comment
Share on other sites

This topic is 2237 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.