Person
Petr Plenkov
Capabilities
Contributes to
ABAP Cloud readinessABAPABAP Cloud readinessWhether code can run in ABAP Cloud — released APIs only, no direct table access, no obsolete statements — and what to do with the code that cannot.Agent access to your systemsBTPABAPCAPAgent access to your systemsGiving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. [Serving your application over MCP](capability:mcp-servers) exposes your own service contract; system access reaches the systems behind it, and one implementation may do both. Development assistance belongs to [agent access to your code](capability:agent-code-access).Database administrationBTPDatabase administrationRunning the database a project uses once it exists: watching its health and performance, managing users and their access privileges, and keeping backups that a recovery can rest on. Connecting an application to the database is [database connectors](capability:database-connectors), moving files in and out of tables is [importing and exporting table data](capability:data-import-export), and what the instance costs is [consumption monitoring](capability:consumption-monitoring).Error handlingCAPABAPError handlingTurning a failure into a response a client can act on — protocol-correct error payloads, correlation, and a boundary between internal detail and what a caller sees.GraphQLCAPGraphQLServing the same model over GraphQL instead of OData — one endpoint, the client naming the fields it wants, for consumers who expect that shape rather than an OData one.HTTP clientsABAPHTTP clientsCalling an HTTP API outside the system from application code, with the request, the credential and the response handled by a client each time the call is made. Serving HTTP is the other direction, and where the address and the credential are kept is [destinations](capability:destinations).Native SAP HANA artifactsCAPNative SAP HANA artifactsUsing native SAP HANA database objects alongside an application’s generated data model, including objects and database features the modelling layer cannot express. Choosing a database is [database connectors](capability:database-connectors); changing an existing schema is [schema evolution](capability:schema-evolution).Parallel processingABAPParallel processingSplitting one run's work across several work processes so that it finishes sooner, and collecting what each part returned before the run goes on. [Async processing](capability:async-processing) is the neighbouring concern: work deferred past the request with a guarantee that it eventually happens, where parallel processing is throughput inside a run that waits for its results.SerialisationABAPSerialisationTurning typed in-memory data into a text or binary format such as JSON, CSV or protobuf and reading it back, including the mapping of names and types the language does not do for you. The protocol that carries the payload is a separate concern: an HTTP or OData client moves the bytes, and serialisation decides what they say.Static analysisABAPStatic analysisCatching problems in code before it runs: naming, obsolete statements, security findings, and compatibility with a target environment. Style linting, security scanning and cloud-readiness checks are often treated as one concern.TypingCAPTypingMaking the model visible to the compiler — generated types for entities and events so a rename breaks the build rather than production.Unit testingABAPUnit testingTesting application logic without a running business process — and the test doubles that make dependencies on the database and on framework services tractable.
Entries
Group by13 of 13 entries
EntrySignals
Contributes to
@abapify/acds@abapify/acdsA parser for ABAP CDS DDL source — tokenizer, parser and a typed AST covering tables, structures, simple types, service definitions and metadata extensions.independent, abap
Parser for ABAP CDS DDL source with a typed AST
@cap-js/cds-types@cap-js/cds-typesType definitions for the CAP Node.js SDK.sap official, cap
Type definitions for the CAP Node.js SDK
@cap-js/graphql@cap-js/graphqlA protocol adapter that generates a GraphQL schema from the model and serves it, so the same services answer GraphQL without a second definition of them.sap official, cap
GraphQL protocol adapter generated from the CDS model
ABAP JSON APIABAP JSON APIA JSON renderer and parser for ABAP built on the standard identity transformation, adding automatic camelCase conversion and support for polymorphic arrays.independent, abap
JSON renderer and parser for ABAP with camelCase conversion
abapify/fetchabapify/fetchA Fetch API-style polyfill for ABAP: one facade over request, response and destination, with the release-specific HTTP client of cloud or classic systems supplied by a plugin like Cloud fetch.independent, abap
Neither the package manifest nor the repository tree declares a licence.
Fetch API-style HTTP polyfill for cloud and classic ABAP
abapify/fetch-cloudabapify/fetch-cloudA plugin for the abapify/fetch polyfill that supplies its BAdI implementation for ABAP Cloud, where cl_http_client cannot be used directly; the polyfill is installed first.independent, abap
No published releases; repository quiet for 26 months.
Cloud-compatible plugin for the abapify Fetch API polyfill
abapify/fetch-legacyabapify/fetch-legacyA legacy-release implementation of the Fetch API interface for outbound HTTP calls from ABAP, plugging into abapify/fetch so the calling code needs no refactoring when it moves to the cloud.independent, abap
Legacy-release Fetch API implementation for outbound HTTP in ABAP
abapify/promiseabapify/promiseA Promise and async/await implementation for ABAP, modelled on JavaScript's Promise API, that runs a resolver as a background task and offers all, race, resolve, reject and all_settled.independent, abap
No published releases; repository quiet for 36 months.
Promise and async/await implementation for ABAP
assertassertA fluent assertion helper for ABAP Unit tests that wraps cl_abap_unit_assert in chained calls such as assert(x)->equals(y), also usable outside tests through ZCL_ASSERTABLE.independent, abap
Fluent assertion helper for ABAP Unit tests
codepagecodepageA polyfill class, ZCL_ABAP_CODEPAGE, that converts strings to binary and back behind one interface, where Clean Core blocks CL_ABAP_CODEPAGE and older systems lack CL_ABAP_CONV_CODEPAGE.independent, abap
Polyfill for CL_ABAP_CODEPAGE under Clean Core
SAP-samples/cap-sflightSAP-samples/cap-sflightA travel-booking reference application built with CAP and SAP Fiori elements, whose same UIs run against a Node.js and a Java backend so the two stacks can be compared directly.sap official, cap
Travel-booking reference app on CAP Node.js and Java backends
SAP-samples/hana-developer-cli-tool-exampleSAP-samples/hana-developer-cli-tool-exampleA developer-centric command line for SAP HANA, built for local development outside SAP tooling and connecting to a local, cloud or remote HANA instance the same way.sap official, btp
Developer-centric command line for SAP HANA
throwthrowA minimalistic way to raise an ABAP exception, from a text passed directly or, with no argument, from the system fields a preceding MESSAGE statement filled, as a static method or through an interface.independent, abap
Release and repository quiet for 26 months.
Raises an ABAP exception from a text or the last system message
Details
For your agent
- Ref
actor:theplenkov- JSON
- /actors/theplenkov.json
- MCP
- Connecting an agent