SAP SP_MODIFY_PDCALL Function Module for









SP_MODIFY_PDCALL is a standard sp modify pdcall 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 modify pdcall FM, simply by entering the name SP_MODIFY_PDCALL into the relevant SAP transaction such as SE37 or SE38.

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



Function SP_MODIFY_PDCALL 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_MODIFY_PDCALL'"
  EXPORTING
   GUID =  "Planned Call GUID
*  NUMBER2 =  "
*  COUNTRY2 =  "
*  STARTTIME2 =  "
*  ENDTIME2 =  "
*  NUMBER3 =  "
*  COUNTRY3 =  "
*  STARTTIME3 =  "
*  ENDTIME3 =  "
*  START_TMSP =  "
*  END_TMSP =  "
*  ADDRNUMBER =  "
*  FINISHED =  "
*  PERSNUMBER =  "
*  ADDR_TYPE =  "
*  F_SELECT_NEW =  "
*  NUMBER1 =  "
*  COUNTRY1 =  "
*  STARTTIME1 =  "
*  ENDTIME1 =  "

 IMPORTING
   PDERROR =  "3-Byte Field

EXCEPTIONS
   SP_ERROR = 1    SP_CTI_FAILURE = 2    PLANNED_CALL_NOT_DOWNLOADED = 3
.



IMPORTING Parameters details for SP_MODIFY_PDCALL

GUID - Planned Call GUID

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

NUMBER2 -

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

COUNTRY2 -

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

STARTTIME2 -

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

ENDTIME2 -

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

NUMBER3 -

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

COUNTRY3 -

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

STARTTIME3 -

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

ENDTIME3 -

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

START_TMSP -

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

END_TMSP -

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

ADDRNUMBER -

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

FINISHED -

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

PERSNUMBER -

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

ADDR_TYPE -

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

F_SELECT_NEW -

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

NUMBER1 -

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

COUNTRY1 -

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

STARTTIME1 -

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

ENDTIME1 -

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

EXPORTING Parameters details for SP_MODIFY_PDCALL

PDERROR - 3-Byte Field

Data type: CHAR3
Optional: No
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)

PLANNED_CALL_NOT_DOWNLOADED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SP_MODIFY_PDCALL 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_guid  TYPE SP_PCGUID, "   
lv_pderror  TYPE CHAR3, "   
lv_sp_error  TYPE CHAR3, "   
lv_number2  TYPE SP_TELNO, "   
lv_country2  TYPE LAND1, "   
lv_starttime2  TYPE SP_TIME, "   
lv_endtime2  TYPE SP_TIME, "   
lv_number3  TYPE SP_TELNO, "   
lv_country3  TYPE LAND1, "   
lv_starttime3  TYPE SP_TIME, "   
lv_endtime3  TYPE SP_TIME, "   
lv_start_tmsp  TYPE TIMESTAMP, "   
lv_end_tmsp  TYPE TIMESTAMP, "   
lv_addrnumber  TYPE AD_ADDRNUM, "   
lv_sp_cti_failure  TYPE AD_ADDRNUM, "   
lv_finished  TYPE CHAR1, "   
lv_persnumber  TYPE AD_PERSNUM, "   
lv_planned_call_not_downloaded  TYPE AD_PERSNUM, "   
lv_addr_type  TYPE AD_ADRTYPE, "   
lv_f_select_new  TYPE SP_BOOLEAN, "   
lv_number1  TYPE SP_TELNO, "   
lv_country1  TYPE LAND1, "   
lv_starttime1  TYPE SP_TIME, "   
lv_endtime1  TYPE SP_TIME. "   

  CALL FUNCTION 'SP_MODIFY_PDCALL'  "
    EXPORTING
         GUID = lv_guid
         NUMBER2 = lv_number2
         COUNTRY2 = lv_country2
         STARTTIME2 = lv_starttime2
         ENDTIME2 = lv_endtime2
         NUMBER3 = lv_number3
         COUNTRY3 = lv_country3
         STARTTIME3 = lv_starttime3
         ENDTIME3 = lv_endtime3
         START_TMSP = lv_start_tmsp
         END_TMSP = lv_end_tmsp
         ADDRNUMBER = lv_addrnumber
         FINISHED = lv_finished
         PERSNUMBER = lv_persnumber
         ADDR_TYPE = lv_addr_type
         F_SELECT_NEW = lv_f_select_new
         NUMBER1 = lv_number1
         COUNTRY1 = lv_country1
         STARTTIME1 = lv_starttime1
         ENDTIME1 = lv_endtime1
    IMPORTING
         PDERROR = lv_pderror
    EXCEPTIONS
        SP_ERROR = 1
        SP_CTI_FAILURE = 2
        PLANNED_CALL_NOT_DOWNLOADED = 3
. " SP_MODIFY_PDCALL




ABAP code using 7.40 inline data declarations to call FM SP_MODIFY_PDCALL

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!