Replicating dump on ABAP Program CLUR_NW7_USER_AGENT_INFO in quality server

[Former Member]

System raises exception CX_SY_CONVERSION_NO_NUMBER on ABAP Program CLUR_NW7_USER_AGENT_INFO.

Short text message is Unable to interpret "537.36 Google Favicon" as a number.

1. On the Source code part of the dump, on line 87 you can see the system is verifying if USER_AGENT_INFO-VERSION is a floating point number:

* rule for "(Chrome, >= 8.0, *)"
if user_agent_info-browser eq 'Chrome' and is_float( user_agent_info-version ) eq abap_true and user_agent_info-version - '8.0' ge 0. "#EC NOTEXT
lightspeed_info-supported = abap_true. "#EC NOTEXT

2. On the chosen variables section, you can see USER_AGENT_INFO-VERSION has some extra information and therefore cannot be interpreted as a number:

ME->USER_AGENT_INFO-VERSION
537.36 Google Favicon
333233246666624676666
537E3607FF7C5061693FE

3533372E333620476F6F676C652046617669636F6E

I raised a OSS and SAP told to implement note 2297238 update UR for fix.

Before implementing the same in production client wants me to replicate the same dump in quality system and do one round of testing. Kindly let us know how to replicate the same in quality server.

[pokrakam]

OK, all this very relevant information was missing from your original post.

Can you reproduce it in Development? Or for that matter can you reproduce it anywhere?

You could set a breakpoint at the point of the dump and see if it's being called, and under what circumstances. If you don't hit the breakpoint then you need to find out what the Vendor is doing to make it go there.

But my usual approach for SAP notes is as long as it's not high-risk, I'd apply it rather than waste days on it. It's unlikely to make the problem worse, most notes can be rolled back easily, and any changes should be supported by SAP. Regression testing through your landscape should uncover any obvious side-effects.

[Former Member]

Thanks Mike for the response. There are a few things that I need to explain.

1) I am not able to replicate the dump in development, quality or production server.

2) The issue is there in production server. We have built a webdynpro application with different views, tabs and other functionality that can be accessed by over 2000 vendors from any where.

3) I have checked note 2297238 which states when using Google Chrome browser version 49 or higher system raises above dump so I guess some of the vendors are using Google Chrome browser version 49 or higher to access our webdynpro application.

4) I have also installed Google Chrome browser version 49 and used the webdynpro application quality version but the same dump is not happening in quality server even after using Google Chrome version 49.

5) I tried reaching out to some of the vendors who use this application but they are not aware of how it is happening probably as they are the end users and not aware of the technical side.

[pokrakam]

Log on to QA and do the same thing that causes the dump in development.