Skip to Content
avatar image
Former Member

Issue & Concerns with NWDI Transports (Project transports & Bug Fixes)

Dear All,

We need some urgent help.

We are on JDI 7 SP12 on HPUX 11.23. We have an issue with

NWDI track.

We were having a 4 systems SAP CRM landscape. CRM Dev(CRMD), CRM IST (CRMI), CRM Q (CRMQ) & CRM P (CRMP).

We have the JDI instance connected to the CRM system

and all the 4 systems were configured as the run time systems in the JDI. In the track which we are using,in the Runtime systems tab, the Development system points to the CRD instace, the Consolidation system points to the CRI box, the test system points to the CRQ box and the production system points to the CRP box.

Now we have added a new tier for the User Acceptance testing called CRU there by coming into 5 system landscape CRD,CRI,CRU,CRQ,CRP). We now need to add this system in the JDI instance in the same

track and configure it in the runtime system tab and link it to the CRU box. We have planned to define a new track and do the track connection between them.

But, we have an issue with the transports. We have 2 Developers who release a request from NWDS. The request comes in the consolidation queue and then I individually assemble them (in this way the request gets applied to CRD & CRI) one by one to the test queue. Now, we have these 2 requests(with 3 components each, SAP-SHRAPP, SAP-SHRWEB, SAP-CUSTCRM in our case-so total 6 components) in the test queue. But when I start importing one component,say, SAP-SHRAPP component, of the first request, the other request becomes outdated and all the changes are combined into this one SHRAPP request.Similarly when I start importing the SAP-SHRWEB component of the first request, the other becomes outdated. But here the 2nd developer does not want his request to go to test system and further, but the 1st developer wants to the request to P system.

We have developers who work for production system and other who work for the project work. We at the present moment have a reqmt where in only the bug fixes need to go to the P system and not the new developement and both of them are right now in the test queue. We have only one track and are in the process of configuring the 2nd track to add the 5th CRM system.

Can you please let us know what to do to avoid

this situation. Its critical to us. Thanks a lot in advance.

Warm Regards,


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Apr 14, 2008 at 05:12 PM


    You can define two tracks - one for production support and the other for project work. You can send all changes from your production support to your project track using track connections in the landscape configurator. It's similar to dual maintenance in ABAP world during upgrades etc.


    Add comment
    10|10000 characters needed characters exceeded