Issue related to CTS+ Transports

[Former Member]

Hello,

We have completed CTS+ configuration on PI (EHP1 SAP Netweaver 7.0) following SAP CTS+ How-To-Guide.PI Development is Domain controller and all paths and parameters in SAP Exchange profile are maintained.

Transport request is successfully created from PI with no errors. Also If we create empty Non ABAP transport u2013 with no object included it works fine.

Now we are facing some issue related to release of Non ABAP transports (transport remains in status u201CRelease Startedu201D for hours and no process/file update at OS) and no export file is created in path maintained.

For release started status issue we were able to change the status of same to modifiable after 32 hours from release started status to sort this issue.

But we are unable to release transports successfully with these non-ABAP objects.

Please help.

Thanks & Regards,

Nisha

[TomCenens]

Dear Nisha

Perhaps check the following SAP note:

[Note 1316239 - CTS + PI use case: Automatic release is not possible|https://service.sap.com/sap/support/notes/1316239]

You can search service marketplace notes using keywords "CTS+ release" to find more relevant notes. Lots of fixes exist for CTS+ so I would surely advise to patch your components (if stack is impossible) update to the latest available bug fix patch for your current SP stack version.

Kind regards

Tom

[Former Member]

Thanks for quick reply Tom!

We have performed EHP1 Upgrade few weeks back and below are SP levels - so I don't think any issue related to patch levels:

SAP_ABA 701 0007 SAPKA70107 Cross-Application Component

SAP_BASIS 701 0007 SAPKB70107 SAP Basis Component

PI_BASIS 701 0007 SAPK-70107INPIBASIS Basis Plug-In

ST-PI 2008_1_700 0003 SAPKITLRD3 SAP Solution Tools Plug-In

SAP_BW 701 0007 SAPKW70107 SAP Business Warehouse

ST-A/PI 01M_BCO700 0000 - Servicetools for other App./Netweaver 04

I am trying to check SAP notes as well.

Thanks & Regards,

Nisha

[TomCenens]

Hello Nisha

I'm especially referring to Java bug fix patches. In older maintenance optimizer versions there is no option to include automatically them into the download basket, the current version of maintenance optimizer has the option to also add java patches to the stack download.

Can you check your Java components that they have bug fix patches applied and perhaps also check how many are available on SAP service marketplace

For example 7.0.1.7.0 to 7.0.1.7.6

Kind regards

Tom

[Former Member]

Thanks Tom.

We currently have Version as 7.01 SP7 (1000.7.01.7.0.20100612172118) for Java stack.

Could you please tell us which Java component from XI java stack we need to check for patch levels:

e.g 7.0.1.7.0 to 7.0.1.7.6

Also please note we used Maintenence Optimizer of SAP Solution manager 7.0 EHP1 SP24 for stack generation.

Regards,

Nisha

[TomCenens]

Hello Nisha

Component DI_CMS is normally used by CTS+ to perform the actual deployment so ensure you are on the latest bug fix patch level (not the same as stack level).

The maintenance optimizer in your version should have the add java patches button when you create a new maintenace transaction to apply a support package stack.

Kind regards

Tom

[Former Member]

Dear Tom,

We do not have DI_CMS component on XI system as we have not configured NWDI and we are not using NWDI integration with CTS+ also.

You can also refer 1360910 for further details.

Regards,

Nisha

[TomCenens]

Hello Nisha

Then you will have LM-TOOLS but the updating is important in the SAP systems where you deploy something. Releasing is not the same and will more likely be solved by a SAP note correction or parameter change.

If it's a rather large transport request, a possible problem can be that the PROCTIMEOUT value of the icm/server_port_0 parameter of your abap instance is too low.

Kind regards

Tom

[Former Member]

Dear Nisha,

Did you got any solution to this problem? We are also facing exactly same problem and we have same SP level i.e PI 7.0 EHP1 & SP7.

Any inputs will be very helpful.

Thanks in Advance!

Kind Regards,

Abhijeet.