SAP PPC1IP_MOD_CONVERT Function Module for NOTRANSL: Konvertiert iPPE-Modi: Intern <-> Extern









PPC1IP_MOD_CONVERT is a standard ppc1ip mod convert 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: Konvertiert iPPE-Modi: Intern <-> Extern 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 ppc1ip mod convert FM, simply by entering the name PPC1IP_MOD_CONVERT into the relevant SAP transaction such as SE37 or SE38.

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



Function PPC1IP_MOD_CONVERT 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 'PPC1IP_MOD_CONVERT'"NOTRANSL: Konvertiert iPPE-Modi: Intern <-> Extern
  EXPORTING
*  IF_MOD_GUID =  "Internal Identification for PVS Objects
*  IF_ACT_NAME =  "iPPE Node Description
*  IF_ACT_CLASS_EXT =  "Class number
*  IF_ACT_CLASS_TYPE =  "Class Type
*  IF_MOD_NUM =  "Alternative of an iPPE Node

 IMPORTING
   EF_MOD_GUID =  "Internal Identification for PVS Objects
   EF_ACT_NAME =  "iPPE Node Description
   EF_ACT_CLASS_EXT =  "Class number
   EF_ACT_CLASS_TYPE =  "Class Type
   EF_MOD_NUM =  "Alternative of an iPPE Node
   EF_MOD_EXT =  "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
   MISSING_DATA = 1    IPPE_READ_ERROR = 2    ACTIVITY_CONVERT_ERROR = 3    NOT_A_MODE = 4
.



IMPORTING Parameters details for PPC1IP_MOD_CONVERT

IF_MOD_GUID - Internal Identification for PVS Objects

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

IF_ACT_NAME - iPPE Node Description

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

IF_ACT_CLASS_EXT - Class number

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

IF_ACT_CLASS_TYPE - Class Type

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

IF_MOD_NUM - Alternative of an iPPE Node

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

EXPORTING Parameters details for PPC1IP_MOD_CONVERT

EF_MOD_GUID - Internal Identification for PVS Objects

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

EF_ACT_NAME - iPPE Node Description

Data type: PVS_PNODE
Optional: No
Call by Reference: Yes

EF_ACT_CLASS_EXT - Class number

Data type: KLASSE_D
Optional: No
Call by Reference: Yes

EF_ACT_CLASS_TYPE - Class Type

Data type: KLASSENART
Optional: No
Call by Reference: Yes

EF_MOD_NUM - Alternative of an iPPE Node

Data type: PVS_ALTNUM
Optional: No
Call by Reference: Yes

EF_MOD_EXT - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: PPET_PALTID_EXT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

MISSING_DATA - Not all necessary parameters were transferred

Data type:
Optional: No
Call by Reference: Yes

IPPE_READ_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

ACTIVITY_CONVERT_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

NOT_A_MODE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PPC1IP_MOD_CONVERT 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_ef_mod_guid  TYPE PVS_GUID, "   
lv_if_mod_guid  TYPE PVS_GUID, "   
lv_missing_data  TYPE PVS_GUID, "   
lv_ef_act_name  TYPE PVS_PNODE, "   
lv_if_act_name  TYPE PVS_PNODE, "   
lv_ippe_read_error  TYPE PVS_PNODE, "   
lv_ef_act_class_ext  TYPE KLASSE_D, "   
lv_if_act_class_ext  TYPE KLASSE_D, "   
lv_activity_convert_error  TYPE KLASSE_D, "   
lv_not_a_mode  TYPE KLASSE_D, "   
lv_ef_act_class_type  TYPE KLASSENART, "   
lv_if_act_class_type  TYPE KLASSENART, "   
lv_ef_mod_num  TYPE PVS_ALTNUM, "   
lv_if_mod_num  TYPE PVS_ALTNUM, "   
lv_ef_mod_ext  TYPE PPET_PALTID_EXT. "   

  CALL FUNCTION 'PPC1IP_MOD_CONVERT'  "NOTRANSL: Konvertiert iPPE-Modi: Intern <-> Extern
    EXPORTING
         IF_MOD_GUID = lv_if_mod_guid
         IF_ACT_NAME = lv_if_act_name
         IF_ACT_CLASS_EXT = lv_if_act_class_ext
         IF_ACT_CLASS_TYPE = lv_if_act_class_type
         IF_MOD_NUM = lv_if_mod_num
    IMPORTING
         EF_MOD_GUID = lv_ef_mod_guid
         EF_ACT_NAME = lv_ef_act_name
         EF_ACT_CLASS_EXT = lv_ef_act_class_ext
         EF_ACT_CLASS_TYPE = lv_ef_act_class_type
         EF_MOD_NUM = lv_ef_mod_num
         EF_MOD_EXT = lv_ef_mod_ext
    EXCEPTIONS
        MISSING_DATA = 1
        IPPE_READ_ERROR = 2
        ACTIVITY_CONVERT_ERROR = 3
        NOT_A_MODE = 4
. " PPC1IP_MOD_CONVERT




ABAP code using 7.40 inline data declarations to call FM PPC1IP_MOD_CONVERT

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!