Hex character is only interpreted as ‘#’ in PSA.ĭepends on individual to select the method to overcome special char issue in BW ETL.The English language debut of the bestselling Dutch novel, Hex, from Thomas Olde Heuvelt-a Hugo and World Fantasy award nominated talent to watch Whoever is born here, is doomed to stay 'til death. If you are maintaining # in RSKC that doesn’t mean you have maintained hex character value. Please note – We can maintain only special character in RSKC, it is not possible to maintain hex character in RSKC as Hex character can not be entered via standard QUERTY keyboard.
We can maintain all required characters in RSKC tcode after proper business approval.
I have seen many consultants are writing code to eliminate # and results failure of solution to overcome scenario.ġ.
Now if you are writing code to overcome this issue then please note you have to consider Hex values not ‘#’. # have Hex value 23 but other special character in local language will have different hex value. Please note # & hexadecimal character both are different. Such characters are visible in PSA in format of #. But fact is hexadecimal character is not permitted local language/ special character. Usually consultants working on such ETL thinks # is hexadecimal character. So if while maintaining data in source system user might enter special character to highlight particular field or local language word so which will be interpreted as special / non recognised or hexadecimal character in SAP