SAP PPEUISOP_COPY_CONF Function Module for NOTRANSL: Copy configuration









PPEUISOP_COPY_CONF is a standard ppeuisop copy conf SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Copy configuration 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 ppeuisop copy conf FM, simply by entering the name PPEUISOP_COPY_CONF into the relevant SAP transaction such as SE37 or SE38.

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



Function PPEUISOP_COPY_CONF 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 'PPEUISOP_COPY_CONF'"NOTRANSL: Copy configuration
  EXPORTING
*  IM_GUID =  "Internal Identification for PVS Objects
*  IM_OTYPE =  "iPPE Object Type
*  IM_PXTYPE =  "iPPE Node Type, Alternative Type, or Variant Type
*  IM_MODUS =  "Generic Type
*  IM_MAP =  "Dialog Structure for Navigation Tree in iPPE Workbench
.



IMPORTING Parameters details for PPEUISOP_COPY_CONF

IM_GUID - Internal Identification for PVS Objects

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

IM_OTYPE - iPPE Object Type

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

IM_PXTYPE - iPPE Node Type, Alternative Type, or Variant Type

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

IM_MODUS - Generic Type

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

IM_MAP - Dialog Structure for Navigation Tree in iPPE Workbench

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

Copy and paste ABAP code example for PPEUISOP_COPY_CONF 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_im_guid  TYPE PVS_GUID, "   
lv_im_otype  TYPE PVS_OTYPE, "   
lv_im_pxtype  TYPE PVS_CUST_TYPE, "   
lv_im_modus  TYPE C, "   
lv_im_map  TYPE PVSGI_MAP. "   

  CALL FUNCTION 'PPEUISOP_COPY_CONF'  "NOTRANSL: Copy configuration
    EXPORTING
         IM_GUID = lv_im_guid
         IM_OTYPE = lv_im_otype
         IM_PXTYPE = lv_im_pxtype
         IM_MODUS = lv_im_modus
         IM_MAP = lv_im_map
. " PPEUISOP_COPY_CONF




ABAP code using 7.40 inline data declarations to call FM PPEUISOP_COPY_CONF

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!