Assignment Handout $-$ ER & Schema Design

Complete the ER diagram with minimum$/$maximum relationships $-$ As you are building it$,$ assume the vendor does NOT combine orders together for shipments, but assume sometimes an order can be backordered $($split into multiple shipments & invoices$).$

Remember Maximum asks "can there be more than $1$ related recorded"; Minimum asks "does there have to be a related record"

Then create a schema based on your ER diagram $($create the tables and identify the Primary Key and some of the basic information that would be stored in the table$).$ Link the tables: remember to use the "Maximum" relationship to link up the tables.

Put the primary key from the $1$ side table as an attribute$/$Foreign Key in the Many side table.

If you have a M:M relationship, you need a new table. Put the Primary Keys from both tables you are trying to connect into the that new table.

I filled in the minimum$/$maximum for the relationship between Vendor and Vendor Invoice table. I also created the VENDOR TABLE and VENDOR INVOICE TABLE already for you with the Primary Key identified and some of the attributes we would store in those table listed also. I also added the Primary $($PK$)$ from the Vendor Table and put it as an attribute in the Vendor Invoice Table to link those two tables together.

$---$ As you work through the rest of the ER diagram and schema design, you may need to add attributes to Vendor Invoice table in order to link it to the Purchase Order table.

The Minimum participation does not have any impact on the design of the schema for the database.

Purchasing Process $-$ ER Diagram

$$LIVIA ULJIUIV

VENDOR TABLE: VendorID $-$ PK$,$ Name, Address, Phone, email

VENDOR INVOICE TABLE:Invoice# $-$ PK$,$ Date, Due Date, Shipping Terms, Invoice Total, $[$VendorID $-$ FK$]$