Without getting into the detail too heavily (I don't know your business model), you should have something like a top level Parts table, with PartID, PartNumber , PartDescription , Min and Max stock levels perhaps.
You transaction table is then something like PartTransID, PartID_FK, UsageTypeFK, UsageRef , TransQty , TransDate, Location (if you want parts stored in a location(s))
Your Usage type is another table where you set up your usage descriptors, maybe with some cost codes, and some reporting groups something like UsageID, UseDescTxt , ReportingOptId , CostCode , etc
A typical usage type would be Stock Replenish , Product Build , Write Off , Stock Take etc.
In the Trans table you record the usageIDFK, and in the UasgeRef you could record a batch or final product code to help track what you used it on.
This gives you some of the basics for ins / out and the ability to calculate the quantities on hand in a location.
Stock tracking is not as obviously simple as you might think, but if you get the basic structure correct initially , it makes it much easier process to grasp.
You may need to account for different manufacturers / suppliers of the same incoming parts, you may need to record dated costs. Start with a paper model of your inputs and outputs (reporting requirements) design the tables to accommodate all the information to produce those and you should be on your way. Pretty forms and other things should be the last thing you get into.