SAP SPI_REPLACE_AGENT_DB Function Module for









SPI_REPLACE_AGENT_DB is a standard spi replace agent db 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 spi replace agent db FM, simply by entering the name SPI_REPLACE_AGENT_DB into the relevant SAP transaction such as SE37 or SE38.

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



Function SPI_REPLACE_AGENT_DB 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 'SPI_REPLACE_AGENT_DB'"
EXPORTING
IP_AGENT_ID = "
IS_SSPIAGD = "

TABLES
IT_SSPIAGD_T = "
IT_SSPIAGFLD_T = "
IT_SSPIAGFLD = "
.



IMPORTING Parameters details for SPI_REPLACE_AGENT_DB

IP_AGENT_ID -

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

IS_SSPIAGD -

Data type: SSPIAGD
Optional: No
Call by Reference: Yes

TABLES Parameters details for SPI_REPLACE_AGENT_DB

IT_SSPIAGD_T -

Data type: SSPIAGD_T
Optional: No
Call by Reference: Yes

IT_SSPIAGFLD_T -

Data type: SSPIAGFLD_T
Optional: No
Call by Reference: Yes

IT_SSPIAGFLD -

Data type: SSPIAGFLD
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SPI_REPLACE_AGENT_DB 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_ip_agent_id  TYPE SPIAGNTID, "   
lt_it_sspiagd_t  TYPE STANDARD TABLE OF SSPIAGD_T, "   
lv_is_sspiagd  TYPE SSPIAGD, "   
lt_it_sspiagfld_t  TYPE STANDARD TABLE OF SSPIAGFLD_T, "   
lt_it_sspiagfld  TYPE STANDARD TABLE OF SSPIAGFLD. "   

  CALL FUNCTION 'SPI_REPLACE_AGENT_DB'  "
    EXPORTING
         IP_AGENT_ID = lv_ip_agent_id
         IS_SSPIAGD = lv_is_sspiagd
    TABLES
         IT_SSPIAGD_T = lt_it_sspiagd_t
         IT_SSPIAGFLD_T = lt_it_sspiagfld_t
         IT_SSPIAGFLD = lt_it_sspiagfld
. " SPI_REPLACE_AGENT_DB




ABAP code using 7.40 inline data declarations to call FM SPI_REPLACE_AGENT_DB

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!