Global Update Rule/Allowed Characters

Question: Since a recent addition of Brazil to our R/3 system we are finding that the characters "##" are coming across in data from R/3 (text fields, Descriptions, etc.). The data is getting rejected during the BW extraction process because "##" are not "Allowed Characters" (transaction RSKC) in BW.

What we have done for the interim is create update rules for the affected extractors to change the "##" to "space space". What we would like to do is create a global update rule that applies to all data coming from R/3. Anybody have any ideas on how we can do this?

Another option would be to find a user-exit in the BW routine that checks the "allowed character" in table RSALLOWEDCHAR. When we find a character is not allowed, we could do a substitution. I haven't found such an exit. Any ideas?



Regards,

mfwstchas

Answer:
start routine in transfer rules?

Answer:
You can define a conversion routine (like ALPHA) and apply it where you need. Only problem is when you already need an existing conversion routine
_________________
When my car stops, I first look at the gasoline's level before dismounting the engine.


Tuly Idiot's fan club active member.
Copyright ?2007 - 2008 www.jt77.com