Skip to main content
Nintex Community Menu Bar
Solved

executing bapi in test cockpit produces value_not_fltp error

  • August 12, 2020
  • 2 replies
  • 101 views
  • Translate
M

Hi.

Hope someone can help with this. I've been struggling with testing this bapi.

I am trying to run a SAP BAPI, MEASUREM_DOCUM_RFC_SINGLE_001, in the K2 Connect test cockpit. I am getting a RfcInvoke failed(RFC_ABAP_EXCEPTION): VALUE_NOT_FLTP error.

This is occurring when I enter a value, for example, 35.12 as the RECORDED_VALUE. If I enter 3512 it works. Entering 35 works but 35.00 doesn't.

The bapi works fine entering 35.12 from within SAP via transaction SE37

As an aside, I had trouble with the READING_TIME before discovering that hhmmss is the expected format rather than hh:mm:ss.

Cheers

Ian 

Best answer by macca

Hi.

Google is my friend

using a comma has resolved this

Cheers

RECORDED_VALUE is transferred in CHAR format. If the field contains decimal places, these must be separated using a comma or period according to the setting in the user master

 

View original
    Did this topic help you find an answer to your question?

    2 replies

    M
    • macca
    • Author
    • 2 replies
    • Answer
    • August 12, 2020

    Hi.

    Google is my friend

    using a comma has resolved this

    Cheers

    RECORDED_VALUE is transferred in CHAR format. If the field contains decimal places, these must be separated using a comma or period according to the setting in the user master

     

    Translate
    M
    • macca
    • Author
    • 2 replies
    • August 20, 2020

    Possibly a better soution is to change the user profile. Transaction SU01, Defaults tab. Set the decimal notation as required. This was the solution implemented in my case.

    Translate

    Reply


    Sidebar Buttons
    Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
    Terms & ConditionsCookie Settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie Settings