SAP RAP Unmanaged scenario example-Simplified

[anjan_paul]

SAP RAP (ABAP RESTful Application Programming Model) has two main flavors: managed and unmanaged. Let's focus on the unmanaged version.

Unmanaged SAP RAP refers to a development approach where developers have more control over the data persistence and business logic compared to the managed approach. Here are some key aspects:

1. Custom Logic: In unmanaged RAP, developers write their own custom logic for handling data retrieval, manipulation, and persistence. This gives more flexibility in how data is processed and stored.
2. Direct Database Access: Developers can directly access the database tables and define their own data models using Core Data Services (CDS) views or ABAP classes.
3. Explicit Service Definition: Unlike managed RAP, where service definitions are automatically generated based on annotations, unmanaged RAP requires developers to explicitly define service implementations and behaviors.
4. Manual CRUD Operations: CRUD (Create, Read, Update, Delete) operations need to be implemented explicitly in unmanaged RAP, giving full control over how data is managed.
5. Integration with Existing Systems: Unmanaged RAP is often used when integrating with existing systems or when there is a need for complex business logic that cannot be easily handled by the managed approach.
6. Flexibility: Developers have more freedom to implement complex validation rules, authorization checks, and other custom requirements directly in the application logic.

Overall, unmanaged SAP RAP provides a more hands-on approach to application development compared to the managed approach, allowing developers to leverage their expertise in ABAP programming and database handling while building modern RESTful APIs.

Top of Form

In this example, we will show a simple application for Employee build with RAP Unmanaged flavors.

Development steps.

To be summarized below object will be created for Unmanaged scenario.

Table ZT01_EMPLOYEE

Base CDS View Z_I_EMPLOYEES_U

Consumption CDS view  Z_C_EMPLOYEES_U

Behavior Definition

Bottom of Form

Behavior  definition

Implement the Create  method

Implement Update Method

Implement Delete Method

Implement Adjust_Numbers method.

Implement Save method.

Test

1. Open the Application.

 2. Click on Create. Give Input value and Create.

3. New Record got created.

4. Select any Row , click on Edit.

5. Change the value and Save.

6. Record will be updated.

7. Select the Rows and click on Delete.

8. Records will be deleted.

9. In the Database table also you can see the records.

So, all the  CRUD operation is successful using RAP Unmanaged flavors.

[Andre_Fischer]

In my opinion you describe the option of "unmanaged" in a too positive way.  

I wouldn't formulate it like this:   

"... allowing developers to leverage their expertise in ABAP programming and database handling while building modern RESTful APIs."   

but more "... forces developers to handle database access themselves which only makes sense when dealing with legacy API's".  

But even then developers should check if it is not possible to use a managed approach with an unmanaged save since this way lots of the implementations you described above are not necessary. 

Managed with unmanaged save is the recommended option. Unmanaged is the last resort.

Kind regards,

Andre

[Sandra_Rossi]

Is there a reason to post code as image rather than text? Code as image discourages people from trying by themselves.

[anjan_paul]

@Andre_Fischer   Thanks for your valuable opinion. Totally agree Unmanaged is the next option after Managed with Unmanaged Save.

@Sandra_Rossi  Thought of Code collection is very small. Might be User can just see and write the code help them to practice more. In case of lots of line of code definitely will give the code snippet.

Thanks,

Anjan Paul

[myhoa_pham]

Hello Anjan, 
Thanks for your helpful blog post.
I'm newbie in RAP development and currently practicing your sample. Could you please share me where lcl_buffer is initialized? 
Thanks.

[rcaziraghi]

@anjan_paulgreat work! It's really interesting. However, we are missing the lcl_buffer implementation. I'm really curious about it.
@Andre_Fischerone question about the managed vs. unmanaged scenario: Is there a scenario where unmanaged would be preferred? It looks like managed is preferable in almost all cases, so there should be very few situations where we would go with unmanaged. Maybe custom/abstract entities would be cases where unmanaged would be preferable?

[Jayasurya11]

Hello anjan,

Thanks for your helpful blog post,

I am currently working on an ABAP class implementation and encountered an issue with the type LCL_BUFFER being unknown. I understand that the lcl_buffer class or type needs to be defined, but I am not sure how to proceed with this. Could you please provide guidance on how to define the lcl_buffer class and implement the necessary logic for handling the creation values?

Thank you for your assistance.

[martinc_mb]

Thanks for the post; for me it is valuable because I have a scenario where I only need the draft table for the input of data from which I will then create a SAP document, and I don't need (and don't want) to persist the data; I only want the draft functionality. (And of course I need a v4 OData service so I can create a Fiori Elements app).

You did, however, skip some steps, specifically the adding of the service definition and binding, which might be helpful to someone who is completely new to RAP; it may just be helpful to point someone who wants to know more about that to e.g. the RAP100 developer course or the SAP Help.

Also, as @Sandra_Rossi points out, it would be much more helpful to insert the code into the post, not screenshots of it.