Analyze PERFORM ON COMMIT vs. CALL FUNCTION IN UPDATE TASK

[brunobex]

This blog demonstrates a scenario for updating a transparent table using (PERFORM ON COMMIT) and (CALL FUNCTION IN UPDATE TASK).

The main goal is to show what is most priority and the global variables flow.

I did this test in 2008 but only now am publishing with the creation of my blog.

Create transparent table

Create the table with fields bellow:

Create Function

Create the function module bellow with processing type in (update module):

Add the field parameter I_COUNTER

Put the source code in function.

FUNCTION ZBR_FUNCTION. *"---------------------------------------------------------------------- *"*"Update function module: *" *"*"Local interface: *"  IMPORTING *"     VALUE(I_COUNTER) TYPE  P08_CNT *"----------------------------------------------------------------------  *Create a work area  data: wa_zbr_table type zbr_table.  *Wait 1 second  wait up to 1 seconds.  *Add 1 to the input field I_COUNTER  add 1 to i_counter.  *Fill the work area  wa_zbr_table-zdate           = sy-datum.  wa_zbr_table-zhour           = sy-uzeit.  wa_zbr_table-zcounter      = i_counter.  wa_zbr_table-zdescription = 'FUNCTION'.       *Insert the registry in the table  insert zbr_table from wa_zbr_table.  ENDFUNCTION.

Create report executable program

Create the program with the source code below:

REPORT ZR_BR_PROGRAM no standard page heading.  *Work area data: wa_zbr_table type zbr_table.  *Starting with 1 wa_zbr_table-zcounter = 1.  *Determines the sequence execute = 2 perform f_write_2 on commit LEVEL 2.  *Add 1 to the field WA_ZBR_TABLE-ZCOUNTER add 1 to wa_zbr_table-zcounter.  *call the function in update task CALL FUNCTION 'ZBR_FUNCTION' IN UPDATE TASK   EXPORTING     i_counter       = wa_zbr_table-zcounter.  *Add 1 to the field WA_ZBR_TABLE-ZCOUNTER add 1 to wa_zbr_table-zcounter.  *Determines the sequence execute = 1 perform f_write_1 on commit LEVEL 1.  *Add 1 to the field WA_ZBR_TABLE-ZCOUNTER add 1 to wa_zbr_table-zcounter.  *call the function in update task CALL FUNCTION 'ZBR_FUNCTION' IN UPDATE TASK   EXPORTING     i_counter       = wa_zbr_table-zcounter.  *Executes a database commit and *makes the program wait until the type V1 updates have been completed.  commit work and wait.  *&--------------------------------------------------------------------- *&      Form  f_write_1 *&--------------------------------------------------------------------- form f_write_1 . *Output to a list  write: /001 'In WRITE_1 counter value:', wa_zbr_table-zcounter.  *Wait 1 second  wait up to 1 seconds.  *Fill the work area  wa_zbr_table-zdate           = sy-datum.  wa_zbr_table-zhour           = sy-uzeit.  wa_zbr_table-zdescription = 'WRITE_1'.       *Insert the registry in the table  insert zbr_table from wa_zbr_table.  *Add 1 to the field WA_ZBR_TABLE-ZCOUNTER  add 1 to wa_zbr_table-zcounter. endform.                    " f_write_1 *&--------------------------------------------------------------------- *&      Form  f_write_2 *&--------------------------------------------------------------------- form f_write_2 . *Output to a list  write: /001 'In WRITE_2 counter value:', wa_zbr_table-zcounter.  *Wait 1 second  wait up to 1 seconds.  *Fill the work area  wa_zbr_table-zdate        = sy-datum.  wa_zbr_table-zhour        = sy-uzeit.  wa_zbr_table-zdescription = 'WRITE_2'.       *Insert the registry in the table  insert zbr_table from wa_zbr_table.  *Add 1 to the field WA_ZBR_TABLE-ZCOUNTER  add 1 to wa_zbr_table-zcounter. endform.                    " f_write_2

Results of execution and Conclusion

Result in output list:

Result in table:

Looking the result above, you can note that (PERFORM ON COMMIT) is executed before the (CALL FUNCTION IN UPDATE TASK).

However, (CALL FUNCTION IN UPDATE TASK) the value parameter imported to execute the function module are those current at the time of the call.

The (PERFORM ON COMMIT) global data values takes the current at the time of the command COMMIT.

Related Content

http://help.sap.com/saphelp_nw04/Helpdata/EN/41/7af4e3a79e11d1950f0000e82de14a/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/41/7af4e0a79e11d1950f0000e82de14a/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/41/7af4dda79e11d1950f0000e82de14a/content.htm

---

Thanks to friends Fabricio Souza and Rodrigo Ferrari that needed this theory and decided to share with you the knowledge.