Purchases orders are handled by a purchasing clerk who initiates the purchase order with one Plumes vendors. For items that are not in stock, some vendors send partial shipments and then ship the remaining items when they become available. Once the items are received, a receiving clerk inspects the items and forwards them to the correct department. After the bill for each purchase has been approved for payment, a cash disbursements clerk sends the payment to the vendor. Most vendors offer credit terms where Plume, Inc. can pay the invoice within 30 days. Several vendors also send monthly statements which can be paid for multiple purchases during the month. Using the information provided for Plume, Inc. prepare an REA Data Model for the Expenditure Cycle, including cardinalities using the guidelines and appropriate symbols as described in chapter 7 (17) of the textbook. The REA model should be well-formatted, easy to follow, and include appropriate cardinality notations. Prepare the REA model using LucidChart (submit as a pdf file). ALSO, create the appropriate table structures (chapter 8 [18]) which would be implemented in a relational database for this model. See the step-by-step guidelines on how to create an REA model in Lucid Chart with cardinalities and how to add the tables in LucidChart. The tables should be included in the same pdf file with the REA model. Use the following format to create the table structures, similar to the approach used in class: Table Name Primary Key Foreign Key(s) Other non-key Attributes . . . . Include at a minimum three non-key attributes for each table and at least 2 non-key attributes for M:N tables. Indicate a primary key for each table, and include foreign keys as necessary