Skip to Content
avatar image
Former Member

NWDI Transport - All DCs get imported even though Activity is for particular DC

Hi,

I have a query which is actually become a reason for ad-hoc activities which we want to avoid every time we transport the activities from Dev-> QA -> Prod. Please help me in identifying the solution for this problem.

We are on PO 7.4 SP11 version and have BPM, BRM and CAF developments using NWDI. Below is the framework:

SLD
|
|-- Software Comp1


NWDI
|
|-- Track1 (Software Comp1)


NWDS
|
|--Track1
	|-- DC1 (BPM)
	|
	|-- DC2 (BRM)
	|
	|-- DC3 (CAF)

Now suppose we do a change in BPM object i.e. DC1 and create a new activity and release that. It goes to CONS and BASIS transports it from there to next servers i.e. our QA and Prod but the problem that we are facing is that not just DC1 activity related change but all the DCs which were not even touched are getting moved and not just activity change. We are facing problem due to this type of behaviour because due to this we have to load our BRM decision tables again and again and also configure rules that were maintained directly in the individual QA and PROD system.

I tried looking and understanding the procedure of transport but could not find the specific reason why does it import all other DCs even though we have not defined any dependencies between the DCs.

I understand that if I create a separate track for BRM then my issue may get resolved but even in that case when we have multiple BRM DCs and we do a change in one DC, other would get affected when we move transport activity.

Is it because they are all inside one Software component ? but I beleive there must be way to handle this kind of scenario also. Request you to help in solving this.

Thanks,

Amit

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    Jun 20, 2017 at 06:35 AM

    Hi Amit,

    You can use CM services in NWDI and configure it to export at activity level, other DC's will not get exported.This is how we are managing transport for BPM's in our landscape.

    Have a look at this document for more details on configuration:

    https://archive.sap.com/documents/docs/DOC-51948

    Regards,

    Sanjeev

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 20, 2017 at 08:29 AM

    Hi Sanjeev,

    Thanks for the link !

    Going through the document of that link, I wanted little more clarity if you can answer please:

    We are already doing our transports through CTS+ but through CMS and our BASIS does that after we release our activity(just one DC of SC) from NWDS. I see that CMS can handle transports only at SCA level (i.e. whole software component transport). Is that the reason that whenever we transport the activity whole Software component gets imported in next environment ?

    Thanks,

    Amit

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 20, 2017 at 09:48 AM

    Sorry Amit, I have never used CMS so can't really confirm that. But from limited understanding, that could be the reason. Let's see if someone else has can confirm/deny it.

    However, I would recommend trying to set-up CM services in parallel and trying out activity based transports. And as far as I understand you can have both CMS and CM services running in parallel.

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 22, 2017 at 02:47 AM

    the whole sc is packed as a sca file. but it won't overwrite your target server dc if it got no change. check your cts+ setting regarding deployment.

    the normal deployment strategy is DC which is contained in the sca and has higher version than your target server's will get deployed.

    Add comment
    10|10000 characters needed characters exceeded