Question On Release Transfer - Urgent.

[Former Member]

Hi,

We have a NameSpace "XXX" created under the SWC "YYY". We need to move NameSpace and everything underneath to a different SWC AAA.

I know I can do a "Release Transfer" to copy NameSpace XXX to the SWC "AAA". After the namespace is copied, can I delete the source NameSpace from "YYY" SWC??

If not what would be the other alternative for moving the namespace??

Thanks.

[Former Member]

Balu,

frist thing todo Relese transfer you need to have rights to do that.

After the namespace is copied, can I delete the source NameSpace from "YYY" SWC??

>> you can delete the namesapce only if you have tranfered sucessfully otherwise you will lose the data.

Regards

Sreeram.G.Reddy

[Former Member]

HI,

With above answers see below

This was i explained briefly above but clearly below..

Double click on SWCV which you want to transfer objects from one namespace to another.

Goto -- Tools-- Release Transfer . click , you will get the following ..

Use the "Release Transfer" function to transfer objects from one software component version (SWCV) to another to complete development of one version (of a release) and to begin development of a new version. Corrections that need to be made in both versions, can, for example, be made in the source SWCV and then transferred to the target SWCV. This means that changes only need to be made once and any conflicts are automatically identified. No new object versions are created during the release transfer. Instead, the current versions of the source SWCV are transferred to the target SWCV. This has the following consequences for repeated release transfers:

a) 

Objects that were only developed further in the source SWCV are transferred to the target SWCV.

b) 

Objects that were only developed further in the target SWCV are not overwritten. The release transfer does not affect these objects.

c) 

Conflicts occur if objects were developed further in both SWCVs. These conflicts must be resolved after the release transfer.

click on continue..

select the source SWCV ,and target SWCv

click on continue..

Select the option ..

- All object under SWCv

- All objects under namespace

- Individual objects..

Continue / Finish

Sure you will get..

Regards

Chilla..

Points rewarded if it is helpful..

[Former Member]

Hi,

Select the namespace under your SWCV. Go to Tools->Release Transfer.

It will transfer all the objects under this namespace to the specified SWCV.

For reference plese see the following documents:

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm</a>

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/e8/e8573ba5f13048be50532fc3fcea9c/content.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/e8/e8573ba5f13048be50532fc3fcea9c/content.htm</a>

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/18/23078bdbd241f08efb3e36cf10c9d0/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/18/23078bdbd241f08efb3e36cf10c9d0/frameset.htm</a>

Or else you can select individual objects under the namespace and right click on the object and select Copy Object. You will get a dialog box where you can select the new location where you want to copy this object.

Regards,

Subhasha Ranjan

[Former Member]

HI,

I hope , we may have several ways to do it,

-- You can do it through Release,transfer method

-- You can do it export the namespace and import it later.

-- Copy Object , you would have to do it one object or super object.

-- Use CMS , but not sure..

Regards

Chilla..

<i>Points rewarded if it is helpful..</i>

[Former Member]

Hi Balu,

By using release transfer function, you can transfer design objects within an Integration Repository to other software component versions as follows:

• From a current software component version to the subsequent version, once development in the current version is finished

• From a software component version to an older version of the same software component, for example to make a correction available in an older version.

• From a software component version to a version of another software component. For example, this may be necessary because you may want to stop objects of software components that are based on each other from being available in the sub-software component, and only make them available in the superior software component.

For More

http://help.sap.com/saphelp_nw04/helpdata/en/e8/e8573ba5f13048be50532fc3fcea9c/content.htm

Regards,

Ramesh.