Quantcast
Channel: SCN: Message List - Software Support and Maintenance
Viewing all articles
Browse latest Browse all 2823

Use HR_INFOTYPE_OPERATION with nocommit option

$
0
0

Hi,

  I used to use HR_INFOTYPE_OPERATION to create or update a infotype record with NOCOMMIT = 'X' . My calling program will either commit or rollback the work depending on whether the program is running in test mode or live mode. This approach has been working until recently(after support pack upgrade.) I found that the infotype is always committed to database even thought I have NOCOMMIT = 'X' and has ROLLBACK WORK after the call. Does anyone encounter this issue? and how do you fix it?

 

Further research indicates there are changes to HR_MAINTAIN_MASTERDATA, which is called from HR_INFOTYPE_OPERATION, that I think may cause the update to always commit. The new codes added for luw_mode = '0' or '1' or '2' are as the following:

 

        import tbuff buffer_dir del_pclx_tab from

         memory id 'TBUFF'.

        perform import_plog_tab(sapfp50p).                  "YSFN742479

        perform put_infotyp_buffer_commit(sapfp50p) tables ps

                                                           psinfo

                                                           preftab

                                                    using  pspar.

        perform refresh_buffer on commit level 2.          "MELN2130745

 

Regards,

Anna


Viewing all articles
Browse latest Browse all 2823

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>