SAP PPC1IP_RES_CONVERT Function Module for NOTRANSL: Konvertiert iPPE-Ressourcen: Intern <-> Extern









PPC1IP_RES_CONVERT is a standard ppc1ip res 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-Ressourcen: 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 res convert FM, simply by entering the name PPC1IP_RES_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_RES_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_RES_CONVERT'"NOTRANSL: Konvertiert iPPE-Ressourcen: Intern <-> Extern
  EXPORTING
*  IF_RES_GUID =  "Internal Number of iPPE Node
*  IF_RES_NAME =  "iPPE Node Description
*  IF_RES_CLASS_EXT =  "Class number
*  IF_RES_CLASS_TYPE =  "Class Type

 IMPORTING
   EF_RES_GUID =  "Internal Number of iPPE Node
   EF_RES_NAME =  "iPPE Node Description
   EF_RES_CLASS_EXT =  "Class number
   EF_RES_CLASS_TYPE =  "Class Type
   EF_RES_CLINT =  "Internal Class Number

EXCEPTIONS
   MISSING_DATA = 1    IPPE_READ_ERROR = 2    NOT_A_RESSOURCE = 3    CLASS_READ_ERROR = 4
.



IMPORTING Parameters details for PPC1IP_RES_CONVERT

IF_RES_GUID - Internal Number of iPPE Node

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

IF_RES_NAME - iPPE Node Description

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

IF_RES_CLASS_EXT - Class number

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

IF_RES_CLASS_TYPE - Class Type

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

EXPORTING Parameters details for PPC1IP_RES_CONVERT

EF_RES_GUID - Internal Number of iPPE Node

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

EF_RES_NAME - iPPE Node Description

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

EF_RES_CLASS_EXT - Class number

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

EF_RES_CLASS_TYPE - Class Type

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

EF_RES_CLINT - Internal Class Number

Data type: CLINT
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

NOT_A_RESSOURCE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

CLASS_READ_ERROR - Error while reading the class

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PPC1IP_RES_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_res_guid  TYPE PVS_PNGUID, "   
lv_if_res_guid  TYPE PVS_PNGUID, "   
lv_missing_data  TYPE PVS_PNGUID, "   
lv_ef_res_name  TYPE PVS_PNODE, "   
lv_if_res_name  TYPE PVS_PNODE, "   
lv_ippe_read_error  TYPE PVS_PNODE, "   
lv_not_a_ressource  TYPE PVS_PNODE, "   
lv_ef_res_class_ext  TYPE KLASSE_D, "   
lv_if_res_class_ext  TYPE KLASSE_D, "   
lv_class_read_error  TYPE KLASSE_D, "   
lv_ef_res_class_type  TYPE KLASSENART, "   
lv_if_res_class_type  TYPE KLASSENART, "   
lv_ef_res_clint  TYPE CLINT. "   

  CALL FUNCTION 'PPC1IP_RES_CONVERT'  "NOTRANSL: Konvertiert iPPE-Ressourcen: Intern <-> Extern
    EXPORTING
         IF_RES_GUID = lv_if_res_guid
         IF_RES_NAME = lv_if_res_name
         IF_RES_CLASS_EXT = lv_if_res_class_ext
         IF_RES_CLASS_TYPE = lv_if_res_class_type
    IMPORTING
         EF_RES_GUID = lv_ef_res_guid
         EF_RES_NAME = lv_ef_res_name
         EF_RES_CLASS_EXT = lv_ef_res_class_ext
         EF_RES_CLASS_TYPE = lv_ef_res_class_type
         EF_RES_CLINT = lv_ef_res_clint
    EXCEPTIONS
        MISSING_DATA = 1
        IPPE_READ_ERROR = 2
        NOT_A_RESSOURCE = 3
        CLASS_READ_ERROR = 4
. " PPC1IP_RES_CONVERT




ABAP code using 7.40 inline data declarations to call FM PPC1IP_RES_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!