No maintanance of a tables technical settings possible with a namespace ?

[Former Member]

Dear specialists,

we use an own SAP-namespace for our developments. The namespace itself is not delivered/installed to/at our customers systems because they are not supposed to do changes to our development. Not having this namespace in the system unfortunetaly also seems to prevent that the customers can change the technical settings of an ABAP dictionary table (transaction SE13).

We would actually like our customers to be able to maintain those settings. Can we grant them the right to do so without giving them the namespace keys?

Thanks in advance

Andreas

[Former Member]

Hello Andreas,

normally the namespaces should be transported into the customer systems. With the import, the role of the namespace is automatically changed from P (producer) to C (receipient).

When the namespace has been imported, you have to add the repair licence key (one of the keys you got from SAP), in the customer system, to be able to make repairs.

You can also have a look here:

http://help.sap.com/saphelp_40b/helpdata/en/57/38dedc4eb711d182bf0000e829fbfe/content.htm

Best regards

Stephan

[Former Member]

Dear Stephan,

thanks a lot for your input.

I haven't set the question to "answered" yet because my problem actually isn't quite solved yet. It may very well be possible that it cannot be solved and that your answer is actually the best I can expect to get. In case it turns out to be so, please be assured to get the rest of the available contribution points.

To be a bit more precise about what we're up to:

We want to offer our customers a data change history functionality based on the database protocol functionality which needs to be activated in the technical settings of a DDIC table, but we don't want to dictate them the tables that are supposed to be logged by the database. We would rather leave up this decision to our customers, without giving them the allowance to do any other changes.

I've beeen setting up one of our test systems with our namespace in Recipient role. Without the repair key I have no access to the technical settings, but with it I can do any other change to our development, too.

Do you see a way to solve this up ?

Thanks

Andreas

[Former Member]

Hello Andreas,

having a look at the error message, I would say that it is impossible w/o the repair key.

Message no. TO 127
Diagnosis
You cannot edit the object TABL /XXXX/XXXX. This may be due to the following reasons:
The corresponding namespace /XXXX/ is not entered in the namespace table with a valid change license.
In the namespace table there is no entry with a valid change license that matches the template /XXXX/.
System Response
The function terminates.
Procedure
Check the name of the object TABL /XXXX/XXXX. If necessary, choose another object name.
Otherwise, let the system administrator check the change licenses of the namespaces in your SAP System.
Maintain the namespaces in the Tools of the Transport Organizer under Administration -> Display/Change Namespaces.
You need to check and correct the entries that match the template /XXXX/.
You need to distinguish between the following cases:
The namespace is /0SAP/:
Make sure that the namespace role is C (recipient) and the flags SSCR popup and SAP standard are activated. The license fields remain empty.
You did not create the namespace yourself. Instead, the namespace owner is SAP or another software vendor.
Make sure that the namespace role is C (recipient). The field Repair license must either contain the valid license, or the flag SSCR popup must be activated. Contact the namespace owner and ask what you should now do, and what the valid repair license is.
You are the namespace owner:
Proceed according to the documentation on applying for and setting up namespaces. If the namespace role is P (producer) then you need a valid development license. For information on this, see the R/3 Library under BC - Basis Components -> Change and Transport System -> BC - Namespaces and Naming Conventions -> Reservation of Namespaces).

The only idea from my side, w/o delivering the repair key to the customer would be to create an individual transport for each customer with the specific table settings, made in your system, for the customer.

Best regards

Stephan

[Former Member]

Dear Stephan,

once again - thanks a lot for your help !

best regards

Andreas

P.S.: Full points for your contribution !