Upload of InfoCube 0SD_C03 fails due to "#" in 0PO_NUMBER

[Former Member]

Hello everybody,

I cannot upload data into 0SD_C03, due to the error "#" is invalid character.

I have checked the data coming into the cube and in 0PO_ORDER we have vale like this: "SIBN /#3".

What is confusing me a little bit is this: if I change the update rule and set the constant "SIBN /#3" it is fine. But if the value is coming from the ODS before, it fails

The ODS is of course not BeX enabled.

Any help appreciated.

Pawel

[Former Member · Accepted solution]

As mentioned before: according to SAP help:

The following characters are not permitted in characteristic values and cause errors in the system:

#

!

Thnx to everybody trying to solve this issue.

p.

[Former Member · Accepted solution]

Hi Pawel, I just read your question/answer. I have another question related to 0po_number. i mapped 0po_number to 2LIS_22_VAITM-BSTKD. In R/3 the field BSTKD is an 35 CHAR field. In BW it is just 20 CHAR. How did you solve the length discrepancy? Thx in advance, Peggy

[Former Member]

A blank character can be a non visible char. Try to copy the field and convert in Hex. You should see the invalid character

[Former Member]

Hello everybody,

I have reproduced this error while loading into BeX Enabled ODS (it failed during activation).

Then I have checked the long text of he error. There was a magic link: <i>if you want to know more about special characters in BW click here</i>. As I would like to know more about special characters, I have pressed and there was a nice documentation regarding this topic:

according to this documentation (see below) it is not possible to have "#" within a string.

)))))

For me it is the end of the story. If anybody knows something new about this, please let me know.

I will close the topic.

Pawel

<b>Invalid characters

The following characters are not permitted in characteristic values and cause errors in the system:

#

</b>!

Control characters with the hex-display 00 to 1F, if lower-case letters were permitted

Characters with a hex-code that represents lower-case letters in one of the installed languages

You can validate lower-case letters for any characteristic. You change the settings in the InfoObject maintenance screen- on the 'General' tab page- by selecting the lower-case letters option. If you select this indicator, the system does not run a consistency check for the characteristic values, and the system makes no distinction between capital and lower-case letters in the maintenance screens for variables.

[Former Member]

Hi,

May be the value comming from ODS has some extra unvisible characterstics.

With rgds,

Anil Kumar Sharma .P

[Former Member]

Hi,

yes, this was my first idea. But how to check it?

The second idea was: maybe the update program/activation program behaves in other way if I set in the update rule constant.

Short additional information: 0PO_NUMBER has neither Master data nor Text.

Pawel

[Former Member]

Hi,

Check it in PSA which is there before to ODS . If there is any blank sort of values in PSA , then you need to reload the Data to ODS first.

With rgds,

Anil Kumar Sharma .P

[Former Member]

I'm not really sure, whether I got you right:

1)Why should I check PSA if I can check ODS. In ODS is everything fine as it is not Bex enabled.

2) What does it mean: any blank sort of values. There is a blank in the string - that is for sure. But in rskc I have blank included and this was never a problem. Or do you mean blanks at the end (if yes how to check them).

Pawel