Observed Behavior
Direct MCP runtime probe with object_type = "INCL" returns:
Unsupported object type: INCL (supported: PROG, CLAS, INTF, DDLS, BDEF, SRVD, SRVB)
This confirms the limitation is enforced by the MCP server itself, not just by a client-side description.
Impact
Because INCL is unsupported:
- WriteSource cannot create or update true ABAP includes
- Include-based report refactors cannot be deployed cleanly through MCP
- using PROG as a workaround creates standalone programs, not include objects
- this prevents full support for report layouts that split logic into:
- selection-screen include
- event include
- productive local class include
- test include
Expected Behavior
The MCP server should support ABAP include objects as a first-class object type, ideally by allowing:
object_type = "INCL" in WriteSource
include-aware detection/import for .incl.abap files in ImportFromFile
Suggested Enhancement
Add INCL support to MCP write/import flows so agents and automation can create and maintain true include objects, not just monolithic reports or standalone helper programs. This would close an important gap for ABAP report development workflows that rely on classic include composition.
Observed Behavior
Direct MCP runtime probe with object_type = "INCL" returns:
Unsupported object type: INCL (supported: PROG, CLAS, INTF, DDLS, BDEF, SRVD, SRVB)
This confirms the limitation is enforced by the MCP server itself, not just by a client-side description.
Impact
Because INCL is unsupported:
Expected Behavior
The MCP server should support ABAP include objects as a first-class object type, ideally by allowing:
object_type = "INCL" in WriteSource
include-aware detection/import for .incl.abap files in ImportFromFile
Suggested Enhancement
Add INCL support to MCP write/import flows so agents and automation can create and maintain true include objects, not just monolithic reports or standalone helper programs. This would close an important gap for ABAP report development workflows that rely on classic include composition.