There was an absolutely genius sarcastic comment in this thread that was posted by a throw-away and then deleted. I was going to reply to it, but saw it was de

There was an absolutely genius sarcastic comment in this thread that was posted by a throw-away and then deleted. I was going to reply to it, but saw it was deleted when I clicked to reply but was luckily able to copy it out of my cached version of the page. I'm going to reproduce it below, because it was hilarious: The deal was 800 millions. Unfortunately, Alice, a local purchaser, made a mistake in the Purchase Requisition in ME51N. After clicking on the "diskette" icon (or was it the "mountain"?), she noticed that she had written one zero too much (so 8 Billions). She immediately wanted to correct the error in ME52N (by clicking on the "pencil"). Unfortunately, her access to ME52N was revoked by the SAP Basis Authorization Team because the internal audit team wanted to improved "security" to respect the GDPR. She tried to contact Bob from the SAP Basis Authorization Team, but he was on holiday. Charlie answered for him but told Alice that she had to introduce a ticket in Solution Manager to ask for an access to ME52N. She had no access to SolMan, so she had to ask her Super Key User to make a ticket for her. The list of Super Key Users was available on a SharePoint list on the company's intranet, but had not been updated for a long time. Eventually she found out that her SKU, David, was retired. Fortunately her colleague Erika (a former SKU that moved from another division), had kept her access to SolMan and wrote the ticket for Alice. In the meantime, the Purchase Requisition had been approved by Fernand (from Finance) in the Workflow. Gerard, a (bored) new recruit, immediately converted it to a Purchase Order with ME21N. After a few weeks, Alice, who got access to ME52N, noticed that the PO had already been made by Gerard. She contacted him with Lync to inform him of the mistake. But the "Cancel" button for a PO was not working. During the User Acceptance Test, Gerard had noticed that Cancel did not work, but the consultants told him that he had to follow the scenario, otherwise they would tell his boss that he was "resistant to change" and that he had to sign off the UATs. (The bonus of the consultants was based on the number of successful UATs). It escalated quickly. The Director wanted to stop the transaction! But it was needed an unexpected Change Request to make the Cancel button work. The CRs, like authorizations, must be asked via SolMan, but the Director was unable to use it because it did not work on his iPad Pro (but it will soon because Fiori will solve all the problems). Eventually, as the CR was too complicated to implement, the purchase went through and SAP bought Qualtrix for $8B (but they still are unable to find the scanned invoice in VIM).