Skip to Content
0
Mar 31, 2010 at 06:27 AM

CTS+ usablity in our scenario

113 Views

We had done an evaluation of SAP CTS+ technology for our current SAP Landscape w.r.t. its usability and advantages

After our evaluation, we have found that SAP CTS+ is primarily useful in following two scenarios, where we have development on both stack (ABAP and JAVA) and CTS+ is used to bring synchronization on both developments

SAP NetWeaver Process Integration

Not applicable to us, since we donu2019t have any development on ABAP Stack of PI

SAP NetWeaver Portal

 Not Applicable to us, Since we donu2019t have much development on Portal Front which requires synchronization on back end systems (ECC/CRM/BI)

Also, there are following limitations of SAP CTS+

 No Collision Management

 The order of the transport requests in the queues and the order of objects within the

request defines the import order.

 Objects are imported without any respect to change date etc of already existing

content in the target system.

 No Change Recording

 If applications provides change recording u2013 fine. CTS+ does not change anything in here (up to now).

 You have to use the export tools of the applications.

 No Version Management

 Non-ABAP objects are not connected to the versioning mechanisms of CTS

 If applications provide versioning u2013 fine. CTS+ does not change anything in here

 No Organization of transports

 No control mechanisms that all the content that is needed for a certain change is

included in a transport request.

 No synchronization of transports across tracks - e.g. ECC, EP (up to now).

Let me know if our understanding is correct and what is usablity of CTS+ in our case