SAP RSPC_PROCESS_FINISH_ASYNC Function Module for Confirming completion of the process asynchronously









RSPC_PROCESS_FINISH_ASYNC is a standard rspc process finish async SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Confirming completion of the process asynchronously 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 process finish async FM, simply by entering the name RSPC_PROCESS_FINISH_ASYNC into the relevant SAP transaction such as SE37 or SE38.

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



Function RSPC_PROCESS_FINISH_ASYNC 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_PROCESS_FINISH_ASYNC'"Confirming completion of the process asynchronously
  EXPORTING
*  I_USE_JOBNAME =  "If run as a job: name of a background job
*  I_JOB_COUNT =  "Job ID
*  I_BATCHDATE =  "Release date for background schedule
*  I_BATCHTIME =  "Release time of scheduled background job
*  I_AS_JOB =  "Always run as a job, not only for entry into RSADMIN
   I_LOGID =  "Log-ID of a Process Chain Run
*  I_CHAIN =  "Process Chain
   I_TYPE =  "Process Type
   I_VARIANT =  "Process Variant (Name)
   I_INSTANCE =  "Process Instance (Value)
*  I_STATE =  "Status of a Process
*  I_EVENTNO =  "Case; Decision; Event Number

EXCEPTIONS
   FAILED = 1
.



IMPORTING Parameters details for RSPC_PROCESS_FINISH_ASYNC

I_USE_JOBNAME - If run as a job: name of a background job

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

I_JOB_COUNT - Job ID

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

I_BATCHDATE - Release date for background schedule

Data type: BTCRELDT
Optional: Yes
Call by Reference: Yes

I_BATCHTIME - Release time of scheduled background job

Data type: BTCRELTM
Optional: Yes
Call by Reference: Yes

I_AS_JOB - Always run as a job, not only for entry into RSADMIN

Data type: RS_BOOL
Optional: Yes
Call by Reference: Yes

I_LOGID - Log-ID of a Process Chain Run

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

I_CHAIN - Process Chain

Data type: RSPC_CHAIN
Optional: Yes
Call by Reference: Yes

I_TYPE - Process Type

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

I_VARIANT - Process Variant (Name)

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

I_INSTANCE - Process Instance (Value)

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

I_STATE - Status of a Process

Data type: RSPC_STATE
Optional: Yes
Call by Reference: Yes

I_EVENTNO - Case; Decision; Event Number

Data type: RSPC_EVENTNO
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSPC_PROCESS_FINISH_ASYNC 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_failed  TYPE STRING, "   
lv_i_use_jobname  TYPE BTCJOB, "   
lv_i_job_count  TYPE BTCJOBCNT, "   
lv_i_batchdate  TYPE BTCRELDT, "   
lv_i_batchtime  TYPE BTCRELTM, "   
lv_i_as_job  TYPE RS_BOOL, "   
lv_i_logid  TYPE RSPC_LOGID, "   
lv_i_chain  TYPE RSPC_CHAIN, "   
lv_i_type  TYPE RSPC_TYPE, "   
lv_i_variant  TYPE RSPC_VARIANT, "   
lv_i_instance  TYPE RSPC_INSTANCE, "   
lv_i_state  TYPE RSPC_STATE, "   
lv_i_eventno  TYPE RSPC_EVENTNO. "   

  CALL FUNCTION 'RSPC_PROCESS_FINISH_ASYNC'  "Confirming completion of the process asynchronously
    EXPORTING
         I_USE_JOBNAME = lv_i_use_jobname
         I_JOB_COUNT = lv_i_job_count
         I_BATCHDATE = lv_i_batchdate
         I_BATCHTIME = lv_i_batchtime
         I_AS_JOB = lv_i_as_job
         I_LOGID = lv_i_logid
         I_CHAIN = lv_i_chain
         I_TYPE = lv_i_type
         I_VARIANT = lv_i_variant
         I_INSTANCE = lv_i_instance
         I_STATE = lv_i_state
         I_EVENTNO = lv_i_eventno
    EXCEPTIONS
        FAILED = 1
. " RSPC_PROCESS_FINISH_ASYNC




ABAP code using 7.40 inline data declarations to call FM RSPC_PROCESS_FINISH_ASYNC

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!