Introduction to unmanaged scenario in RAP

An Unmanaged RAP scenario is one where the developer is fully responsible for implementing the logic for data persistence (create, update, delete), rather than relying on the RAP framework to handle it.

Key Characteristics:

  • Marked using the keyword unmanaged in the behavior definition.

  • Requires a custom implementation class (CLASS ZBP_...) where the developer codes the logic.

  • The RAP framework only provides infrastructure like:

    • Locking

    • Transaction handling

    • Draft support (optional and manual)

  • Used for existing legacy tables, custom business logic, or integration with BAPIs/function modules.

When to Use Unmanaged:

  • Working with existing or complex database structures.

  • Business logic cannot be mapped using standard CRUD operations.

  • You need to integrate with existing code, modules, or systems.

Limitations:

  • No automatic data handling—everything must be manually implemented.

  • More development effort than managed scenarios.

  • Draft functionality is not automatic and must be manually implemented if required.

Typical Use Cases:

  • Reusing existing tables or BAPIs.

  • Migrating classical applications into RAP without changing persistence logic.

  • Implementing complex transactional logic or validations.


********************************Thank you*****************************

Comments

Post a Comment

Popular posts from this blog

New syntax for append- VALUE (new syntax 7.4+) in ABAP

Image
* We use APPEND statement to insert the records at the last of the internal table. * In SAP ABAP new syntax, we can use VALUE expression instead of APPEND statement. * Value expression is a powerful mechanism to declare as well as initialize the internal tables. * It is a powerful utility where we can achieve the result with minimal coding. * Value expression is of 2 types.      -  Define the type before using it with VALUE keyword. The type defined is structure type  or table type.      -  Using # character for type and use it with VALUE keyword. Report REPORT  zab_rp_append_value . TYPES :  BEGIN  OF  ls_stu ,          st_id ( 10 )    TYPE  n ,          st_name ( 15 )  TYPE  c ,         END  OF  ls_stu . DATA :  lt_stu  TYPE  TABLE...
Read more

Read statement new syntax in ABAP. (7.4+).

Image
*  Before ABAP 7.4, we used READ TABLE statement to read the first matching record from the internal table  based upon key or index . * In SAP ABAP new syntax, instead of READ TABLE , we can use the table expressions. * We need to use the square bracket [ ], In the square bracket, we need to specify the key or index. * While using table expression, If the table entry does not exist, system throws the exception CX_SY_ITAB_LINE_NOT_FOUND. * Use line_exists statement to check the existence of a record. Report REPORT  zab_rp_read_new . TABLES :   vbak . SELECT-OPTIONS :   s_vbeln  FOR  vbak - vbeln . SELECT  vbeln , erdat , erzet , ernam , auart         FROM  vbak         INTO  TABLE  @DATA ( lt_vbak )          WHERE  vbeln  IN  @s_vbeln . WRITE :   'Index value'  COLOR  5 . READ  T...
Read more

Concatenation new syntax( 7.4+ ).

Image
  Report REPORT  zab_rp_concat_7_4 . DATA :   lv_str1    TYPE  string  VALUE  'ajay' ,       lv_str2    TYPE  string  VALUE  'babu' ,       lv_str3    TYPE  string  VALUE  'varikallu' ,       lv_final1  TYPE  string ,       lv_final2  TYPE  string . CONCATENATE  lv_str1 lv_str2 lv_str3  INTO  lv_final1  SEPARATED  BY  space . WRITE :   /  'Old syntax: '  ,  lv_final1  COLOR  4 . lv_final2  =  | { lv_str1 } { lv_str2 } { lv_str3 } | . WRITE :   /  'New syntax: '  ,  lv_final2  COLOR  5 . Output ****** *********** ******** Thank You ****** ******* *********
Read more