SAP MY_PARAMETERS_GET Function Module for









MY_PARAMETERS_GET is a standard my parameters get 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 my parameters get FM, simply by entering the name MY_PARAMETERS_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function MY_PARAMETERS_GET 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 'MY_PARAMETERS_GET'"
EXPORTING
* I_BUKRS = "
* I_MYKEY = "LIFO Valuation Level
* I_METHOD = "
* I_MYXXFO = "
* I_MYFID = "

IMPORTING
E_MYPAR = "
E_METHTEXT = "

EXCEPTIONS
T001_ERROR = 1 T009_ERROR = 2 TMY01_ERROR = 3 TMY02_ERROR = 4 TMY03_ERROR = 5 T001Y_ERROR = 6 BAD_METHOD = 7
.



IMPORTING Parameters details for MY_PARAMETERS_GET

I_BUKRS -

Data type: T001-BUKRS
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MYKEY - LIFO Valuation Level

Data type: T001Y-MYKEY
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_METHOD -

Data type: TMY02-METHOD
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MYXXFO -

Data type: TMY01-MYXXFO
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MYFID -

Data type: TMY01-MYFID
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for MY_PARAMETERS_GET

E_MYPAR -

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

E_METHTEXT -

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

EXCEPTIONS details

T001_ERROR -

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

T009_ERROR -

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

TMY01_ERROR -

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

TMY02_ERROR -

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

TMY03_ERROR -

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

T001Y_ERROR -

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

BAD_METHOD -

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

Copy and paste ABAP code example for MY_PARAMETERS_GET 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_e_mypar  TYPE MYPAR, "   
lv_i_bukrs  TYPE T001-BUKRS, "   
lv_t001_error  TYPE T001, "   
lv_i_mykey  TYPE T001Y-MYKEY, "   
lv_e_methtext  TYPE MYMETHTEXT, "   
lv_t009_error  TYPE MYMETHTEXT, "   
lv_i_method  TYPE TMY02-METHOD, "   
lv_tmy01_error  TYPE TMY02, "   
lv_i_myxxfo  TYPE TMY01-MYXXFO, "   
lv_tmy02_error  TYPE TMY01, "   
lv_i_myfid  TYPE TMY01-MYFID, "   
lv_tmy03_error  TYPE TMY01, "   
lv_t001y_error  TYPE TMY01, "   
lv_bad_method  TYPE TMY01. "   

  CALL FUNCTION 'MY_PARAMETERS_GET'  "
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_MYKEY = lv_i_mykey
         I_METHOD = lv_i_method
         I_MYXXFO = lv_i_myxxfo
         I_MYFID = lv_i_myfid
    IMPORTING
         E_MYPAR = lv_e_mypar
         E_METHTEXT = lv_e_methtext
    EXCEPTIONS
        T001_ERROR = 1
        T009_ERROR = 2
        TMY01_ERROR = 3
        TMY02_ERROR = 4
        TMY03_ERROR = 5
        T001Y_ERROR = 6
        BAD_METHOD = 7
. " MY_PARAMETERS_GET




ABAP code using 7.40 inline data declarations to call FM MY_PARAMETERS_GET

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 BUKRS FROM T001 INTO @DATA(ld_i_bukrs).
 
 
"SELECT single MYKEY FROM T001Y INTO @DATA(ld_i_mykey).
 
 
 
"SELECT single METHOD FROM TMY02 INTO @DATA(ld_i_method).
 
 
"SELECT single MYXXFO FROM TMY01 INTO @DATA(ld_i_myxxfo).
 
 
"SELECT single MYFID FROM TMY01 INTO @DATA(ld_i_myfid).
 
 
 
 


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!