import activity no needed

[Former Member]

Hi ,

We recently upgraded our nwdi environment from nw 7.0 sp 12 to sp 15 , and after that we are facing the follwoing problem . we have primary track with all the developments and another 4 tracks with repair connection between them and the source track ,

After releasing an activity from the primary track (named dev-test) we see the activity in the import queue of the target track , but when importing the activity to the new track nothing happens

i have attached the log

Repository-import:

20081231150646 Info :Starting Step Repository-import at 2008-12-31 15:06:46.0103 +2:00 20081231150646 Info :Component:cellcom.co.il/CELLCOM_SC 20081231150646 Info :Version :EST_DEVTST_D.120 20081231150646 Info :1. propagation request is of type TCSChangeRequest 20081231150646 Info :Propagatable:9e4261cfd73211ddb443005056a532cc exists allready in the repository. No import necessary. 20081231150702 Info :Integration of changelist:9e4261cfd73211ddb443005056a532cc succeeded without conflicts. 20081231150702 Info :Step Repository-import ended with result 'success' at 2008-12-31 15:07:02.0915 +2:00

CBS-make:

20081231150702 Info :Starting Step CBS-make at 2008-12-31 15:07:02.0915 +2:00 20081231150702 Info :Propagation request 'cellcom.co.il_CELLCOM_SC.EST_DEVTST_D.120' is backpropagated. Containing activities are not activated during import. The step is not performed for this request. 20081231150702 Info :Step CBS-make ended with result 'not needed' at 2008-12-31 15:07:02.0931 +2:00

SDM-deployment-notification:

20081231150702 Info :Starting Step SDM-deployment-notification at 2008-12-31 15:07:02.0931 +2:00 20081231150702 Info :Step is not executed. No Runtime System defined for this location. 20081231150702 Info :Step SDM-deployment-notification ended with result 'not needed' at 2008-12-31 15:07:02.0931 +2:00

it seems to be that the new activity refereance the source track EST_DEVTST_D.120 ,

is there a way of chanig this

Regards,

Oren

[Former Member]

Oren,

It looks like you use repare connection where you need to do transport connection.

Repare connections aka back transports are designed to allow modifications to be pushed back to the source tracks. More about repare connections here:

http://help.sap.com/saphelp_nw04s/helpdata/en/73/cf61253f4c4536b5047faf6e9e7f71/content.htm

More about Transport connections:

http://help.sap.com/saphelp_nw04s/helpdata/en/13/602b27f6fb41b4a9eb4f72eabb9832/frameset.htm

Thus, changes from dev-test should go to 4 tracks via Transport connection.

After that, if you modified code in any of the 4 tracks, you can push them back to dev-test via Repair connection.

Regards,

Slava

[Former Member]

Hi ,

You are right , but what is the difference , if I create a new software component and assign it to two new tracks and before starting to work I create repair connection between the tracks , it seems to work OK .

From my investigation reapir connection is simmilar to integrare activity to another track ,and then perfrom activation of the activity

Regards,

Oren