SAP EVAL_DEFAULT_ORGUNIT Function Module for
EVAL_DEFAULT_ORGUNIT is a standard eval default orgunit 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 eval default orgunit FM, simply by entering the name EVAL_DEFAULT_ORGUNIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: ESS_ORG_TREE
Program Name: SAPLESS_ORG_TREE
Main Program: SAPLESS_ORG_TREE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EVAL_DEFAULT_ORGUNIT 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 'EVAL_DEFAULT_ORGUNIT'".
EXPORTING
PERS_OBJID = "
IMPORTING
DEFAULT_ORGUNIT = "
EXCEPTIONS
INVALID_PERS_NUMBER = 1
IMPORTING Parameters details for EVAL_DEFAULT_ORGUNIT
PERS_OBJID -
Data type: OBJEC-OBJIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EVAL_DEFAULT_ORGUNIT
DEFAULT_ORGUNIT -
Data type: OBJEC-OBJIDOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_PERS_NUMBER -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EVAL_DEFAULT_ORGUNIT 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_pers_objid | TYPE OBJEC-OBJID, " | |||
| lv_default_orgunit | TYPE OBJEC-OBJID, " | |||
| lv_invalid_pers_number | TYPE OBJEC. " |
|   CALL FUNCTION 'EVAL_DEFAULT_ORGUNIT' " |
| EXPORTING | ||
| PERS_OBJID | = lv_pers_objid | |
| IMPORTING | ||
| DEFAULT_ORGUNIT | = lv_default_orgunit | |
| EXCEPTIONS | ||
| INVALID_PERS_NUMBER = 1 | ||
| . " EVAL_DEFAULT_ORGUNIT | ||
ABAP code using 7.40 inline data declarations to call FM EVAL_DEFAULT_ORGUNIT
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 OBJID FROM OBJEC INTO @DATA(ld_pers_objid). | ||||
| "SELECT single OBJID FROM OBJEC INTO @DATA(ld_default_orgunit). | ||||
Search for further information about these or an SAP related objects