PersonIndependent
Mio Yasutake
GitHub@miyasutalast push
Capabilities
Provides
Soft deleteCAPSoft deleteDeleting a record without removing it — flagging the row, recording who deleted it and when, and keeping it out of reads. The question underneath is what DELETE should mean to a client that cannot tell the difference, and what happens to a composition tree when its root is flagged.
Demonstrates
Analytical queriesCAPAnalytical queriesGrouped, aggregated and filtered reads for analytical clients, answered by the database rather than in application memory. This concerns the queries a chart or report sends, while [analytic modelling](capability:analytic-modelling) defines the measures and dimensions they read.App hostingCAPBTPUI5App hostingWhere a built frontend lives and what serves it — the static files of a frontend application after the build, reachable behind a login and beside the API it talks to, without a web server of your own.AttachmentsCAPUI5ABAPBTPAttachmentsStoring a file somebody uploaded next to the record it belongs to, and getting it back out — where the bytes actually live, who may read them, and what the UI shows while they are being scanned.AuthenticationCAPBTPABAPUI5AuthenticationEstablishing who is calling: validating credentials or tokens, resolving the user, and making that identity available to the application. [Authorization](capability:authorization) decides what that identity may do; [identity provisioning](capability:identity-provisioning) manages its lifecycle across systems.AuthorizationCAPBTPABAPAuthorizationDeciding who may read or change what, at service, entity and instance level — role checks, forwarded user context, and restrictions evaluated as query filters rather than after the fact.CI/CD pipelinesCAPBTPCI/CD pipelinesA pipeline that builds, tests and delivers an application each time its source repository changes, with a build log that shows which step failed. [Deployment](capability:deployment) describes getting the build onto its target runtime.Database connectorsCAPBTPABAPDatabase connectorsConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).DeploymentCAPBTPDeploymentGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.DestinationsCAPBTPUI5DestinationsReaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.Draft handlingCAPDraft handlingLetting a user edit a record over several requests before it becomes real — saving unfinished changes, locking, and activating a completed draft.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.Event MeshCAPBTPABAPEvent MeshEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to [async processing](capability:async-processing).Fiori annotationsCAPUI5ABAPFiori annotationsDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.Input validationCAPABAPUI5Input validationRejecting bad input before it reaches the database. While this can be done manually inside a handler, there are solutions in place to derive type, range, enum and mandatory checks from the model definitions.LLM integrationCAPUI5BTPABAPLLM integrationCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.Local developmentCAPABAPLocal developmentRunning the whole stack on a laptop against real bindings — the service, the UI and the routing in front of it — without deploying to see a change.LoggingCAPBTPABAPUI5LoggingSeeing what a running service did, in a form something can read afterwards — levels, a formatter that suits a laptop and one that suits a log service.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).NotificationsCAPABAPNotificationsTelling a person something happened when they are not looking at the screen — a notification in the launchpad, an email, a message somewhere they already are.ODataCAPABAPODataExposing data and operations through OData, including the service model, metadata and protocol versions clients require. Version differences affect which clients can consume a service and which query features they can use.OpenAPICAPABAPBTPOpenAPIHanding a description of the service to clients and tools — an API portal, a code generator, a partner who wants a contract before they write anything.Retrieval-augmented generationCAPABAPBTPRetrieval-augmented generationGrounding a model's answer in data retrieved at question time: text split into chunks, each chunk embedded as a vector, and the chunks nearest to the question placed into the prompt. Semantic search is the same retrieval with a person reading the matches, and fine-tuning changes the model's weights, not its input.RFC connectivityCAPBTPABAPRFC connectivityCalling ABAP function modules from outside the system over RFC, with destinations and connection pooling handled rather than hand-wired on the calling side.Service compositionCAPService compositionBuilding one solution out of parts other projects published: a reuse package brings its models, code, initial data and texts into your project through npm or Maven, you serve what you reference and extend what you import, and the same modules deploy as one application or as several on a shared database. Distinct from [service integration](capability:service-integration), which reaches a service that stays deployed elsewhere, and from [tenant extensibility](capability:tenant-extensibility), which is a subscriber extending a running SaaS.Service integrationCAPService integrationUsing a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from [destinations](capability:destinations), which is how the address and the credentials are found, and from [replication](capability:replication), which is holding the data locally.TestingCAPBTPTestingProving the service still does what it did — against the model and the handlers, without a deployed system and without a database somebody has to keep clean.TypingCAPTypingMaking the model visible to the compiler — generated types for entities and events so a rename breaks the build rather than production.
Entries
Group by39 of 39 entries
EntrySignals
Maintains
cds-feature-softdeletecds-feature-softdeleteThe CAP Java counterpart to cds-softdelete-plugin: the same softdelete aspect, the same annotation, DELETE rewritten as a flag.independent, cap
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The Maven coordinate its README gives, io.github.miyasuta:cds-feature-softdelete:1.0.0, does not resolve on Maven Central as of 2026-09-07 — you build and install it from source.
CAP Java plugin for soft delete with a softdelete aspect
cds-softdelete-plugincds-softdelete-pluginA CAP plugin that turns DELETE into a flag on the record: annotated entities keep the row, record who deleted it and when, flag composition children with it, and drop out of reads.independent, cap
It changes what DELETE means for every client of the annotated projection, so anything that must actually remove a row — an erasure request, a retention job — has to go around it.
CAP plugin turning DELETE into a flag on annotated entities
Maintains: samples, sketches and references
assert-targetassert-targetA minimal sample of which paths fire @assert.target: an OData POST and this.run do, cds.run and db.run do not, and the ASSERT_TARGET message is overridden per locale in messages.properties.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Which CAP paths trigger @assert.target and which do not
attachment-reuse-controls-sampleattachment-reuse-controls-sampleA CAP Node.js service on @cap-js/attachments with a Fiori Elements object page that embeds the ui5-upload-controls library as a custom section.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Fiori Elements page embedding upload controls on @cap-js/attachments
auth-samplesauth-samplesTwo CAP services and a UI over them, set up so role and instance restrictions can be tried out against three mock users instead of a real identity provider.independent, cap
Neither the package manifest nor the repository tree declares a licence.
CAP services and a UI for trying role restrictions with mock users
blog-bookshopblog-bookshopA CAP service with a Fiori elements UI deployed whole to Cloud Foundry: an approuter, an HTML5 deployer, a launchpad content deployer and xs-security.json beside the db and srv modules in one mta.yaml.independent, cap
Neither the package manifest nor the repository tree declares a licence.
CAP bookshop with Fiori elements UI deployed whole to Cloud Foundry
blog-cap-chartblog-cap-chartA Fiori elements overview page over a CAP service whose two donut-chart cards read the same measure from an aggregating view and from the plain entity, so what the aggregation annotations change is visible side by side.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Fiori overview page comparing aggregated and plain donut-chart cards
cap-alpcap-alpAn Analytical List Page over a CAP OData V4 service, showing the aggregation annotations a CDS model needs before an analytical floorplan will render, kept in their own file beside the service.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Analytical List Page over a CAP OData V4 service
cap-ams-a2acap-ams-a2aFour app-to-app configurations between CAP Java and CAP Node.js under AMS and IAS, each recording which destination setup makes user propagation and token validation hold.independent, cap
Neither the package manifest nor the repository tree declares a licence.
App-to-app setups between CAP Java and CAP Node.js under AMS and IAS
cap-bp-ragcap-bp-ragAn event-driven RAG application: Cloud Integration embeds a Business Partner event taken off a broker, and the CAP service stores the vector in SAP HANA Cloud and answers questions from it.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Event-driven RAG app with CAP, Cloud Integration and SAP HANA Cloud
cap-cds-typercap-cds-typerA CAP service in TypeScript whose handlers import Books and Order from #cds-models/CatalogService, the types @cap-js/cds-typer generates from the model.independent, cap
CAP service in TypeScript using types from @cap-js/cds-typer
cap-cross-containercap-cross-containerA sample of five CAP services reading each other's HANA tables across HDI containers, with the grantor service key turned into a user-provided service.independent, cap
Neither the package manifest nor the repository tree declares a licence.
CAP services reading each other's HANA tables across HDI containers
cap-defaultvalue-functioncap-defaultvalue-functionCommon.DefaultValuesFunction pointed at a service function: getDefaultValues() selects the highest existing ID and returns that plus one, leaving the second key element to the user.independent, cap
Common.DefaultValuesFunction pointed at a CAP service function
cap-embedding-functioncap-embedding-functionA CAP service that computes a note's Vector(768) embedding in its own handlers, selecting SAP HANA Cloud's vector_embedding as a column from a Dummy entity.independent, cap
CAP service computing embeddings with HANA Cloud vector_embedding
cap-external-northwindcap-external-northwindA CAP service that serves an external OData service as its own: Northwind's Products imported as a CSN model, projected read-only, with the incoming query run against the remote service.independent, cap
CAP service serving Northwind's external OData Products as its own
cap-fe-masseditcap-fe-masseditA sample that switches on mass edit in a Fiori elements list report over CAP with enableMassEdit in manifest.json, against a draft-enabled Books entity with a status code list.independent, cap
Mass edit enabled in a Fiori elements list report over CAP
cap-feature-controlcap-feature-controlA singleton entity whose two flags drive what a Fiori elements page offers: the restriction, action-availability and button-visibility annotations all reach it by $edmJson $Path.independent, cap
Singleton entity whose flags drive Fiori elements feature control
cap-github-actioncap-github-actionA CAP project whose MTA build and Cloud Foundry deploy run as two jobs of one GitHub Actions workflow, with the Cloud Foundry credentials read from repository secrets.independent, cap
CAP project built and deployed to Cloud Foundry by GitHub Actions
cap-java-auth-checkcap-java-auth-checkCAP Java authorization checked case by case against cds-services-bom 4.8.0 — what a WRITE grant does not cover on a bound action, and where a where-condition carries over.independent, cap
Neither the package manifest nor the repository tree declares a licence.
CAP Java authorization checks tried case by case
cap-java-childcap-java-childThe consumer side of a promotion model for CAP Java: a parent pom pinned to a fixed version, Renovate opening the bump as a pull request, the application's own tests as the gate, and auto-merge only on green.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Consumer side of a CAP Java parent pom promotion model with Renovate
cap-java-draft-composition-deletecap-java-draft-composition-deleteDraft cancel on composition items turned into a flag update instead of a cascading physical delete, with the handler reading the incoming CQN so both delete paths behave the same.independent, cap
Neither the package manifest nor the repository tree declares a licence.
CAP Java draft cancel on composition items as a flag update
cap-java-parent-pom-samplecap-java-parent-pom-sampleA Maven parent pom published to GitHub Packages that pins cds-services-bom, the Spring Boot BOM and a shared CAP Java plugin, so a child application names the parent coordinate and no versions of its own.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Maven parent pom pinning cds-services-bom and Spring Boot for CAP Java
cap-java-resiliencecap-java-resilienceA CAP Java service consuming a Business Partner API that a CAP Node.js project in the same repository mocks, with the SAP Cloud SDK caching and resilience it is named for recorded as planned.independent, cap
Neither the package manifest nor the repository tree declares a licence.
CAP Java service consuming a Business Partner API mocked in Node.js
cap-java-snippetscap-java-snippetsTen short CAP Java references, one per document: handler phases, CQN analysis, CQL, error handling, actions, authentication, logging, remote services, hybrid runs and the test layers.independent, cap
Ten short CAP Java references, one document per topic
cap-js-notificationscap-js-notificationsA CAP Node.js order service that sends a notification after every create, published as a sample implementation of @cap-js/notifications.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Order service sending notifications via @cap-js/notifications
cap-mediacap-mediaMedia handling with nothing but core CDS: a LargeBinary element annotated with @Core.MediaType, @Core.IsMediaType and @Core.ContentDisposition, uploaded from a UI5 UploadSet.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Media handling in core CDS with a UI5 UploadSet
cap-oauth-destinationcap-oauth-destinationA sample that declares a destination for OAuth2UserTokenExchange in mta.yaml, so it is deployed with the application rather than created by hand in the cockpit.independent, cap
Neither the package manifest nor the repository tree declares a licence.
OAuth2UserTokenExchange destination declared in mta.yaml
cap-openaicap-openaiTwo actions on one CAP service that reach OpenAI's chat completions endpoint by two routes: the openai npm client with the key from the environment, and a CAP remote service of kind: rest that goes through a destination in production.independent, cap
Neither the package manifest nor the repository tree declares a licence.
CAP service actions calling OpenAI chat completions two ways
cap-openapicap-openapiA CAP Java service whose two handlers call role collection endpoints through a client the Cloud SDK's OpenAPI generator builds at build time from a specification kept in the project.independent, cap
Neither the package manifest nor the repository tree declares a licence.
CAP Java service calling role collection APIs via a generated client
cap-principal-propagationcap-principal-propagationAn on-premise ABAP OData V2 service read through a named destination and the SAP Connectivity service, with a Fiori elements list report and an approuter in front of the CAP service.independent, cap
Neither the package manifest nor the repository tree declares a licence.
On-premise ABAP OData V2 service read from CAP over Connectivity
cap-rediscap-redisA sample that holds the approuter's session, CSRF token included, in a bound instance of Redis on SAP BTP, hyperscaler option instead of the approuter's own memory, around a CAP and Fiori elements app.independent, cap
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary Not a descriptor to deploy as it stands: the approuter's `sessionSecret` is written out in `mta.yaml`.
Approuter session held in a bound Redis cache instance
cap-reuse-html5cap-reuse-html5A Fiori elements app uploaded to the HTML5 Application Repository together with a cdm.json, and a second repository instance on the app-runtime plan behind a subaccount destination pointing at /applications/cdm/cap-reuse-html5.independent, cap
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The subaccount destination's url names the us10 trial's repository runtime, so another region or subaccount needs it rewritten before the descriptor deploys.
Fiori elements app in the HTML5 Application Repository with cdm.json
cap-rfccap-rfcA CAP Node.js action that calls BAPI_EPM_BP_CREATE over RFC, with the function module's own signature imported as CDS and a destination standing in for the system once deployed.independent, cap
Neither the package manifest nor the repository tree declares a licence.
CAP Node.js action calling BAPI_EPM_BP_CREATE over RFC
cap-uicap-uiAn MTA that deploys a CAP service, a HANA HDI container and a Fiori elements app into the HTML5 Application Repository, with two destinations to the same CAP service configured side by side.independent, cap
MTA deploying CAP, HDI container and a Fiori elements app
cap-vector-hccap-vector-hcA sample that declares VECTOR_EMBEDDING in a CDS entity: an FAQ model whose embedding column HANA Cloud generates and stores, then answers questions by similarity search.independent, cap
Neither the package manifest nor the repository tree declares a licence.
VECTOR_EMBEDDING in a CDS entity for FAQ similarity search
fiori-dynamic-feature-controlfiori-dynamic-feature-controlMaking one object page field non-editable from the value of another, implemented twice — through a default-value entity with side effects, and through a virtual element with a CAP Java handler.independent, cap
Neither the package manifest nor the repository tree declares a licence.
One object page field made read-only from another's value, two ways
fiori-inline-editfiori-inline-editList report inline edit on a draft-enabled service, pinned to @sap/cds 9.9.1 and SAPUI5 1.136.7 — whether a save message appears, and whether value help works inside an edited cell.independent, cap
Neither the package manifest nor the repository tree declares a licence.
List report inline edit on a draft-enabled CAP service
fiori-invoke-functionfiori-invoke-functionCalling an unbound CAP Java function from a freestyle UI5 app through a deferred ODataContextBinding — the (...) path that issues no request until invoke().independent, cap
Neither the package manifest nor the repository tree declares a licence.
Calling an unbound CAP Java function from freestyle UI5
fiori-navigation-patternsfiori-navigation-patternsA sample of outbound navigation from a Fiori Elements list report, worked through as the triggers that start it, from semantic links to intent-based buttons, and the context each one carries.independent, cap
Neither the package manifest nor the repository tree declares a licence.
Outbound navigation patterns from a Fiori Elements list report
Writing and topics
Piece, what it offersStill applies
CAP JavaでObject Pageの項目の動的な入力制御を実装するCAP JavaでObject Pageの項目の動的な入力制御を実装するTwo ways to make an object page field editable or not from the value of another field in CAP Java, with the same rule implemented both ways. The first routes the decision through a separate entity holding default values, reached by Side Effects annotations; the second adds a virtual element the Java event handler fills. The piece is about the trade the two make — annotation-only versus a handler that runs — rather than about which is correct, and the running code is the repository it links.published 2025-10-13
Using HANA Cloud’s "VECTOR_EMBEDDING" Function in CAPUsing HANA Cloud’s "VECTOR_EMBEDDING" Function in CAPEmbeddings generated inside the database rather than fetched from AI Core or an external model — a Q4 2024 HANA Cloud function, used from CAP. The shift it describes is where the embedding step lives, which changes what has to be deployed and what has to be called.published 2025-03-02
Building an Analytical List Page with CAP OData V4Building an Analytical List Page with CAP OData V4The annotations a CAP OData V4 service needs before an Analytical List Page will render — the write-up behind the cap-alp sample indexed here. Candid about its provenance: the author credits a GitHub repository she found the approach in, and notes that the repository is no longer available, which is the whole argument for indexing the reasoning rather than only linking the code.published 2023-06-12
Building an Analytical List Page with CAP OData V4
cap-alp: no published releases, repository quiet for 24 months. Affects A recipe, Runnable code.
Fiori Elements Analytical Table with CAP: Does it work with V2 and V4?Fiori Elements Analytical Table with CAP: Does it work with V2 and V4?A question in the title and an answer in the post, with the boundary drawn carefully: this is an analytical table inside a List Report, not the Analytical List Page, and the two protocol versions do not behave the same.published 2023-04-03
Fiori Elements Analytical Table with CAP: Does it work with V2 and V4?
Fiori annotations changed in @sap/cds-dk 9.6.0, 2025-12-17. Affects Runnable code.
How to share tables across different CAP projectsHow to share tables across different CAP projectsFour scenarios for reading one CAP project's table from another, worked out as a matrix of what each one needs: the same HDI container and namespace, the same container under a different namespace, a different container, and a different Cloud Foundry space. The mechanics change with each step — @cds.persistence.exists on the reused entity throughout, an .hdbsynonym once namespaces diverge, .hdbrole and .hdbgrants once containers do, and a user-provided service built from the grantor's credentials once spaces do. The author flags the caveat themselves: these are learning scenarios, and consuming the OData service is often the better answer than reaching into another project's database. Dated corrections from twelve days after publication sit inline — synonyms need only the name because the configuration comes from .hdbsynonymconfig, SERVICE_REPLACEMENTS in mta.yaml removes the hard-coded service name, and the reused container need not be bound to the srv module.published 2021-10-03
Details
History
- cap-vector-hcThe capability moved to a neutral id when it opened to HANA, BTP and ABAP; the concern and this entry's edge to it are unchanged.
- cds-feature-softdeleteEntered unmapped because no capability fitted: change-tracking is history of changes, data-privacy is close to the opposite, and inventing an edge would have been worse than the gap. The capability now exists, so the edge is the honest one rather than the nearest one.
- cds-softdelete-pluginEntered unmapped because no capability fitted: change-tracking is history of changes, data-privacy is close to the opposite, and inventing an edge would have been worse than the gap. The capability now exists, so the edge is the honest one rather than the nearest one.
- First entry seenDiscovered via GitHub API · miyasuta, GitHub organisations and accounts · miyasuta, npm registry.
For your agent
- Ref
actor:mio-yasutake- JSON
- /actors/mio-yasutake.json
- MCP
- Connecting an agent