abap-cloud-migration

Identify unreleased ABAP APIs and plan replacements for ABAP Cloud migrations.

49|15|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/likweitan/abap-skills --skill abap-cloud-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: abap-cloud-migration
Source: https://github.com/likweitan/abap-skills/tree/main/skills/abap-cloud-migration
Command: npx skills add https://github.com/likweitan/abap-skills --skill abap-cloud-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating classic ABAP code to ABAP Cloud can be complex due to compatibility gaps, API unreleased statuses, and the need for safe wrappers. This guide provides a structured approach to assess readiness, identify the right replacement strategies, and implement migration patterns that align with cloud-native practices.

Core Features & Use Cases

  • Migration Planning: Run ATC Cloud Readiness checks, classify findings, and prioritize remediation tasks for cloud migration.
  • API Replacement & Wrappers: Use released RAP/CDS APIs where possible or design Tier-2 wrappers for unreleased APIs to enable cloud deployment.
  • Migration Playbooks: Follow end-to-end playbooks for Reports, Dynpro, BAPIs, and RFCs to transition to ABAP Cloud-ready artifacts.

Quick Start

Start by running an ATC Cloud Readiness check on your ABAP package and capture unreleased API findings to begin the migration plan.

Frequently Asked Questions about abap-cloud-migration

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

FAQPage Schema
How do I migrate classic ABAP code to ABAP Cloud?

To migrate classic ABAP code to ABAP Cloud, run an ATC Cloud Readiness check to identify unreleased APIs, then plan safe replacements using released RAP/CDS APIs or Tier-2 wrappers for cloud deployment readiness.

What is the ABAP wrapper pattern for unreleased APIs?

The ABAP wrapper pattern involves developing Tier-2 wrappers for unreleased APIs. This enables classic ABAP codebases to achieve cloud deployment readiness when direct released RAP or CDS replacements are not available.

How do I run an ATC Cloud Readiness check for ABAP migration?

Running an ATC Cloud Readiness check involves analyzing your ABAP package to capture unreleased API findings. You then classify these findings to prioritize remediation tasks and plan your ABAP Cloud migration.

Can I use released RAP and CDS APIs to replace classic ABAP artifacts?

Yes, you can use released RAP and CDS APIs to replace classic ABAP artifacts. This approach is preferred for ABAP Cloud migrations, utilizing end-to-end playbooks for Reports, Dynpro, BAPIs, and RFCs.

What are the limitations of using Tier-2 wrappers for ABAP Cloud migration?

Tier-2 wrappers for ABAP Cloud migration are used when direct released RAP or CDS replacements are unavailable. They serve as a bridge for unreleased APIs, though prioritizing native released API mapping remains the preferred cloud-native strategy.