RH_FPM_INITIAL_START_JOB SAP Function module

RH_FPM_INITIAL_START_JOB is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name RH_FPM_INITIAL_START_JOB into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: RHFPM_FUNCTIONS
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM RH_FPM_INITIAL_START_JOB - RH FPM INITIAL START JOB

CALL FUNCTION 'RH_FPM_INITIAL_START_JOB' "
  EXPORTING
    p_job_number =              " tbtcjob-jobcount
    p_job_name =                " btcjob
    p_ar_parameters =           " arc_params
    p_pri_parameters =          " pri_params
    p_runid =                   " hrfpm_runid
    p_schedman_key =            " schedman_key
*   p_srvgrp =                  " bpsrvgrp
*   p_no_enq =                  " flag
  EXCEPTIONS
    ERROR_OCCURRED = 1          "
    .  "  RH_FPM_INITIAL_START_JOB

ABAP code example for Function Module RH_FPM_INITIAL_START_JOB

The ABAP code below is a full code listing to execute function module RH_FPM_INITIAL_START_JOB including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA(ld_p_job_number) = some text here

DATA(ld_p_job_name) = 'Check type of data required'.

DATA(ld_p_ar_parameters) = 'Check type of data required'.

DATA(ld_p_pri_parameters) = 'Check type of data required'.

DATA(ld_p_runid) = 'Check type of data required'.

DATA(ld_p_schedman_key) = 'Check type of data required'.

DATA(ld_p_srvgrp) = 'Check type of data required'.

DATA(ld_p_no_enq) = 'Check type of data required'.
.

CALL FUNCTION 'RH_FPM_INITIAL_START_JOB'
  EXPORTING
    p_job_number =               ld_p_job_number
    p_job_name =                 ld_p_job_name
    p_ar_parameters =            ld_p_ar_parameters
    p_pri_parameters =           ld_p_pri_parameters
    p_runid =                    ld_p_runid
    p_schedman_key =             ld_p_schedman_key
*   p_srvgrp =                   ld_p_srvgrp
*   p_no_enq =                   ld_p_no_enq
  EXCEPTIONS
    ERROR_OCCURRED =             1
    .  "  RH_FPM_INITIAL_START_JOB

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_p_job_number
 
 TYPE TBTCJOB-JOBCOUNT ,
ld_p_job_name
 
 TYPE BTCJOB ,
ld_p_ar_parameters
 
 TYPE ARC_PARAMS ,
ld_p_pri_parameters
 
 TYPE PRI_PARAMS ,
ld_p_runid
 
 TYPE HRFPM_RUNID ,
ld_p_schedman_key
 
 TYPE SCHEDMAN_KEY ,
ld_p_srvgrp
 
 TYPE BPSRVGRP ,
ld_p_no_enq
 
 TYPE FLAG .



ld_p_job_number = some text here
ld_p_job_name = 'Check type of data required'.
ld_p_ar_parameters = 'Check type of data required'.
ld_p_pri_parameters = 'Check type of data required'.
ld_p_runid = 'Check type of data required'.
ld_p_schedman_key = 'Check type of data required'.
ld_p_srvgrp = 'Check type of data required'.
ld_p_no_enq = 'Check type of data required'.