SAP SCWH_PATCH_CHECK_VISIBLE Function Module for









SCWH_PATCH_CHECK_VISIBLE is a standard scwh patch check visible 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 scwh patch check visible FM, simply by entering the name SCWH_PATCH_CHECK_VISIBLE into the relevant SAP transaction such as SE37 or SE38.

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



Function SCWH_PATCH_CHECK_VISIBLE 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 'SCWH_PATCH_CHECK_VISIBLE'"
IMPORTING
EP_VISIBLE = "

CHANGING
CS_DE = "

EXCEPTIONS
NO_PATCH = 1 INVALID_DATA = 2
.



EXPORTING Parameters details for SCWH_PATCH_CHECK_VISIBLE

EP_VISIBLE -

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

CHANGING Parameters details for SCWH_PATCH_CHECK_VISIBLE

CS_DE -

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

EXCEPTIONS details

NO_PATCH -

Data type:
Optional: No
Call by Reference: Yes

INVALID_DATA -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SCWH_PATCH_CHECK_VISIBLE 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_cs_de  TYPE BCWBN_DELIVERY_EVENT, "   
lv_no_patch  TYPE BCWBN_DELIVERY_EVENT, "   
lv_ep_visible  TYPE C, "   
lv_invalid_data  TYPE C. "   

  CALL FUNCTION 'SCWH_PATCH_CHECK_VISIBLE'  "
    IMPORTING
         EP_VISIBLE = lv_ep_visible
    CHANGING
         CS_DE = lv_cs_de
    EXCEPTIONS
        NO_PATCH = 1
        INVALID_DATA = 2
. " SCWH_PATCH_CHECK_VISIBLE




ABAP code using 7.40 inline data declarations to call FM SCWH_PATCH_CHECK_VISIBLE

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!