topic Re: 3rd Party Object Names in Application Development and Automation Discussions

3rd Party Object Names

Former Member — Wed, 11 Feb 2009 22:01:40 GMT

Hello SDN Community, if this is not the right place to post this, please do not hesitate to re-direct it to the proper forum.

When 3rd party companies develop SAP solutions, I assume they have to use the "Z" and "Y" namespaces. That being said, how does company ABC, who created module pool SAPMZMM_MATERIAL_TRACKER, keep from conflicting with company DEF who also has a module pool for their Material program called SAPMZMM_MATERIAL_TRACKER? Or conflicts with report names, screen names, function module names, etc.

I have seen this type of question posted in Delphi shareware forums and the best answer was "nothing to keep it from happening". Although there was an enterprising Delphi person who set up a web-site for shareware developers to post their software names and namespaces so that you could at least look at what was already out there before you started building. It was strictly a voluntary effort and am not sure if it is still supported or not.

Thank you,

Dean Atteberry.

Re: 3rd Party Object Names

mvoros — Wed, 11 Feb 2009 23:24:39 GMT

Hi,

you can use name spaces to prevent this type of conflict. So you will have names like /ABC/FUNCTION_MODULE and /DEF/FUNCTION_MODULE. You can get more information about namespaces in transaction SE03 as well as [SAP documentation|https://help.sap.com/saphelp_nw04s/helpdata/en/57/38dec24eb711d182bf0000e829fbfe/content.htm].

Cheers

Re: 3rd Party Object Names

Former Member — Thu, 12 Feb 2009 13:43:49 GMT

Thank you, Martin. Exactly what I was looking for.

I have seen the /<someName>/<...moreName...> convention when searching for objects in SE38 and SE37 and was never quite sure what that was about. Now I know..... the rest of the story! 8-)

Dean.