skills.rest
BoxLogoDev
BoxLogoDevCOMMUNITY
Explore all skills by this author →
GitHub

sap-cloud

Guide SAP S/4HANA Cloud Public Edition extension decisions with Clean Core and tiering.

16|6|Updated Apr 11, 2026
Search Tags:#extensibility#sap#s4hana#clean-core#cloud-pe#cloud-alm#fit-to-standard
One-click install
npx skills add https://github.com/BoxLogoDev/sapstack --skill sap-cloud
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sap-cloud
Source: https://github.com/BoxLogoDev/sapstack/tree/main/plugins/sap-cloud/skills/sap-cloud
Command: npx skills add https://github.com/BoxLogoDev/sapstack --skill sap-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides structured operational guidance and step-by-step decisions for implementing and operating SAP S/4HANA Cloud Public Edition while enforcing Clean Core constraints, minimizing custom code, and ensuring safe deployments across monthly/quarterly releases and Cloud ALM processes.

Core Features & Use Cases

  • Clean Core Guardrails: Clear list of forbidden activities (classic ABAP, table modifications, SMOD/CMOD, SE38/SE80) and recommended alternatives (CDS, RAP, Key User Extensibility).
  • Tiered Extensibility Decisioning: Decision tree and examples for Tier 1 (Custom Fields, CDS validations, RAP), Tier 2 (BTP side-by-side integrations, CAP), and Tier 3 (ABAP Cloud/RAP when released APIs are required).
  • Fit-to-Standard & Delta Design: Workshop structure, gap analysis templates, and delta design deliverables to minimize custom footprint and accelerate go-live.
  • Cloud ALM & CSP Deployment Guidance: CSP packaging, quality gates, deployment flow (DEV→TEST→PROD), quarterly release impact analysis, and rollback considerations.
  • Regional & Compliance Notes: Korean data residency, audit trail, and governance considerations for regulated industries.
  • Use Case: Run a Fit-to-Standard workshop to replace legacy IDOC-based vendor EDI with a Tier 2 BTP integration while moving reporting to Tier 1 CDS analytics.

Quick Start

Assess my Cloud PE environment (release 2405, production tenant) and produce a delta design recommending Tier 1/2/3 actions, an estimated effort, and a Cloud ALM deployment plan.

Frequently Asked Questions about sap-cloud

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Clean Core principles when extending SAP S/4HANA Cloud Public Edition?▼

Clean Core extension in S/4HANA Cloud PE forbids classic ABAP, table modifications, and SMOD/CMOD. Instead, use CDS views, RAP, and Key User Extensibility to minimize custom code and maintain system upgradeability.

How do I choose between Tier 1, Tier 2, and Tier 3 extensibility for SAP S/4HANA Cloud?▼

Extensibility tier selection uses a decision tree: Tier 1 covers custom fields and CDS validations, Tier 2 handles BTP side-by-side integrations via CAP, and Tier 3 applies ABAP Cloud/RAP when released APIs are strictly required.

What is the best way to run a Fit-to-Standard workshop for SAP S/4HANA Cloud Public Edition?▼

The best way to run a Fit-to-Standard workshop is to follow a structured gap analysis and delta design process. This approach minimizes your custom footprint by leveraging standard S/4HANA Cloud PE features and accelerates your overall go-live timeline.

How do I package and deploy extensions using Cloud ALM and CSP for S/4HANA Cloud?▼

To deploy extensions using Cloud ALM and CSP, package your artifacts, pass defined quality gates, and follow the deployment flow from DEV to TEST to PROD. This process includes quarterly release impact analysis and rollback considerations for safe operations.

Does S/4HANA Cloud Public Edition support regional data residency and compliance checks?▼

Yes, S/4HANA Cloud Public Edition operations include regional and compliance notes. The system addresses Korean data residency, audit trails, and governance considerations specifically required for deployment in regulated industries.

When should I not use classic ABAP extensions in my SAP S/4HANA Cloud environment?▼

You should not use classic ABAP extensions in S/4HANA Cloud when enforcing Clean Core constraints. Classic ABAP, SE38/SE80, and table modifications break the clean core, requiring a shift to Key User Extensibility or BTP side-by-side extensions instead.

Related Skills

Explore More Software Engineering Skills→
ajmeyers42ajmeyers42
1

thread-suggest

Evaluate Elastic standard demo fit against three criteria and decide predefined or custom path.

Community
Advanced
vigneshbarani24vigneshbarani24
6

sap-activate-methodology

Plan SAP Activate projects with phase deliverables and governance gates.

Community
Advanced
MarioDeFelipeMarioDeFelipe
25

S/4HANA Import Assistant

Import SAP S/4HANA and BW/4HANA entities into SAP Datasphere.

Community
Advanced
arc-mcparc-mcp
156

migrate-custom-code

Automate ABAP code migration to S/4HANA with ATC readiness checks and fixes.

Official
Advanced