Use of ChaRM with 3rd party vendor supplied transports?
Can you use ChaRM with 3rd party vendor supplied transports? The only thing we can think of to allow this is to (1) import the vendor supplied transports into DEV and then (2) create a 'transport of copies' DEV sourced transport containing all of the objects in the 3rd party vendor transport for migration to QA and PRD using ChaRM. Does anyone have any recommendations or best practice approaches? We do not use that many SAP-certified 3rd party vendors but do want to monitor and provide audit trail on 3rd party vendor transports just like we do for our internal developments.
this feature (real integration of 3rd party transports) is currently not available for ChaRM (or QGM.)
However, this is something we have heard from a lot of customers already. Mostly because of warranty issues (Example: Add-on is delivered from a 3rd party vendor, they only give you warranty if you take the delivered transports and move them through the landscape - any kind of reassign/change/integration will not be allowed).
Therefore we are currently improving this functionality and providing new features to support this use case, as described above. More details about this will be published at the SAP TechEd this year.