SAP CONSULT_CALL_PROCESS Function Module for









CONSULT_CALL_PROCESS is a standard consult call process 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 consult call process FM, simply by entering the name CONSULT_CALL_PROCESS into the relevant SAP transaction such as SE37 or SE38.

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



Function CONSULT_CALL_PROCESS 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 'CONSULT_CALL_PROCESS'"
EXPORTING
* TEL_NUMBER = "
* COUNTRY_TO = "
* ADDRESS_NUMBER = "
* DISPLAY_POPUP = 'X' "
REF_HANDLE = "
* POPUP_MODE = 'X' "

IMPORTING
HANDLE_OUT = "

TABLES
* EXTCALLS = "
* CALLDATA = "
* EXTCALLS_PER_EXTENSION = "

EXCEPTIONS
SP_ERROR = 1 SP_CTI_FAILURE = 2
.



IMPORTING Parameters details for CONSULT_CALL_PROCESS

TEL_NUMBER -

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

COUNTRY_TO -

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

ADDRESS_NUMBER -

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

DISPLAY_POPUP -

Data type: SPH_BOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

REF_HANDLE -

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

POPUP_MODE -

Data type: SP_BOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CONSULT_CALL_PROCESS

HANDLE_OUT -

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

TABLES Parameters details for CONSULT_CALL_PROCESS

EXTCALLS -

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

CALLDATA -

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

EXTCALLS_PER_EXTENSION -

Data type: SPH_TCSTAT
Optional: 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 CONSULT_CALL_PROCESS 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:
lt_extcalls  TYPE STANDARD TABLE OF SPH_CSTATE, "   
lv_sp_error  TYPE SPH_CSTATE, "   
lv_handle_out  TYPE SPH_CALL-HANDLE, "   
lv_tel_number  TYPE SPH_CALL-NO_DIALED, "   
lt_calldata  TYPE STANDARD TABLE OF SPH_IOCONT, "   
lv_country_to  TYPE T005-LAND1, "   
lv_sp_cti_failure  TYPE T005, "   
lv_address_number  TYPE ADDR_KEY, "   
lt_extcalls_per_extension  TYPE STANDARD TABLE OF SPH_TCSTAT, "   
lv_display_popup  TYPE SPH_BOOLEAN, "   'X'
lv_ref_handle  TYPE SPH_CALL-HANDLE, "   
lv_popup_mode  TYPE SP_BOOLEAN. "   'X'

  CALL FUNCTION 'CONSULT_CALL_PROCESS'  "
    EXPORTING
         TEL_NUMBER = lv_tel_number
         COUNTRY_TO = lv_country_to
         ADDRESS_NUMBER = lv_address_number
         DISPLAY_POPUP = lv_display_popup
         REF_HANDLE = lv_ref_handle
         POPUP_MODE = lv_popup_mode
    IMPORTING
         HANDLE_OUT = lv_handle_out
    TABLES
         EXTCALLS = lt_extcalls
         CALLDATA = lt_calldata
         EXTCALLS_PER_EXTENSION = lt_extcalls_per_extension
    EXCEPTIONS
        SP_ERROR = 1
        SP_CTI_FAILURE = 2
. " CONSULT_CALL_PROCESS




ABAP code using 7.40 inline data declarations to call FM CONSULT_CALL_PROCESS

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 HANDLE FROM SPH_CALL INTO @DATA(ld_handle_out).
 
"SELECT single NO_DIALED FROM SPH_CALL INTO @DATA(ld_tel_number).
 
 
"SELECT single LAND1 FROM T005 INTO @DATA(ld_country_to).
 
 
 
 
DATA(ld_display_popup) = 'X'.
 
"SELECT single HANDLE FROM SPH_CALL INTO @DATA(ld_ref_handle).
 
DATA(ld_popup_mode) = 'X'.
 


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!