SAP SCWB_NOTE_IMPL_STATUS Function Module for









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

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



Function SCWB_NOTE_IMPL_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 'SCWB_NOTE_IMPL_STATUS'"
EXPORTING
* IV_IGNORE_MANUAL_ACTIVITIES = ' ' "
* IV_UPDATE_NOTE = 'X' "
* IV_SILENT_MODE = ' ' "
IS_NOTE = "

IMPORTING
EV_STATUS = "Implementation Status
ET_TO_BE_IMPLEMENTED = "
ET_TO_BE_DEIMPLEMENTED = "
ET_TO_BE_RESET_TO_ORIGINAL = "
ET_ALREADY_IMPLEMENTED = "

EXCEPTIONS
NOTE_NOT_FOUND = 1 INCONSISTENT_DELIVERY_DATA = 2 UNDEFINED_COMPONENT_STATE = 3 INCOMPLETE_NOTE_DATA = 4
.



IMPORTING Parameters details for SCWB_NOTE_IMPL_STATUS

IV_IGNORE_MANUAL_ACTIVITIES -

Data type: BCWBN_BOOL
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_UPDATE_NOTE -

Data type: BCWBN_BOOL
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SILENT_MODE -

Data type: BCWBN_BOOL
Default: SPACE
Optional: Yes
Call by Reference: Yes

IS_NOTE -

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

EXPORTING Parameters details for SCWB_NOTE_IMPL_STATUS

EV_STATUS - Implementation Status

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

ET_TO_BE_IMPLEMENTED -

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

ET_TO_BE_DEIMPLEMENTED -

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

ET_TO_BE_RESET_TO_ORIGINAL -

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

ET_ALREADY_IMPLEMENTED -

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

EXCEPTIONS details

NOTE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

INCONSISTENT_DELIVERY_DATA -

Data type:
Optional: No
Call by Reference: Yes

UNDEFINED_COMPONENT_STATE -

Data type:
Optional: No
Call by Reference: Yes

INCOMPLETE_NOTE_DATA -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SCWB_NOTE_IMPL_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_status  TYPE CWBPRSTAT, "   
lv_note_not_found  TYPE CWBPRSTAT, "   
lv_iv_ignore_manual_activities  TYPE BCWBN_BOOL, "   SPACE
lv_iv_update_note  TYPE BCWBN_BOOL, "   'X'
lv_et_to_be_implemented  TYPE BCWBN_CORR_INSTRUCTIONS, "   
lv_inconsistent_delivery_data  TYPE BCWBN_CORR_INSTRUCTIONS, "   
lv_iv_silent_mode  TYPE BCWBN_BOOL, "   SPACE
lv_et_to_be_deimplemented  TYPE BCWBN_CORR_INSTRUCTIONS, "   
lv_undefined_component_state  TYPE BCWBN_CORR_INSTRUCTIONS, "   
lv_is_note  TYPE BCWBN_NOTE, "   
lv_incomplete_note_data  TYPE BCWBN_NOTE, "   
lv_et_to_be_reset_to_original  TYPE BCWBN_CORR_INSTRUCTIONS, "   
lv_et_already_implemented  TYPE BCWBN_CORR_INSTRUCTIONS. "   

  CALL FUNCTION 'SCWB_NOTE_IMPL_STATUS'  "
    EXPORTING
         IV_IGNORE_MANUAL_ACTIVITIES = lv_iv_ignore_manual_activities
         IV_UPDATE_NOTE = lv_iv_update_note
         IV_SILENT_MODE = lv_iv_silent_mode
         IS_NOTE = lv_is_note
    IMPORTING
         EV_STATUS = lv_ev_status
         ET_TO_BE_IMPLEMENTED = lv_et_to_be_implemented
         ET_TO_BE_DEIMPLEMENTED = lv_et_to_be_deimplemented
         ET_TO_BE_RESET_TO_ORIGINAL = lv_et_to_be_reset_to_original
         ET_ALREADY_IMPLEMENTED = lv_et_already_implemented
    EXCEPTIONS
        NOTE_NOT_FOUND = 1
        INCONSISTENT_DELIVERY_DATA = 2
        UNDEFINED_COMPONENT_STATE = 3
        INCOMPLETE_NOTE_DATA = 4
. " SCWB_NOTE_IMPL_STATUS




ABAP code using 7.40 inline data declarations to call FM SCWB_NOTE_IMPL_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.

 
 
DATA(ld_iv_ignore_manual_activities) = ' '.
 
DATA(ld_iv_update_note) = 'X'.
 
 
 
DATA(ld_iv_silent_mode) = ' '.
 
 
 
 
 
 
 


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!