SAP RS_MANDT_UNIQUE_GET Function Module for Determine BW Client









RS_MANDT_UNIQUE_GET is a standard rs mandt unique get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine BW Client 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 rs mandt unique get FM, simply by entering the name RS_MANDT_UNIQUE_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function RS_MANDT_UNIQUE_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 'RS_MANDT_UNIQUE_GET'"Determine BW Client
IMPORTING
E_UNIQUE_MANDT = "
E_BWMANDTRFC = "RFC Destination for Logon to BW Client

EXCEPTIONS
NO_BW_MANDT = 1 X_MESSAGE = 2
.



EXPORTING Parameters details for RS_MANDT_UNIQUE_GET

E_UNIQUE_MANDT -

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

E_BWMANDTRFC - RFC Destination for Logon to BW Client

Data type: RSBWMANDRFC
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_BW_MANDT -

Data type:
Optional: No
Call by Reference: Yes

X_MESSAGE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RS_MANDT_UNIQUE_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_no_bw_mandt  TYPE STRING, "   
lv_e_unique_mandt  TYPE SY-MANDT, "   
lv_x_message  TYPE SY, "   
lv_e_bwmandtrfc  TYPE RSBWMANDRFC. "   

  CALL FUNCTION 'RS_MANDT_UNIQUE_GET'  "Determine BW Client
    IMPORTING
         E_UNIQUE_MANDT = lv_e_unique_mandt
         E_BWMANDTRFC = lv_e_bwmandtrfc
    EXCEPTIONS
        NO_BW_MANDT = 1
        X_MESSAGE = 2
. " RS_MANDT_UNIQUE_GET




ABAP code using 7.40 inline data declarations to call FM RS_MANDT_UNIQUE_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 MANDT FROM SY INTO @DATA(ld_e_unique_mandt).
 
 
 


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!