SAP PMEVC_FUNCTION_SYNCHRONIZE Function Module for Synchronize Editor UI for variant function









PMEVC_FUNCTION_SYNCHRONIZE is a standard pmevc function synchronize SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Synchronize Editor UI for variant function 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 pmevc function synchronize FM, simply by entering the name PMEVC_FUNCTION_SYNCHRONIZE into the relevant SAP transaction such as SE37 or SE38.

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



Function PMEVC_FUNCTION_SYNCHRONIZE 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 'PMEVC_FUNCTION_SYNCHRONIZE'"Synchronize Editor UI for variant function
EXPORTING
* PARENT_ENTITY = "General Engine Object
* CHILD_TYPE = "
.



IMPORTING Parameters details for PMEVC_FUNCTION_SYNCHRONIZE

PARENT_ENTITY - General Engine Object

Data type: IF_PMEVC_ENGINE_ENTITY
Optional: Yes
Call by Reference: Yes

CHILD_TYPE -

Data type: I
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for PMEVC_FUNCTION_SYNCHRONIZE 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_parent_entity  TYPE IF_PMEVC_ENGINE_ENTITY, "   
lv_child_type  TYPE I. "   

  CALL FUNCTION 'PMEVC_FUNCTION_SYNCHRONIZE'  "Synchronize Editor UI for variant function
    EXPORTING
         PARENT_ENTITY = lv_parent_entity
         CHILD_TYPE = lv_child_type
. " PMEVC_FUNCTION_SYNCHRONIZE




ABAP code using 7.40 inline data declarations to call FM PMEVC_FUNCTION_SYNCHRONIZE

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!