The double booked Pizza order of 30,000 Pizzas and 30000 Kung Po Chili Chicken dishes. Tiene Cuenta Pizza? Ho gui?

It is criminal harassment to call a lot of people who are related to someone possibly as old friends and associates and provide spurious information or suggest that they won't be showing up for free school. It is also criminal harassment and a fraud on the pizza parlor to make false orders. The frozen pizza was born when someone double booked a pizza order of 30,000 pizzas made with deep fettuccine instead of the usual mozzarella. It is not clear if the double booked order was deliberate but the pizza parlor did not have a system function to highlight unusually similar double booked orders in a 48-72 hour period before the pizzas were baked and how many double booked orders of 30000 pizzas could any parlor bank on digesting or could they presume that the double booking customer would redeem the double booked pizza order when they needed another 30000 pizzas?  If a contract for pizza dough is being booked twice internally but a price or rate was only given once, the order taker isn't getting two commissions for dealing with the public; only one commission for an order that was transmitted twice and processed twice in error based on one quote with the sexy chick voice; let's talk!  The real issue is the orders that are processed overnight that are paid for on customer credit that could be duplicates of an order that went through the day before with the exact toppings.  But nobody has parties of that size soo often unless it's a Spanish football team. Maybe the system just printed the order twice after a power failure or when they had to reboot the DOS based windows system after a system freeze. So, the parlor decided to set up a system function on their AS/400 module to catch such unusually double booked pizza contracts that were entered into their order system over a short 24 hour or 72 hour period of time on the account of a particular client. The function, as a filter, would hold the duplicate order on the system and pend it as a potential duplicate without putting the dough order through where there is an immediate and potential loss of dough on day one as it is being purchased from Sienna in euros with exchange involved against the Cuban peso; gracias!  The cost of cancellation that would involve buying back the Lira could involve a loss.   The pended order would not be released unless there is confirmation from the client in writing since there could be exposure and someone has to know what they are communicating and take responsibility.  They would also have to confirm it is a duplicate for deletion and this would not be required.  There is no need to "hang" anyone on our side if it is a system accountability and the order needs to be deleted at a loss but how can we prevent the phenomenon of a loss? It is best not to process an apparent duplicate order twice and create a system filter on the AS/400 to pend the order if such an order appears on the system.    The good thing is that the parlor only provides one rate per pizza dough order even if it is processed twice in error so there is only one commission for the pizza order taker or is it two commissions if the order is transmitted on the smart phone pizza app twice electronically in error due to a system reboot after a power failure and is processed internally?  If it goes through the order system ( soon to be totally automated- plug in amounts of dough over  US$ 10000.00 and you get a discount via the web portal for dough), there could be a loss on day one as the cost of buying back the dough could incur a loss.    A report (a new pending contract report) would be generated with all of the double booked contracts; contracts that would remain in a pending status by the pizza processing back office, waiting for the parlor manager's override before preparation, baking and release on the parlor's baking system where the potential loss begins on day one of booking. The pending contract report is different from the general outstanding contract report. You know why the pending contract is pending. It is because it appears to be an evident duplication.   The pending contract report would generate each day instead of once a week in the case of the outstanding pizza contract report. The outstanding contract report is generated once a week.  Market movement and time is an important variable in protecting the bank's position. So, a daily report with current information of the previous business day's potentially double booked orders is helpful. The outstanding contact report is only available weekly. It did not tell you why the contract was outstanding. The customer service pizza person had to run around, speak to staff in the back office dough processing department and, at last resort, call the client to find out what they want to do with the outstanding contract for which payment was not received or for which there were no instructions.  The second  double booked contracts would stay outstanding because the instructions to process the dough were applied to the first contract in addition to the actual payment.  This was the tireless job of the customer service pizza person who may have had to do this too often for the same scenario several times a week to find out why something is outstanding and why there are no instructions for the dough. These solutions were suggested a long time ago and before law school but I don't know what happened?   But, why do they call it a computer? Have you heard of Atari and the various inputs that make Pong possible or uh Pole Position or your Frigidaire microwave? Where is your mind?  The truth is everyone has a perfect expectation of how fast you should be able to fly to Paris or how fast you should receive your perfect pizza but the service provide provider and the customers live in the reality of existing technology, perfect service and system expectations and the reality of emerging technologies. There is sometimes a gap between expectations on one hand and delivery with existing technology on the other hand. We have to, therefore, mind the gap.   The issue in the end, however, is not how fast you are communicating but what is being communicated?    With the suggested pending contract report, a customer service officer is to call the client before the contract is fully booked to verify if they really wanted two orders of 30000 pizzas to go through on their credit facility.  If the answer is yes, the client would send the necessary confirmation and the two orders of 30000 pizzas would be released with confirmation that the client needs them and intends to pay for them. The second order was confirmed before booking as should be required for so much Gianini dough on order.    They would call the client and then verify the order to ensure there is no wasted dough before the put the order through on the client's credit.  You could spend a lot of time getting your knickers in a twist afterwards as to who is at fault for the wasted dough. Why get upset when no one did anything wrong and there is no problem because there is no problem but how can you improve the system delivery and ensure there is no waste of precious resources or potential loss for the various stakeholders; including the client? Who would pay for the wasted dough as no one is accountable for what might have been a power failure on the customer's side?  But, how do you ensure there is no waste with the system in light of potential double booked pizza contracts that appear in the system because of power failures where the system would re-transmit an order automatically upon rebooting. It's a micro pizza exchange.     How much could it cost to delete the baked and boxed 30000 pizza order because I need to know and  my managers will have to decide what to do with the loss.  I can't just delete it with the loss but you would want someone to do that.  It's not my job to decide and why is this happening? Capiche?  Why is this happening with the my Giannini's dough and how often?  But, without making a full account of it with my managers who will decide how to solve it in the end, where is the solution or the plug for the whole in your dam?  Have you heard of Cisco  a' la "almost here" in the year 1997? In the final analysis, the issue is not speed of communication but what is being communicated. Is it one or two orders of 30000 pizzas because the system says the client asked for two or three?  But, I will just go to law school since I got in a month and a half ago and after I graduate prayerfully (it's not as if it is born on your tongue that you  will say or understand lacuna),  I will come back to serve the pizza parlor another day and who can speculate when he is not in a position to trade anything but is employed to improve and ensure system delivery for the client and the bank?  Capiche ?  In the mean time, before you put the system function in to catch erroneous double booked orders on a customer's account in a 15-30 day window ( your input is welcome) to save the potentially wasted Giannini dough, a side pizza service called the General Cuenta frozen pizza service should be set up.    You put all the double booked pizzas under the Cuenta brand after freezing them and then you parcel them out to over the counter clients who would show up for small orders to get the type of pizza that was ordered possibly erroneously until the entire order of 30000 pizzas is sold off and that was ordered by that client some time ago and, as such, there is no waste of the dough or the very special toppings that were provided to the original client upon that unfortunately double booked order of the pizzas. In this way, frozen pizza was born and the General Cuenta frozen pizza lived on forever as a very popular and dough saving frozen pizza brand.  Now, you may have left the dough ordered in various languages or currencies in suspense since you never fixed the problem and a person in fear of solutions may have tried to normalize the double booking since they thought solutions might cause too much efficiency and job losses.  Many of the currencies used to buy the dough have been blended into one currency by new Federal Banking and common market arrangements although the original contracts sit in suspense under the original currencies that should have been deleted but the pizzeria covered them. So, you could just convert the old contracts in suspense to the new single currency and sell the entirety of the dough  piece meal in over the counter money market deals at a profit. This is Cuenta Pizza.