Release 2.2.2.202609081736
This commit is contained in:
@@ -152,14 +152,14 @@ The `systemId` description in every tool's schema is dynamically populated from
|
||||
|
||||
Each connected system has an access mode: write or read-only. A new connection starts in write. The mode lives in the third column of the **ABAP MCP Server** view table, next to Project and Status. The **Toggle Read-Only** button flips the mode of the selected system.
|
||||
|
||||
A read-only system refuses the 9 write tools and makes no ADT call against SAP. Every other tool works on a read-only system. The 9 write tools are `sap_push_source`, `sap_push_source_from_file`, `sap_push_element`, `sap_create_object`, `sap_activate`, `sap_lock`, `sap_unlock`, `sap_transport_create`, and `sap_transport_release`.
|
||||
A read-only system refuses the 10 write tools and makes no ADT call against SAP. Every other tool works on a read-only system. The 10 write tools are `sap_push_source`, `sap_push_source_from_file`, `sap_push_element`, `sap_push_message`, `sap_create_object`, `sap_activate`, `sap_lock`, `sap_unlock`, `sap_transport_create`, and `sap_transport_release`.
|
||||
|
||||
The mode survives an Eclipse restart and a reconnect. The plugin stores the mode per project name. `sap_list_systems` shows the mode of each connected system.
|
||||
|
||||
|
||||
## MCP Tools
|
||||
|
||||
The plugin exposes 30 tools covering the full ABAP development workflow:
|
||||
The plugin exposes 31 tools covering the full ABAP development workflow:
|
||||
|
||||
### Search & Navigation
|
||||
|
||||
@@ -184,6 +184,7 @@ The plugin exposes 30 tools covering the full ABAP development workflow:
|
||||
| `sap_push_source` | Write source code from context to an ABAP object in SAP — runs the full lock → write → unlock → activate pipeline in one call |
|
||||
| `sap_push_source_from_file` | Save a local file back to SAP through the same one-call pipeline |
|
||||
| `sap_push_element` | Write one member block. The server merges the block into the current full source and pushes it — the model never holds the class. CLAS, INTF, PROG, FUGR |
|
||||
| `sap_push_message` | Write one message or several messages into an existing message class (MSAG). The server reads the class, merges the messages, and writes the class back in one call. A new number is appended. An existing number is updated |
|
||||
| `sap_pretty_print` | Format (pretty-print) ABAP source through the ADT pretty-printer service. The tool takes only the source and uses the server's stored settings |
|
||||
|
||||
### Lifecycle
|
||||
@@ -193,7 +194,7 @@ The plugin exposes 30 tools covering the full ABAP development workflow:
|
||||
| `sap_lock` | Lock an object for editing (returns a lock handle) |
|
||||
| `sap_unlock` | Release a previously acquired lock |
|
||||
| `sap_activate` | Activate an ABAP object |
|
||||
| `sap_create_object` | Create a new ABAP object: class, interface, program, function group, data element, domain, table, structure, or CDS-family source (DDLS, DDLX, SRVD, DCLS, DDLA) |
|
||||
| `sap_create_object` | Create a new ABAP object: class, interface, program, function group, data element, domain, table, structure, table type (TTYP), message class (MSAG), or CDS-family source (DDLS, DDLX, SRVD, DCLS, DDLA) |
|
||||
|
||||
### Transport Management
|
||||
|
||||
|
||||
Reference in New Issue
Block a user