SAP SCWB_API_NOTES_IMPLEMENT_TCI Function Module for
SCWB_API_NOTES_IMPLEMENT_TCI is a standard scwb api notes implement tci 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 api notes implement tci FM, simply by entering the name SCWB_API_NOTES_IMPLEMENT_TCI into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCWB_API
Program Name: SAPLSCWB_API
Main Program: SAPLSCWB_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SCWB_API_NOTES_IMPLEMENT_TCI 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_API_NOTES_IMPLEMENT_TCI'".
EXPORTING
* IV_REQID = "
* IV_FILENAME = "
IMPORTING
ES_MANUAL_ACTIVITY = "
EV_RC = "
ES_MSG = "
ET_MSG = "
TABLES
IT_NOTES = "
IT_COMPONENT_VECTOR = "
* ET_MISSING_COMPONENT_VECTOR = "
* ET_MISSING_NOTES = "
IMPORTING Parameters details for SCWB_API_NOTES_IMPLEMENT_TCI
IV_REQID -
Data type: SCWB_REQUEST_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_FILENAME -
Data type: EPSFILNAMOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SCWB_API_NOTES_IMPLEMENT_TCI
ES_MANUAL_ACTIVITY -
Data type: SCWB_API_CORRECTION_INSTROptional: No
Call by Reference: No ( called with pass by value option)
EV_RC -
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
ES_MSG -
Data type: SCWB_API_MSGOptional: No
Call by Reference: No ( called with pass by value option)
ET_MSG -
Data type: SCWB_API_T_MSGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SCWB_API_NOTES_IMPLEMENT_TCI
IT_NOTES -
Data type: SCWB_API_NOTENUMBEROptional: No
Call by Reference: No ( called with pass by value option)
IT_COMPONENT_VECTOR -
Data type: SCWB_API_COMP_VECTOROptional: No
Call by Reference: No ( called with pass by value option)
ET_MISSING_COMPONENT_VECTOR -
Data type: SCWB_API_COMP_VECTOROptional: Yes
Call by Reference: No ( called with pass by value option)
ET_MISSING_NOTES -
Data type: SCWB_API_NOTENUMBEROptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SCWB_API_NOTES_IMPLEMENT_TCI 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: | ||||
| lt_it_notes | TYPE STANDARD TABLE OF SCWB_API_NOTENUMBER, " | |||
| lv_iv_reqid | TYPE SCWB_REQUEST_ID, " | |||
| lv_es_manual_activity | TYPE SCWB_API_CORRECTION_INSTR, " | |||
| lv_ev_rc | TYPE I, " | |||
| lv_iv_filename | TYPE EPSFILNAM, " | |||
| lt_it_component_vector | TYPE STANDARD TABLE OF SCWB_API_COMP_VECTOR, " | |||
| lv_es_msg | TYPE SCWB_API_MSG, " | |||
| lt_et_missing_component_vector | TYPE STANDARD TABLE OF SCWB_API_COMP_VECTOR, " | |||
| lv_et_msg | TYPE SCWB_API_T_MSG, " | |||
| lt_et_missing_notes | TYPE STANDARD TABLE OF SCWB_API_NOTENUMBER. " |
|   CALL FUNCTION 'SCWB_API_NOTES_IMPLEMENT_TCI' " |
| EXPORTING | ||
| IV_REQID | = lv_iv_reqid | |
| IV_FILENAME | = lv_iv_filename | |
| IMPORTING | ||
| ES_MANUAL_ACTIVITY | = lv_es_manual_activity | |
| EV_RC | = lv_ev_rc | |
| ES_MSG | = lv_es_msg | |
| ET_MSG | = lv_et_msg | |
| TABLES | ||
| IT_NOTES | = lt_it_notes | |
| IT_COMPONENT_VECTOR | = lt_it_component_vector | |
| ET_MISSING_COMPONENT_VECTOR | = lt_et_missing_component_vector | |
| ET_MISSING_NOTES | = lt_et_missing_notes | |
| . " SCWB_API_NOTES_IMPLEMENT_TCI | ||
ABAP code using 7.40 inline data declarations to call FM SCWB_API_NOTES_IMPLEMENT_TCI
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