abap-cloud-migrationlisted

# ABAP Cloud Migration Strategies for migrating existing ABAP code to ABAP Cloud (Steampunk-ready). ## Migration Assessment ### ATC Cloud Readiness Check ``` ATC Transaction → Check Variant: SAP_CP_READINESS_REMOTE → Run on custom code packages (Z* and Y*) → Results: 1. Released API violations 2. Direct DB access 3. Dynpro usage 4. Deprecated function modules ``` ## Migration Patterns by Technology ### Dynpro → Fiori Elements ``` Old: Dynpro transaction (SE80 screen painter) 1. Extract PBO/PAI logic into RAP behavior implementation 2. Map screen fields to CDS view entity 3. Generate Fiori Elements UI via Service Binding 4. Annotate CDS for UI layout (@UI.lineItem, @UI.selectionField) New: Fiori Elements List Report + Object Page ``` ### RFC → RAP OData ``` Old: Custom RFC function module (SE37) 1. Map RFC parameters to CDS entity fields 2. Create BDEF with actions for each RFC function 3. Expose via OData V4 service binding 4. Replace RFC consumers with OData clients New: RAP OData V4 endpoint ``` ### IDoc → SOAP ``` Old: IDoc processing (WE19/WE20) 1. Map IDoc segments to SOAP message types 2. Create Enterprise Service (SOA Manager) 3. Configure SAP_COM_0465 communication scenario 4. Migrate IDoc partner profiles to SOA consumers New: SOAP Web Service via released scenario ``` ### Direct DB Access → CDS Views ``` Old: SELECT * FROM mara INTO TABLE lt_mara. 1. Create CDS View Entity for mara (or use SAP standa