#How to make a mashup how to

I joined our EC with standard Purchase Request BO's output.ДЄnd then I need some value of Purchase Request to use in our EC's field.

#How to make a mashup how to

This is bound to the Inport of the Mashup which ultimately receives values that we have passed from the Outport and hence the URL is launched with the values in these parameters !Дone !! Now save and activate your solution and test itвЂ¦Д«ut, I would like to know one point, that is when we join the output of standard BO and input of our EC, how to check the value of input field of EC's in absl. When the link is created, the event Handler basically launches the Outport. O Define this new Event Handler with 2 Operations: SyncDataContainer and FireOutportДЇireOutport -> Specify the Outport that we created for the EC O Define a new event handler for the OnCLick event You can get the mashup id by clicking on your mashup from your solution O In the properties of the Link, go to Event Arguments and create a new Argument with Argument name вЂњ$MashupPipeIDвЂќ and constant: your mashup ID. Once in the Design tab in the UI Designer, using the toolbox, add a Link to the screen We can create a Link for launching the mashup -> for each line item of the products facet containing the Travel product. вЂ“ Now, all that we need to do is to be able to call the mashup. Add a new navigation item and define the Outport вЂ“ Inport mapping. вЂ“ Double click on the mashup just added and go the Simple Navigation tab. вЂ“ On the EC, right click on the Mashup Components and add the mashup. This step is required to be able to bind the Outport of the EC and the Inport of the mashup.

On the Controller tab of the mashup, edit it and create an Inport вЂ“ with the same Package and Port type as we defined earlier. вЂ“ Go to the Configuration Explorer and Open your mashup. Step 5: We now need to specify the relation between the Outport of the EC and the Mashup. By doing this, we are ultimately passing values to the mashup from the values that are bound to the Outport of the EC, hence: вЂ“ Bind the parameters to the parameters of the Outport defined in step 3 above. вЂ“ Choose the same Mashup Category as in step 2 above and the related Port Binding By introducing the Outport in our Embedded Component, we are able to achieve that.ДЄdd parameters and bind them to the custom BOвЂ™s fields (recall that we had adjusted these fields in the action fillparams() Recall, that the Opportunity TIвЂ™s /OIF Outport cannot be enhanced, and for our usecase we needed more parameters. This is where you control what parameters you want to pass to the mashup. Step 3: Create an Outport for your embedded Component. For the Package, choose the one created in the step above Choose a Category that you would also use in the third step of creating a URL mashup. Step 1: To create a mashup, you first define a Port Type Package which consists of a Port Type and the parameters you want the binding to be done forвЂ¦ Part B is essentially different, and is highlighted below. Please refer to Part A of the blog вЂ“launched-from-an-embedded-component for the Use Case and Creating the Embedded Component In this blog, I talk about having a URL mashup that is launched from the Embedded Component. In my previous blog вЂ“launched-from-an-embedded-component I talked about creating an HTML script mashup that was being launched from an embedded component of a standard SAP Screen.