SAP RERA_GET_ADJUST_PARAMETERS Function Module for
RERA_GET_ADJUST_PARAMETERS is a standard rera get adjust parameters 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 rera get adjust parameters FM, simply by entering the name RERA_GET_ADJUST_PARAMETERS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVMA10
Program Name: SAPLFVMA10
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RERA_GET_ADJUST_PARAMETERS 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 'RERA_GET_ADJUST_PARAMETERS'".
EXPORTING
I_SANPNR = "
I_SACTNR = "
IMPORTING
E_VVOBJCT = "
E_VVACTVT = "
E_MC_ID = "
E_WORK_AREA = "
E_NEED_AGREEMENT = "
E_TITLE_TEXT = "
E_SANPNR_TEXT = "
E_SACTNR_TEXT = "
E_XMODK = "
EXCEPTIONS
UNKNOWN_ADJUST_MODE = 1 UNKNOWN_ADJUST_ACTIVITY = 2 CUSTOMIZING_ERROR = 3
IMPORTING Parameters details for RERA_GET_ADJUST_PARAMETERS
I_SANPNR -
Data type: TIV11-SANPNROptional: No
Call by Reference: No ( called with pass by value option)
I_SACTNR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RERA_GET_ADJUST_PARAMETERS
E_VVOBJCT -
Data type: TSTCA-OBJCTOptional: No
Call by Reference: No ( called with pass by value option)
E_VVACTVT -
Data type: RFVZBEROBJ-VVACTVTOptional: No
Call by Reference: No ( called with pass by value option)
E_MC_ID -
Data type: DDSHDESCR-SHLPNAMEOptional: No
Call by Reference: No ( called with pass by value option)
E_WORK_AREA -
Data type: TZW02-SARBGOptional: No
Call by Reference: No ( called with pass by value option)
E_NEED_AGREEMENT -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
E_TITLE_TEXT -
Data type: SY-TITLEOptional: No
Call by Reference: No ( called with pass by value option)
E_SANPNR_TEXT -
Data type: SY-TITLEOptional: No
Call by Reference: No ( called with pass by value option)
E_SACTNR_TEXT -
Data type: SY-TITLEOptional: No
Call by Reference: No ( called with pass by value option)
E_XMODK -
Data type: TIV1A-XMODKOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
UNKNOWN_ADJUST_MODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_ADJUST_ACTIVITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CUSTOMIZING_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RERA_GET_ADJUST_PARAMETERS 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_sanpnr | TYPE TIV11-SANPNR, " | |||
lv_e_vvobjct | TYPE TSTCA-OBJCT, " | |||
lv_unknown_adjust_mode | TYPE TSTCA, " | |||
lv_i_sactnr | TYPE TSTCA, " | |||
lv_e_vvactvt | TYPE RFVZBEROBJ-VVACTVT, " | |||
lv_unknown_adjust_activity | TYPE RFVZBEROBJ, " | |||
lv_e_mc_id | TYPE DDSHDESCR-SHLPNAME, " | |||
lv_customizing_error | TYPE DDSHDESCR, " | |||
lv_e_work_area | TYPE TZW02-SARBG, " | |||
lv_e_need_agreement | TYPE C, " | |||
lv_e_title_text | TYPE SY-TITLE, " | |||
lv_e_sanpnr_text | TYPE SY-TITLE, " | |||
lv_e_sactnr_text | TYPE SY-TITLE, " | |||
lv_e_xmodk | TYPE TIV1A-XMODK. " |
  CALL FUNCTION 'RERA_GET_ADJUST_PARAMETERS' " |
EXPORTING | ||
I_SANPNR | = lv_i_sanpnr | |
I_SACTNR | = lv_i_sactnr | |
IMPORTING | ||
E_VVOBJCT | = lv_e_vvobjct | |
E_VVACTVT | = lv_e_vvactvt | |
E_MC_ID | = lv_e_mc_id | |
E_WORK_AREA | = lv_e_work_area | |
E_NEED_AGREEMENT | = lv_e_need_agreement | |
E_TITLE_TEXT | = lv_e_title_text | |
E_SANPNR_TEXT | = lv_e_sanpnr_text | |
E_SACTNR_TEXT | = lv_e_sactnr_text | |
E_XMODK | = lv_e_xmodk | |
EXCEPTIONS | ||
UNKNOWN_ADJUST_MODE = 1 | ||
UNKNOWN_ADJUST_ACTIVITY = 2 | ||
CUSTOMIZING_ERROR = 3 | ||
. " RERA_GET_ADJUST_PARAMETERS |
ABAP code using 7.40 inline data declarations to call FM RERA_GET_ADJUST_PARAMETERS
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 SANPNR FROM TIV11 INTO @DATA(ld_i_sanpnr). | ||||
"SELECT single OBJCT FROM TSTCA INTO @DATA(ld_e_vvobjct). | ||||
"SELECT single VVACTVT FROM RFVZBEROBJ INTO @DATA(ld_e_vvactvt). | ||||
"SELECT single SHLPNAME FROM DDSHDESCR INTO @DATA(ld_e_mc_id). | ||||
"SELECT single SARBG FROM TZW02 INTO @DATA(ld_e_work_area). | ||||
"SELECT single TITLE FROM SY INTO @DATA(ld_e_title_text). | ||||
"SELECT single TITLE FROM SY INTO @DATA(ld_e_sanpnr_text). | ||||
"SELECT single TITLE FROM SY INTO @DATA(ld_e_sactnr_text). | ||||
"SELECT single XMODK FROM TIV1A INTO @DATA(ld_e_xmodk). | ||||
Search for further information about these or an SAP related objects