In CAP, while service definitions in .cds files are core, they need to be declared as ‘provides’ in the package.json file (or bound via ‘cds.requires’ in a consuming service) to be served. The framework uses this configuration to automatically set up the endpoints and routing.

For on-premise connectivity via Cloud Connector, the most common initial point of failure is the connector itself. You must first ensure the Cloud Connector is online, the subaccount ID is correctly mapped, and the internal host/port for the S/4HANA system is exposed in the connector’s configuration. Other checks are relevant but come after this foundational connectivity is confirmed.

The Managed Database Schema approach for multitenancy in CAP creates physically separate schemas in the same HANA database instance for each tenant. This provides strong data isolation, as each tenant’s data resides in its own schema, which is the native and recommended pattern for data separation in SaaS applications on BTP with HANA Cloud.

In Kyma (a Kubernetes-based runtime), a Service Binding is a Kubernetes custom resource that creates a secure connection between a workload (e.g., a Deployment) and a managed service instance (e.g., a PostgreSQL database). It automatically injects the service’s connection details and credentials as environment variables or a volume mount into the associated pods.

CAP’s generic handlers translate OData queries (like $filter) into database queries. If these queries run on large tables without appropriate indexes, performance will degrade. The first, most impactful step is to analyze the queries being generated and ensure the underlying database tables have indexes on the columns frequently used in filters, sorts, and joins. This is a foundational database optimization step.

In Cloud Foundry, the manifest.yml file (or manifest.yaml) is the standard deployment descriptor. It contains the declarative configuration for an application, including its name, memory, disk, buildpack, environment variables, routes, and services to bind. While mta.yaml is used for multi-target application (MTA) deployments, a simple cf push relies on manifest.yml.

SAP Event Mesh (part of the Integration Suite) is the messaging and eventing backbone of BTP. It enables event-driven architectures via publish/subscribe and message queuing patterns. S/4HANA can publish change events (e.g., via Event Mesh Bridge or directly) to topics, and your CAP application can subscribe to those topics to react asynchronously, ensuring loose coupling and reliable delivery.

The ‘Application’ plan (formerly ‘hdi-shared’) provisions an HDI container that is tightly coupled to a single application. Its lifecycle (creation, deletion) is typically managed via the application’s deployment (e.g., MTA). The ‘Standard’ plan provisions a standalone HANA database instance that can be shared by multiple applications and managed independently.