Page 1 of 1

invalid char, when I try to activate this data,BRAIN290

PostPosted: Mon Jun 11, 2007 10:46 am
by learn sap
Hi,

I have read several posts on using special characters and the customization in RSKC. At the moment in out 3.5 system, NW 7.0 ,we have customized it with the value ALL_CAPITAL, which should accept most special characters as well.

However, I have some data records containing a character :)( may be  ) , ., (.) and when I try to activate this data, SAP rejects those records due to invalid characters. Function module RSKC_ALLOWED_CHAR_CHECK does not compain here, neither does RSKC_CHAVL_OF_IOBJ_CHECK with my InfoObject.

I have an InfoObject for a note , which may contain keywords for an event. This is a char 60 field.

This field is used in an ODS and it is not a key field. When I load the data from source system all looks OK, until I start activating the data. Then the system complains about the invalid characters.

RSKC only contains ALL_CAPITAL and I am not allowed to touch it (but I think I needn't to anyway).

It fail data load ………………………..……. Richey. Bob plans…..

It didn’t fail with data load ……….data 10 th. Bob plans…..

ABAP routine to avoid HEX00 - HEX1F

PostPosted: Thu Jun 14, 2007 10:57 am
by learn sap
more information

"
Characters that have a hexadecimal format between HEX00 and HEX1F are not permitted in characteristic values. The 28th character is one of these characters. The value is therefore not permitted."

Is their any ABAP routine to avoid this error in future

I need to display ' ' if there is char between HEX00 and HEX1F

PostPosted: Thu Jun 14, 2007 1:28 pm
by skarkada
Code: Select all
  l_strlen = STRLEN( c_text ).

  DO l_strlen TIMES.
    IF c_text+l_offset(1) < ' '.
      c_text+l_offset(1) = ' '.
    ENDIF.

    ADD 1 TO l_offset.
  ENDDO.

PostPosted: Thu Jun 14, 2007 2:00 pm
by learn sap
Thanks for your reply.

Today I found in source system that has following enrty

....real Data.####Bob had....

Please send me a code to change "#" char as ' ' in Transformation (NW 7.0)

PostPosted: Fri Jun 15, 2007 6:19 am
by skarkada
The above code should fix this also. What you see as # is really some unprintable ASCII characters that SAP shows as #.

PostPosted: Sat Jul 14, 2007 7:19 am
by learn sap
Thanks a lot. it works