sap-cloud
This skill handles SAP S/4HANA Cloud Public Edition tasks including Clean Core principles, Key User Extensibility (Custom Logic, Custom Fields, Custom CDS Views, Custom Business Objects), 3-Tier Extension Model (Tier 1 Key User, Tier 2 Side-by-Side, Tier 3 On-Stack), Fit-to-Standard workshops, Cloud ALM (Application Lifecycle Management), Feature Scope Description (FSD), Quarterly Release management, and CSP (Custom Software Package) deployment. Use when user mentions Cloud PE, Public Cloud, Clean Core, Key User Extensibility, Custom Logic, Custom Fields, Custom CDS, Fit-to-Standard, Cloud ALM, FSD, quarterly release, CSP, 클라우드, 퍼블릭 클라우드, 클린 코어.
BoxLogoDev · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add BoxLogoDev/sapstack --skill sap-cloud技能说明
name: sap-cloud description: > This skill handles SAP S/4HANA Cloud Public Edition tasks including Clean Core principles, Key User Extensibility (Custom Logic, Custom Fields, Custom CDS Views, Custom Business Objects), 3-Tier Extension Model (Tier 1 Key User, Tier 2 Side-by-Side, Tier 3 On-Stack), Fit-to-Standard workshops, Cloud ALM (Application Lifecycle Management), Feature Scope Description (FSD), Quarterly Release management, and CSP (Custom Software Package) deployment. Use when user mentions Cloud PE, Public Cloud, Clean Core, Key User Extensibility, Custom Logic, Custom Fields, Custom CDS, Fit-to-Standard, Cloud ALM, FSD, quarterly release, CSP, 클라우드, 퍼블릭 클라우드, 클린 코어. allowed-tools: Read, Grep
1. Environment Intake Checklist
When any Cloud PE issue or extension task is reported, collect before answering:
- Cloud PE Version: 2401 / 2402 / 2403 / 2405 / (specific release month/year)
- Tenant Type: Production / Non-Production (Test / Staging)
- Extension Tier: Tier 1 (Key User Extensibility) / Tier 2 (Side-by-Side BTP) / Tier 3 (On-Stack ABAP Cloud)
- Deployment Model: Cloud PE (never mention on-premise SE38/SE80/SMOD/CMOD — they are forbidden)
- Industry Sector: Manufacturing / Finance / Retail / Public Sector / Other
- Change Control: Are you in Fit-to-Standard phase or Operations phase?
2. Clean Core Principles (Non-Negotiable)
SAP S/4HANA Cloud PE enforces Clean Core — no modifications to SAP standard code or tables.
| Activity | On-Premise (ECC/S/4HANA OP) | Cloud PE |
|---|---|---|
| ABAP Modifications (SE38) | ✓ Allowed | ✗ FORBIDDEN |
| Function Module Enhancements (SMOD/CMOD) | ✓ Allowed | ✗ FORBIDDEN |
| Workflow Customizing (SWDD) | ✓ Allowed | △ Limited (no code exits) |
| IMG Configuration | ✓ Full (SPRO) | △ Limited (Manage Your Solution) |
| BAdI Implementation | ✓ Standard (SE19) | ✗ FORBIDDEN (use RAP instead) |
| Enhancement Spots | ✓ Full (BADI_DEF) | ✗ FORBIDDEN |
| Standard Table Modifications | ✓ Allowed (append structures) | ✗ FORBIDDEN |
| Transport Mechanism | ✓ TMS (TP/TP4) | ✗ Direct upload to Cloud ALM |
Forbidden T-codes in Cloud PE:
- SE11 (ABAP Dictionary modifications)
- SE38 (Classic ABAP program creation)
- SE80 (Object Navigator for custom code)
- SMOD / CMOD (Exit/Enhancement modification)
- SWDD (Classic Workflow definition)
- SPAM / SAINT (Transport/patch — managed by SAP)
3. Key User Extensibility — Tier 1 (Self-Service)
3.1 Custom Fields (Extensibility Add-Ons)
Enable end users (non-developers) to add business fields without coding.
How to Create Custom Fields:
- In Cloud PE UI → Manage Your Solution → Custom Fields
- Select object (Purchase Order, Sales Order, Material Master, etc.)
- Click Create Custom Field
- Field Name:
ZZ_CUSTOM_FIELD(naming convention) - Data Type: Quantity / Amount / Date / Text / Dropdown
- Label: Business-facing label (Korean: "사용자정의 필드")
- Field Name:
- Deploy: Activation is immediate (no transport)
- UI Integration: Auto-added to relevant screens (Fiori UIs)
Limitations:
- No transactional logic (no derived fields)
- No cross-object validation
- Max 200 custom fields per object
- Field length: Text max 255 characters
Example: Add "승인 요청 코드" (approval code) to PO header:
- T-code: MANAGE_CUSTOM_FIELDS (Fiori)
- Object: Purchasing Document (PO)
- Field: ZZ_APPR_CODE (Text, length 20)
- Result: Auto-visible in PO Fiori app (no coding needed)
3.2 Custom Logic (ABAP Cloud with RAP)
For business logic beyond custom fields — use Restricted ABAP Programming (RAP) on released SAP APIs.
What is RAP (Restful ABAP Programming)?
- Cloud-native ABAP development model (CDS-based)
- No classic ABAP (SELECT, MODIFY, DELETE) — replaced by CDS + Event Handler
- Event-driven (Create, Update, Delete hooks)
- Published as OData V4 APIs automatically
Tier 1 Custom Logic Entry Points (Key User-friendly):
-
Calculations/Derivations — Automatic field computation
- Example: "Invoice Amount = Net Amount + Tax" (tax auto-calc on item save)
- Implementation: CDS Calculation / Transient Field
-
Validations — Block invalid data
- Example: "PO quantity must not exceed contract qty"
- Implementation: CDS Validation (CDS element WITH ... , associations)
-
Default Values — Pre-fill fields on creation
- Example: "Set cost center from user default"
- Implementation: CDS Default Handler
ABAP Cloud Restrictions:
- ✗ SELECT FROM database table (use CDS instead)
- ✗ MODIFY table directly
- ✗ CALL FUNCTION (classic RFC)
- ✓ CALL API (SAP standard APIs released)
- ✓ SQL queries via CDS Views
- ✓ OData consumption via HTTP
Example: Validate PO quantity vs. contract
CDS View: ZC_PO_CUSTOM
element ZZ_CONTRACT_QTY : Contract Qty;
Validation Rule:
if (PO_QTY > ZZ_CONTRACT_QTY) {
raise_severity(error, 'Qty exceeds contract');
}
3.3 Custom CDS Views (Read-Only Analytics)
Expose custom data models for reporting without modifying SAP tables.
Use Case: Create custom analytics on top of SAP data.
- Example: "Monthly spend by cost center vs. budget"
- Technology: CDS (Core Data Services)
- Consumption: Fiori Analytical App / Excel / Analytics Cloud
Steps:
- ABAP Workbench (in Cloud PE) → Create CDS View
- Define associations to standard SAP tables (PO, Invoice, GL, etc.)
- Add calculations (SUM, AVG, COUNT)
- Publish as OData (automatic)
- Create Fiori app or connect to Analytics Cloud (SAC)
Limitations:
- Read-only (no CRUD operations)
- Max 100M rows per query (performance limits)
- Must use released SAP tables (not custom Z-tables)
3.4 Custom Business Objects (Transactional Objects)
For completely new entities (not extending existing SAP objects).
Example: "Internal Service Request" (separate from Purchase Order)
Technology: ABAP Cloud Busines
阅读完整来源 ↗