Unicode Compatibility

[Former Member]

Hi peeps:

Currently I am undergoing a shift from 4.6 to ECC 6 and I have encountered this issue testing my program in ECC 6. When I execute the program I will get this runtime error with the message "The following syntax error was found in the program SAPLZMM_JV_CUTBACK : The program "SAPLZMM_JV_CUTBACK" is not Unicode-compatible, according to its program attributes."

The error shows when it comes into this function module "OPEN_FI_PERFORM_RWBAPI01_P":

*----

---

Open FI Interface with local destination -

---

CALL FUNCTION fmtab-funct

TABLES

it_accit = c_accit

it_acccr = c_acccr

return = c_return

extension = c_extension

it_accwt = c_accwt

CHANGING

document_header = c_acchd.

I was wondering if this function module is obsolete and could there be new function module for this? Please help and thanks.

Matt

[Former Member]

The SAP function is flagged as Unicode compatible (see function pool ACC9, main program SAPLACC9)... but from the message you give the source of your error seems to be that the custom function group ZMM_JV_CUTBACK has not been flagged with "Unicode checks are active"... goto SE80, display that function group, and right click on function group object name and Display > Definition and check there.

Jonathan

[Former Member]

Hi Jonathan:

I followed your instructions to go to the Function Group and edit the definition by checking the "Unicode checks active". Upon changing I tried to compile the codes and got a compilation error saying:

"Include LZMM_JV_CUTBACK$05

Field "ROIUH_BAPIACEXTC" is unknown. It is neither in one of the

specified tables nor defined by a "DATA" statement . . . . . . . . . ."

[Former Member]

Hi Jonathan:

I followed your instructions to go to the Function Group and edit the definition by checking the "Unicode checks active". Upon changing I tried to compile the codes and got a compilation error saying:

"Include LZMM_JV_CUTBACK$05

Field "ROIUH_BAPIACEXTC" is unknown. It is neither in one of the

specified tables nor defined by a "DATA" statement . . . . . . . . . ."

[Former Member]

Hi Jonathan:

I followed your instructions to go to the Function Group and edit the definition by checking the "Unicode checks active". Upon changing I tried to compile the codes and got a compilation error saying:

"Include LZMM_JV_CUTBACK$05

Field "ROIUH_BAPIACEXTC" is unknown. It is neither in one of the

specified tables nor defined by a "DATA" statement . . . . . . . . . ."

[Former Member]

Hi Jonathan:

I followed your instructions to go to the Function Group and edit the definition by checking the "Unicode checks active". Upon changing I tried to compile the codes and got a compilation error saying:

"Include LZMM_JV_CUTBACK$05

Field "ROIUH_BAPIACEXTC" is unknown. It is neither in one of the

specified tables nor defined by a "DATA" statement . . . . . . . . . ."

[Former Member]

Hi Jonathan:

I followed your instructions to go to the Function Group and edit the definition by checking the "Unicode checks active". Upon changing I tried to compile the codes and got a compilation error saying:

"Include LZMM_JV_CUTBACK$05

Field "ROIUH_BAPIACEXTC" is unknown. It is neither in one of the

specified tables nor defined by a "DATA" statement . . . . . . . . . ."

[Former Member]

Hi

Hmm, I think you will find the "$" in "LZMM_JV_CUTBACK$05" indicates that it is a piece of code which was generated when someone used the test functionality built into SE37 for function #05 in the group.

Within SE37, I think you may be able to use something like "Function module > Test > Regenerate test" - or maybe you can just execute the test again on function "05" to regeneate it (look at the LZMM_JV_CUTBACKUXX code to see which function module name #05 is)... {{ or perhaps try killing LZMM_JV_CUTBACK$05 via SE38 - but please do check that the source code in it is indeed the SAP test harness before you proceed with that course of action!... it will say something like * THIS FILE IS GENERATED BY THE FUNCTION LIBRARY. * }}

Jonathan