 In this segment, I want to showcase you how simple and easy it is to create a new outbound object event. In order to do that, we already prepared a more complete use case where we utilize an Azure Event Grid. We have a logic app configured there that sends our event into a Teams channel and allows us there in the Teams channel to approve a SAP purchase order. So what we are going to do is to configure the outbound event for when the purchase order is released so that we send this event into the Event Grid and then through the logic app. So in order to do that, I go into our SAP system and the configuration happens in the IMG just as any other SAP configuration does and the framework has a subsection here and all the configuration will be done here in connection and replication object customizing. So we do want to send data to our Azure Grid. So we choose that connection and as you can see we have no objects configured yet and we have to create a new entry for it. So first of all, we have to give it a name and we then have to define how the payload should look like and we want to utilize our database view extraction so that you don't have to code anything but just define a database view. So we first give here a name of a database view. So this database view does not yet exist. We will create it in a second. And the data extraction then can be done using our generic view extractor and this goes hand in hand with a formatting function for the Event Grid event format and we then also have to specify an ALE message type that we created beforehand. So it's called ZACIPoReleaseGrid and we have to specify that it should be an incremental load and for development purposes we do activate the tracing so that we can in our monitoring transaction see the payloads going out. So now as I said the database view does not yet exist so we have to still create it. It does not exist so we create it. As I said we want to send out data on a purchase order so that we can approve it in a Teams channel. So we want to fetch data from the purchase order header that's EKKO and from the line items that's EKPO. And based on the data definition inside SAP we can take the already known relationships there and utilize those as our join conditions. And then we have to select the fields that we want and we do start with the key fields. So we have to take the client and purchase order number from the header and we take the item number from the item table. So this important step to get started with the key as we later link it to a business object event and then want to extract data based on the key. For our use case we need some additional information so we need the company code, type of the purchase order, we need the render number and we also want to output the purchasing organization group and the currency and from the item table we take also a few additional fields. We want to have the short text, the material number, the plant and the quantity and unit and we also want to take the net value just to have these as information for our approval. So now we got the complete list of fields that we want to add and as you see it has the cryptic SAP field names and you probably want to rename them that are utilized in the event. So we just rename the ones now that I need for the prepared flow and not all of them are expected in the flow so we just rename the ones that we really need. Currency, this we named material text and material number and the quantity, we also want to rename that and the net value. So now that we renamed everything we can save, we have to assign it to package and then can activate it. So once we have activated it, we can continue to link it to our application event. So as said we want to send out purchase order information when the purchase order is released so we choose a business object 2012 which is for purchase order and this has an event that we can utilize here, an application event, release step created and when this happens we want to trigger our framework and we have a function module to do so, we have to enter that and activate the linkage. So to save that and now the last running step is to define where in our Azure event grid it should go. So we choose the topic that we created there, it is called PO Approval Events and we have to also change the subject. This is part of the event grid header in the payload and we want it to be our system ID. So now that we have configured all that and saved it, we can already use it. So here on the right hand side you see my Fiori Launchpad. On the left hand side you see my Teams channel where the approval notifications will be posted to and so now I create a new purchase order. I have to choose the type with external approval, select a supplier to use and also add an item that we want to order here. So having the item we want to get 100 of that item. Now we can create the purchase order. So purchase order is in approval and as you can see on the left hand side the notification on the approval has already arrived. It does give me some data from the purchase order, so purchase order number, which company code, which vendor and which material it was, quantity and price as well. So we can click here on approve and this will now send data back to the SAP system and that's basically it for creating a new outbound event.