Hi Roy,
the procedure is described in SAP Note 150451 - Setting up development namespaces.
Excerpts:
Solution
Preconditions for the mainenance of a namespace:
You require the appropriate development license key for the namespace and for the installation number.You can obtain the namespace license key in the Online Service System via the function REGISTER NAMESPACE (path:R/3 Service, Registration, Namespaces) (see Note 105132).
Procedure to eliminate the described symptoms:
1. Go to the Workbench Organizer: Tools (SE03), and select the category "Administration" (only visible with CTS administration authorization), and start the function "Display/change namespaces".Select the 'New entries' function afterwards, and enter the namespace /XYZ/ with the necessary attributes.
Go to the Workbench Organizer: Tools (SE03), and select the category "Administration" (only visible with CTS administration authorization), and start the function "Display/change namespaces".Change to the detail display by double-clicking on the entry /XYZ/, and enter a valid development license key.
If namespace /XYZ/ is really a foreign namespace, you may only repair it. Do not change the namespace entry in that case.If namespace /XYZ/ is your own namespace which was reserved for your project, go to the namespace maintenance, change to the detail display by double-clicking on the entry /XYZ/, and change the namespace role from "C" to "P". You can only save this change if you have entered a valid development license key.
As of Release 4.6A: You must ensure that the software components assigned to the objects are set to 'Modifiable' (not only 'Restricted modifiability'). You can check ot if necessary change this via setting the system change option (go to Workbench Organizer Tools (SE03), category "Administration", function 'Set system change option).
The following attributes must be maintained in the namespace table when you enter a namespace:
Namespace role
In a system in which you want to make developments in this namespace, the role must be P (producer) and at the same time a valid development license key must be entered.The role C (recipient) should be entered in all other systems so that repairs in the namespace are only possible there.(You can make these settings by first entering the namespace in the development with role C and then exporting the change request in order to supply all follow-up systems with this configuration.Afterwards you can change the role to P in the development system without releasing the newly created change request and start with the development.)
Development license
The field is only ready for input with role P.You can obtain the development license via the function "Register namespace" in the Online Service System.It is installation-dependent and can therefore not be transferred to other systems.
Repair license
For namespaces delivered by SAP, the SSCR flag is set and the object license is requested when you make changes. You can obtain the license from the Online Service System ("Register objects").The repair license is not required in this case.For developments of SAP customers and partners in reserved namespaces the repair license which is valid independent of the installation is required for the own namespace to make repairs at the customer/branches possible either generally (through delivery of the repair license) or on request (transmission of repair license in the case of problems).
SSCR dialog box
This indicator should not be set for customer and partner namespaces.
If the SSCRFLAG is set, the object license key is queried during the repair of objects of an installed namespace (role recipient).The use of this attribute only makes sense for SAP namespaces for which the object license key can be obtained via the SAP service systems.Other owners of namespaces can make repairs possible via the delivery of a repair license.
SAP standard
This indicator should not be set for customer and partner namespaces.
This namespace attribute characterizes a namespace as belonging to the standard SAP.
Only gen. objects
This indicator should not be set for customers and partner namespaces.
Namespaces which are provided with this indicator can only be used for generations, not for developments.
Source code corrections
Kind regards,
Clemens
Bluesky
