Skip to Content

OVS error on selecting an item for a custom BO

I have created an OVS based on a custom business object via the create-screens menu off the business object so that its auto-generated.

My BO only has two fields and I have selected only the ID (the first field) for the OVS.

When I try to use this OVS on a screen field by choosing the type of the field as OVS and setting the ValueHelp parameter to my new OVS - it fails at runtime.

It display my result list just fine showing all my business object ID's. But when I select one it crashes with a no-argument error.

From what I can see in the help the above is all I need to do when creating an OVS via this method. However there must be something else missing in the outport or something??

Any ideas?

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    Posted on Jul 15, 2016 at 03:33 PM

    Hi Jason,

    • Try Dump Analysis, if anything found, correct it.
    • Make sure you bind your VallueHelpQuery to QueryByElements.
    • If nothing works, and you need solution for sure, raise a ticket

    Regards,

    Senthil

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 14, 2016 at 02:11 AM

    It seems that nowhere is there step-by-step instructions on how to create an OVS against a custom business object and actually make it WORK!

    As usual for SAP - the high level overview documentation is very good. The details on how to make things work is pathetically BAD!

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Richie, thanks for posting.

      I'm not sure what you mean? Are you saying that I am supposed to create new queries to make an OVS work.

      As you can see in my series of screen shots above I have simply followed the SAP Help in creating the OVS. According to that when I create screen - ovs I should already end up with a usable OVS without having to create queries, do binding and so on... But no it does not work like that.

      Interestingly I have got the OVS to work now by pretty much randomly clicking around. I changed the names of the fields that are bound to ObjectId and ObjectName and magically it started to work and send back the fields to the screen field the OVS is attached to.

      So why on earth id the standard OVS generation create it with different names!??

      Anyway - the OVS now displays all values and I can successfully choose one. 50% there.

      However if I try to narrow down my search by typing T for example to get those entries starting with T it still shows them all but I see an error saying the inport is incorrectly configured and that suggestion won't work.

      I fixed it by simply disabling suggestion! ;-)

      This is real dodgy stuff. If only someone at SAP could actually document stuff good.

  • Posted on Jul 13, 2016 at 09:43 AM

    Hello Jason,

    Please provide the screenshots of all settings done in the OVS.

    Thanks & Regards,

    Meghna

    Add a comment
    10|10000 characters needed characters exceeded

    • Hello Jason,

      In the screen "Select OVS Component ..." there is something to do: 🤪

      • You need to bind the Inport of your OVS to the /Root/Terms1 parameter of the EC.

      How else should the UI know which value to transfer? From the calling UI (the EC) as well as the result back?

      HTH,

      Horst

  • Posted on Jul 13, 2016 at 10:23 AM

    Hi Jason,

    1) In the UI designer compare the element type of the input field with the OVS outport element type

    to see if they are same
    2) Do you have AfterModify or BeforeSave event on the Custom BO, if yes debug it

    Thanks, Pradeep.

    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.