SAP SPTA_PARA_PROCESS_START_2 Function Module for









SPTA_PARA_PROCESS_START_2 is a standard spta para process start 2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 spta para process start 2 FM, simply by entering the name SPTA_PARA_PROCESS_START_2 into the relevant SAP transaction such as SE37 or SE38.

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



Function SPTA_PARA_PROCESS_START_2 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 'SPTA_PARA_PROCESS_START_2'"
EXPORTING
SERVER_GROUP = "
* MAX_NO_OF_TASKS = "
BEFORE_RFC_CALLBACK_FORM = "
IN_RFC_CALLBACK_FORM = "
AFTER_RFC_CALLBACK_FORM = "
CALLBACK_PROG = "
* SHOW_STATUS = ' ' "
* RESOURCE_TIMEOUT = 600 "
* TASK_CALL_MODE = 1 "

CHANGING
* USER_PARAM = "

EXCEPTIONS
INVALID_SERVER_GROUP = 1 NO_RESOURCES_AVAILABLE = 2
.



IMPORTING Parameters details for SPTA_PARA_PROCESS_START_2

SERVER_GROUP -

Data type: SPTA_RFCGR
Optional: No
Call by Reference: No ( called with pass by value option)

MAX_NO_OF_TASKS -

Data type: SY-INDEX
Optional: Yes
Call by Reference: No ( called with pass by value option)

BEFORE_RFC_CALLBACK_FORM -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

IN_RFC_CALLBACK_FORM -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

AFTER_RFC_CALLBACK_FORM -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CALLBACK_PROG -

Data type: SY-REPID
Optional: No
Call by Reference: No ( called with pass by value option)

SHOW_STATUS -

Data type: XFLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

RESOURCE_TIMEOUT -

Data type: I
Default: 600
Optional: Yes
Call by Reference: No ( called with pass by value option)

TASK_CALL_MODE -

Data type: SPTA_TCM
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for SPTA_PARA_PROCESS_START_2

USER_PARAM -

Data type:
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

INVALID_SERVER_GROUP -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_RESOURCES_AVAILABLE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SPTA_PARA_PROCESS_START_2 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_user_param  TYPE STRING, "   
lv_server_group  TYPE SPTA_RFCGR, "   
lv_invalid_server_group  TYPE SPTA_RFCGR, "   
lv_max_no_of_tasks  TYPE SY-INDEX, "   
lv_no_resources_available  TYPE SY, "   
lv_before_rfc_callback_form  TYPE SY, "   
lv_in_rfc_callback_form  TYPE SY, "   
lv_after_rfc_callback_form  TYPE SY, "   
lv_callback_prog  TYPE SY-REPID, "   
lv_show_status  TYPE XFLAG, "   SPACE
lv_resource_timeout  TYPE I, "   600
lv_task_call_mode  TYPE SPTA_TCM. "   1

  CALL FUNCTION 'SPTA_PARA_PROCESS_START_2'  "
    EXPORTING
         SERVER_GROUP = lv_server_group
         MAX_NO_OF_TASKS = lv_max_no_of_tasks
         BEFORE_RFC_CALLBACK_FORM = lv_before_rfc_callback_form
         IN_RFC_CALLBACK_FORM = lv_in_rfc_callback_form
         AFTER_RFC_CALLBACK_FORM = lv_after_rfc_callback_form
         CALLBACK_PROG = lv_callback_prog
         SHOW_STATUS = lv_show_status
         RESOURCE_TIMEOUT = lv_resource_timeout
         TASK_CALL_MODE = lv_task_call_mode
    CHANGING
         USER_PARAM = lv_user_param
    EXCEPTIONS
        INVALID_SERVER_GROUP = 1
        NO_RESOURCES_AVAILABLE = 2
. " SPTA_PARA_PROCESS_START_2




ABAP code using 7.40 inline data declarations to call FM SPTA_PARA_PROCESS_START_2

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.

 
 
 
"SELECT single INDEX FROM SY INTO @DATA(ld_max_no_of_tasks).
 
 
 
 
 
"SELECT single REPID FROM SY INTO @DATA(ld_callback_prog).
 
DATA(ld_show_status) = ' '.
 
DATA(ld_resource_timeout) = 600.
 
DATA(ld_task_call_mode) = 1.
 


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!