SAP SPI_REPLACE_PROCESS_DB Function Module for
SPI_REPLACE_PROCESS_DB is a standard spi replace process 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 process db FM, simply by entering the name SPI_REPLACE_PROCESS_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_PROCESS_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_PROCESS_DB'".
EXPORTING
IP_PROCESS_ID = "
IS_SSPIPD = "
TABLES
IT_SSPISGD_T = "
IT_SSPIPSRTFLD = "
IT_SSPIPSRFLD = "
IT_SSPIPSR = "
IT_SSPIPVD_T = "
IT_SSPIPVD = "
IT_SSPIPVC = "
IT_SSPIPD_T = "
IT_SSPISGCON = "
IT_SSPISGFLD_T = "
IT_SSPISGFLD = "
IT_SSPISGD = "
IT_SSPIPST_T = "
IT_SSPIPST = "
IT_SSPIPSD = "
IT_SSPIPDTA = "
IMPORTING Parameters details for SPI_REPLACE_PROCESS_DB
IP_PROCESS_ID -
Data type: SPIPROCTPOptional: No
Call by Reference: No ( called with pass by value option)
IS_SSPIPD -
Data type: SSPIPDOptional: No
Call by Reference: Yes
TABLES Parameters details for SPI_REPLACE_PROCESS_DB
IT_SSPISGD_T -
Data type: SSPISGD_TOptional: No
Call by Reference: Yes
IT_SSPIPSRTFLD -
Data type: SSPIPSRTFLDOptional: No
Call by Reference: Yes
IT_SSPIPSRFLD -
Data type: SSPIPSRFLDOptional: No
Call by Reference: Yes
IT_SSPIPSR -
Data type: SSPIPSROptional: No
Call by Reference: Yes
IT_SSPIPVD_T -
Data type: SSPIPVD_TOptional: No
Call by Reference: Yes
IT_SSPIPVD -
Data type: SSPIPVDOptional: No
Call by Reference: Yes
IT_SSPIPVC -
Data type: SSPIPVCOptional: No
Call by Reference: Yes
IT_SSPIPD_T -
Data type: SSPIPD_TOptional: No
Call by Reference: Yes
IT_SSPISGCON -
Data type: SSPISGCONOptional: No
Call by Reference: Yes
IT_SSPISGFLD_T -
Data type: SSPISGFLD_TOptional: No
Call by Reference: Yes
IT_SSPISGFLD -
Data type: SSPISGFLDOptional: No
Call by Reference: Yes
IT_SSPISGD -
Data type: SSPISGDOptional: No
Call by Reference: Yes
IT_SSPIPST_T -
Data type: SSPIPST_TOptional: No
Call by Reference: Yes
IT_SSPIPST -
Data type: SSPIPSTOptional: No
Call by Reference: Yes
IT_SSPIPSD -
Data type: SSPIPSDOptional: No
Call by Reference: Yes
IT_SSPIPDTA -
Data type: SSPIPDTAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SPI_REPLACE_PROCESS_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: | ||||
| lt_it_sspisgd_t | TYPE STANDARD TABLE OF SSPISGD_T, " | |||
| lv_ip_process_id | TYPE SPIPROCTP, " | |||
| lt_it_sspipsrtfld | TYPE STANDARD TABLE OF SSPIPSRTFLD, " | |||
| lt_it_sspipsrfld | TYPE STANDARD TABLE OF SSPIPSRFLD, " | |||
| lt_it_sspipsr | TYPE STANDARD TABLE OF SSPIPSR, " | |||
| lt_it_sspipvd_t | TYPE STANDARD TABLE OF SSPIPVD_T, " | |||
| lt_it_sspipvd | TYPE STANDARD TABLE OF SSPIPVD, " | |||
| lt_it_sspipvc | TYPE STANDARD TABLE OF SSPIPVC, " | |||
| lt_it_sspipd_t | TYPE STANDARD TABLE OF SSPIPD_T, " | |||
| lv_is_sspipd | TYPE SSPIPD, " | |||
| lt_it_sspisgcon | TYPE STANDARD TABLE OF SSPISGCON, " | |||
| lt_it_sspisgfld_t | TYPE STANDARD TABLE OF SSPISGFLD_T, " | |||
| lt_it_sspisgfld | TYPE STANDARD TABLE OF SSPISGFLD, " | |||
| lt_it_sspisgd | TYPE STANDARD TABLE OF SSPISGD, " | |||
| lt_it_sspipst_t | TYPE STANDARD TABLE OF SSPIPST_T, " | |||
| lt_it_sspipst | TYPE STANDARD TABLE OF SSPIPST, " | |||
| lt_it_sspipsd | TYPE STANDARD TABLE OF SSPIPSD, " | |||
| lt_it_sspipdta | TYPE STANDARD TABLE OF SSPIPDTA. " |
|   CALL FUNCTION 'SPI_REPLACE_PROCESS_DB' " |
| EXPORTING | ||
| IP_PROCESS_ID | = lv_ip_process_id | |
| IS_SSPIPD | = lv_is_sspipd | |
| TABLES | ||
| IT_SSPISGD_T | = lt_it_sspisgd_t | |
| IT_SSPIPSRTFLD | = lt_it_sspipsrtfld | |
| IT_SSPIPSRFLD | = lt_it_sspipsrfld | |
| IT_SSPIPSR | = lt_it_sspipsr | |
| IT_SSPIPVD_T | = lt_it_sspipvd_t | |
| IT_SSPIPVD | = lt_it_sspipvd | |
| IT_SSPIPVC | = lt_it_sspipvc | |
| IT_SSPIPD_T | = lt_it_sspipd_t | |
| IT_SSPISGCON | = lt_it_sspisgcon | |
| IT_SSPISGFLD_T | = lt_it_sspisgfld_t | |
| IT_SSPISGFLD | = lt_it_sspisgfld | |
| IT_SSPISGD | = lt_it_sspisgd | |
| IT_SSPIPST_T | = lt_it_sspipst_t | |
| IT_SSPIPST | = lt_it_sspipst | |
| IT_SSPIPSD | = lt_it_sspipsd | |
| IT_SSPIPDTA | = lt_it_sspipdta | |
| . " SPI_REPLACE_PROCESS_DB | ||
ABAP code using 7.40 inline data declarations to call FM SPI_REPLACE_PROCESS_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