Automate

 View Only
  • 1.  Studio Query - Wrong numerical value from SAP floating point field (dot vs. comma)

    Posted 27 days ago

    I am developing a query on SAP table AUSP. This table contains several fields of SAP data type FLTP (floating point). For example field ATFLV with the value "2,000000000000000000E+02" (comma is decimal separator!). So I expect the value "200". 

    Unfortunately, the query in Winshuttle-Studio returns the (double) value "20.000.000.000.000.000.000,00" (dot is thousands separator!).

    Apparently it has something to do with the local number format (own vs. studio). But how do I get the right value? Where do I have to pay attention on to fix the query?

    Appreciate your ideas.



    ------------------------------
    Norbert
    ------------------------------


  • 2.  RE: Studio Query - Wrong numerical value from SAP floating point field (dot vs. comma)

    Employee
    Posted 27 days ago

    Hi Norbert,

    IDK if this is the same as what I'm running into with equipment measurement values. 

    You didn't share if you're in Excel or a form.  I found in a form the format is usually ok when you map to excel and run it there - not in preview.

    If it a form, but if I multiply by 1, I get the value I'm expecting.

    Hope that works for you, too.

    Sigrid



    ------------------------------
    Sigrid Kok
    Precisely Software Inc.
    ------------------------------



  • 3.  RE: Studio Query - Wrong numerical value from SAP floating point field (dot vs. comma)

    Posted 26 days ago

    Thanks Sigrid,

    unfortunately I am in an EXCEL based query in Winshuttle-Studio. So your multiplication by 1 is not applicable there. 

    Here the original value in SAP(-QuickView):

    And here the outcome in Studio-Query ("Run" tab, "Excel" data file type):

    Open the Sheet in EXCEL app (local German language settings), same faulty numbers are shown. 

    I don't expect that a transform formula to the Query-Mapping in Studio will help. Because this is obviously the basic outcome when running the query and the formula will transform the incorrect value into an even worse one. Please correct me if I am wrong.

    I hope for your further ideas.

     



    ------------------------------
    Norbert
    ------------------------------