SAP IPMO_ACE_TREE_LAYOUT_SET Function Module for
IPMO_ACE_TREE_LAYOUT_SET is a standard ipmo ace tree layout set 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 ipmo ace tree layout set FM, simply by entering the name IPMO_ACE_TREE_LAYOUT_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: IPMO_ACE_USER_INTERFACE
Program Name: SAPLIPMO_ACE_USER_INTERFACE
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IPMO_ACE_TREE_LAYOUT_SET 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 'IPMO_ACE_TREE_LAYOUT_SET'".
EXPORTING
IS_OBJECT_KEY = "
ID_FIELD_NAME = "
ID_TREE_VARIANT = "
IMPORTING
ED_NODE_TEXT = "
IMPORTING Parameters details for IPMO_ACE_TREE_LAYOUT_SET
IS_OBJECT_KEY -
Data type: CRM_ACE_TREE_STRUCTUREOptional: No
Call by Reference: Yes
ID_FIELD_NAME -
Data type: DFIES-FIELDNAMEOptional: No
Call by Reference: Yes
ID_TREE_VARIANT -
Data type: ACE_TREEVARIOptional: No
Call by Reference: Yes
EXPORTING Parameters details for IPMO_ACE_TREE_LAYOUT_SET
ED_NODE_TEXT -
Data type: LVC_VALUEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for IPMO_ACE_TREE_LAYOUT_SET 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_ed_node_text | TYPE LVC_VALUE, " | |||
| lv_is_object_key | TYPE CRM_ACE_TREE_STRUCTURE, " | |||
| lv_id_field_name | TYPE DFIES-FIELDNAME, " | |||
| lv_id_tree_variant | TYPE ACE_TREEVARI. " |
|   CALL FUNCTION 'IPMO_ACE_TREE_LAYOUT_SET' " |
| EXPORTING | ||
| IS_OBJECT_KEY | = lv_is_object_key | |
| ID_FIELD_NAME | = lv_id_field_name | |
| ID_TREE_VARIANT | = lv_id_tree_variant | |
| IMPORTING | ||
| ED_NODE_TEXT | = lv_ed_node_text | |
| . " IPMO_ACE_TREE_LAYOUT_SET | ||
ABAP code using 7.40 inline data declarations to call FM IPMO_ACE_TREE_LAYOUT_SET
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 FIELDNAME FROM DFIES INTO @DATA(ld_id_field_name). | ||||
Search for further information about these or an SAP related objects