customising the production transport via nwdi (.SCA file issue)

[former_member249412]

hello exports,

i am working on sap nwdi netweaver 7.0 oracle 10g database

our project is now in support phase. we are facing a very big issue in the support activity.

the issue is our client is giving aproval to only some of the activities to b deployed on the production server and the problem is as we get an .SCA file in quality phase of transport via track we are not able to deploy that .SCA file on the production server as it will deploy evrythg in it which we dont want as we dnt have aproval for alll the activities in it

i am not able to understand how shuold i send only the required activities to the production server without lossing my other SCA files.

kindly advice earliest possible issue is on very high priority

Thanx and regards

[former_member128291 · Accepted solution]

Dear Customer,

Kindly note that under the decribed scenario you will have to recreate the SCAs with the approved/tested SDAs and then only can move and deploy the new SCA on your production system.

However, their is a workaround to deploy the approved/tested SDAs on to the PRD system instead of deploying the complete SCA. But this is not recommended because then you will have to decide about the SDA dependencies and their order of deployment. Whereas when deploying a complete SCA its taken care by the system itself.

Regards,

Abhishek

[ErvinSzolke]

Hi,

by that sentence I only wanted to emphasize that one cannot remove something from the cons. If you don't require a given feature (or a dc), then you need to get rid of it in dev and then transport it through the landscape up to cons, so when you assemble again, it won't be part of the product any more.

Best Regards,

Ervin

[ErvinSzolke]

Hi LNT Power Shakti Project Basis User ,

after importing into the CONS it is not really possible.

Assembly means that the whole state of the software from the CONS/active workspace is taken for assemble.

Therefore you cannot filter out which changes should go into the assembly since they already have arrived in the cons system.

If you want to filter out changes that should not go into production then these changes should not be imported into consolidation before, since every change that is imported into cons will be part of the assembled software.

You can also delete DCs in dev and transport them to cons so that they will be deleted before assembly. (such a deletion should be able to activate even if there are predecessor activities to be activated).

Regards,

Ervin

[former_member249412]

hello Ervin

thank u very much for ur knd attention for ths issue.

m abit not clear abt ur last two lines about deleting the DC from dev.... can u elaborate more on same...????

in my currentsenario i have to move all the changes till quality as client will do testing on quality and then he will aprove only thosse changes to be moved to prd server which he wants

ur reply has gvn me sm very good hints will work on it

thanx and regards

Amar

[shreyas_pandya]

Hi LNT Power Shakti Project Basis User,

Please refer to the below mentioned blog to get a clear picture...

:[Source Code Journey (NWDI under the Hood)|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/25521] [original link is broken] [original link is broken] [original link is broken];

Please consider Ervin's input.

You really can't get rid of or separate out the changes (Activities) once you have imported them into Consolidation.

But, There's a way out to achieve what you are looking for as it is already explained by Ervin, I am just elaborating it....

Consider the following scenario.

There are 2 Activities which you created.

Act1 & Act2

Both, were imported into consolidation and Assembly was also triggered...

But, just before moving the generated .SCA file (as a result of Assembly) to your Quality system, you realize that Act1 is not required, and you want to get rid of those changes. Now what..!

So, here you need to understand that the .SCA that you are going to move is not having the required changes.

So what you have to do is, go back to your developer studio and undo the changes that you performed in Act1.

To undo the changes you need to create one new activity, let's call it Act3.

Check-In, Activate, Release and Import the Act3 into Consolidation and then perform the Assembly operation again.

This Time the new .SCA that will be generated is according to your requirement (i.e. without the unwanted changes that were associated to Act1).

I hope the Example will clear your doubts.

Regards,

Shreyas Pandya

[pramod_gopisetty1]

Hi,

Why don't you deploy the DC from NWDS directly?

In NWDS go to Window - Preferences - Enterprise Portal - Configure the runtime system in this case your production system and deploy the required DC's to production.

And when you are ready to move all the activities then move the SCA to Production through NWDI.

When Deploying you can have some dependencies missing which you can deploy when needed.

If it's ESS/MSS related track I would suggest deploy the PCUI_GP SCA to production.

And then deploy the required DC's to Prod through NWDS.

Hope this helps.

Cheers-

Pramod

[former_member249412]

hello

thank u very much for all the reaplies

we are currently doing direct deployments in prd system using.

[junwu]

if you have imported the activity to consolidation, i don't think you have option to customize. you can only deploy all(the imported activity)

Edited by: John Wu on Dec 27, 2011 3:41 PM

[former_member249412]

thank u for ur reply

we have imported the activity notonly to consolidation but also to quality after testing in quality the user want only some actvity to go ahead from the current .SCA patch which is creating problem right now