‎2010 Jul 07 5:57 PM
Hi ABAP experts,
Have you ever come across ABAP custom objects with "/" names, such as /BPPwhatever
I'm wondering if developers can use such names for custom objects instead og "usual" Z_ or Y_
Thanks,
‎2010 Jul 08 2:43 AM
This is a namespace.
Developer organisations (SAP, customers, Partners, ISVs, etc.) can register their own namespace with SAP.
Then they can create their own objects inside this namespace without worrying about nameing conflict with others.
E.g IBM might register the namespace "IBM". Then they can create objects such as /IBM/PROGRAM1, /IBM/DBTAB1, etc.
If they created objects in the "customer namespace" (i.e. starting with "Z" or "Y") someone else could create an object of the same name in another development system and when the two development streams were consolidated there would be a conflict. Namespaces prevent this from happening.
Cheers
Graham Robbo
‎2010 Jul 07 6:17 PM
Perhaps start here with 3rd party namespace:
[http://help.sap.com/saphelp_nw04/helpdata/en/8c/50ba4bcb6e4d7f93aee02c21e8de55/frameset.htm]
‎2010 Jul 07 6:26 PM
Custom objects should starts with Y or Z. In BW, when you create cubes/info objects, at the backend tables/view are created automatically and they starts with /BI0..etc...
‎2010 Jul 07 6:29 PM
we can create custom ABAP object starting with Z or Y only. As per my knowledge the objects which started with '/' are the objects generated by sap. Otherwise these objects will generate by executing some sap standard programs. For example when you are creating smartforms system will automatically create a function module which starts with / but we cant edit this function module manually.
‎2010 Jul 08 2:43 AM
This is a namespace.
Developer organisations (SAP, customers, Partners, ISVs, etc.) can register their own namespace with SAP.
Then they can create their own objects inside this namespace without worrying about nameing conflict with others.
E.g IBM might register the namespace "IBM". Then they can create objects such as /IBM/PROGRAM1, /IBM/DBTAB1, etc.
If they created objects in the "customer namespace" (i.e. starting with "Z" or "Y") someone else could create an object of the same name in another development system and when the two development streams were consolidated there would be a conflict. Namespaces prevent this from happening.
Cheers
Graham Robbo
‎2010 Jul 08 9:36 AM
Graham & All,
Thanks a lot for your very useful and helpful answers!