Problem statement
What is the current state, unmet need, or symptom?
Kyma currently lacks full support for automated integration based on the Unified Connectivity Layer (UCL), as required by the product standard INTG‑04R2.
While the Application Connector Module implements UCL for SAP Commerce Cloud V2 (CCv2) integrations, this implementation is highly specialized and cannot be reused for other systems.
As a result, Kyma does not provide a generic, scalable, or standards-compliant approach for automated integrations with external SAP or non‑SAP systems. Teams integrating with Kyma must fallback to manual approaches or custom event-dispatching mechanisms, leading to inconsistent patterns, higher integration costs, and limited compliance with INTG‑04R2.
Who is affected?
- Product teams relying on Kyma as an extension or integration platform
- Architects and developers integrating external systems with Kyma
- Customers using Kyma as part of SAP BTP who expect standardized and automated integration capabilities
- Internal Kyma engineering and compliance teams responsible for meeting INTG‑04R2
When and where does this problem occur?
The problem appears whenever a new external system needs to be integrated with Kyma in an automated and standardized manner.
It occurs during:
- Design and onboarding of new integrations
- Compliance reviews for INTG‑04R2
- Attempts to reuse the CCv2 UCL integration pattern for other systems
- Customer implementations requiring consistent and maintainable integration flows
The issue is ongoing and becomes more critical as more systems aim to integrate with Kyma.
Why does it matter?
The root cause is the absence of a general-purpose UCL‑based integration framework within Kyma. Only a CCv2‑specific implementation exists, limiting Kyma’s ability to meet the broader INTG‑04R2 requirements.
Solving this would:
- Ensure Kyma complies with INTG‑04R2 across all integration scenarios
- Reduce effort and complexity for integration partners
- Enable scalable, automated, and standardized integration flows
- Strengthen Kyma’s position as a reliable integration and extension platform within SAP’s ecosystem
- Decrease custom implementations and maintenance overhead
Original request/trigger
- Triggered by the need to assess Kyma’s compliance with INTG‑04R2 and the gap in automated UCL‑based integration support.
- Raised internally during reviews of the Application Connector and planned integration scenarios.
Relevant reference:
- Product Standard INTG‑04R2
- Existing UCL‑based CCv2 integration implementation in ACM (not reusable for other systems)
Success metrics and targets
- Kyma provides a generic, reusable UCL integration capability suitable for multiple external systems
- Compliance with INTG‑04R2 is achieved and validated
- Reduction in custom integration effort (measured through engineering hours or customer project reports)
- Increase in number of systems integrated with Kyma using a standardized pattern
- Positive feedback from solution architects and integration teams
Risks, unknowns, and constraints
- The effort and complexity required to generalize UCL support across different systems is unclear
- Potential architectural constraints in Kyma may limit automated integration capabilities
- Adoption barriers if customers or systems do not fully support UCL
- Overlap or conflict with upcoming SAP integration platforms or strategies
- The CCv2 implementation may not serve as a viable reference for a generic solution
Dependencies and stakeholder map
Teams/systems we depend on:
- UCL framework owners
- SAP Integration Suite / SAP BTP Core Integration teams (for alignment)
- Eventually SAP Commerce Cloud team (for insights on the existing integration)
Decision owners and approvers:
- Kyma Product Management
- Kyma Architecture Owners
- Compliance and Product Standards team responsible for INTG‑04R2
Customer access/recruiting needs:
- Customers integrating multiple systems with Kyma to validate generic use cases
- Internal integration partners for pilots or early feedback
Problem statement
What is the current state, unmet need, or symptom?
Kyma currently lacks full support for automated integration based on the Unified Connectivity Layer (UCL), as required by the product standard INTG‑04R2.
While the Application Connector Module implements UCL for SAP Commerce Cloud V2 (CCv2) integrations, this implementation is highly specialized and cannot be reused for other systems.
As a result, Kyma does not provide a generic, scalable, or standards-compliant approach for automated integrations with external SAP or non‑SAP systems. Teams integrating with Kyma must fallback to manual approaches or custom event-dispatching mechanisms, leading to inconsistent patterns, higher integration costs, and limited compliance with INTG‑04R2.
Who is affected?
When and where does this problem occur?
The problem appears whenever a new external system needs to be integrated with Kyma in an automated and standardized manner.
It occurs during:
The issue is ongoing and becomes more critical as more systems aim to integrate with Kyma.
Why does it matter?
The root cause is the absence of a general-purpose UCL‑based integration framework within Kyma. Only a CCv2‑specific implementation exists, limiting Kyma’s ability to meet the broader INTG‑04R2 requirements.
Solving this would:
Original request/trigger
Relevant reference:
Success metrics and targets
Risks, unknowns, and constraints
Dependencies and stakeholder map
Teams/systems we depend on:
Decision owners and approvers:
Customer access/recruiting needs: