SAP AMYO_GET_MY_OBJECTS Function Module for









AMYO_GET_MY_OBJECTS is a standard amyo get my objects 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 amyo get my objects FM, simply by entering the name AMYO_GET_MY_OBJECTS into the relevant SAP transaction such as SE37 or SE38.

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



Function AMYO_GET_MY_OBJECTS 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 'AMYO_GET_MY_OBJECTS'"
  EXPORTING
*  UNAME = SY-UNAME "
*  FILTER_NODE = ' ' "
*  FILTER_OBJTYPE = ' ' "
*  MAX_COUNT = 0 "

 IMPORTING
   OBJ_COUNT =  "

TABLES
   MY_OBJECTS =  "

EXCEPTIONS
   NODE_DEFINITION_NOT_EXIST = 1    OBJECTTYPE_NOT_ALLOWED = 2    FILTER_NODE_NOT_EXIST = 3    PERSONALISATION_ERROR = 4    DB_ERROR = 5
.



IMPORTING Parameters details for AMYO_GET_MY_OBJECTS

UNAME -

Data type: AMYOTREE-USER_NAME
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

FILTER_NODE -

Data type: AMYOTREE-PARENT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FILTER_OBJTYPE -

Data type: AMYOTREE-OBJTYPE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MAX_COUNT -

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

EXPORTING Parameters details for AMYO_GET_MY_OBJECTS

OBJ_COUNT -

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

TABLES Parameters details for AMYO_GET_MY_OBJECTS

MY_OBJECTS -

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

EXCEPTIONS details

NODE_DEFINITION_NOT_EXIST -

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

OBJECTTYPE_NOT_ALLOWED -

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

FILTER_NODE_NOT_EXIST -

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

PERSONALISATION_ERROR -

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

DB_ERROR -

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

Copy and paste ABAP code example for AMYO_GET_MY_OBJECTS 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_uname  TYPE AMYOTREE-USER_NAME, "   SY-UNAME
lv_obj_count  TYPE AMYOTREE-POSI, "   
lt_my_objects  TYPE STANDARD TABLE OF AMYO_S_OBJ, "   
lv_node_definition_not_exist  TYPE AMYO_S_OBJ, "   
lv_filter_node  TYPE AMYOTREE-PARENT, "   SPACE
lv_objecttype_not_allowed  TYPE AMYOTREE, "   
lv_filter_objtype  TYPE AMYOTREE-OBJTYPE, "   SPACE
lv_filter_node_not_exist  TYPE AMYOTREE, "   
lv_max_count  TYPE AMYOTREE-POSI, "   0
lv_personalisation_error  TYPE AMYOTREE, "   
lv_db_error  TYPE AMYOTREE. "   

  CALL FUNCTION 'AMYO_GET_MY_OBJECTS'  "
    EXPORTING
         UNAME = lv_uname
         FILTER_NODE = lv_filter_node
         FILTER_OBJTYPE = lv_filter_objtype
         MAX_COUNT = lv_max_count
    IMPORTING
         OBJ_COUNT = lv_obj_count
    TABLES
         MY_OBJECTS = lt_my_objects
    EXCEPTIONS
        NODE_DEFINITION_NOT_EXIST = 1
        OBJECTTYPE_NOT_ALLOWED = 2
        FILTER_NODE_NOT_EXIST = 3
        PERSONALISATION_ERROR = 4
        DB_ERROR = 5
. " AMYO_GET_MY_OBJECTS




ABAP code using 7.40 inline data declarations to call FM AMYO_GET_MY_OBJECTS

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 USER_NAME FROM AMYOTREE INTO @DATA(ld_uname).
DATA(ld_uname) = SY-UNAME.
 
"SELECT single POSI FROM AMYOTREE INTO @DATA(ld_obj_count).
 
 
 
"SELECT single PARENT FROM AMYOTREE INTO @DATA(ld_filter_node).
DATA(ld_filter_node) = ' '.
 
 
"SELECT single OBJTYPE FROM AMYOTREE INTO @DATA(ld_filter_objtype).
DATA(ld_filter_objtype) = ' '.
 
 
"SELECT single POSI FROM AMYOTREE INTO @DATA(ld_max_count).
 
 
 


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!