SAP SUSR_ZBV_CHECK_IF_TEMP_OFF Function Module for









SUSR_ZBV_CHECK_IF_TEMP_OFF is a standard susr zbv check if temp off 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 susr zbv check if temp off FM, simply by entering the name SUSR_ZBV_CHECK_IF_TEMP_OFF into the relevant SAP transaction such as SE37 or SE38.

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



Function SUSR_ZBV_CHECK_IF_TEMP_OFF 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 'SUSR_ZBV_CHECK_IF_TEMP_OFF'"
IMPORTING
TEMP_OFF = "
CENTRAL_SYSTEM_LOGSYS = "
CENTRAL_SYSTEM_RFC_DEST = "
BAPILINK = "

EXCEPTIONS
INVALID_MODEL = 1 CHECK_ERROR = 2
.



EXPORTING Parameters details for SUSR_ZBV_CHECK_IF_TEMP_OFF

TEMP_OFF -

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

CENTRAL_SYSTEM_LOGSYS -

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

CENTRAL_SYSTEM_RFC_DEST -

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

BAPILINK -

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

EXCEPTIONS details

INVALID_MODEL -

Data type:
Optional: No
Call by Reference: Yes

CHECK_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SUSR_ZBV_CHECK_IF_TEMP_OFF 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_temp_off  TYPE CUA_TEMP_OFF, "   
lv_invalid_model  TYPE CUA_TEMP_OFF, "   
lv_check_error  TYPE CUA_TEMP_OFF, "   
lv_central_system_logsys  TYPE USZBVLNDSC-SENDSYSTEM, "   
lv_central_system_rfc_dest  TYPE RFCDES-RFCDEST, "   
lv_bapilink  TYPE CUSTMODEL. "   

  CALL FUNCTION 'SUSR_ZBV_CHECK_IF_TEMP_OFF'  "
    IMPORTING
         TEMP_OFF = lv_temp_off
         CENTRAL_SYSTEM_LOGSYS = lv_central_system_logsys
         CENTRAL_SYSTEM_RFC_DEST = lv_central_system_rfc_dest
         BAPILINK = lv_bapilink
    EXCEPTIONS
        INVALID_MODEL = 1
        CHECK_ERROR = 2
. " SUSR_ZBV_CHECK_IF_TEMP_OFF




ABAP code using 7.40 inline data declarations to call FM SUSR_ZBV_CHECK_IF_TEMP_OFF

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 SENDSYSTEM FROM USZBVLNDSC INTO @DATA(ld_central_system_logsys).
 
"SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_central_system_rfc_dest).
 
 


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!