query

[Former Member]

what is customer namespace?

[Former Member]

hi,

namespace is name convertion which used for separating different programs, for example, customer namespace (used by developer or users ) and partner namespace (used by a specific partner ) or sap standard namespace.

if you create a program with name begins with Y or Z, it's said that you are wring code under customer namespace, note that as a developer, only you can program under customer namespace. and more, when upgrading, program under customer namespace is not support by authority.

[Former Member]

hi,

In simple words, We can create programs only using the starting alpahabet 'X' and 'Y'.

this is called customer name space.

Rgds

Reshma

[Former Member]

Namespace is used to identify your objects.SAP has reserved name ranges for customer objects and SAP objects. Use these customer

name ranges to make sure that your objects are not overwritten by SAP objects during the import of corrections or an upgrade.

Also see these

http://help.sap.com/saphelp_nw04/helpdata/en/53/ec2c37b995184890c6d8ba5b668a86/frameset.htm

http://help.sap.com/search/highlightContent.jsp

This doc gives the naming conventions in sap

uniquely.http://www.sapfriends.com/HelpSAP/BC%20-%20Namespaces%20and%20Naming%20Conventions.pdf

Hope this is helpful

[Former Member]

Hi Soumya,

The namespace concept describes how customers and partners have to name their development objects to avoid overlapping when SAP software is upgraded.

Customers and partners can create their own development objects, for example, to implement a new BAPI or to modify an existing BAPI.

In R/3 Release 3.1, the namespaces Y* and Z* were provided for customers, and the namespace J_<number> was reserved for partners.

In R/3 Release 4.0, a new namespace concept was introduced which, together with the longer development object names, made it easier to assign names to objects developed by customers and partners.

The Business Object Repository (BOR) introduced before R/3 Release 4.0 still uses the old namespace concept. For this reason, the limitations of the old namespace concept still apply to the namespaces for BAPI development objects.

If a customer or partner creates a new object type that is not a sub-type of another object type, the naming convention for this object type applies to all the sub-objects. In principle, therefore, SAP object types cannot overlap with each other, regardless of the names of the methods, attributes and so on.

Sub-object types split the namespace for methods, attributes and so on with the superordinate object type. You must follow the naming conventions for the sub-objects too.

Thanks,

Vinay

[Former Member]

thank u

[Former Member]

thank u