Introduction

With the evolution of SAP development models, Business Object Processing Framework (BOPF) is gradually being replaced by the RESTful ABAP Programming Model (RAP), which provides a more modern, cloud-ready, and Fiori-optimized approach for building business applications. To help developers transition, SAP provides a guided migration procedure that converts CDS-based BOPF Business Objects into RAP Business Objects.

This migration ensures that existing business logic, determinations, validations, and actions can be reused in the RAP model, reducing redevelopment effort while aligning applications with SAP’s strategic direction. The migration process can be executed in two modes:

• Simulation Mode – to check the feasibility of migration and identify potential errors or warnings.
• Migration Mode – to perform the actual migration of objects.

The following procedure outlines the step-by-step approach for performing this migration, including checking transactional processing (TP) and consumption views, handling transport requests, and reviewing logs to ensure a smooth transition.

Procedure

1. In your ABAP project, navigate to your CDS based BOPF BO under BOPF Business Objects in the Project Explorer.        

    

   

    

2. Open the context menu and choose RAP Business Object   Migrate….

    

3. In the Migration to RAP Business Objects wizard, select any one of the following modes:
    Simulation- checks and tests for errors and warnings before performing any changes. No object is migrated productively.
    Migration- migrates all the related objects.
    

    

4. Choose Next.
5. Check the TP views of the business objects affected by the migration.

   The transactional processing (TP) views display the lists of CDS views containing the transactional processing enabled object model annotations.

6. Choose Next.
7. Check the consumption views of the business objects affected by migration.

   The consumption views display the list of CDS views containing the transactional processing delegated annotations.

8. For migration, select or create a transport request for the objects.
9. Choose Next.
10. To start the simulation, choose Finish.
11. For migration, read the disclaimer in the Disclaimer page and the linked migration documentation carefully as the migrated business object cannot be reverted.

    The simulation log is displayed in the BO Migration Log view. Please read the outcome carefully, as errors or warnings indicate additional manual adjustments after the migration.

12. To continue with migration, select Continue Migration.
13. Choose Finish.

The migration log is displayed in the BO Migration Log view. Please read the outcome carefully, as errors or warnings indicate additional manual adjustments after the migration.

Conclusion
Migrating CDS-based BOPF objects to RAP helps modernize applications while reusing existing logic and reducing redevelopment. Always start with simulation to identify issues, carefully review migration logs, and then proceed with the actual migration. This ensures a smooth transition to SAP’s strategic RAP model.