To find sales revenue collected for food items by store by day requires which tables?
CustomerBill, CustomerBillItem, CustomerPayment
CustomerBill, CustomerBillItem, CustomerPayment, FoodItem
Sales revenue billed for food and beverage is in Subtotal from CustomerBill.
CustomerPayment is required to determine whether the revenue was collected.
Suppose two queries are available as follows:
1. soldByFoodByStore contains StoreID, FoodID, and SumOfQuantity from CustomerBillItem
2. wasteFoodByStore contains StoreID, FoodID, and SumOfQuantity from FoodWaste.
To sum food quantities sold and food quantities wasted, how should the queries be joined?
join (inner) soldByFoodByStore and wasteFoodByStore on StoreID; join (inner) outer soldByFoodByStore and wasteFoodByStore on FoodID
join (inner) soldByFoodByStore and wasteFoodByStore on StoreID; join (left) outer soldByFoodByStore and wasteFoodByStore on FoodID
join (left outer) soldByFoodByStore and wasteFoodByStore on StoreID; join (inner) outer soldByFoodByStore and wasteFoodByStore on FoodID
join (left outer) soldByFoodByStore and wasteFoodByStore on StoreID;join (left) outer soldByFoodByStore and wasteFoodByStore on FoodID
Left outer joins are needed for both joins to ensure that all the food items are included.
Because all food items have been sold but not every food item has been wasted,
all rows from soldByFoodByStore should be included.
The best expression for at attribute representing the week that food is received so it can be matched with food already in inventory is:
The Format function must be executed on the result of having used DateAdd to subtract two days from
[ReceivedTimestamp]. Executing the Format function first returns a result like “4/23/2257”
instead of “130506”. The choices with “ww” would add or subtract weeks rather than days.
To determine shrinkage by week by store, (1) the Monday inventory counts were added to the Wednesday purchases received and converted to dollar costs, (2) counts of food items served were summed and converted to dollar costs, and (3) the sum of costs of food items served and in ending inventory (inventory on the next Monday) were subtracted from the costs of food available. The result of executing this query strategy gives:
an accurate value for shrinkage from unknown causes
an overstated value for shrinkage from unknown causes
an understated value for shrinkage from unknown causes
an understated value for shrinkage from unknown causes depending on the circumstances
Because it does not include the costs from known causes of wasted food (recook, dropped, server, spoilage)
in the uses of food, the result will overstate the value for shrinkage from unknown causes.
The functions needed to get the day of the week from timestamp values for food served and convert it to values for determining weekly usage are:
Day and DateAdd
DateAdd and Weekday
DatePart and Weekday
DateAdd and DateSerial
The Weekday function returns the day of the week (Sunday = 1, Monday = 2, etc.), and the DateAdd function
returns a date to which days have been added or subtracted.
For example to reset a Friday date to the preceding Monday, use DateAdd("d",-4,[WasteTimestamp]).
Your assistant showed you a query result intended to calculate shrinkage by week by store by food item that had thousands of rows. You tell your assistant to:
fix attribute name errors
create an expression
reconfigure the joins
The number of rows should be the number of weeks times the number of stores times the
number of food items inventoried, which is much less than thousands.
Suppose each restaurant had a dashboard showing useful operating results. The most informative value for weekly shrinkage would be calculated at:
6 am Mondays
10 am Mondays
6 am Sundays
Because the data for a week are complete (beginning inventory, purchases, food items served,
wasted food items, and ending inventory) when the next inventory is taken on Monday morning,
the most informative value for weekly shrinkage would be calculated at 10 am Mondays,
after inventory has been counted.
Your assistant said that a query that subtracted the sum of food items served and food items wasted from the sum of an inventory plus items received was giving results only when an item had been wasted. You tell the assistant to use:
a Group By function
an Nz function
The query needs an Nz function for the wasted items to make null values for items not wasted to
be treated as zeroes in the computations.
Suppose the following queries are available to determine costs for food items:
1. In inventory on Mondays
2. Received from vendors on Wednesdays
3. Served to customers by day
4. Wasted by day
Before creating a query to subtract the sum of food items served to customers and food items wasted from the sum of food items in inventory and food items received from vendors, which of the following changes would not need to be made?
apply the Nz function on the PhysicalCount attribute
format timestamps to a uniform year, month, day format
create an expression to set food items received to Mondays
group food items served to customers and wasted by week
The Nz function needs to be applied to the quantity of wasted food items, not to the PhysicalCount attribute.
Formatting timestamps to a “yymmdd” format:
allows values of long form date fields to be changed
prevents date fields from being used for grouping
allows date fields to be used for grouping by day
prevents date fields from being used in calculations
Because timestamps contain hours, minutes, and seconds, they cannot be used for grouping by day,
week, month, or year. Formatting timestamps to a “yymmdd” format allows grouping by day.
Bottom of Form
Assignment Writing Help
Engineering Assignment Services
Do My Assignment Help
Write My Essay Services