SAP MI_SYNEWS_SYNC_WRP Function Module for Wrapper for MI_SYNEWS_SYNC
MI_SYNEWS_SYNC_WRP is a standard mi synews sync wrp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Wrapper for MI_SYNEWS_SYNC 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 mi synews sync wrp FM, simply by entering the name MI_SYNEWS_SYNC_WRP into the relevant SAP transaction such as SE37 or SE38.
Function Group: MI_SYNEWS_SYNC
Program Name: SAPLMI_SYNEWS_SYNC
Main Program: SAPLMI_SYNEWS_SYNC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MI_SYNEWS_SYNC_WRP 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 'MI_SYNEWS_SYNC_WRP'"Wrapper for MI_SYNEWS_SYNC.
EXPORTING
INBOUND_HEADER = "
INBOUND_BODY = "String für generischen Body
IMPORTING
OUTBOUND_HEADER = "
OUTBOUND_BODY = "String für generischen Body
IMPORTING Parameters details for MI_SYNEWS_SYNC_WRP
INBOUND_HEADER -
Data type: MESYHEADOptional: No
Call by Reference: Yes
INBOUND_BODY - String für generischen Body
Data type: MEGENBODYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for MI_SYNEWS_SYNC_WRP
OUTBOUND_HEADER -
Data type: MESYHEADOptional: No
Call by Reference: Yes
OUTBOUND_BODY - String für generischen Body
Data type: MEGENBODYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MI_SYNEWS_SYNC_WRP 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_inbound_header | TYPE MESYHEAD, " | |||
| lv_outbound_header | TYPE MESYHEAD, " | |||
| lv_inbound_body | TYPE MEGENBODY, " | |||
| lv_outbound_body | TYPE MEGENBODY. " |
|   CALL FUNCTION 'MI_SYNEWS_SYNC_WRP' "Wrapper for MI_SYNEWS_SYNC |
| EXPORTING | ||
| INBOUND_HEADER | = lv_inbound_header | |
| INBOUND_BODY | = lv_inbound_body | |
| IMPORTING | ||
| OUTBOUND_HEADER | = lv_outbound_header | |
| OUTBOUND_BODY | = lv_outbound_body | |
| . " MI_SYNEWS_SYNC_WRP | ||
ABAP code using 7.40 inline data declarations to call FM MI_SYNEWS_SYNC_WRP
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