Skip to Content
author's profile photo Former Member
Former Member

Possible bug in OVS component

Hi all,

i played around a little bit with the OVS value help service described in the WebDynpro homepage article by Bertram Ganz. I'm using a selfdefined structure Person defined in my "Local Dictionary". There are two custom controllers PersonCC and PersonCCOvs and a view controller PersonView. The context structure of PersonCC is comparable to the structure in the article (Input with some attributes(1:1) and a child node Output with some attr.(0..n)). The view context is mapped to the context of PersonCC. The context of PersonCCOVS is something like a subset of PersonCC's context (there are only the attributes in Output, which are necessary to identify a person in the table displayed in the OVS dialog). Doing this i ran into the following problem:

I would expect, that only the attributes of Input and Output in PersonCCOvs are used for the generation of the input form and the output table of the OVS dialog.

This is true, if i set the types of Input and Output attributes to the simple types defined in the Person structure.

This is not true, if i bind the Input and Output nodes to the structure and select the attributes needed for OVS. Then always all structure elements are used, regardless which attributes are available in Input/Output.

I guess, this is a bug in the system component which handles OVS?

Furthermore, i'd like to make two proposals to enhance this great feature:

1. The "UI generator" of the OVS component seems to use an alphabetically sorted context attributes list for the sequence of the form input elements and table columns. This is not always the best from a more logical point of view.

It would be nice to have a possibility to influence this without naming the context attributes from AAFirst to ZZLast, maybe by adding two optional IWDAttributeInfo arrays to the addOVSExtension method, which define the desired sequence:

  new PersonCCContextNotificationListener());

2. There should be a possibility to provide "custom components" which build and handle the OVS dialog contents by themselves. The necessary component interface including init-,callback- and so on methods and including the interface view displayed in the dialog could be predefined by SAP. The WD developer would have to implement this interface to ensure "well formed" components.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jun 04, 2004 at 09:48 AM

    Hi Stefan.

    I'm also busy trying to understand the way the OVS works.

    Can you give me a hint about the public methods getOVSListener(), getOVSinputNode() and getOVSOutputNode(). They are not described in the document.


    Bertil Rebergen

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Bertil,

      getOVSOutputNode() returns wdContext.nodeFlight_List(). After having declared the model binding a context structure <i>model node 'Bapi_Flight_Getlist_Input' - inner node 'Output' - inner node 'Flight_List'</i> is created. The OVS Service needs a reference to the node containing the collection of model node elements of type 'Flight_List' or model objects of type 'Bapisfldat'. The node 'Output' has the cardinality 0..1. It is associated to the singleton node 'Flight_List' containing the search result data.

      Regards, Bertram

      Here the correct code:

      public IWDNode getOVSInputNode() {
         return wdContext.nodeBapi_Flight_Getlist_Input();
       public IWDNode getOVSOutputNode() {
         return wdContext.nodeFlight_List();
       public IWDOVSContextNotificationListener
       getOVSListener() {
         return ovsListener;

  • author's profile photo Former Member
    Former Member
    Posted on May 26, 2004 at 08:26 AM

    Hi Stefan,

    Bertram is on vacation for a couple of weeks, so we need to discuss this as soon as he is back!

    Best regards,


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.