Skip to Content
Former Member
Jul 08, 2013 at 02:07 PM

DSO Activation failed due to # character


Hi all,

I'm loading from R/3 a Product Description that is failing DSO Activation many times because in R/3 field, user can put an "enter" value, I mean, Product Description may contain 2 rows and from 1st to 2nd row user press "enter".

For example:

1row "Product description

2rows "Product description [enter]

continues here"

When 2nd case happens, that [enter] is translated to # in BW. In RSKC '#' character is already included, but this is only helpful when customer has written that value directly, not when is translated from [enter].

According to SAP help, when a string contains # or starts by !, it looks like the solution is to modify values in PSA, but this is annoying me because I have to do it almost every data load.

Does anyone know if there's a solution for that [enter] value translated to '#' ? Just to let you know, I cannot change R3 field properties, so user will always be able to press enter in Product Description.