Skip to Content

ADSO Activation Fails due to Special Characters BW/4HANA 1.0 sp7

ADSO Activation Fails due to Special Characters BW/4HANA 1.0 sp7

We have an activation failing due to special characters in one of the fields. Characters are maintained in RSKC, which does not seem to be used in this case.

Question is, in previous version with a PSA you could correct the issue in the PSA and then load the target, but now since there is no PSA, is the only solution to edit the source document in ECC and reload?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jan 09 at 01:56 PM

    With the problem in hand, without making changes to your configuration, your only option is to do exactly as you said.
    It is of course recommended to add a routine to remove special characters. Here is a good example how to do this with an AMDP transformation:
    https://blogs.sap.com/2017/06/15/removing-invalid-and-non-printable-characters-in-hana-based-bw-transformation/

    Unfortunately, the error only comes up during activation, not during load.
    If you would prefer a manual step in the load process, you could add a routine to check if any illegal characters exist in the string (based on the code in the blog) and let the record error as a result. If you then create an Error DTP so you can make a manual change in the Error Stack. Seems a bit laborious though - it will be easier to just get rid of the special characters. (If you do go down the route of Error DTP / Error Stack, make sure you are familiar with note 2494151) https://launchpad.support.sap.com/#/notes/2494151

    Also worth noting (some background) - there is a different between special characters and invalid characters.
    Just in case you haven't seen it, the below is an interesting read....
    blogs.sap.com/2006/07/08/invalid-characters-in-sap-bw-3x-myths-and-reality-part-1

    Good luck!

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Pratish, this is a documented missing feature only recently resolved, in SP08. Depending what SP you are on, there might be a workaround available though. Please check note 2494151.