SAP CONV_FROM_RE_PL_MAP_DATC Function Module for
CONV_FROM_RE_PL_MAP_DATC is a standard conv from re pl map datc 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 conv from re pl map datc FM, simply by entering the name CONV_FROM_RE_PL_MAP_DATC into the relevant SAP transaction such as SE37 or SE38.
Function Group: RELM_BAPI_PL_MAP
Program Name: SAPLRELM_BAPI_PL_MAP
Main Program: SAPLRELM_BAPI_PL_MAP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CONV_FROM_RE_PL_MAP_DATC 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 'CONV_FROM_RE_PL_MAP_DATC'".
EXPORTING
BAPI_RE_PL_MAP_DATC = "
CHANGING
BAPI_RE_PL_MAP_INTC = "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for CONV_FROM_RE_PL_MAP_DATC
BAPI_RE_PL_MAP_DATC -
Data type: BAPI_RE_PL_MAP_DATCOptional: No
Call by Reference: Yes
CHANGING Parameters details for CONV_FROM_RE_PL_MAP_DATC
BAPI_RE_PL_MAP_INTC -
Data type: BAPI_RE_PL_MAP_INTCOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CONV_FROM_RE_PL_MAP_DATC 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_error | TYPE STRING, " | |||
| lv_bapi_re_pl_map_datc | TYPE BAPI_RE_PL_MAP_DATC, " | |||
| lv_bapi_re_pl_map_intc | TYPE BAPI_RE_PL_MAP_INTC. " |
|   CALL FUNCTION 'CONV_FROM_RE_PL_MAP_DATC' " |
| EXPORTING | ||
| BAPI_RE_PL_MAP_DATC | = lv_bapi_re_pl_map_datc | |
| CHANGING | ||
| BAPI_RE_PL_MAP_INTC | = lv_bapi_re_pl_map_intc | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " CONV_FROM_RE_PL_MAP_DATC | ||
ABAP code using 7.40 inline data declarations to call FM CONV_FROM_RE_PL_MAP_DATC
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