ADT for VS Code — cannot save modified class in ChaRM-controlled system

[#1]

Hey!

Environment:

• VS Code: 1.139.0
• ABAP Development Tools for VS Code (SAPSE.adt-vscode): 1.1.2
• SAP backend release: 7.5.8
• Transport managed via Change Request Management (ChaRM / Solution Manager)

Problem:
I'm trying to save changes to an existing ABAP class (opened and edited directly in ADT for VS Code) in our DEV system. An open transport containing two other objects exists. The save fails with:

Failed to save '<classname>.clas.abap': Unable to write file '<repository path>' (Error: The file <object> could not be written: Object not assigned to a transport).

Screenshot attached.

The same save works without issue when performed through ADT for Eclipse on the same object/system — the ChaRM transport-assignment dialog appears offering the existing transport there as expected.

Question:
Has anyone found a way to save a modification to an existing classic ABAP object (not object creation) in a Change Request Management (ChaRM/Solution-Manager)-controlled system directly from ADT for VS Code — e.g. explicitly assigning it to an already-open transport request?

Any pointers appreciated — happy to provide more details if useful.

Thanks!

Regards,
Vlad

[anupkumarbharti · Accepted solution]

Hi @Vlad_Ghitulescu #Currently, ADT for VS Code does not support the transport-assignment workflow that is available in ADT for Eclipse, particularly in ChaRM-controlled landscapes. When you modify an existing transportable ABAP object that is not yet assigned to a transport, saving fails with "Object not assigned to a transport"

May be try a Quick workaround is to assign the object to a transport using:  

• ADT for Eclipse, or
• SAP GUI (SE80/SE24/SE38, depending on the object type), or
• another transport management tool available in your landscape,

and then continue editing in VS Code. and see if that works for you

[Vlad_Ghitulescu · Accepted solution]

Hi, @anupkumarbharti

and many thanks for the reply!

I'll wait then until ADT for VS Code gain the same functionality as in Eclipse.
Until then I'll use your suggested workaround - thanks again for this!