cancel
Showing results for 
Search instead for 
Did you mean: 

# invalid character

Former Member
0 Kudos
699

Hi Folks,

I tried to activate data in the ODS but there is an error message that said: # invalid character.

I put the symbol # into the TX RSKC but doesn´t work.

Some good idea?

thks

EV

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi EV,

BW often uses # to denote invalid characters and they may not necessarily be #. It could be a carriage return or line feed as well, which can never be corrected thru RSKC. Try to debug in hex mode and see which characters they are. We have had this issue in the past and the best way is to correct it in the source system itself. If not, u could try to write a routine to include only valid characters, rather than exclude a character u have no idea about.

Cheers,

Zubin

Answers (6)

Answers (6)

Former Member
0 Kudos

The exactly error:

Error getting SID for ODS object 0FIAR_O03

Value 'D#' (hex. '4423') of characteristic 0SP_GL_IND contains invalid characters Error when assigning SID

Value '#' (hex. '23') of characteristic 0SP_GL_TT contains invalid characters

Error when assigning SID

Activation of data records from ODS object 0FIAR_O03 terminated

does anyone has an idea? Thanks in advance.

EV

Former Member
0 Kudos

Hi EV,

So, Hex 23 is a '#' symbol code. Characteristic values that only consist of the character '#' are not valid.

You need to write a routine in transfer rules to eliminate this char.

Best regards,

Eugene

Former Member
0 Kudos

eugene,

what routine would u write to eliminate this invalid one.

Former Member
0 Kudos

Hi,

why to effect globally by using tx rskc,better load using a constant in update rules

Thanks

Raman

Former Member
0 Kudos

Hi,

Please give us an exact error message, including HEX codes. # character may represent some another symbols.

Best regards,

Eugene

krzysztof_konitz4
Contributor
0 Kudos

Hi,

Try to use ALL_CAPITALS instead of listing all permitted codes...

Krzys

Former Member
0 Kudos

Hi ,

We had a similar issue..

All we ended up doing is replacing the # with a blank in the transfer rules.

Ashish

Former Member
0 Kudos

Hi,

Can you be more specific about the error message. May a snap of ST22 or others

Regards

GPK