SAP UI_ORDER_USER_DATA Function Module for









UI_ORDER_USER_DATA is a standard ui order user data 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 ui order user data FM, simply by entering the name UI_ORDER_USER_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function UI_ORDER_USER_DATA 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 'UI_ORDER_USER_DATA'"
EXPORTING
I_USERNAME = "

IMPORTING
ES_ADDRESS = "

TABLES
* ET_RETURN = "
* ET_LANG = "
.



IMPORTING Parameters details for UI_ORDER_USER_DATA

I_USERNAME -

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

EXPORTING Parameters details for UI_ORDER_USER_DATA

ES_ADDRESS -

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

TABLES Parameters details for UI_ORDER_USER_DATA

ET_RETURN -

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

ET_LANG -

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

Copy and paste ABAP code example for UI_ORDER_USER_DATA 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:
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_es_address  TYPE BAPIADDR3, "   
lv_i_username  TYPE BAPIBNAME-BAPIBNAME, "   
lt_et_lang  TYPE STANDARD TABLE OF T002T. "   

  CALL FUNCTION 'UI_ORDER_USER_DATA'  "
    EXPORTING
         I_USERNAME = lv_i_username
    IMPORTING
         ES_ADDRESS = lv_es_address
    TABLES
         ET_RETURN = lt_et_return
         ET_LANG = lt_et_lang
. " UI_ORDER_USER_DATA




ABAP code using 7.40 inline data declarations to call FM UI_ORDER_USER_DATA

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 BAPIBNAME FROM BAPIBNAME INTO @DATA(ld_i_username).
 
 


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!