SAP FRML210_ATTR_MAPPING Function Module for NOTRANSL: RMSFRM: Mapping API-PVS: Übertragen der Werte gemeinsamer Attrib
FRML210_ATTR_MAPPING is a standard frml210 attr mapping 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: RMSFRM: Mapping API-PVS: Übertragen der Werte gemeinsamer Attrib 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 frml210 attr mapping FM, simply by entering the name FRML210_ATTR_MAPPING into the relevant SAP transaction such as SE37 or SE38.
Function Group: FRML210
Program Name: SAPLFRML210
Main Program: SAPLFRML210
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FRML210_ATTR_MAPPING 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 'FRML210_ATTR_MAPPING'"NOTRANSL: RMSFRM: Mapping API-PVS: Übertragen der Werte gemeinsamer Attrib.
EXPORTING
I_ATTR_TAB = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_API_PVS = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_PVS_API = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_PVFRMS = "
* I_PVFRMM = "
* I_PVFRMI = "
* I_API_SUB = "
* I_API_MAT = "
* I_API_STR = "
CHANGING
* C_PVFRMS = "
* C_PVFRMM = "
* C_PVFRMI = "
* C_API_SUB = "
* C_API_MAT = "
* C_API_STR = "
EXCEPTIONS
NO_ATTR_GIVEN = 1 INDIFFERENT_INTERFACE = 2 NO_ACTION_REQUIRED = 3
IMPORTING Parameters details for FRML210_ATTR_MAPPING
I_ATTR_TAB - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: FRM20_ATTR_NAME_TABOptional: No
Call by Reference: Yes
I_API_PVS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: FRM20_BOOLEAN_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PVS_API - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: FRM20_BOOLEAN_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PVFRMS -
Data type: FRM20_PVFRMS_LIOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PVFRMM -
Data type: FRM20_PVFRMM_LIOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PVFRMI -
Data type: FRM20_PVFRMI_LIOptional: Yes
Call by Reference: No ( called with pass by value option)
I_API_SUB -
Data type: FRM20_API_SUB_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_API_MAT -
Data type: FRM20_API_MAT_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_API_STR -
Data type: FRM20_API_STR_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for FRML210_ATTR_MAPPING
C_PVFRMS -
Data type: FRM20_PVFRMS_LIOptional: Yes
Call by Reference: Yes
C_PVFRMM -
Data type: FRM20_PVFRMM_LIOptional: Yes
Call by Reference: Yes
C_PVFRMI -
Data type: FRM20_PVFRMI_LIOptional: Yes
Call by Reference: Yes
C_API_SUB -
Data type: FRM20_API_SUB_TYPEOptional: Yes
Call by Reference: Yes
C_API_MAT -
Data type: FRM20_API_MAT_TYPEOptional: Yes
Call by Reference: Yes
C_API_STR -
Data type: FRM20_API_STR_TYPEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_ATTR_GIVEN - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
INDIFFERENT_INTERFACE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
NO_ACTION_REQUIRED - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FRML210_ATTR_MAPPING 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_c_pvfrms | TYPE FRM20_PVFRMS_LI, " | |||
| lv_i_attr_tab | TYPE FRM20_ATTR_NAME_TAB, " | |||
| lv_no_attr_given | TYPE FRM20_ATTR_NAME_TAB, " | |||
| lv_c_pvfrmm | TYPE FRM20_PVFRMM_LI, " | |||
| lv_i_api_pvs | TYPE FRM20_BOOLEAN_TYPE, " | |||
| lv_indifferent_interface | TYPE FRM20_BOOLEAN_TYPE, " | |||
| lv_c_pvfrmi | TYPE FRM20_PVFRMI_LI, " | |||
| lv_i_pvs_api | TYPE FRM20_BOOLEAN_TYPE, " | |||
| lv_no_action_required | TYPE FRM20_BOOLEAN_TYPE, " | |||
| lv_i_pvfrms | TYPE FRM20_PVFRMS_LI, " | |||
| lv_c_api_sub | TYPE FRM20_API_SUB_TYPE, " | |||
| lv_i_pvfrmm | TYPE FRM20_PVFRMM_LI, " | |||
| lv_c_api_mat | TYPE FRM20_API_MAT_TYPE, " | |||
| lv_i_pvfrmi | TYPE FRM20_PVFRMI_LI, " | |||
| lv_c_api_str | TYPE FRM20_API_STR_TYPE, " | |||
| lv_i_api_sub | TYPE FRM20_API_SUB_TYPE, " | |||
| lv_i_api_mat | TYPE FRM20_API_MAT_TYPE, " | |||
| lv_i_api_str | TYPE FRM20_API_STR_TYPE. " |
|   CALL FUNCTION 'FRML210_ATTR_MAPPING' "NOTRANSL: RMSFRM: Mapping API-PVS: Übertragen der Werte gemeinsamer Attrib |
| EXPORTING | ||
| I_ATTR_TAB | = lv_i_attr_tab | |
| I_API_PVS | = lv_i_api_pvs | |
| I_PVS_API | = lv_i_pvs_api | |
| I_PVFRMS | = lv_i_pvfrms | |
| I_PVFRMM | = lv_i_pvfrmm | |
| I_PVFRMI | = lv_i_pvfrmi | |
| I_API_SUB | = lv_i_api_sub | |
| I_API_MAT | = lv_i_api_mat | |
| I_API_STR | = lv_i_api_str | |
| CHANGING | ||
| C_PVFRMS | = lv_c_pvfrms | |
| C_PVFRMM | = lv_c_pvfrmm | |
| C_PVFRMI | = lv_c_pvfrmi | |
| C_API_SUB | = lv_c_api_sub | |
| C_API_MAT | = lv_c_api_mat | |
| C_API_STR | = lv_c_api_str | |
| EXCEPTIONS | ||
| NO_ATTR_GIVEN = 1 | ||
| INDIFFERENT_INTERFACE = 2 | ||
| NO_ACTION_REQUIRED = 3 | ||
| . " FRML210_ATTR_MAPPING | ||
ABAP code using 7.40 inline data declarations to call FM FRML210_ATTR_MAPPING
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