cancel
Showing results for 
Search instead for 
Did you mean: 

Thousand separator conversion issue with SEGW for BW queries service

Former Member
0 Kudos

Dear All,

We have created a project in SEGW for SAP BW MDX query. While testing the service we found that if the amount/number is more than 6 digits then it is failing to display the results. We are getting below error message saying The argument '6.925.8477300000' cannot be interpreted as a number.

If we restrict the amounts to less than 6 digits it works fine. This is considering COMMA as decimal place and DOT as thousand separator.

Can any one tell me is there any setting we need to do to identify COMMA "  , " as thousand separator and DOT  ( . ) as decimal place in netweaver gateway . I have tried to set this in SU3 (User specific settings in both Netweaver Gateway and back end BW system however this did not solve my problem.

Our Netweaver gateway server is Unicode system and the back end SAP BW system is Non-Unicode system. Is there any setting that needs to be set for this issue?

Appreciate your help.

Below is the complete error log.

  <?xml version="1.0" encoding="utf-8" ?>

- <SAPGW_ERROR_LOG>

- <item timestamp="20140523071748">

- <ERROR_DATA>

  <SAPCLIENT>100</SAPCLIENT>

  <OPID>537C98FC266B1270E1008000911132D1</OPID>

  <SUBNO>1</SUBNO>

  <USERNAME>ZS224ABAPDEV</USERNAME>

  <TIMESTAMP>20140523071748.631168</TIMESTAMP>

  <ERROR_COUNT>1</ERROR_COUNT>

  <FIRST_TSTMP>20140523071748.631168</FIRST_TSTMP>

  <EXPIRY_DATE>2014-06-06</EXPIRY_DATE>

  <T100_MSGID>/IWFND/CM_CONSUMER</T100_MSGID>

  <T100_MSGNO>122</T100_MSGNO>

  <LOCATION>G</LOCATION>

  <ERROR_TEXT>The argument '6.925.8477300000' cannot be interpreted as a number</ERROR_TEXT>

  <ERROR_COMPONENT>OPU-BSE-SDE</ERROR_COMPONENT>

  <ERROR_PACKAGE>/IWBEP/ANA_ADP_ODATA</ERROR_PACKAGE>

  <SOURCE_PROGRAM>/IWBEP/CL_ANA_ODATA_DATA======CP</SOURCE_PROGRAM>

  <SOURCE_INCLUDE>/IWBEP/CL_ANA_ODATA_DATA======CM002</SOURCE_INCLUDE>

  <SOURCE_LINE>24</SOURCE_LINE>

  <NAMESPACE>/SAP/</NAMESPACE>

  <SERVICE_NAME>***Hide_due_to_secure_log_level***</SERVICE_NAME>

  <TRANSACTION_ID>537C989B266B1270E1008000911132D1</TRANSACTION_ID>

  <REMOTE_ADDRESS>127.0.0.1</REMOTE_ADDRESS>

  <DESTINATION>NONE</DESTINATION>

  <REQUEST_URI>/sap/opu/odata/sap/***Hide_due_to_secure_log_level***</REQUEST_URI>

  <BALOGNO>00000000000000122360</BALOGNO>

  <LOCAL_DATE>2014-05-23</LOCAL_DATE>

  <LOCAL_TIME>12:47:48</LOCAL_TIME>

  <FIRST_DATE>2014-05-23</FIRST_DATE>

  <FIRST_TIME>12:47:48</FIRST_TIME>

  <ICF_NODE>odata</ICF_NODE>

  <REQUEST_ID>537D9B9721C10900E1008000911132D1</REQUEST_ID>

  <LOG_LEVEL>S</LOG_LEVEL>

  </ERROR_DATA>

- <ERROR_CONTEXT>

  <ERROR_INFO>The argument '6.925.8477300000' cannot be interpreted as a number</ERROR_INFO>

  <_-IWCOR_-CX_DS_INTERNAL_ERROR />

- <CX_SY_NO_HANDLER>

  <CLASSNAME>CX_SY_CONVERSION_NO_NUMBER</CLASSNAME>

  </CX_SY_NO_HANDLER>

- <CX_SY_CONVERSION_NO_NUMBER>

  <VALUE>6.925.8477300000</VALUE>

  </CX_SY_CONVERSION_NO_NUMBER>

- <SERVICE_INFO>

  <NAMESPACE>/SAP/</NAMESPACE>

  <VERSION>0001</VERSION>

  <SERVICE_NAME>***Hide_due_to_secure_log_level***</SERVICE_NAME>

  <REQUEST_DIRECTION>Consumer to Gateway</REQUEST_DIRECTION>

  <AGENT>SAP Netweaver Gateway Logger</AGENT>

  <SYSTEM_ALIAS>BQ3</SYSTEM_ALIAS>

  <DESTINATION>NONE</DESTINATION>

  </SERVICE_INFO>

- <SYSTEM_INFO>

  <REQUEST_ID>537D9B9721C10900E1008000911132D1</REQUEST_ID>

  <REQUEST_URI>/sap/opu/odata/sap/***Hide_due_to_secure_log_level***</REQUEST_URI>

  <REMOTE_ADDRESS>127.0.0.1</REMOTE_ADDRESS>

  <APPLICATION_SERVER>BWsap121_BR1_04</APPLICATION_SERVER>

  </SYSTEM_INFO>

  </ERROR_CONTEXT>

- <CALL_STACK>

- <_-IWFND_-SUTIL_CALLSTACK>

  <MAINPROGRAM>/IWFND/CL_SODATA_ROOT_HANDLER=CP</MAINPROGRAM>

  <INCLUDE>/IWFND/CL_SODATA_ROOT_HANDLER=CM007</INCLUDE>

  <LINE>17</LINE>

  <BLOCKTYPE>METHOD</BLOCKTYPE>

  <BLOCKNAME>HANDLE_ERROR</BLOCKNAME>

  <LEVELNO>7</LEVELNO>

  </_-IWFND_-SUTIL_CALLSTACK>

- <_-IWFND_-SUTIL_CALLSTACK>

  <MAINPROGRAM>/IWCOR/CL_DS_HDLR_ROOT========CP</MAINPROGRAM>

  <INCLUDE>/IWCOR/CL_DS_HDLR_ROOT========CM00G</INCLUDE>

  <LINE>18</LINE>

  <BLOCKTYPE>METHOD</BLOCKTYPE>

  <BLOCKNAME>HANDLE_EXCEPTION</BLOCKNAME>

  <LEVELNO>6</LEVELNO>

  </_-IWFND_-SUTIL_CALLSTACK>

- <_-IWFND_-SUTIL_CALLSTACK>

  <MAINPROGRAM>/IWCOR/CL_DS_HDLR_ROOT========CP</MAINPROGRAM>

  <INCLUDE>/IWCOR/CL_DS_HDLR_ROOT========CM009</INCLUDE>

  <LINE>204</LINE>

  <BLOCKTYPE>METHOD</BLOCKTYPE>

  <BLOCKNAME>/IWCOR/IF_REST_HANDLER~HANDLE</BLOCKNAME>

  <LEVELNO>5</LEVELNO>

  </_-IWFND_-SUTIL_CALLSTACK>

- <_-IWFND_-SUTIL_CALLSTACK>

  <MAINPROGRAM>/IWCOR/CL_REST_HTTP_HANDLER===CP</MAINPROGRAM>

  <INCLUDE>/IWCOR/CL_REST_HTTP_HANDLER===CM001</INCLUDE>

  <LINE>103</LINE>

  <BLOCKTYPE>METHOD</BLOCKTYPE>

  <BLOCKNAME>IF_HTTP_EXTENSION~HANDLE_REQUEST</BLOCKNAME>

  <LEVELNO>4</LEVELNO>

  </_-IWFND_-SUTIL_CALLSTACK>

- <_-IWFND_-SUTIL_CALLSTACK>

  <MAINPROGRAM>CL_HTTP_SERVER================CP</MAINPROGRAM>

  <INCLUDE>CL_HTTP_SERVER================CM00I</INCLUDE>

  <LINE>627</LINE>

  <BLOCKTYPE>METHOD</BLOCKTYPE>

  <BLOCKNAME>EXECUTE_REQUEST</BLOCKNAME>

  <FLAG_SYSTEM>X</FLAG_SYSTEM>

  <LEVELNO>3</LEVELNO>

  </_-IWFND_-SUTIL_CALLSTACK>

- <_-IWFND_-SUTIL_CALLSTACK>

  <MAINPROGRAM>SAPLHTTP_RUNTIME</MAINPROGRAM>

  <INCLUDE>LHTTP_RUNTIMEU02</INCLUDE>

  <LINE>1218</LINE>

  <BLOCKTYPE>FUNCTION</BLOCKTYPE>

  <BLOCKNAME>HTTP_DISPATCH_REQUEST</BLOCKNAME>

  <FLAG_SYSTEM>X</FLAG_SYSTEM>

  <LEVELNO>2</LEVELNO>

  </_-IWFND_-SUTIL_CALLSTACK>

- <_-IWFND_-SUTIL_CALLSTACK>

  <MAINPROGRAM>SAPMHTTP</MAINPROGRAM>

  <INCLUDE>SAPMHTTP</INCLUDE>

  <LINE>13</LINE>

  <BLOCKTYPE>MODULE (PBO)</BLOCKTYPE>

  <BLOCKNAME>%_HTTP_START</BLOCKNAME>

  <FLAG_SYSTEM>X</FLAG_SYSTEM>

  <LEVELNO>1</LEVELNO>

  </_-IWFND_-SUTIL_CALLSTACK>

  </CALL_STACK>

- <REQUEST_DATA>

- <HTTP_HEADER>

- <IHTTPNVP>

  <NAME>~request_method</NAME>

  <VALUE>GET</VALUE>

  </IHTTPNVP>

- <IHTTPNVP>

  <NAME>~request_uri</NAME>

  <VALUE>/sap/opu/odata/sap/***Hide_due_to_secure_log_level***</VALUE>

  </IHTTPNVP>

- <IHTTPNVP>

  <NAME>host</NAME>

  <VALUE>BWsap121:8000</VALUE>

  </IHTTPNVP>

- <IHTTPNVP>

  <NAME>~remote_addr</NAME>

  <VALUE>127.0.0.1</VALUE>

  </IHTTPNVP>

  </HTTP_HEADER>

  <HTTP_BODY />

  </REQUEST_DATA>

- <RESPONSE_DATA>

  <HTTP_CODE>500</HTTP_CODE>

  <HTTP_REASON>Internal Server Error</HTTP_REASON>

- <HTTP_HEADER>

- <IHTTPNVP>

  <NAME>content-type</NAME>

  <VALUE>application/xml</VALUE>

  </IHTTPNVP>

- <IHTTPNVP>

  <NAME>dataserviceversion</NAME>

  <VALUE>1.0</VALUE>

  </IHTTPNVP>

  </HTTP_HEADER>

  <HTTP_BODY>***Hide_due_to_secure_log_level***</HTTP_BODY>

  </RESPONSE_DATA>

  </item>

  </SAPGW_ERROR_LOG>

Thanks

Manjunath

Accepted Solutions (0)

Answers (1)

Answers (1)

ChandraMahajan
Active Contributor
0 Kudos

Hi,

what is the EDM type for the field for which you are getting error? if it is Edm.Decimal then you may need to set precision as 8 and scale as 3.

Regards,

Chandra

Former Member
0 Kudos

HI Chandra,

Thanks for the reply.

The data type by default coming as Edm.Double however this is not editable to change as the definition is coming from SAP BW (Redefine --> BW Query Service). Also the thousand separator issue is coming only with ( if the number is more than 6 digits i.e 0,000,000.00 ). it is recognizing comma as decimal separator and a number can not have two decimal separators hence it is failing to convert. Is there any setting to change the thousand separator from COMMA to DOT in gateway service.

FYI: The BW system is Non Unicode system where as the gateways system is Unicode . There is no issue with Unicode BW system to Uni code Gateway system.

thanks

Manjunath

Former Member
0 Kudos

I believe we might a similar issue. We developed a query via Bex QueryDesigner and exposed it via Odata. Then we activated the service but when we want to test it, we get the following error:

The argument '-2,89' cannot be interpreted as a number.

Hence the service was generated automatically, we don't know where to debug some code or whatever.

Does anyone know any help?