Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Namespace

Former Member
0 Likes
3,070

Hi experts,

Can anyone plz tell me abot the concept of namespace? I am totally new to this term.

I will reward all the helpful answers.

Thanks,

Ajay.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
2,141

hi

To avoid naming conflicts.

Name space is there to differentiate between SAP standard ones and the ones developed by us.

'Z' and 'Y' are the name spaces allocates for objects created by us.

where as A TO X for SAP STANDARD.

for lock objects alone name space gain differs,

'EZ' / 'EY' for us

Chk this also

http://help.sap.com/saphelp_erp2005/helpdata/en/57/38dee94eb711d182bf0000e829fbfe/frameset.htm

rgds

Arun

4 REPLIES 4
Read only

Former Member
0 Likes
2,141

Hi Ajay,

As soon as you have reserved the namespace at SAP and obtained the namespace license key for your SAP Systems you can enter the namespace. When you do this, the validity of the license is checked.

Prerequisites

Use the maintenance view V_TRNSPACE to maintain the namespaces. To do this, you need the authorization S_CTS_ADMIN.

Procedure

To maintain the namespaces, proceed as follows:

Go to the Transport Organizer (transaction SE09).

Choose Goto ® Transport Organizer tools.

Go to Administration and choose Display/Change Namespaces.

The screen Display View "Repository Namespaces": Overview appears. Only those namespaces relevant to you appear in this maintenance view.

To maintain the namespaces, choose Table view ® Display ® Change.

Confirm the information box.

To enter new namespaces, choose New entries.

Detail maintenance appears.

Fill out the fields as follows. Save your entries each time.

Namespace

Enter the namespace ID that you have reserved. It begins and ends with a slash ("/") and has a maximum length of 10 characters.

Namespace role

Keep the default "P" if you want to develop in this namespace. The role of the namespace can have one of two values:

"P" (producer)

Originals are created when you create objects. Choose this setting in the development system of the namespace owner to enable development work if there is a valid development license key.

"C" (recipient)

Choose this setting if the namespace (namespace entry and the objects in the namespace) have been imported into this system. You can use the functions installed with the import. You cannot develop in this namespace in the SAP System. You can make repairs if you have a valid repair license key . When you create objects, the original system is set to "SAP".

Develop.license

Enter the 20-character development license key given to you by SAP for your development system. You cannot transfer development license keys to other SAP Systems. Instead you need a new key for each installation number.

Repair license

If you enter the 20-character repair license key given to you by SAP for your namespace in your development system, then it is imported into all subsequent systems, unlike the development license key.

In subsequent systems you can allow repairs by setting the namespace role to "C".

Repair license keys are not installation-specific. The namespace owner can deliver the keys or pass them on for solving errors if there are any serious problems.

If you do not want your repair license key to be delivered to a third-party, delete the repair license key before the delivery export.

SSCR popup

This flag is only relevant to SAP namespaces (repairs require an object license key). You cannot set this flag in a customer system.

SAP standard

This flag is only relevant to SAP namespaces (standard SAP applications handle objects in a standard SAP namespace differently to other namespaces). You cannot set this flag in a customer system.

Only gen. objs

This flag is only relevant to SAP namespaces (namespace reserved for applications that generate objects). You cannot set this flag in a customer system.

Last changed by

You cannot fill out this field yourself. It is automatically filled with the name of the user who is making the license entry.

Date

You cannot fill out this field yourself. It is automatically filled with date on which the namespace is entered.

Short text

Enter a short text for the namespace. You can include the following information:

Purpose of the namespace

the product developed on the basis of SAP applications

the SAP components developed in this namespace

Owner

Enter the namespace owner registered by SAP.

Result

Your changes are recorded in a change request. When you transport this request into all subsequent systems, the namespace will also be transported. If there is a repair license, this is also transported. However, the development license is not transported.

If useful give reward.

Regards,

Narasimha

Read only

Former Member
0 Likes
2,142

hi

To avoid naming conflicts.

Name space is there to differentiate between SAP standard ones and the ones developed by us.

'Z' and 'Y' are the name spaces allocates for objects created by us.

where as A TO X for SAP STANDARD.

for lock objects alone name space gain differs,

'EZ' / 'EY' for us

Chk this also

http://help.sap.com/saphelp_erp2005/helpdata/en/57/38dee94eb711d182bf0000e829fbfe/frameset.htm

rgds

Arun

Read only

Former Member
0 Likes
2,141

hi

good

check this link

http://abap.wikiprog.com/wiki/Template:Ph:Namespace

thanks

mrutyun^