Function module to remove special characteristics while loading data into SAP BW from different sources.

* Create ZSTRING OF LENGH "25O" AND TYPE "CHAR".
* Create STR_IN and STR_OUT with reference to ZSTRING.

FUNCTION <   >.
*"----------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     REFERENCE(STR_IN) TYPE  Z_STRING
*"  EXPORTING
*"     REFERENCE(STR_OUT) TYPE  Z_STRING
*"----------------------------------------------------------------------
  CONSTANTS:
    cc_okchar(59)   TYPE c VALUE ' !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ'.

  DATA:
    lc_okchar1(72)  TYPE c,
    lc_okchar2(59)  TYPE c,
    lc_okchar(131)  TYPE c,
    l_d_offset      LIKE sy-index,
    ls_string       TYPE Z_STRING,
    li_strlen       TYPE i.

* Get the list of allowed characters.
  CALL FUNCTION 'RSKC_ALLOWED_CHAR_GET'
    IMPORTING
      e_allowed_char = lc_okchar1
      e_default_char = lc_okchar2.
  IF sy-subrc IS INITIAL.

*   No error .. set the Ok Char variable
    CONCATENATE lc_okchar1 lc_okchar2 INTO lc_okchar.
    CONDENSE    lc_okchar NO-GAPS.
  ELSE.

*   Error ... Just use the value in the constant.
    lc_okchar = cc_okchar.
  ENDIF.

  ls_string = STR_IN.
  CONDENSE  ls_string.
  TRANSLATE ls_string TO UPPER CASE.

* Remove initial characters that can cause problems: !, #, ?, etc
  IF ls_string(1) = '!'.
    ls_string(1) = ' '.
  ELSEIF ls_string(1) = '#'.
    ls_string(1) = ' '.
  ELSEIF ls_string(1) = '?'.
    ls_string(1) = ' '.
  ENDIF.

* Get the length of the string being processed.
  DESCRIBE FIELD ls_string LENGTH li_strlen IN CHARACTER MODE.

* Process string and remove unwanted characters
  DO li_strlen TIMES.
    l_d_offset = sy-index - 1.
    IF ls_string+l_d_offset(1) CO lc_okchar.

*Character allowed, do nothing
    ELSE.
      ls_string+l_d_offset(1) = ' '.
    ENDIF.
  ENDDO.

  str_out = ls_string.

ENDFUNCTION.

To change source system in BW without impacting objects developed in BW system.

Please check: ECC source systems on SAP BW environment without impacting the Data modeling objects built in the SAP BW system.

There seems to be a big wall between the worlds of BW and "traditional EDW" (whatever it means). Go to the LinkedIn forum of The Data Warehouse Institute (TDWI) and try to open a mouth that you are working with BW - you will be smashed immediately with many comments like "[BW] has always been an ancient, clunky and monstrous solution to implement.", "I'm yet to come across an SAP customer that isn't into their Nth attempt at trying to get it to work properly or efficiently." or "How much did [BW implementation] cost (software, hardware, consulting, etc.), how long did it take and how much frustration did the business users feel while waiting for a solution?
Nice blog available @ Is your BW the Data Warehouse, anyway?
Read & write your comments.