Skip to content

Dynamic ABAP Version Resolution

stud0709 edited this page Oct 16, 2026 · 5 revisions

Dynamic ABAP Version Resolution

SAP determines which ABAP language versions and syntax are supported by the target system, package, and object. sap-dev uses this backend context during object creation and syntax validation.

Package language versions during creation

When creation metadata specifies an ABAP language version and target package, sap-dev queries the target SAP system for the package's allowed language versions. It uses the response to normalize supported standard/cloud version labels before creating the object. Use the metadata returned by sap_get_creation_template and keep the intended package and language semantics when editing it.

The lookup depends on backend support. Older systems may lack it; SAP still accepts or rejects the resulting creation request. If creation reports an unsupported language version, inspect the returned technical error and select a version supported by that package.

Syntax validation for existing objects

sap_check_syntax sends the staged source to SAP's native ADT compiler using the target object and, where needed, its parent container. SAP checks the source in the backend language and Dictionary context. Workspace lint runs first, and configured rule errors are returned before the SAP syntax request.

ABAP Unit test-class discovery and deep CALL FUNCTION parameter validation remain enabled independently of Cloudification. Function-call checks compare supplied parameters and their directions with SAP signatures. SAP syntax checking and ATC provide the authoritative backend validation.

Workspace rules and Cloudification profiles

A workspace-root abaplint.json configures naming, code style, and other local rules. Initialization supplies the current default profile when the file is missing and preserves existing customizations. The Cloudification dashboard separately selects a SAP release dataset for API policy across the workspace's Dev → Quali → Prod landscape. That dataset selection leaves the object's ABAP language version under SAP control.

See Workspace lint and Cloudification for check outcomes and coverage, and Cloudification reviews and exceptions for developer approvals.

Clone this wiki locally