SAP RMXM950_GENERATE_OBJ_MODEL Function Module for NOTRANSL: ROM: Generiert das Rezeptobjektmodell
RMXM950_GENERATE_OBJ_MODEL is a standard rmxm950 generate obj model 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: ROM: Generiert das Rezeptobjektmodell 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 rmxm950 generate obj model FM, simply by entering the name RMXM950_GENERATE_OBJ_MODEL into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMXM950
Program Name: SAPLRMXM950
Main Program: SAPLRMXM950
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RMXM950_GENERATE_OBJ_MODEL 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 'RMXM950_GENERATE_OBJ_MODEL'"NOTRANSL: ROM: Generiert das Rezeptobjektmodell.
EXPORTING
* I_FORCE_API_INIT = 'X' "
* I_LOGSYS = "Logical System
* I_DATA_SCENARIO = 'D' "Data Scenario
I_VALFROM = "Valid-From Date
* I_VALTO = "Valid-To Date
* I_RANGE_INDEP = 'X' "
I_GRP = "Transformation Group
IT_KEYS = "
* I_LANGU = SY-LANGU "Logon Language
* I_PLANT = "Plant
IMPORTING
ET_OBJ = "
ET_NO_AUTH = "Authorization error
ET_ERROR = "Error Message Table
IMPORTING Parameters details for RMXM950_GENERATE_OBJ_MODEL
I_FORCE_API_INIT -
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LOGSYS - Logical System
Data type: LOGSYSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATA_SCENARIO - Data Scenario
Data type: RCPE_DATASCENDefault: 'D'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VALFROM - Valid-From Date
Data type: RCPE_ADATUMOptional: No
Call by Reference: No ( called with pass by value option)
I_VALTO - Valid-To Date
Data type: RCPE_BDATUMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RANGE_INDEP -
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_GRP - Transformation Group
Data type: RMXME_ROM_GRPOptional: No
Call by Reference: No ( called with pass by value option)
IT_KEYS -
Data type: RMXMTY_RCP_INFOOptional: No
Call by Reference: Yes
I_LANGU - Logon Language
Data type: SYLANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
I_PLANT - Plant
Data type: WERKS_DOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RMXM950_GENERATE_OBJ_MODEL
ET_OBJ -
Data type: RMXMTY_ROM_TREEOptional: No
Call by Reference: Yes
ET_NO_AUTH - Authorization error
Data type: RCPTY_API_NO_AUTHOptional: No
Call by Reference: Yes
ET_ERROR - Error Message Table
Data type: RMXMTY_MESSAGESOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RMXM950_GENERATE_OBJ_MODEL 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_et_obj | TYPE RMXMTY_ROM_TREE, " | |||
| lv_i_force_api_init | TYPE FLAG, " 'X' | |||
| lv_i_logsys | TYPE LOGSYS, " | |||
| lv_et_no_auth | TYPE RCPTY_API_NO_AUTH, " | |||
| lv_i_data_scenario | TYPE RCPE_DATASCEN, " 'D' | |||
| lv_et_error | TYPE RMXMTY_MESSAGES, " | |||
| lv_i_valfrom | TYPE RCPE_ADATUM, " | |||
| lv_i_valto | TYPE RCPE_BDATUM, " | |||
| lv_i_range_indep | TYPE FLAG, " 'X' | |||
| lv_i_grp | TYPE RMXME_ROM_GRP, " | |||
| lv_it_keys | TYPE RMXMTY_RCP_INFO, " | |||
| lv_i_langu | TYPE SYLANGU, " SY-LANGU | |||
| lv_i_plant | TYPE WERKS_D. " |
|   CALL FUNCTION 'RMXM950_GENERATE_OBJ_MODEL' "NOTRANSL: ROM: Generiert das Rezeptobjektmodell |
| EXPORTING | ||
| I_FORCE_API_INIT | = lv_i_force_api_init | |
| I_LOGSYS | = lv_i_logsys | |
| I_DATA_SCENARIO | = lv_i_data_scenario | |
| I_VALFROM | = lv_i_valfrom | |
| I_VALTO | = lv_i_valto | |
| I_RANGE_INDEP | = lv_i_range_indep | |
| I_GRP | = lv_i_grp | |
| IT_KEYS | = lv_it_keys | |
| I_LANGU | = lv_i_langu | |
| I_PLANT | = lv_i_plant | |
| IMPORTING | ||
| ET_OBJ | = lv_et_obj | |
| ET_NO_AUTH | = lv_et_no_auth | |
| ET_ERROR | = lv_et_error | |
| . " RMXM950_GENERATE_OBJ_MODEL | ||
ABAP code using 7.40 inline data declarations to call FM RMXM950_GENERATE_OBJ_MODEL
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_i_force_api_init) | = 'X'. | |||
| DATA(ld_i_data_scenario) | = 'D'. | |||
| DATA(ld_i_range_indep) | = 'X'. | |||
| DATA(ld_i_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects