Next go to context of view and navigate to attribute CARRID. Navigate to view MAIN and define component usage for WDR_OVS using new button.
To implement OVS search help first step is to add component WDR_OVS to web Dynpro. If you test web Dynpro and take value help on input Airline you will get SAP standard value help based on search help S_CARRIER_ID. At this point create web dynro application and activate all objects. You should now have Airline input on screen. On next screen press ‘Context’ button and choose node FLIGHT and press OK. Go to layout tab and right click on ROOTUIELEMENTCONTAINER and choose ‘Create Container Form’ option. We have context attribute, let add this to screen as input. Now go to view context and create Node based on dictionary structure SCARR and ‘Add Attribute from Structure’ CARRID to screen. I will do this in steps to explain one thing at a timeĬreate Web Dynpro ZPW_OVSDEMO1 with Window ZPW_DEMOOVS1 and view MAIN. Using WDR_OVS component I will implement search to display values based on plane type. Automatic search help on this field is based on search help S_CARRIER_ID I am going to create a simple Web Dynpro with input based on field SCARR-CARRID. Typically used to fill returned value in input where user took value help. This triggers when user has made selection from list. In case you have implemented phase 1 you will also get selection values entered by user which you can include in you logic. This can be a complex logic to a normal select. In this phase we write logic to create list. From user point of view they will get list when they take value help. This is however optional, if you ignore this phase, PHASE_3 will be invoked.
Make sense if your result set is large as this will help user to narrow down selection. Here you can specify any selection screen you want to issue before you display any result. Window title, Group header, table header, labels if they are different from data element labels.
Get web dynpro code#
I will very briefly explain about what code should be included in each phase, more details about each phase is explained at link OVS Value Help. Instance attribute OVS_CALLBACK_OBJECT->PHASE_INDICATOR contains value for phase. This event is triggered at four different times also known as phase, essentially when component expects data from used component or when selected data is available to consume. WDR_OVS raises event OVS, this is where you will need to put all your coding. Therefore, the value help is automatically available for each input field that is bound to this context attribute. The OVS value help is linked to the context attribute. OVS value help is implemented using component WDR_OVS.
Get web dynpro how to#
OVS linked value help puts you in control of selection fields that search help will display, selection logic, and columns displayed in result and how to use value returned by user selection. If standard search help does not fulfil your business requirement in web dynpro then you can implement OVS value help.
Before I start with example I should mention that you can find SAP standard demo in your SAP system DEMO_VALUE_HELP and WDR_TEST_OVS.
0 kommentar(er)
