SAP Note

Header Data

Symptom

SAP customers (for example, central corporate group development) and partners wish to deliver their developments to third parties (for example, corporate groups to subsidiaries, complementary software partners to SAP customers). When importing the developments, a name clash occurs between imported objects and objects available locally in the system.

Other Terms

namespace, name range, naming convention, reservation V_TRNSPACE, V_TRESN, RESP

Reason and Prerequisites

Traditionally there are two name ranges in the development workbench of the SAP R/3 System: The SAP name range is reserved for development at SAP, whereas the customer name range (Y* and Z*, see Note 16466) is available to all customers for your own customer developments. In principle, you must distinguish between the following cases in which naming conflicts can occur:

1. Distributed development in a system group An SAP customer or partner develops various projects in several development systems which are transported into a common consolidation system and forwarded into a common production system. Naming conflicts in the consolidation system should be avoided.

2. Delivery of developments An SAP customer or partner develops extensions for standard SAP R/3 System applications and delivers them to third parties who potentially carry out their own developments. If the vendor and the person being supplied work in the customer name range, naming conflicts must be expected. These naming conflicts should be avoided when installing (importing) extensions.

Solution

Naming conflicts can be avoided either by agreeing on naming conventions or by developments in separate namespaces.

1. Distributed development in a SAP system group In a transport system group which includes several development systems, naming conflicts can be avoided by complying with naming conventions. To do this, you must define a standard generic naming convention (that is, determine the beginning of the object name) for all objects of a development class. If you store this specification in all development systems (entry via extended table maintenance in table V_TRESN, see online documentation on the workbench organizer), the development workbench prevents use of the convention by other projects, that is, assignment to other development classes is refused.

2. Delivery of developments The declaration of naming conventions is not possible for the delivery of developments to third parties since in general it cannot be determined in advance who will be supplied once with the developments, and which local development projects will be available in the systems to be supplied. In this case, development in a separate namespace reserved exclusively for an SAP customer or partner is therefore the correct solution.

Requirements for Name space assignment

To reserve development name spaces, the following requirements must be fulfilled:

l ABAP/4 Development Workbench License An ABAP/4 Development Workbench License must be available under the submitted customer number, which authorizes you to perform your own developments.

l Name assignment in the namespace Only name spaces are assigned that have a clear reference to a customer name or to a product of the partner.

84282 - Development namespaces for customers and partners

Version 23 Validity: 06/11/2001 - active Language English

Released On 06/11/2001 Release Status Released for Customer Component BC-CTS-ORG Workbench/Customizing Organizer

XX-SER-DNSP Development Namespaces for Customers and Partners

Priority Recommendations / Additional Info Category Consulting

Other Components

l Number of reservations Since the pool is limited to the development namespaces, namespaces are only assigned individually and not generically. If necessary, you can assign several namespaces per group or development partner (see below).

l Returning the signed namespace agreement If a namespace contract was checked and accepted by SAP, the applicant will be sent a namespace agreement, which regulates the legal aspects. The namespace is not actually reserved until the signed namespace agreement is received by SAP. If the contract is not received by SAP within one month's period, an already accepted namespace will later be rejected. If the namespace was requested via the SAP Service Marketplace and accepted by SAP, a namespace agreement is not delivered. The applicant himself can accept the namespace agreement online in the SAP Service Marketplace and finally reserve the namespace with this acceptance. If he does not accept electronically within one month, the namespace already accepted is rejected later.

Reserving a namespace

One namespace per company is sufficient to organize and deliver the development of individual SAP-R/3 based extensions, components and products since developments in one namespace can be structured in subprojects by assignment to development classes. By defining and storing naming conventions for each development class (extended table maintenance of table V_TRESN) naming conflicts can be avoided even in the case of a development distributed over various locations (automatic monitoring of naming conventions in the Development Workbench). It is only possible to assign additional namespaces for developments which

l are carried out at several locations which are organized independently and separated geographically within one group, between which a declaration of naming conventions is impossible

l and which are at the same time aimed for delivery to independent third parties (production locations, subsidiaries and so on).

Due to the restricted pool of possible namespaces we cannot carry out generic reservations of namespace names (as for example /COMPANY*/) which would always block a wider namespace than actually required. Furthermore we do not assign namespaces for potential applications at a later date. The reservation of a namespace is free, that means you do not need to pay initial costs or current costs to SAP. You can reserver a namespace in both the SAPNet R/3 Frontend and in the Service Marketplace. In the Service Marketplace, you can find the functionality and documentation under http://service.sap.com/namespaces. In the SAPNet Frontend you can find the functionality under SAPNet ->Registration ->Namespaces->Namespace create You do need the access right 'NAMESPACE' to carry out the reservation (See Note 105132 for exact procedure). The following inputs are necessary:

l Specify the desired namespace name You can freely choose names for namespaces from the pool of names not yet reserved. The names should have a recognizable reference to the reserving company. The names should be selected with a minimum of five and maximum of ten digits. The first and last character is a slash "/". Thus a maximum of eight characters are available for each namespace. Letters and numbers are allowed. Namespaces starting with a number or the character strings 'SAP' or 'R3' are not available. Only individual names are assigned. Possible names are: "/CUST/", "/SYSHOUSE/", etc.

l Specify the intended purpose (for example name of the planned component or the product)

l Select the installations for the namespace development Note that you can only enter the authorization for which you have the SSCR (SOURCE) authorization. With the function "Namespace change" you can specify additional installation numbers at a later date for which a query of the development license should be allowed. If you require the namespace for developments in systems other than the installations assigned to your customer number, you can also enter the corresponding customer or installation numbers for which a development license is required.

The state of the namespace assignment can be seen in the SAPNet R/3 Frontend.

Releasing a namespace

The use of namespaces is protected by a license check in the R/3 System. When reserving a namespace, you receive the authorization to retrieve the namespace license key for the installations of your customer number at SAP. (For the installations of additional customer numbers assigned to you by the organization, namespace license keys can also be collected at SAP if you enter these customer numbers when reserving the namespace.) Using these license keys, you can then release the use of object names in your namespace. You obtain namespace license keys for namespaces already reserved via function "Register namespace" where you must specify the desired installation number The release of the development in the namespace you reserved uses the entry of the namespace and the license key in the namespace table in your development system (via Workbench Organizer Tools (Transaction SE03), category "Administration", function "Display/change namespaces". For this you need administration authorization in the Workbench Organizer (S_CTS_ADMIN). You can find further information on maintaining namespaces in the online documentation on the workbench organizer.

Development in a namespace

Assigning objects to a namespace is carried out by placing the reserved namespace name in between slashes before every object name as a prefix. Example: You reserved the namespace 'ABCDE'. The namespace prefix you used in the

development workbench is then called '/ABCDE/'. A program created by you in this namespace is then called '/ABCDE/PROGRAMM', for example. To be able to make changes to objects in your namespace, you must set the namespace to changeable (Transaction SE06, function system changeability). Objects in your namespace can be assigned to either local ($*) or test development classes (T*) or they must belong to development classes which start with the same namespace prefix. You can find a list of the supported object types in the online documentation on the workbench organizer. When you create extended table maintenance the use of function groups with a namespace prefix is only possible as of Release 4.0B (see Note 99143). If you have carried out customer development in the Development Workbench in Release 3.0/3.1, also see Note 89898.

Partner name ranges in Releases 2.X and 3.X

Partner name ranges reserved in earlier releases and used for additional developments (in accordance with Notes 39524 and 38781) can continue to be used unchanged in Release 4.0. Only the storage of the project number has changed: Regarding two-digit project ID nx (n = number, x = letter), the RESP/RESPT entries were transferred into the namespace table V_TRNSPACE (display and maintenance using extended table maintenance) as logical namespaces /0SJnx/ and are only maintainable using the namespace table. Tables RESP and RESPT no longer function.

Validity

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (20)

Software Component From Rel. To Rel. And Subsequent

SAP_APPL 40A 40B

45A 45B

46A 46B

46C 46C

SAP_BASIS 46D 46D

610 640

700 700

710 710

1293588 KJCPH: Important Note for EKPM add-on on ERP 6.0 850592 TO140: Customer object assignment for package not possible 846500 Reassigning namespaces 757234 Namespace/development license/corporate functions 710315 New prefix namespace for SAP NetWeaver 401778 Using namespaces to develop individual BW objects 395083 FAQ: Namespace for authorizations and auth. objects, fields, and profiles 171831 ESS 2.0x: J_2WUSR1 creates multiple auth. profiles 150451 Setting up development namespaces 141969 ESS: J_2W_PASSWORD_CHANGE '+' in USR40 patterns 136781 ESS 2.0A: Problems when creating ESS users in 4.0B 122307 ESS: Function module HR_GET_QUOTA_DATA for 4.0B 105132 Reserving namespaces 104010 Restrictions for development in namespaces

99143 Use of development namespace in SE54 89898 Extending namespace in 4.0: Effects 39524 Development in the partner namespace: Preconditions 38781 Partner name space SAP objects 16466 Customer name range for SAP objects

136781 ESS 2.0A: Problems when creating ESS users in 4.0B 141969 ESS: J_2W_PASSWORD_CHANGE '+' in USR40 patterns 171831 ESS 2.0x: J_2WUSR1 creates multiple auth. profiles 710315 New prefix namespace for SAP NetWeaver 757234 Namespace/development license/corporate functions 1293588 KJCPH: Important Note for EKPM add-on on ERP 6.0 846500 Reassigning namespaces 850592 TO140: Customer object assignment for package not possible 1903323 SU21: Navigation errors and namespace 401778 Using namespaces to develop individual BW objects

39524 Development in the partner namespace: Preconditions 38781 Partner name space SAP objects 16466 Customer name range for SAP objects 105132 Reserving namespaces 104010 Restrictions for development in namespaces 150451 Setting up development namespaces 395083 FAQ: Namespace for authorizations and auth. objects, fields, and profiles 99143 Use of development namespace in SE54 89898 Extending namespace in 4.0: Effects 122307 ESS: Function module HR_GET_QUOTA_DATA for 4.0B