SAP SPAM_SET_STATUS Function Module for









SPAM_SET_STATUS is a standard spam set status 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 spam set status FM, simply by entering the name SPAM_SET_STATUS into the relevant SAP transaction such as SE37 or SE38.

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



Function SPAM_SET_STATUS 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 'SPAM_SET_STATUS'"
EXPORTING
* IV_LOGFILE = "Char255

IMPORTING
EV_RC = "Natural Number
EV_MESSAGE = "Char 80

TABLES
PATCH_LIST = "
* CVERS_ERRORS = "
.



IMPORTING Parameters details for SPAM_SET_STATUS

IV_LOGFILE - Char255

Data type: GSUGI_PA-LOGFILE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SPAM_SET_STATUS

EV_RC - Natural Number

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

EV_MESSAGE - Char 80

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

TABLES Parameters details for SPAM_SET_STATUS

PATCH_LIST -

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

CVERS_ERRORS -

Data type: SPROT_U
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for SPAM_SET_STATUS 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_ev_rc  TYPE GSUGI_PA-NR_CONV, "   
lv_iv_logfile  TYPE GSUGI_PA-LOGFILE, "   
lt_patch_list  TYPE STANDARD TABLE OF PAT_LIST, "   
lv_ev_message  TYPE GSUGI_PA-RCMESSAGE, "   
lt_cvers_errors  TYPE STANDARD TABLE OF SPROT_U. "   

  CALL FUNCTION 'SPAM_SET_STATUS'  "
    EXPORTING
         IV_LOGFILE = lv_iv_logfile
    IMPORTING
         EV_RC = lv_ev_rc
         EV_MESSAGE = lv_ev_message
    TABLES
         PATCH_LIST = lt_patch_list
         CVERS_ERRORS = lt_cvers_errors
. " SPAM_SET_STATUS




ABAP code using 7.40 inline data declarations to call FM SPAM_SET_STATUS

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.

"SELECT single NR_CONV FROM GSUGI_PA INTO @DATA(ld_ev_rc).
 
"SELECT single LOGFILE FROM GSUGI_PA INTO @DATA(ld_iv_logfile).
 
 
"SELECT single RCMESSAGE FROM GSUGI_PA INTO @DATA(ld_ev_message).
 
 


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!