Skip to Content
avatar image
Former Member

FX099: Wrong fieldtype for CURSOR. Has to be binary/hex type

Hi Experts,

I have problem with calling Classic BAdl in SE19. In detail; when I go into SE19 and select Classic BAdl there I call BAdl starts with u2018Zu2019 then click on display, new window comes with the TABs , when I change the TAB to Interface there I get the Runtime error u201CDYNPRO_ITAB_ERRORu201D.

When I search the Error in sdn.sap.com, I found couple of case which match the my case and the solutions are referred to kernel upgrade. I tried to upgrade kernel to available uppest level in OSS, but it did not..

Note: There has been recently migration made successfully on the system from Windows/Oracle to AIX/Oracle. Could this problem be related to migration?

Error analysis:

The program "SAPLSEXO" has terminated.

The following error occurred (short text of cause of error):

"FX099: Wrong fieldtype for CURSOR. Has to be binary/hex type."

The following elements are affected:

Screen name.............. "SAPLSEXO"

Screen number............ 0170

This error is connected to the processing of an internal table with the

field or variable "TC_METHOD-CURRENT_LINE", and was triggered within in the

program.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Nov 03, 2008 at 02:36 PM

    Hi Experts,

    I found a solution for this problem. You need to look at SAPNote 1257931. This has solved my problem.

    I wish you won't need it....

    Regards,

    Ali Taner

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 05, 2008 at 11:41 AM

    Hi, Mr. Ali Taner

    I am also facing the same issue, what you have specified the note is not available in sap market place. Please specify the correct sap note no.

    Thanks & Regards

    Venkat

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Mr. Venkat,

      The problem might be wrong typing of SAPNote number. I can open the SAPNote. "Note 1257931 - Screen output problems for transactions with large screens" so there seems to be no problem.

      Anyhow, the solution is that you need to add parameter 'ztta/diag_area' and the value '350000' into your systems' Instance Profile. Then save it and restrat the system. That will solve the problem.

      Let me know the result...

      Regards,

      Ali Taner