跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
法律与合规

abap-cloud-migration

Help with migrating classic ABAP custom code to ABAP Cloud including custom code adaptation, identifying unreleased API replacements, generating wrapper classes for unreleased objects, ATC Cloud Readiness checks, handling incompatible language constructs, and step-by-step migration workflows. Use when users ask about migrating to ABAP Cloud, custom code migration, cloud readiness, unreleased API replacement, wrapper pattern, ATC cloud checks, code adaptation, classic to cloud migration, S/4HANA cloud migration, or clean core compliance. Triggers include "migrate to ABAP Cloud", "cloud readiness check", "unreleased API", "replace with released API", "custom code adaptation", "wrapper for unreleased", "ATC cloud", "clean core migration", "move to tier 1", or "ABAP Cloud compatibility".

likweitan · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add likweitan/abap-skills --skill abap-cloud-migration

技能说明


name: abap-cloud-migration description: Help with migrating classic ABAP custom code to ABAP Cloud including custom code adaptation, identifying unreleased API replacements, generating wrapper classes for unreleased objects, ATC Cloud Readiness checks, handling incompatible language constructs, and step-by-step migration workflows. Use when users ask about migrating to ABAP Cloud, custom code migration, cloud readiness, unreleased API replacement, wrapper pattern, ATC cloud checks, code adaptation, classic to cloud migration, S/4HANA cloud migration, or clean core compliance. Triggers include "migrate to ABAP Cloud", "cloud readiness check", "unreleased API", "replace with released API", "custom code adaptation", "wrapper for unreleased", "ATC cloud", "clean core migration", "move to tier 1", or "ABAP Cloud compatibility".

ABAP Cloud Migration Patterns

Guide for systematically migrating classic ABAP custom code to ABAP Cloud (Tier 1) compliance.

Workflow

  1. Assess current state: Run ATC Cloud Readiness checks on existing code
  2. Categorize findings: Group by finding type (unreleased API, language construct, etc.)
  3. Plan migration: Prioritize by impact and determine replacement strategy
  4. Implement replacements: Apply released API replacements or create wrappers
  5. Validate: Re-run ATC checks and test functionality

Migration Assessment

Running ATC Cloud Readiness Checks

  1. In ADT: Right-click package → Run As → ABAP Test Cockpit
  2. Use check variant ABAP_CLOUD_READINESS or a custom variant with cloud-relevant checks
  3. Review findings in the ATC Results view

Key ATC Check Messages

Message IDDescriptionAction
NROBUse of unreleased number range APIUse CL_NUMBERRANGE_RUNTIME
BAPIDirect BAPI callUse released RAP API or wrapper
DYNPDynpro/screen usageReplace with Fiori/UI5
FUGRUnreleased function module callFind released replacement or wrap
CLASUnreleased class usageFind released replacement or wrap
TABLDirect DB table access (not released)Use released CDS view entity
LANGIncompatible language constructRefactor to use modern ABAP

Common API Replacements

Database Access

Classic PatternABAP Cloud Replacement
SELECT FROM maraSELECT FROM i_product
SELECT FROM bkpf / bsegSELECT FROM i_journalentry
SELECT FROM vbak / vbapSELECT FROM i_salesorder
SELECT FROM ekko / ekpoSELECT FROM i_purchaseorder
SELECT FROM kna1SELECT FROM i_customer
SELECT FROM lfa1SELECT FROM i_supplier
SELECT FROM t001SELECT FROM i_companycode
Direct table accessUse I_* released CDS views

Function Modules → Released Classes

Classic FMReleased Replacement
GUID_CREATEcl_system_uuid=>create_uuid_x16_static( )
CONVERSION_EXIT_ALPHA_INPUTcl_abap_format=>alpha_input( )
CONVERSION_EXIT_ALPHA_OUTPUTcl_abap_format=>alpha_output( )
POPUP_TO_CONFIRMNot available — use Fiori UI
NUMBER_GET_NEXTcl_numberrange_runtime=>number_get( )
BAPI_TRANSACTION_COMMITHandled by RAP framework (no explicit commit)
SO_NEW_DOCUMENT_ATT_SEND_API1cl_bcs_mail_message (send emails)
READ_TEXT / SAVE_TEXTNot released — wrap or use custom persistence
JOB_OPEN / JOB_CLOSE / JOB_SUBMITcl_apj_rt_api (Application Jobs)
ENQUEUE_* / DEQUEUE_*RAP draft / managed locking or CL_ABAP_LOCK_OBJECT

Language Constructs

Incompatible ConstructCloud-Compatible Alternative
CALL TRANSACTIONNot available — use API or RAP
SUBMIT ... AND RETURNNot available — use Application Jobs
WRITE / SKIP / ULINE (list output)Not available — use Fiori UI for output
CALL SCREEN / CALL SELECTION-SCREENNot available — use Fiori/UI5
MESSAGE ... RAISINGRAISE EXCEPTION TYPE ...
CALL FUNCTION ... IN UPDATE TASKRAP saver class / managed save
EXEC SQL (Native SQL)ABAP SQL or AMDP
GENERATE SUBROUTINE POOLNot available — use strategy/factory pattern
DESCRIBE FIELD ... TYPERTTI: cl_abap_typedescr=>describe_by_data( )
GET/SET PARAMETER IDNot available — use method parameters

Wrapper Pattern

When no released API exists, create a wrapper class in Tier 2 (classic ABAP) and release it for Tier 1 consumption.

Step 1: Create Wrapper Interface (Tier 2, released for Cloud)

"Released for use in ABAP Cloud (C1 contract)
INTERFACE zif_text_handler
  PUBLIC.
  METHODS read_text
    IMPORTING iv_id          TYPE thead-tdid
              iv_name        TYPE thead-tdname
              iv_object      TYPE thead-tdobjec
阅读完整来源 ↗