SAP SP_CALL_ATTACHED_DATA_GET_PD Function Module for









SP_CALL_ATTACHED_DATA_GET_PD is a standard sp call attached data get pd 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 call attached data get pd FM, simply by entering the name SP_CALL_ATTACHED_DATA_GET_PD into the relevant SAP transaction such as SE37 or SE38.

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



Function SP_CALL_ATTACHED_DATA_GET_PD 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_CALL_ATTACHED_DATA_GET_PD'"
  EXPORTING
   HANDLE =  "

 IMPORTING
   PD_GUID =  "Planned Call GUID
   END_TMSP =  "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
   PD_ADDRESS =  "
   PD_CALLID =  "
   PD_TELNO1 =  "
   PD_TELNO2 =  "
   PD_TELNO3 =  "
   PD_FINISHED =  "
   CAMPAIGNID =  "SAPphone: Automatic Dialing Campaign ID
   START_TMSP =  "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

EXCEPTIONS
   NO_PD_CALL = 1    SP_ERROR = 2    SP_CTI_FAILURE = 3
.



IMPORTING Parameters details for SP_CALL_ATTACHED_DATA_GET_PD

HANDLE -

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

EXPORTING Parameters details for SP_CALL_ATTACHED_DATA_GET_PD

PD_GUID - Planned Call GUID

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

END_TMSP - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

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

PD_ADDRESS -

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

PD_CALLID -

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

PD_TELNO1 -

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

PD_TELNO2 -

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

PD_TELNO3 -

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

PD_FINISHED -

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

CAMPAIGNID - SAPphone: Automatic Dialing Campaign ID

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

START_TMSP - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

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

EXCEPTIONS details

NO_PD_CALL -

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

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_CALL_ATTACHED_DATA_GET_PD 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, "   
lv_pd_guid  TYPE SP_PCGUID, "   
lv_no_pd_call  TYPE SP_PCGUID, "   
lv_end_tmsp  TYPE TIMESTAMP, "   
lv_sp_error  TYPE TIMESTAMP, "   
lv_pd_address  TYPE ADDR_KEY, "   
lv_pd_callid  TYPE SP_CALLID, "   
lv_sp_cti_failure  TYPE SP_CALLID, "   
lv_pd_telno1  TYPE SPH_PDTEL, "   
lv_pd_telno2  TYPE SPH_PDTEL, "   
lv_pd_telno3  TYPE SPH_PDTEL, "   
lv_pd_finished  TYPE SP_BOOLEAN, "   
lv_campaignid  TYPE SP_CAMPID, "   
lv_start_tmsp  TYPE TIMESTAMP. "   

  CALL FUNCTION 'SP_CALL_ATTACHED_DATA_GET_PD'  "
    EXPORTING
         HANDLE = lv_handle
    IMPORTING
         PD_GUID = lv_pd_guid
         END_TMSP = lv_end_tmsp
         PD_ADDRESS = lv_pd_address
         PD_CALLID = lv_pd_callid
         PD_TELNO1 = lv_pd_telno1
         PD_TELNO2 = lv_pd_telno2
         PD_TELNO3 = lv_pd_telno3
         PD_FINISHED = lv_pd_finished
         CAMPAIGNID = lv_campaignid
         START_TMSP = lv_start_tmsp
    EXCEPTIONS
        NO_PD_CALL = 1
        SP_ERROR = 2
        SP_CTI_FAILURE = 3
. " SP_CALL_ATTACHED_DATA_GET_PD




ABAP code using 7.40 inline data declarations to call FM SP_CALL_ATTACHED_DATA_GET_PD

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!