SAP SP_WAITFORCALL Function Module for
SP_WAITFORCALL is a standard sp waitforcall 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 sp waitforcall FM, simply by entering the name SP_WAITFORCALL into the relevant SAP transaction such as SE37 or SE38.
Function Group: PH1F
Program Name: SAPLPH1F
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SP_WAITFORCALL 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 'SP_WAITFORCALL'".
EXPORTING
WORKMODE = "
IMPORTING
HANDLE = "
REASON = "
TYPE_OF_REQUEST = "SAPphone: Type of Inbound Inquiry
ORIGINATOR = "SAPphone: Applicant - Originator
SENT_TO = "SAPphone: Type and Content of Address
TITLE = "SAPphone: Title
LINK = "SAPphone: Link
BAS_ID = "Routing: Value of an Attribute Group Member
TABLES
* EXTCALLS = "
CALLDATA = "
* EXTCALLS_PER_EXTENSION = "
EXCEPTIONS
SP_ERROR = 1 SP_CTI_FAILURE = 2
IMPORTING Parameters details for SP_WAITFORCALL
WORKMODE -
Data type: SP_WRKMODEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SP_WAITFORCALL
HANDLE -
Data type: SP_HANDLEOptional: No
Call by Reference: No ( called with pass by value option)
REASON -
Data type: SP_REASONOptional: No
Call by Reference: No ( called with pass by value option)
TYPE_OF_REQUEST - SAPphone: Type of Inbound Inquiry
Data type: SP_TYPE_RQOptional: No
Call by Reference: No ( called with pass by value option)
ORIGINATOR - SAPphone: Applicant - Originator
Data type: SPHADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
SENT_TO - SAPphone: Type and Content of Address
Data type: SPHADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
TITLE - SAPphone: Title
Data type: SP_TITLEOptional: No
Call by Reference: No ( called with pass by value option)
LINK - SAPphone: Link
Data type: SP_URLOptional: No
Call by Reference: No ( called with pass by value option)
BAS_ID - Routing: Value of an Attribute Group Member
Data type: SR_MEMBEROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SP_WAITFORCALL
EXTCALLS -
Data type: SPH_CSTATEOptional: Yes
Call by Reference: No ( called with pass by value option)
CALLDATA -
Data type: SPH_IOCONTOptional: No
Call by Reference: No ( called with pass by value option)
EXTCALLS_PER_EXTENSION -
Data type: SPH_TCSTATOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SP_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SP_CTI_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SP_WAITFORCALL 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_handle | TYPE SP_HANDLE, " | |||
| lt_extcalls | TYPE STANDARD TABLE OF SPH_CSTATE, " | |||
| lv_sp_error | TYPE SPH_CSTATE, " | |||
| lv_workmode | TYPE SP_WRKMODE, " | |||
| lv_reason | TYPE SP_REASON, " | |||
| lt_calldata | TYPE STANDARD TABLE OF SPH_IOCONT, " | |||
| lv_sp_cti_failure | TYPE SPH_IOCONT, " | |||
| lv_type_of_request | TYPE SP_TYPE_RQ, " | |||
| lt_extcalls_per_extension | TYPE STANDARD TABLE OF SPH_TCSTAT, " | |||
| lv_originator | TYPE SPHADDRESS, " | |||
| lv_sent_to | TYPE SPHADDRESS, " | |||
| lv_title | TYPE SP_TITLE, " | |||
| lv_link | TYPE SP_URL, " | |||
| lv_bas_id | TYPE SR_MEMBER. " |
|   CALL FUNCTION 'SP_WAITFORCALL' " |
| EXPORTING | ||
| WORKMODE | = lv_workmode | |
| IMPORTING | ||
| HANDLE | = lv_handle | |
| REASON | = lv_reason | |
| TYPE_OF_REQUEST | = lv_type_of_request | |
| ORIGINATOR | = lv_originator | |
| SENT_TO | = lv_sent_to | |
| TITLE | = lv_title | |
| LINK | = lv_link | |
| BAS_ID | = lv_bas_id | |
| TABLES | ||
| EXTCALLS | = lt_extcalls | |
| CALLDATA | = lt_calldata | |
| EXTCALLS_PER_EXTENSION | = lt_extcalls_per_extension | |
| EXCEPTIONS | ||
| SP_ERROR = 1 | ||
| SP_CTI_FAILURE = 2 | ||
| . " SP_WAITFORCALL | ||
ABAP code using 7.40 inline data declarations to call FM SP_WAITFORCALL
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