Remote Services
Add a remote service integration to an existing CAP Node.js application using the Calesi pattern. Imports external APIs (from other CAP apps or OData/S4 sources), creates consumption views, wires up delegation and data federation handlers, and validates the result with cds watch. Use when a developer wants to consume an external service in their CAP app.
Help with OData service development in ABAP including OData V2 and V4 services via RAP service bindings, SEGW-based services, service definitions, service bindings, OData annotations, consumption of external OData services, and troubleshooting common OData errors. Use when users ask about OData, OData V2, OData V4, service binding, service definition, SEGW, OData annotations, OData consumption, OData client proxy, HTTP client, communication arrangement, external API consumption, /IWBEP/ errors, or exposing a RAP BO as OData. Triggers include "create OData service", "expose RAP BO", "service binding", "OData V4", "consume external OData", "OData annotations", "SEGW service", or "OData error".
Combined developer assistant for SAP Customer Experience (CX) covering three capabilities: CX API Explorer (finds and scaffolds OCC, Sales Cloud v2, and Service Cloud API calls from api.sap.com), CAP CDS Assistant (generates CDS entities, annotations, service definitions, and extension patterns using cap.cloud.sap), and CX Error Resolver (diagnoses Commerce Cloud, Sales/Service Cloud v1/v2, CAP, and BTP errors using public SAP Help and KBAs). Grounded in public SAP sources only via live web search; no authentication required.
Assists SAP Integration Suite Cloud Integration developers with the Pipeline framework. Use for pipeline architecture selection, Step01 headers, Partner Directory entries, fully decoupled or integrated messaging runtime, asynchronous or synchronous interfaces, virtual landscape stages, receiver/interface determination, XSLT, retries, JMS, ProcessDirect, monitoring, migration, review, and troubleshooting. This skill provides guidance only and does not generate deployable iFlow artifacts.