plugins/sap-btp-cias/skills/sap-btp-cias/SKILL.md
SAP BTP Cloud Integration Automation Service (CIAS) skill for guided integration workflows. Use when: setting up CIAS subscriptions, configuring destinations, assigning roles (CIASIntegrationAdministrator, CIASIntegrationExpert, CIASIntegrationMonitor), planning integration scenarios, working with My Inbox tasks, monitoring scenario execution, troubleshooting CIAS errors, creating OAuth2 instances, configuring identity providers for CIAS, understanding CIAS security architecture, or integrating SAP products (S/4HANA, SuccessFactors, BTP services, SAP Build, IBP).
npx skillsauth add secondsky/sap-skills sap-btp-ciasInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Cloud Integration Automation Service provides guided workflows to integrate SAP cloud solutions with on-premise and other SAP cloud solutions. It offers both manual task instructions and automated configuration capabilities.
Use this skill when subscribing to CIAS, assigning CIAS role collections, planning guided integration scenarios, working My Inbox tasks, monitoring scenario execution, configuring OAuth2 API access, or troubleshooting CIAS workflow/task failures.
| Plan | Type | Purpose | |------|------|---------| | Standard | Application | UI access for scenario planning, task monitoring, integration management | | OAuth2 | Service | API access for programmatic operations (required for ABAP automation) |
| Role | Collection | Capabilities |
|------|------------|--------------|
| Integration Administrator | CIASIntegrationAdministrator | Full access: Plan for Integration, My Inbox, Monitoring; terminate scenarios |
| Integration Expert | CIASIntegrationExpert | My Inbox access; work on assigned tasks |
| Integration Monitor | CIASIntegrationMonitor | Read-only access to Scenario Execution Monitoring |
AWS: EU10 (Frankfurt), EU11 (Frankfurt EU Access), US10 (Virginia), AP10 (Sydney), JP10 (Tokyo), CA10 (Montreal) Azure: EU20 (Netherlands), CN20 (China North 3) Alibaba: CN40 (Shanghai)
CIASIntegrationAdministrator)Multiple users can be assigned per role using comma-separated user IDs.
Always use HTTPS for secure communication.
BC-INS-CIT-RT)CIAS comprises six core components:
Security features:
Symptom: Destination dropdown shows no options during task execution.
Cause: No destinations exist matching the tenant's Host Base URL.
Solution:
Symptom: Cannot proceed with task; execution lock activated.
Cause: Multiple integration workflows exist with identical system components.
Solutions:
Symptom: Users cannot access CIAS application after identity provider change.
Cause: Users not managed by newly configured identity provider.
Solution:
Symptom: Cannot claim task; shows "Reserved" status.
Cause: Another assigned user has already claimed the task.
Solution: Coordinate with team; only one user can work on claimed task at a time.
| Issue Type | Component | Action |
|------------|-----------|--------|
| General CIAS support | BC-INS-CIT-RT | Create support ticket |
| Manual task instructions | Check Support Information tab | Submit incident to listed component |
| Data deletion request | BC-INS-CIT-RT | Include email ID and subaccount name |
| Service availability | Consumer account | Check Service Availability feature |
For programmatic access (required for ABAP automation):
With mTLS (Certificate):
{
"xsuaa": {
"credential-type": "x509",
"x509": {
"key-length": 2048,
"validity": 365,
"validity-type": "DAYS"
}
}
}
Without Certificate: Create with name only.
Use generated client ID and client secret to create OAuth JWT token for API authentication.
| Term | Definition | |------|------------| | Personal Data | Any information relating to identified/identifiable natural person | | Sensitive Personal Data | Racial/ethnic origin, political opinions, religious beliefs, genetic/biometric data | | Residence Period | Time between business end and end-of-purpose when data remains accessible | | Retention Period | Time from last business activity through data deletion | | Blocking | Restricting access to data whose primary business purpose has ended |
| Control | Function | |---------|----------| | Refresh | Update automation statuses | | Expand All | Show all parameter panels | | Collapse All | Hide all parameter panels | | Show/Hide Read-Only Parameters | Toggle read-only visibility | | Save Parameters | Preserve current values | | Logs | View execution records | | Information | Parameter descriptions | | Execute Step | Run automation (async) |
After automation failure:
references/setup-guide.md - Complete subscription, OAuth2, and destination configuration proceduresreferences/security-guide.md - Security architecture, identity provider configuration, and role managementreferences/integration-scenarios.md - Full list of 100+ supported integration scenarios with codes (1M1, 22K, 4A1, etc.)references/troubleshooting.md - Detailed error resolution procedures and common issuesreferences/maintenance-planner.md - Maintenance Planner integration guide and workflow invocationreferences/task-ui-guide.md - Complete task UI controls, tabs, behaviors, and automation stepsreferences/whats-new.md - Complete release notes from 2021-2025 with feature updatestemplates/destination-config.md - Destination configuration templates by target system typetemplates/role-assignment.md - Role assignment procedures and checklists for different scenariosPrimary:
Related:
tools
Use when automating SAP BW query inspection, InfoProvider metadata reads (characteristics, key figures), metadata-verified specification review, unsaved draft preparation, or human-confirmed query draft population through Eclipse or HANA Studio with BW Modeling Tools.
tools
Use when an agent must inspect or operate an authenticated SAP web UI through an in-app Browser, Microsoft Edge CDP, or an existing Playwright client, especially when SAP SSO reuse, isolated Edge profiles, deterministic target selection, screenshots, or browser bootstrap recovery is required.
tools
Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/"confidential" API status, "Documented Use", whether a third-party tool / iPaaS / middleware / RPA bot / AI agent / MCP server may call SAP APIs, agentic or generative-AI access to SAP, bulk data extraction or replication into a lake/warehouse, custom Z/Y OData or RFC/BAPI wrappers and Clean Core, ADT/developer-tooling boundaries, ODP-RFC and other "not permitted" interfaces, partner Integration Certification, or RISE integration remediation. Trigger even when the policy is not named, e.g. "are we allowed to…", "is it compliant to…", "can we connect X to SAP…", "will this break under the new API policy". Produces a sourced technical assessment with a confidence level — explicitly NOT legal advice and NOT a final SAP compliance decision.
development
SAP-RPT-1-OSS local tabular prediction workflows for FI/CO prototype datasets. Use when preparing SAP finance CSV exports for classification or regression experiments with source-verified setup, leakage checks, and governance review.