SAP MAP2I_STR_OMS_NOTES_CHG Function Module for BAPI to MAPI note details
MAP2I_STR_OMS_NOTES_CHG is a standard map2i str oms notes chg SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI to MAPI note details processing and below is the pattern details for this FM, 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 map2i str oms notes chg FM, simply by entering the name MAP2I_STR_OMS_NOTES_CHG into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_BUSISB107_MAPPING_03
Program Name: SAPLCMS_BUSISB107_MAPPING_03
Main Program: SAPLCMS_BUSISB107_MAPPING_03
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP2I_STR_OMS_NOTES_CHG 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 'MAP2I_STR_OMS_NOTES_CHG'"BAPI to MAPI note details.
EXPORTING
BAPICMS_STR_OMS_NOTES_CHG = "
CHANGING
CMS_STR_MOV_TXT_LINES_CHG = "
IMPORTING Parameters details for MAP2I_STR_OMS_NOTES_CHG
BAPICMS_STR_OMS_NOTES_CHG -
Data type: BAPICMS_STR_OMS_NOTES_CHGOptional: No
Call by Reference: Yes
CHANGING Parameters details for MAP2I_STR_OMS_NOTES_CHG
CMS_STR_MOV_TXT_LINES_CHG -
Data type: CMS_STR_MOV_TXT_LINES_CHGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MAP2I_STR_OMS_NOTES_CHG 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_bapicms_str_oms_notes_chg | TYPE BAPICMS_STR_OMS_NOTES_CHG, " | |||
| lv_cms_str_mov_txt_lines_chg | TYPE CMS_STR_MOV_TXT_LINES_CHG. " |
|   CALL FUNCTION 'MAP2I_STR_OMS_NOTES_CHG' "BAPI to MAPI note details |
| EXPORTING | ||
| BAPICMS_STR_OMS_NOTES_CHG | = lv_bapicms_str_oms_notes_chg | |
| CHANGING | ||
| CMS_STR_MOV_TXT_LINES_CHG | = lv_cms_str_mov_txt_lines_chg | |
| . " MAP2I_STR_OMS_NOTES_CHG | ||
ABAP code using 7.40 inline data declarations to call FM MAP2I_STR_OMS_NOTES_CHG
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