SAP RSAU_API_GET_PARAM Function Module for

Search SAP Function Modules

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

Function Group: RSAU_LOG
Program Name: SAPLRSAU_LOG
Main Program: SAPLRSAU_LOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RSAU_API_GET_PARAM 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 'RSAU_API_GET_PARAM'"
  EXPORTING
*  ID_GET_FROM_KP = 'X' "
*  ID_WITH_CONSI_CHK =  "

 IMPORTING
   ED_ACTIV =  "
   ED_MBYTE_DAY =  "
   ED_MBYTE_SGL =  "
   ED_ALIVE_TEST_INTV =  "
   ED_MRP_IN_DB =  "
   ED_POD =  "
   ET_RESULT =  "
   ED_TARGET =  "
   ED_DBMODE =  "
   ED_DB_TAB =  "
   ED_SLOTS =  "
   ED_GEN_USER =  "
   ED_INTEGRITY =  "
   ED_PEER_ADR =  "
   ED_MBYTE_FILE =  "

.

IMPORTING Parameters details for RSAU_API_GET_PARAM

ID_GET_FROM_KP -

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

ID_WITH_CONSI_CHK -

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

EXPORTING Parameters details for RSAU_API_GET_PARAM

ED_ACTIV -

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

ED_MBYTE_DAY -

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

ED_MBYTE_SGL -

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

ED_ALIVE_TEST_INTV -

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

ED_MRP_IN_DB -

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

ED_POD -

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

ET_RESULT -

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

ED_TARGET -

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

ED_DBMODE -

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

ED_DB_TAB -

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

ED_SLOTS -

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

ED_GEN_USER -

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

ED_INTEGRITY -

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

ED_PEER_ADR -

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

ED_MBYTE_FILE -

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

Copy and paste ABAP code example for RSAU_API_GET_PARAM 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.

ABAP code using 7.40 inline data declarations to call FM RSAU_API_GET_PARAM

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.

Search for further information about these or an SAP related objects