SAP RSPLFB_RFC_SERVICE_LOAD_DEBUG Function Module for Load a Service Using Name

Search SAP Function Modules

RSPLFB_RFC_SERVICE_LOAD_DEBUG is a standard rsplfb rfc service load debug SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Load a Service Using Name processing and below is the pattern details for this FM, 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 rsplfb rfc service load debug FM, simply by entering the name RSPLFB_RFC_SERVICE_LOAD_DEBUG into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSPLFB_RFC
Program Name: SAPLRSPLFB_RFC
Main Program: SAPLRSPLFB_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RSPLFB_RFC_SERVICE_LOAD_DEBUG 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 'RSPLFB_RFC_SERVICE_LOAD_DEBUG'"Load a Service Using Name
  EXPORTING
   I_FOR_UPDATE =  "'X' Lock for Changes
   I_SRVNAME =  "Name (ID) of Planning Service

 IMPORTING
   ES_SRVTYPE =  "Service Type Definition, RFC
   ES_INFOPROV_DESC =  "InfoProvider Description
   ES_SERVICE =  "Planning Service, RFC
   E_T_SRV_BAPIRET2 =  "Bapiret2 with Information on Localizing Errors
   E_RETURN =  "Return Value for RFC

.

IMPORTING Parameters details for RSPLFB_RFC_SERVICE_LOAD_DEBUG

I_FOR_UPDATE - 'X' Lock for Changes

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

I_SRVNAME - Name (ID) of Planning Service

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

EXPORTING Parameters details for RSPLFB_RFC_SERVICE_LOAD_DEBUG

ES_SRVTYPE - Service Type Definition, RFC

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

ES_INFOPROV_DESC - InfoProvider Description

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

ES_SERVICE - Planning Service, RFC

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

E_T_SRV_BAPIRET2 - Bapiret2 with Information on Localizing Errors

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

E_RETURN - Return Value for RFC

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

Copy and paste ABAP code example for RSPLFB_RFC_SERVICE_LOAD_DEBUG 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.

ABAP code using 7.40 inline data declarations to call FM RSPLFB_RFC_SERVICE_LOAD_DEBUG

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