cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

invalid characters

phil_moh
Participant
0 Likes
4,640

We're on BI7.

I have loaded the record from Flat File into PSA, no problem.

Now when I try to load the redord from PSA into InfoCube via DTP, I hits the following error:

"

Diagnosis

Only the following standard characters are valid in characteristic

values by default:

!"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.

Furthermore, characteristic values that only consist of the character #

or that begin with ! are not valid.

You are trying to load the invalid characteristic value Capacitor 17 &

(hexidecimal representation 436170616369746F72203137 ).

System Response

"

When I check the value of the record, it is as follow:

Capacitor 17

So dont see any problem with it. Please advise what is wrong and how can I solve it?

Thank you.

Edited by: lynn on Sep 18, 2009 5:03 AM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Likes

most likely its because ur source file contain invalid characters.

I suggest u check your source file,

or actually, you can maintain ur PSA entries, eg, manage the PSA, navigate the error line, double click the line which will show you the detail, and manually change the Caxxx 17 to simple text, like "Fixed",

and load the data again to see if theres difference.

Answers (6)

Answers (6)

phil_moh
Participant
0 Likes

Because the text consists of upper and lower case, so you have check the LOWERCASE indicator in the infobject!!!

Former Member
0 Likes

Hi ,

As the load is flat file load. You can do the changes in that record. Then try loading it again. Or else check in RSKC

!"%&''()*+,-./:;<=>? are maintained or not.

Regards,

Rahul.

Former Member
0 Likes

The transaction to tell the system to accept this characters is; RSKC

Former Member
0 Likes

The PSA would accept invalid character even that is not valid in BW. You will get error only when you run DTP.

Check your Source file. Open the file in Text editor as suggested by D.H. Snellink. You would find some clue. The same happened to us once. Generally You wonu2019t notice any invalid character in PSA entry even it exists.

Ripal

Former Member
0 Likes

Hi There,

Please note that even there contain invalid characters, the data can still be loaded into PSA.

Kenny

Former Member
0 Likes

Possible there is a carriage return or something at the end of a line/record. You cannot always see this when you look in BI. So check your file in a editor like text-editor. There must be a sign somewhere thats not allowed.

phil_moh
Participant
0 Likes

But the thing is I can load this data into PSA.

Only when PSA into Data Target (via Transformation), then I hits the error.

Any other clue?

I remember long time back that someone say need to run some transaction so that system can take invalid character like "@ # $ etc". Do you know what transaction ?

Former Member
0 Likes

Hi lynn,

The Transaction is RSKC to maintain the list of permitted characteristics in BW.

If you want you can add the character in RSKC.

Also At PSA level there is no check for special characters so it will not give any error.

I would suggest to delete that filed data "Capacitor 17" in PSA and manually type "Capacitor 17", and then load it further.

Regards,

Pratap Sone

Former Member
0 Likes

Hi lynn,

as written there aren't checks loading data into the psa. So this can't be the problem. What i do, if i have problems with characters: i write a small routine within the transformation and define the characters by myself which are valid or not. Any other character will be replaced by an blank:


DATA: l_d_offset LIKE sy-index.
  CONSTANTS: c_allowed(100) TYPE c value
  'ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890_-/!?.ÖÜÄ'.
* Es sind nur Großbuchstaben erlaubt, also Umwandlung in Großbuchstaben.
  TRANSLATE RESULT TO UPPER CASE.
  DO 60 TIMES.
    l_d_offset = sy-index - 1.
    IF RESULT+l_d_offset(1) CO c_allowed.
*     Erlaubtes Zeichen, mache nichts
    ELSE.
*     Zeichen nicht erlaubt, ersetzen durch Leerzeichen
      RESULT+l_d_offset(1) = ' '.
    ENDIF.
  ENDDO.
  RETURNCODE = 0.

Maybe this helps.

regards,

Thomas

dennis_scoville4
Active Contributor
0 Likes

Is there a space at the beginning or ending of the value? If so, it needs to be trimmed or condesned in order for it to be acceptable. SAP BW chokes on values that start with or end with a space.

phil_moh
Participant
0 Likes

I check, no space at all...

please help.

dennis_scoville4
Active Contributor
0 Likes

Is the target InfoObject setup to accept lowercase letters? If not, you either have to convert to uppercase or check the 'Lowercase letters' checkbox on the General tab of the InfoObject.