SAP RMXT760_CALL_STD Function Module for NOTRANSL: TMS-TLS: Standardisierung Versuchsverwaltung rufen
RMXT760_CALL_STD is a standard rmxt760 call std 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: TMS-TLS: Standardisierung Versuchsverwaltung rufen 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 rmxt760 call std FM, simply by entering the name RMXT760_CALL_STD into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMXT760
Program Name: SAPLRMXT760
Main Program: SAPLRMXT760
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RMXT760_CALL_STD 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 'RMXT760_CALL_STD'"NOTRANSL: TMS-TLS: Standardisierung Versuchsverwaltung rufen.
EXPORTING
I_ID = "Predefined Type
* IS_POPUP_FIELDS = "TMS-TLS: ID + Text of Stage/Product Being Standardized
* I_FLG_CALL_FROM_WB = "Generic Type
* IV_VALDAT = SY-DATUM "Key Date
* IT_STREAM_DATA = "RMSA: Composition Contribution
* IV_DATA_SOURCE = "Data Source
* I_FLG_DISPLAY = "General Indicator
IMPORTING
E_FLG_CHANGED = "Generic Type
CHANGING
XT_ITEM = "TMS-TLS: Items for the Standardization in Trial Management
EXCEPTIONS
EXC_ABORT = 1 EXC_WRONG_INPUT = 2 EXC_NO_COLUMNS_FOUND = 3 EXC_ERROR = 4 EXC_GET_DATA_ERROR = 5
IMPORTING Parameters details for RMXT760_CALL_STD
I_ID - Predefined Type
Data type: STRINGOptional: No
Call by Reference: Yes
IS_POPUP_FIELDS - TMS-TLS: ID + Text of Stage/Product Being Standardized
Data type: RMXTS_STD_POPUP_FIELDSOptional: Yes
Call by Reference: Yes
I_FLG_CALL_FROM_WB - Generic Type
Data type: COptional: Yes
Call by Reference: Yes
IV_VALDAT - Key Date
Data type: DDefault: SY-DATUM
Optional: Yes
Call by Reference: Yes
IT_STREAM_DATA - RMSA: Composition Contribution
Data type: FRMLTY_CMPOptional: Yes
Call by Reference: Yes
IV_DATA_SOURCE - Data Source
Data type: RMSAE_SRCOptional: Yes
Call by Reference: Yes
I_FLG_DISPLAY - General Indicator
Data type: RMSTE_FLAGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RMXT760_CALL_STD
E_FLG_CHANGED - Generic Type
Data type: COptional: No
Call by Reference: Yes
CHANGING Parameters details for RMXT760_CALL_STD
XT_ITEM - TMS-TLS: Items for the Standardization in Trial Management
Data type: RMXTTY_STD_ITEMOptional: No
Call by Reference: Yes
EXCEPTIONS details
EXC_ABORT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
EXC_WRONG_INPUT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
EXC_NO_COLUMNS_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
EXC_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
EXC_GET_DATA_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RMXT760_CALL_STD 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_i_id | TYPE STRING, " | |||
| lv_xt_item | TYPE RMXTTY_STD_ITEM, " | |||
| lv_exc_abort | TYPE RMXTTY_STD_ITEM, " | |||
| lv_e_flg_changed | TYPE C, " | |||
| lv_exc_wrong_input | TYPE C, " | |||
| lv_is_popup_fields | TYPE RMXTS_STD_POPUP_FIELDS, " | |||
| lv_i_flg_call_from_wb | TYPE C, " | |||
| lv_exc_no_columns_found | TYPE C, " | |||
| lv_exc_error | TYPE C, " | |||
| lv_iv_valdat | TYPE D, " SY-DATUM | |||
| lv_it_stream_data | TYPE FRMLTY_CMP, " | |||
| lv_exc_get_data_error | TYPE FRMLTY_CMP, " | |||
| lv_iv_data_source | TYPE RMSAE_SRC, " | |||
| lv_i_flg_display | TYPE RMSTE_FLAG. " |
|   CALL FUNCTION 'RMXT760_CALL_STD' "NOTRANSL: TMS-TLS: Standardisierung Versuchsverwaltung rufen |
| EXPORTING | ||
| I_ID | = lv_i_id | |
| IS_POPUP_FIELDS | = lv_is_popup_fields | |
| I_FLG_CALL_FROM_WB | = lv_i_flg_call_from_wb | |
| IV_VALDAT | = lv_iv_valdat | |
| IT_STREAM_DATA | = lv_it_stream_data | |
| IV_DATA_SOURCE | = lv_iv_data_source | |
| I_FLG_DISPLAY | = lv_i_flg_display | |
| IMPORTING | ||
| E_FLG_CHANGED | = lv_e_flg_changed | |
| CHANGING | ||
| XT_ITEM | = lv_xt_item | |
| EXCEPTIONS | ||
| EXC_ABORT = 1 | ||
| EXC_WRONG_INPUT = 2 | ||
| EXC_NO_COLUMNS_FOUND = 3 | ||
| EXC_ERROR = 4 | ||
| EXC_GET_DATA_ERROR = 5 | ||
| . " RMXT760_CALL_STD | ||
ABAP code using 7.40 inline data declarations to call FM RMXT760_CALL_STD
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_valdat) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects