fx ITEM: A 31 32 33 34 24 Order Detail 25 26 27 28 29 item number part number unit price total quantity 30 Delivery Schedule delivery number location number quantity due date 35 36 Part 37 part number 38 39 40 41 42 standard price Customer-Part Relationship customer number part number 43 special price B C D 1 2 3 ITEM: 4 5 6 7 Customer Header customer number buyer name bill-to address 8 buyer phone 9 buyer email 10 credit rating 11 12 Customer Shipping 13 14 N location number receiver name 15 receiver phone 16 receiver email 17 ship-to address 18 19 Order Header 20 20 order number 21 22 E order date shipment method ORDER MANAGEMENT Entity-Relationship D
fx ITEM: A 31 32 33 34 24 Order Detail 25 26 27 28 29 item number part number unit price total quantity 30 Delivery Schedule delivery number location number quantity due date 35 36 Part 37 part number 38 39 40 41 42 standard price Customer-Part Relationship customer number part number 43 special price B C D 1 2 3 ITEM: 4 5 6 7 Customer Header customer number buyer name bill-to address 8 buyer phone 9 buyer email 10 credit rating 11 12 Customer Shipping 13 14 N location number receiver name 15 receiver phone 16 receiver email 17 ship-to address 18 19 Order Header 20 20 order number 21 22 E order date shipment method ORDER MANAGEMENT Entity-Relationship D
Chapter19: Pricing Concepts
Section: Chapter Questions
Problem 11DRQ
Related questions
Question
Design a normalized order management database with the requirements provided below.
Each record should have at least one primary key field specified. After identifying the records and their corresponding fields, draw an entity-relationship (ER) diagram to illustrate the relationships between entities and attributes.
Expert Solution
This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
Step by step
Solved in 2 steps with 1 images