is this possible (about database normalization)?

[wannabesmart]

I'd like to make a new table named Purchasing table.
Is it ok with this? which x -> y (x=primary key)



or is it better with this version (dividing into two tables)?


and another question is can I not use primary key?
what is benefit of primary key?

*Note:
The arrow means dependency, except the arrow between PONo, ProductCode -> Qty
If anyone could help, I would be greteful

[June7]

Is this a class assignment?

If you want to allow multiple products with each purchase, use two tables.

The main benefit of primary key is as a link to related records. By saving just the primary key value as a foreign key, it is not necessary to duplicate data. The one-table structure would require repeating the PONo, Date, EmpID, SupplierID for every product associated with the purchase.

A primary key can be an autonumber field or a custom unique identifier such as PONo. There are pros and cons to each.