As I know, CTS+ allows ABAP change management to steward non-ABAP objects. With ABAP changes, if you have an issue in QA, you simply create a new Transport and correct the issue, eventually moving both transports to Production (assuming no use of ToC).
We use ChaRM with CTS+ extensively to transport .SCA files created from NWDI. Some .SCA files can be very large: +300MB. Therefore, if we have an issue with a Java WDP application in QA, I assume we are supposed is to create a second Transport, attach a new .SCA file, and move it to QA. Eventually, this means moving both Transports (same ChaRM Document) to Production, each one having 300 MB files. Is this SAP's best practice, since all Transports should go to Production? We've seen some issues with Production not being to happy with deploying two 300MB files in a row. What about the fact that .SCA files from the same NWDI track are cumulative, so I truly only need the newest one. Any advice?
FYI - SAP said this was a consulting question and therefore could not address this in my OSS incident.
Thanks,
David