SAP RSPC_TRIGGER_MAINTAIN Function Module for maintainTrigger process
RSPC_TRIGGER_MAINTAIN is a standard rspc trigger maintain SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for maintainTrigger process 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 rspc trigger maintain FM, simply by entering the name RSPC_TRIGGER_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSPC_PROCESSES
Program Name: SAPLRSPC_PROCESSES
Main Program: SAPLRSPC_PROCESSES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RSPC_TRIGGER_MAINTAIN 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 'RSPC_TRIGGER_MAINTAIN'"maintainTrigger process.
EXPORTING
* I_VARIANT = "Process Variant (Name)
IMPORTING
E_VARIANT = "Process Variant (Name)
E_VARIANT_TEXT = "Long Description
IMPORTING Parameters details for RSPC_TRIGGER_MAINTAIN
I_VARIANT - Process Variant (Name)
Data type: RSPC_VARIANTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSPC_TRIGGER_MAINTAIN
E_VARIANT - Process Variant (Name)
Data type: RSPC_VARIANTOptional: No
Call by Reference: Yes
E_VARIANT_TEXT - Long Description
Data type: RSTXTLGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSPC_TRIGGER_MAINTAIN 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_e_variant | TYPE RSPC_VARIANT, " | |||
lv_i_variant | TYPE RSPC_VARIANT, " | |||
lv_e_variant_text | TYPE RSTXTLG. " |
  CALL FUNCTION 'RSPC_TRIGGER_MAINTAIN' "maintainTrigger process |
EXPORTING | ||
I_VARIANT | = lv_i_variant | |
IMPORTING | ||
E_VARIANT | = lv_e_variant | |
E_VARIANT_TEXT | = lv_e_variant_text | |
. " RSPC_TRIGGER_MAINTAIN |
ABAP code using 7.40 inline data declarations to call FM RSPC_TRIGGER_MAINTAIN
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