not Unicode-compatible, according to its program attributes.

[Former Member]

Hi all,

We have completed CU&UC from 4.7-> Ecc 6.0, we are facing the syntax errors for the below programs.

The following syntax error occurred in program "/RTC/AS_UPDATE_ACTIVE " in

include "/RTC/AS_UPDATE_ACTIVE " in

line 0:

"The program "/RTC/AS_UPDATE_ACTIVE" is not Unicode-compatible, accordi"

"ng to its program attributes."

can we add the varaiable abap/unicode_check=on ....

Please suggest...

Thanks,

Subahsh.G

[Former Member]

Thanks

[lucio_rodrigues]

Dear,

It looks that the 3rd-party program is not compatible with Unicode systems. since

the namespace / RTC / belongs to company Realtech. Please contact their support in order to clarify uour Questions concerning Non-Unicode-Capable Programs.

regards,

Lucio Rodrigues

SAP AGS

[Former Member]

Thanks for the reply,

I have checked the other programs which our Abapers have changed listed by UCCHECK , they are also prompting the same syntax error message like this program is not unicode compatable according to it's attribute..

When we change the program attribute to unicode check active it's showing syntatically correct... is there any way to make all programs have unicode check active by default...

Is abap/unicode_check=on is the solution?

please suggest....

Thanks,

Subhash.G

[markus_doehr2]

This is done through UCCHECK - you can select more than one program there and mark them as Unicode compatible.

If you´re in a Unicode system and you create new programs they have that flag automatically.

If you import transports from non-Unicode systems you can add

-Dsetunicodeflag=true

to your TP parameters so that the flag is set after the import.

The profile parameter you refer to, is to be set in non-unicode systems, to enable syntax checking as if the system were a Unicode system already.

--

Markus

[Former Member]

Hi Markus,

Even some standard programs also prompring unicode incompatable according to this attribute.

I had tried ur suggestions by running Uccheck but it's giving time_out error.

please suggest...

Thanks,

Subhash.G

[markus_doehr2]

This shouldn't happen.

Which programs are you referring to? (standard programs)

--

Markus

[Former Member]

Hi Markus,

In MM02 ->After giving MAterial number-> selec view->Basic data then only we are getting the short dump remaining options are working fine purchase ,storage ...

The following syntax error was found in the program SAPLZGD1 :

"The program "SAPLZGD1" is not Unicode-compatible, according to its pro"

"gram attributes."

" "

" "

All the Z* programs and Z*tcodes are prompting the same.

Please suggest...

Thanks,

Subhash.G

Message was edited by:

subhash gadde

[markus_doehr2]

For the Z*-programs, this is normal, you need to mark them either using UCCHECK or one-by-one in the program attributes.

For the standard programs I can just imagine, that an import of a transport/support package was done using a non-unicode R3trans.

Did you modify that program?

--

Markus

[Former Member]

Thanks Markus,

For the Z programs we have done the Uccheck and set the flag but Z -tcodes what we have to do...

Please suggest on MM02. we have Unicode R3trans only during import ...

Thanks,

Subhash.G

[markus_doehr2]

"transaction codes" don't have a Unicode flag in their environment. Transactions are just "wrappers" for the Z-programs; if the program has the flag, it should work.

I have no idea about the standard programs without the unicode flag. How many are they? just the part of the MM02?

--

Markus

[Former Member]

Yes Markus,

We are finding the programs for the Z-tcodes and only MM02-> Baisc data is giving the unicode error and other t-codes like ME22N is prompting for

" "The data object "KOMP" does not have a component called "EMPST"."

and the ME2L is prompting for :

" The following syntax error occurred in program "SAPLMRPP " in include "MM08RCOM " in line 86: "The type "SI_BBKPF" is unknown."

[markus_doehr2]

You wrote in a different thread that you are actually applying support packs, so those kind of errors can relate to that (SPAU not yet done).

I'd wait now for the functional departments to finish their SPAU, finish then the support pack installation and try again.

--

Markus

[Former Member]

Thanks Markus,

We have solved the MM02 problem, the program was a customer enhancement so we manually changed the attributes to make it unicode compatable.

Thanks,

Subahsh.G

[markus_doehr2]

Ok - good to hear it's working!

--

Markus