‎2010 Nov 15 3:23 PM
Hello all,
I was asked to create a function module with the prefix "ZIST_" in its name. Unfortunately this name is part of the SAP namespace, as the system tells me during FM creation (it would be ok to use "Z_IST_" though). Technically it is possible to ignore the error/warning message and create the "ZIST_" function anyway.
My question now is: can this issue have any bad impact, for example during a release upgrade? If not, if it's ok to use "ZIST_" as prefix, why does the SAP system then popup this warning at all?
Thanks in adavance for your help!
Kind regards, Matthias
‎2010 Nov 15 3:33 PM
Well, for function modules SAP sets Y_ and Z_ as customer name space, so why not stick with that. If you check in the repository browser, there are few older SAP function modules starting with Z*. Although I doubt SAP would add any new ones starting with Y or Z, you are on the safe side if you strictly follow the customer name range suggestions.
Thomas
‎2010 Nov 15 3:33 PM
Well, for function modules SAP sets Y_ and Z_ as customer name space, so why not stick with that. If you check in the repository browser, there are few older SAP function modules starting with Z*. Although I doubt SAP would add any new ones starting with Y or Z, you are on the safe side if you strictly follow the customer name range suggestions.
Thomas
‎2010 Nov 16 8:27 AM
Yes, I know, and usually I do stick with the namespace restrictions. But this is a special case now, collegues have alredy created function modules with "ZIST_" as prefix. So the question is: can that have any negative consequences?
Kind regards, Matthias
‎2010 Nov 16 8:38 AM
Theoretically, SAP could introduce function modules starting with ZIST_ in the future.
I'd say the probability is only slightly larger than zero though, and even smaller for an entire duplicate function name collision by any chance. Your server might rather get struck by lightning. And even if it happens, then you are forced to change your names, should not be the end of the world.
But it remains your risk
Thomas
‎2010 Nov 16 8:42 AM