Function Module RH_UPDATE_INFTY throwing odd error

Question

I am trying to update a relationship using this FM, however I keep getting the error "No input help is available" which I assume is a false-negative.
I have traced the code through and the error is being thrown here:
    PERFORM RE777Z_RA(MSTT777Z) USING                      "VWMZB3A
            PPLOG-OTYPE PPLOG-INFTY PPLOG-SUBTY PPLOG-VDATA(2)
            PPPAR-TIMCO PPPAR-ADDCO PPPAR-SCLAS SUBRC.
    IF SUBRC GT 0.
      UI_SUBRC = 16.
      EXIT.
    ENDIF.
UI_SUBRC is getting set to 16, and it is failing. I have been trying for hours to get this and other related FMs to work correctly without luck. I managed to get RH_INSERT_INFTY to work, however it is not really acting as I want it to; hence this FM. The insert FM splits the records if you make an update to enda/begda which is undesirable. This thread details the problem and ther was no posted solution overwriting records in hrp1000
Here is what I have:
  DATA ls_p1001 TYPE p1001.
  DATA lt_p1001 TYPE STANDARD TABLE OF p1001.
  DATA ls_padd2 TYPE padd2.
  MOVE-CORRESPONDING is_dlgt_rprt TO ls_p1001.
  APPEND ls_p1001 TO lt_p1001.
  CALL FUNCTION 'RH_UPDATE_INFTY'
    EXPORTING
      vtask               = 'S'
*     order_flg           = 'X'
*     commit_flg          = 'X'
*     authy               = 'X'
*     pppar_imp           = ''
*     old_tabnr_new_langu = 'X'
*     repid               = sy-cprog
*     form                = ''
*     keep_lupd           = ''
*     workf_actv          = 'X'
    TABLES
      innnn               = lt_p1001
*     ILFCODE             = ILFCODE
    EXCEPTIONS
      error_during_update = 1
      no_authorization    = 2
      repid_form_initial  = 3
      corr_exit           = 4
      OTHERS              = 5.

Answer 1

Hi,
Please find documentation below:
FU RH_UPDATE_INFTY
Text
Change Infotype Records
Functionality
With this function module you can change multiple infotype records for OM objects from Personnel Planning database tables (HRPnnnn). The infotype tables of the table parameter INNNN must all have the structure Pnnnn (logical structure for the infotype nnnn). The records you want to change must exist in the Personnel Planning database tables. If not, this triggers the exception ERROR_DURING_UPDATE.
The values of the parameter VTASK (update type) mean the following:
- 'D' -> update in dialog
- 'S' -> synchronous update via the update task
- 'V' -> asynchronous update via the update task
- 'B' -> internal update in buffer only, no DB update
In HR applications the parameter should be set to 'D' for update in dialog. If there are multiple operations that logically belong together to be updated internally in the buffer first and then saved together to the database, you should set the parameter in each case to 'B' for internal update in buffer only, no DB update. The DB update is then executed by calling the function module 'RH_UPDATE_DATABASE'.
Parameters
VTASK
ORDER_FLG
COMMIT_FLG
AUTHY
PPPAR_IMP
OLD_TABNR_NEW_LANGU
REPID
FORM
KEEP_LUPD
WORKF_ACTV
INNNN
ILFCODE
Exceptions
ERROR_DURING_UPDATE
NO_AUTHORIZATION
REPID_FORM_INITIAL
CORR_EXIT
Thanks,
Sriram Ponna.