SAP COM_PRID_TO_R3_CONVERT_RFC Function Module for









COM_PRID_TO_R3_CONVERT_RFC is a standard com prid to r3 convert rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 com prid to r3 convert rfc FM, simply by entering the name COM_PRID_TO_R3_CONVERT_RFC into the relevant SAP transaction such as SE37 or SE38.

Function Group: COM_PR_CONVERSION
Program Name: SAPLCOM_PR_CONVERSION
Main Program: SAPLCOM_PR_CONVERSION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function COM_PRID_TO_R3_CONVERT_RFC 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 'COM_PRID_TO_R3_CONVERT_RFC'"
EXPORTING
IV_LOGSYS = "Logical System
IV_PRODUCT_TYPE = "Product Type
* IV_OBJECT_FAMILY = ' ' "Object Family
* IV_INTERNAL_MATNR = 'X' "
IV_PRODUCT_ID = "

IMPORTING
EV_PRODUCT_ID = "

TABLES
* ET_ID_PER_OLTP = "

EXCEPTIONS
INVALID_LOGSYS = 1 LENGTH_ERROR = 2 NOT_FOUND = 3
.



IMPORTING Parameters details for COM_PRID_TO_R3_CONVERT_RFC

IV_LOGSYS - Logical System

Data type: COMT_LOGSYS
Optional: No
Call by Reference: No ( called with pass by value option)

IV_PRODUCT_TYPE - Product Type

Data type: COMT_PRODUCT_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

IV_OBJECT_FAMILY - Object Family

Data type: COMT_PRODUCT_OBJECT_FAMILY
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_INTERNAL_MATNR -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_PRODUCT_ID -

Data type: COMT_OLTP_MAT_NUMBER
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for COM_PRID_TO_R3_CONVERT_RFC

EV_PRODUCT_ID -

Data type: COMT_OLTP_MAT_NUMBER
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for COM_PRID_TO_R3_CONVERT_RFC

ET_ID_PER_OLTP -

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

EXCEPTIONS details

INVALID_LOGSYS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

LENGTH_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for COM_PRID_TO_R3_CONVERT_RFC 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_iv_logsys  TYPE COMT_LOGSYS, "   
lv_ev_product_id  TYPE COMT_OLTP_MAT_NUMBER, "   
lt_et_id_per_oltp  TYPE STANDARD TABLE OF COMT_MATERIAL_LOGSYS, "   
lv_invalid_logsys  TYPE COMT_MATERIAL_LOGSYS, "   
lv_length_error  TYPE COMT_MATERIAL_LOGSYS, "   
lv_iv_product_type  TYPE COMT_PRODUCT_TYPE, "   
lv_not_found  TYPE COMT_PRODUCT_TYPE, "   
lv_iv_object_family  TYPE COMT_PRODUCT_OBJECT_FAMILY, "   SPACE
lv_iv_internal_matnr  TYPE XFELD, "   'X'
lv_iv_product_id  TYPE COMT_OLTP_MAT_NUMBER. "   

  CALL FUNCTION 'COM_PRID_TO_R3_CONVERT_RFC'  "
    EXPORTING
         IV_LOGSYS = lv_iv_logsys
         IV_PRODUCT_TYPE = lv_iv_product_type
         IV_OBJECT_FAMILY = lv_iv_object_family
         IV_INTERNAL_MATNR = lv_iv_internal_matnr
         IV_PRODUCT_ID = lv_iv_product_id
    IMPORTING
         EV_PRODUCT_ID = lv_ev_product_id
    TABLES
         ET_ID_PER_OLTP = lt_et_id_per_oltp
    EXCEPTIONS
        INVALID_LOGSYS = 1
        LENGTH_ERROR = 2
        NOT_FOUND = 3
. " COM_PRID_TO_R3_CONVERT_RFC




ABAP code using 7.40 inline data declarations to call FM COM_PRID_TO_R3_CONVERT_RFC

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.

 
 
 
 
 
 
 
DATA(ld_iv_object_family) = ' '.
 
DATA(ld_iv_internal_matnr) = 'X'.
 
 


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!