Error(s) during ecc 6.0 upgrade (UC_OBJECTS_NOT_CHAR)

[former_member1161170]

Hello!

I’m testing my z-programs in the new ecc6.0-quality system (we’re arriving from 4.6c) and I’m getting several errors from standard functions, but these errors seem to be always the same error: “UC_OBJECTS_NOT_CHAR”.

For example I’m getting (OLE2):

“The current ABAP program "SAPLOLEA" had to be terminated because it has come across a statement that unfortunately cannot be executed.

[…]

Bei der Anweisung

"DESCRIBE"

sind an der Argumentposition "<F>" nur flache zeichenartige Datenobjekte

unterstützt.

[…]

319 WHEN 'C' OR 'u' OR 'g'. "char, struc

320 SYSTEM-CALL SOLID POINTER ASSIGN PEXPORT TO <F>.

321 if ABAP_TYPE = 'C'.

>>>>> DESCRIBE FIELD <F> LENGTH l in character mode.

323 if l = 1.

324 TYPE_DESCR = CL_ABAP_TYPEDESCR=>DESCRIBE_BY_DATA( <F>

325 TYPE_NAME = TYPE_DESCR->GET_RELATIVE_NAME( ).

326 IF TYPE_NAME ='ABAP_BOOL'.

327 VARIANT_TYPE = OLE2_TYPE_BOOL.

328 VARIANT_VALUE = ABAP_VALUE.

329 RETURN.”

Or, another example (LIST_TO_ASCII):

“The current ABAP program "SAPLSLST" had to be terminated because it has come across a statement that unfortunately cannot be executed.

[…]

Bei der Anweisung

"DESCRIBE"

sind an der Argumentposition "LISTASCI" nur flache zeichenartige Datenobjekte

unterstützt.

[…]

79 IF listasci IS SUPPLIED.

>>>>> DESCRIBE FIELD listasci LENGTH ascisize IN CHARACTER MODE.

81 ELSEIF list_dyn_ascii IS SUPPLIED.

82 component-name = `TEXT`.”

The same codes are working fine in 4.6c of course.

What can it be?

[Former Member]

check this,

https://archive.sap.com/discussions/thread/772243

After unicode this behaviour is normal and need adjustment i guess.

[former_member1161170]

1) I can't change the code: SAPLOLEA and LISTASCI are standard sap codes

2) Both lines are already "IN CHARACTER MODE"

[pokrakam]

The most likely scenario is that the data structure you are passing in OLE or other external interfaces has changed from 4.6 to 6.0.

For example, you may have:

DATA blah TYPE someSAPstructure.

Anything going outside of SAP (OLE, RFC etc.) can only contain flat character data (see CLIKE under Generic ABAP Types).

If SAP have updated someSAPstructure to include a type P or F, or made it a deep structure, your code will generate such an error. Or indeed if you used someone else's Z-structure and it has been changed in such a manner.

[raymond_giuseppi]

Check if Note 2118249 - ABAP dump with UC_OBJECTS_NOT_CHAR exception is suitable for your version, else it's time to read some of the many wiki documents on UCCHECK... How far are you in Unicode activation?