Display the Interface View of a Component Usage in a Modal Dialog Box Demo in SAP ABAP

Thorsten Desef
A free video tutorial from Thorsten Desef
SAP Senior Consultant
4.0 instructor rating • 1 course • 2,665 students

Lecture description

Demo: Display an interface view in a modal dialog box.

Learn more from the full course

SAP Web Dynpro ABAP

Web Dynpro for ABAP is one of SAP's UI technologies of choice, and this course will show you why.

11:05:21 of on-demand video • Updated August 2014

  • Understand the role and application of Web Dynpro for ABAP in SAP’s UI strategy
  • Develop Web Dynpro ABAP-based applications
  • Integrate Adobe technology into Web Dynpro
  • Prepare you for advanced Web Dynpro topics
English [Auto] This demonstration I want to show you how to use pop ups to pop up we want to use is the provider component that should be displayed here in the consumer component and it should display the customer information where we have a look at our current application and we hit the refresh connection button. Then we have our customer information here at the bottom of the second view. This custom information should not be displayed by default at the bottom of the second view but should be available rather as a pop up whenever the user clicks on the booking table. So it's a redesign which means we have to remove some of the artifacts and create some you coding here. The first thing is in the second you we have our container UI element. This apparently is not required anymore and we can delete it from here because we are not going to display the customer information here. And the second view. Secondly by removing this content element we have made our window inconsistent because in the window this content element is displayed and allows us to embed the providers in the face of you. So we have to go to the window now and we will see the inconsistency right now here it shows here that there's a problem and we will delete this container. So the window is consistent now. Then we are creating the proper code. And this is done when the user clicks on the table so it's the only selective end of the table. And the only select Event of the table is bound to the action display customer. So the display customer action right now which calls component to display customer which then of course interface controller of the provider component to speak customer has to be extended. And this is my using the method to code with. And here's our component use customer for the interface your customer win and here is the generated code. Now when you look at this call you see it. Eventually it doesn't call the Creator. We know for CMPD usage method it calls the new and more modern method create and all pop up. If this is not available in your system then it will be available after upgrade to at least NetWeaver 7:3 answer. Package one. All right. We are already done here there's no local window open call necessary as we have heard already in the lecture and there's only one more step we have to do. And this is in our component controller. We have an unnecessary call right now of display customer. And this is in the read box. So previously we have made sure that the Customer form is always up to date regardless how we were changing the data or whether we clicked on the flight table picked on the booking table or navigated from the first view to the second view. Now because we are just being customer information only undermine. This is not necessary anymore. And after the activation we are ready to go. And clicking a booking opens the customer pop up. Now if your customer Pop-Pop doesn't look that nicely then you should play around with the width of the customer the views round your eye and the man I've tried. Here 750 picks with. And it works quite nicely. You can move this around. You can give it full size resize and that's it for close. But.