Data360 Analyze

 View Only

  • 1.  Unable to map SAP type: e. Error message

    Posted 07-31-2023 02:16

    Good day, community.

    I'm trying to pull the KONV table from SAP. I'm using the Extract ERP Table node. 

    This works well for most tables. I'm able to pull VBRK, BKPF, and more with no problems.

    Whenever I try to extract the KONV table I get this error: Unexpected error occurred during processAll while running the node: java.lang.IllegalArgumentException: Unable to map SAP type: e.

    I'm not too sure where to start looking for the issue. Is it an issue with SAP? Is it a Java issue?

    Any assistance is greatly appreciated.



    ------------------------------
    Joshua Wall
    Knowledge Community Shared Account
    ------------------------------


  • 2.  RE: Unable to map SAP type: e. Error message

    Posted 07-31-2023 02:29

    Hi Joshua,

    If you can't find any solution to this error, please raise a technical case with our Support Team at https://support.precisely.com/.  



    ------------------------------
    Paweł Góralczyk
    Precisely Software Sp. z o.o.
    Warszawa
    ------------------------------

    Original Message


  • 3.  RE: Unable to map SAP type: e. Error message

    Posted 08-01-2023 01:49

    Hello Joshua,

    This error was discovered by us also few months ago. It was confirmed as bug by Precisely on May 8th.

    The problem itself is a SAP field data type (INT64/INT8) that the ERP Table node doesn't support. The tables that don't have this data type fields process ok.

    I have the following response regarding fix:

    "

    Yes, It will be fixed in the next release 3.10.3.

    "

    If you try it out let us know if it worked.

    Best Regards,

    Markku Rantala

    Product Manager

    ADSOTECH



    ------------------------------
    Markku Rantala
    Adsotech Scandinavia Oy
    Espoo
    ------------------------------

    Original Message


  • 4.  RE: Unable to map SAP type: e. Error message

    Posted 08-07-2023 03:50

    @Joshua

    This bug still exists in version 3.10.3



    ------------------------------
    Markku Rantala
    Adsotech Scandinavia Oy
    Espoo
    ------------------------------

    Original Message


  • 5.  RE: Unable to map SAP type: e. Error message

    Posted 10-16-2023 02:08

    Has Precisely made any progress on this issue?



    ------------------------------
    Joshua Wall
    Knowledge Community Shared Account
    ------------------------------

    Original Message


  • 6.  RE: Unable to map SAP type: e. Error message

    Employee
    Posted 02-19-2025 09:01

    This issue was resolved in the Data360 Analyze 3.12.3 release (which was released December 19, 2023). 

    The release notes for the change were:

    ====

    Updated the ERP nodes in analyze to support long ("Int8", ABAP Type "8") and large floating point ("DECFLOAT34", ABAP type "e") types which are present in newer SAP systems.

    These changes require at least SAP JCO library version 3.1.8 to be installed. The node has been verified against SAP JCO 3.1.8.

    When upgrading an Analyze instance which was using the ERP nodes, the JCO library in use will also need to be updated. The locations and file names for the libraries required by the node have not changed.

    ====

    Please note the minimum required version for the SAP JCO library.



    ------------------------------
    Adrian Williams
    Precisely Software Inc.
    ------------------------------

    Original Message