SAP SCWB_GET_COMPONENT_STATE Function Module for









SCWB_GET_COMPONENT_STATE is a standard scwb get component state 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 scwb get component state FM, simply by entering the name SCWB_GET_COMPONENT_STATE into the relevant SAP transaction such as SE37 or SE38.

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



Function SCWB_GET_COMPONENT_STATE 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 'SCWB_GET_COMPONENT_STATE'"
IMPORTING
ES_RELEASE = "
ES_PATCH = "

CHANGING
CS_COMPONENT = "Software Components

EXCEPTIONS
UNKNOWN_COMPONENT = 1 INCONSISTENT_COMPONENT = 2 INCONSISTENT_DELIVERY_DATA = 3 UNDEFINED = 4
.



EXPORTING Parameters details for SCWB_GET_COMPONENT_STATE

ES_RELEASE -

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

ES_PATCH -

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

CHANGING Parameters details for SCWB_GET_COMPONENT_STATE

CS_COMPONENT - Software Components

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

EXCEPTIONS details

UNKNOWN_COMPONENT -

Data type:
Optional: No
Call by Reference: Yes

INCONSISTENT_COMPONENT -

Data type:
Optional: No
Call by Reference: Yes

INCONSISTENT_DELIVERY_DATA -

Data type:
Optional: No
Call by Reference: Yes

UNDEFINED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SCWB_GET_COMPONENT_STATE 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_es_release  TYPE BCWBN_DELIVERY_EVENT, "   
lv_cs_component  TYPE BCWBN_COMPONENT, "   
lv_unknown_component  TYPE BCWBN_COMPONENT, "   
lv_es_patch  TYPE BCWBN_DELIVERY_EVENT, "   
lv_inconsistent_component  TYPE BCWBN_DELIVERY_EVENT, "   
lv_inconsistent_delivery_data  TYPE BCWBN_DELIVERY_EVENT, "   
lv_undefined  TYPE BCWBN_DELIVERY_EVENT. "   

  CALL FUNCTION 'SCWB_GET_COMPONENT_STATE'  "
    IMPORTING
         ES_RELEASE = lv_es_release
         ES_PATCH = lv_es_patch
    CHANGING
         CS_COMPONENT = lv_cs_component
    EXCEPTIONS
        UNKNOWN_COMPONENT = 1
        INCONSISTENT_COMPONENT = 2
        INCONSISTENT_DELIVERY_DATA = 3
        UNDEFINED = 4
. " SCWB_GET_COMPONENT_STATE




ABAP code using 7.40 inline data declarations to call FM SCWB_GET_COMPONENT_STATE

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!