johannaellamay
Registered User.
- Local time
- Today, 09:48
- Joined
- Jul 19, 2014
- Messages
- 190
Hmm. I can't seem to add tables for the assets because I'm so confused. -_- My database should contain the following info on assets w/ (EXAMPLES):
STATUS (Released, In Stock, Damaged)
SEQUENCE NO. (00079)
SEQUENCE LETTER (A)
PROPERTY NUMBER (LOCATION + RECEIVING DOC. NUMBER + RECEIVING DOC. + PROPERTY TYPE NO. + SEQUENCE NUMBER; Ex. BOSTON 3334-RR-00079)
ITEM BRAND (Apple)
MODEL (iMac)
SIZE
UNIT OF MEASURE
SHAPE
COLOR (white)
OTHER DESCRIPTION
SERIAL NO./IMEI/ MODEL NO. /CHASSIS NO. (1234567ZZZ)
ENGINE NO. (VEHICLE)
PLATE NO. (VEHICLE)
DONOR SOURCE (1234)
COUNTRY NO. (890)
PROJECT NO. (1235)
ACCT. CODE (9999)
PROPERTY TYPE (Computer)
PROPERTY TYPE NO. (01)
PO NO./VOUCHER NO. (12345)
PURCHASE PRICE (USD) (3000)
RECEIVING DOCUMENT (RR - Receiving Report)
RECEIVING DOCUMENT NO. (33334)
DATE ACQUIRED (9/3/14)
OFFICE (LOL/USA)
DEP'T (Admin)
LOCATION (Boston)
ASSIGNEE (Family Name) (Erroba)
ASSIGNEE (First Name) (Johanna)
DATE ISSUED (9/4/14)
ACK. NO./PAF NO.
NOTES
It's quite a handful. Wew. Aside from that, I also have to make Property Accountability Forms (PAF) for employees. The PAF should contain:
Name
Department
Location
Property Number
Item Description
Serial Number
Remarks
Released
Returned
It's so complicated. What do you suggest that I do? I'm currently trying to make additional tables and I'll post them here as soon as I can. Property Custodianship has a different scope compared to Inventory Management. Inventory Management deals with tracking the SR, PO, RR, and inventory levels. Property Custodianship deals with assets issued to employees. They overlap for a bit, but they're also very different. Right now, I'm the one handling both. But in our other offices, there might be different people handling Inventory and Property. Which is why I asked you which was better, make two separate databases or make just an incorporated one? Because in the future, I might not be the one to handle both areas.
STATUS (Released, In Stock, Damaged)
SEQUENCE NO. (00079)
SEQUENCE LETTER (A)
PROPERTY NUMBER (LOCATION + RECEIVING DOC. NUMBER + RECEIVING DOC. + PROPERTY TYPE NO. + SEQUENCE NUMBER; Ex. BOSTON 3334-RR-00079)
ITEM BRAND (Apple)
MODEL (iMac)
SIZE
UNIT OF MEASURE
SHAPE
COLOR (white)
OTHER DESCRIPTION
SERIAL NO./IMEI/ MODEL NO. /CHASSIS NO. (1234567ZZZ)
ENGINE NO. (VEHICLE)
PLATE NO. (VEHICLE)
DONOR SOURCE (1234)
COUNTRY NO. (890)
PROJECT NO. (1235)
ACCT. CODE (9999)
PROPERTY TYPE (Computer)
PROPERTY TYPE NO. (01)
PO NO./VOUCHER NO. (12345)
PURCHASE PRICE (USD) (3000)
RECEIVING DOCUMENT (RR - Receiving Report)
RECEIVING DOCUMENT NO. (33334)
DATE ACQUIRED (9/3/14)
OFFICE (LOL/USA)
DEP'T (Admin)
LOCATION (Boston)
ASSIGNEE (Family Name) (Erroba)
ASSIGNEE (First Name) (Johanna)
DATE ISSUED (9/4/14)
ACK. NO./PAF NO.
NOTES
It's quite a handful. Wew. Aside from that, I also have to make Property Accountability Forms (PAF) for employees. The PAF should contain:
Name
Department
Location
Property Number
Item Description
Serial Number
Remarks
Released
Returned
It's so complicated. What do you suggest that I do? I'm currently trying to make additional tables and I'll post them here as soon as I can. Property Custodianship has a different scope compared to Inventory Management. Inventory Management deals with tracking the SR, PO, RR, and inventory levels. Property Custodianship deals with assets issued to employees. They overlap for a bit, but they're also very different. Right now, I'm the one handling both. But in our other offices, there might be different people handling Inventory and Property. Which is why I asked you which was better, make two separate databases or make just an incorporated one? Because in the future, I might not be the one to handle both areas.
Last edited: