SAP RSPC_MIGRATE_JOB Function Module for Generate process from job









RSPC_MIGRATE_JOB is a standard rspc migrate job SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Generate process from job processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for rspc migrate job FM, simply by entering the name RSPC_MIGRATE_JOB into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSSM_PROCESS
Program Name: SAPLRSSM_PROCESS
Main Program: SAPLRSSM_PROCESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RSPC_MIGRATE_JOB pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'RSPC_MIGRATE_JOB'"Generate process from job
  EXPORTING
   I_JOBNAME =  "Background Job Name
   I_JOBCOUNT =  "Job ID

 IMPORTING
   E_TYPE =  "Process Type
   E_VARIANT =  "Process Variant (Name)
   E_EVENT_START =  "Background Processing Events
   E_EVENTP_START =  "Background Event Parameters (for Example, Jobname/Jobcount)
   E_EVENT_RED =  "Background Processing Events
   E_EVENTP_RED =  "Background Event Parameters (for Example, Jobname/Jobcount)
   E_EVENT_GREEN =  "Background Processing Events
   E_EVENTP_GREEN =  "Background Event Parameters (for Example, Jobname/Jobcount)

EXCEPTIONS
   JOB_INVALID = 1    FAILED = 2
.



IMPORTING Parameters details for RSPC_MIGRATE_JOB

I_JOBNAME - Background Job Name

Data type: BTCJOB
Optional: No
Call by Reference: Yes

I_JOBCOUNT - Job ID

Data type: BTCJOBCNT
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for RSPC_MIGRATE_JOB

E_TYPE - Process Type

Data type: RSPC_TYPE
Optional: No
Call by Reference: Yes

E_VARIANT - Process Variant (Name)

Data type: RSPC_VARIANT
Optional: No
Call by Reference: Yes

E_EVENT_START - Background Processing Events

Data type: BTCEVENTID
Optional: No
Call by Reference: Yes

E_EVENTP_START - Background Event Parameters (for Example, Jobname/Jobcount)

Data type: BTCEVTPARM
Optional: No
Call by Reference: Yes

E_EVENT_RED - Background Processing Events

Data type: BTCEVENTID
Optional: No
Call by Reference: Yes

E_EVENTP_RED - Background Event Parameters (for Example, Jobname/Jobcount)

Data type: BTCEVTPARM
Optional: No
Call by Reference: Yes

E_EVENT_GREEN - Background Processing Events

Data type: BTCEVENTID
Optional: No
Call by Reference: Yes

E_EVENTP_GREEN - Background Event Parameters (for Example, Jobname/Jobcount)

Data type: BTCEVTPARM
Optional: No
Call by Reference: Yes

EXCEPTIONS details

JOB_INVALID - Error in Batch processing

Data type:
Optional: No
Call by Reference: Yes

FAILED - Crap!

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSPC_MIGRATE_JOB Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_e_type  TYPE RSPC_TYPE, "   
lv_i_jobname  TYPE BTCJOB, "   
lv_job_invalid  TYPE BTCJOB, "   
lv_failed  TYPE BTCJOB, "   
lv_e_variant  TYPE RSPC_VARIANT, "   
lv_i_jobcount  TYPE BTCJOBCNT, "   
lv_e_event_start  TYPE BTCEVENTID, "   
lv_e_eventp_start  TYPE BTCEVTPARM, "   
lv_e_event_red  TYPE BTCEVENTID, "   
lv_e_eventp_red  TYPE BTCEVTPARM, "   
lv_e_event_green  TYPE BTCEVENTID, "   
lv_e_eventp_green  TYPE BTCEVTPARM. "   

  CALL FUNCTION 'RSPC_MIGRATE_JOB'  "Generate process from job
    EXPORTING
         I_JOBNAME = lv_i_jobname
         I_JOBCOUNT = lv_i_jobcount
    IMPORTING
         E_TYPE = lv_e_type
         E_VARIANT = lv_e_variant
         E_EVENT_START = lv_e_event_start
         E_EVENTP_START = lv_e_eventp_start
         E_EVENT_RED = lv_e_event_red
         E_EVENTP_RED = lv_e_eventp_red
         E_EVENT_GREEN = lv_e_event_green
         E_EVENTP_GREEN = lv_e_eventp_green
    EXCEPTIONS
        JOB_INVALID = 1
        FAILED = 2
. " RSPC_MIGRATE_JOB




ABAP code using 7.40 inline data declarations to call FM RSPC_MIGRATE_JOB

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!