SAP RMXT412_CREATE_STABILITY_STUDY Function Module for NOTRANSL: TMS-QM: Stabilitätsstudie anlegen und bearbeiten









RMXT412_CREATE_STABILITY_STUDY is a standard rmxt412 create stability study 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-QM: Stabilitätsstudie anlegen und bearbeiten 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 rmxt412 create stability study FM, simply by entering the name RMXT412_CREATE_STABILITY_STUDY into the relevant SAP transaction such as SE37 or SE38.

Function Group: RMXT412
Program Name: SAPLRMXT412
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RMXT412_CREATE_STABILITY_STUDY 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 'RMXT412_CREATE_STABILITY_STUDY'"NOTRANSL: TMS-QM: Stabilitätsstudie anlegen und bearbeiten
  EXPORTING
   IS_RELATION =  "Trial Relationships
   IS_TRIAL_HEAD =  "Trial: Header Data
*  I_BIN_RELATIONSHIP = ' ' "Checkbox
*  I_POST = 'X' "Checkbox
*  I_COMMIT = 'X' "Commit Work
*  I_WAIT = 'X' "Commit Work and Wait

 IMPORTING
   ES_VIQMEL =  "Generated Table for View VIQMEL
   E_SUCCESSFUL =  "General Flag

TABLES
*  TE_MESSAGES =  "Return Parameter

EXCEPTIONS
   NOT_CREATED = 1
.



IMPORTING Parameters details for RMXT412_CREATE_STABILITY_STUDY

IS_RELATION - Trial Relationships

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

IS_TRIAL_HEAD - Trial: Header Data

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

I_BIN_RELATIONSHIP - Checkbox

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

I_POST - Checkbox

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

I_COMMIT - Commit Work

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

I_WAIT - Commit Work and Wait

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

EXPORTING Parameters details for RMXT412_CREATE_STABILITY_STUDY

ES_VIQMEL - Generated Table for View VIQMEL

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

E_SUCCESSFUL - General Flag

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

TABLES Parameters details for RMXT412_CREATE_STABILITY_STUDY

TE_MESSAGES - Return Parameter

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

EXCEPTIONS details

NOT_CREATED - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RMXT412_CREATE_STABILITY_STUDY 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_es_viqmel  TYPE VIQMEL, "   
lv_is_relation  TYPE RMXTS_TRIAL_REL, "   
lv_not_created  TYPE RMXTS_TRIAL_REL, "   
lt_te_messages  TYPE STANDARD TABLE OF RMXTTY_MESSAGES, "   
lv_e_successful  TYPE FLAG, "   
lv_is_trial_head  TYPE RMXTS_TRIAL_HD, "   
lv_i_bin_relationship  TYPE RIWO00-SELEC, "   SPACE
lv_i_post  TYPE RIWO00-SELEC, "   'X'
lv_i_commit  TYPE RIWO00-SELEC, "   'X'
lv_i_wait  TYPE RIWO00-SELEC. "   'X'

  CALL FUNCTION 'RMXT412_CREATE_STABILITY_STUDY'  "NOTRANSL: TMS-QM: Stabilitätsstudie anlegen und bearbeiten
    EXPORTING
         IS_RELATION = lv_is_relation
         IS_TRIAL_HEAD = lv_is_trial_head
         I_BIN_RELATIONSHIP = lv_i_bin_relationship
         I_POST = lv_i_post
         I_COMMIT = lv_i_commit
         I_WAIT = lv_i_wait
    IMPORTING
         ES_VIQMEL = lv_es_viqmel
         E_SUCCESSFUL = lv_e_successful
    TABLES
         TE_MESSAGES = lt_te_messages
    EXCEPTIONS
        NOT_CREATED = 1
. " RMXT412_CREATE_STABILITY_STUDY




ABAP code using 7.40 inline data declarations to call FM RMXT412_CREATE_STABILITY_STUDY

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.

 
 
 
 
 
 
"SELECT single SELEC FROM RIWO00 INTO @DATA(ld_i_bin_relationship).
DATA(ld_i_bin_relationship) = ' '.
 
"SELECT single SELEC FROM RIWO00 INTO @DATA(ld_i_post).
DATA(ld_i_post) = 'X'.
 
"SELECT single SELEC FROM RIWO00 INTO @DATA(ld_i_commit).
DATA(ld_i_commit) = 'X'.
 
"SELECT single SELEC FROM RIWO00 INTO @DATA(ld_i_wait).
DATA(ld_i_wait) = '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!