SAP ACE_DISPLAY_SINGLE_ACE_OBJECT Function Module for Display Individual Accrual Object (Without Tree)
ACE_DISPLAY_SINGLE_ACE_OBJECT is a standard ace display single ace object SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Individual Accrual Object (Without Tree) 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 ace display single ace object FM, simply by entering the name ACE_DISPLAY_SINGLE_ACE_OBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: ACE_USER_INTERFACE
Program Name: SAPLACE_USER_INTERFACE
Main Program: SAPLACE_USER_INTERFACE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ACE_DISPLAY_SINGLE_ACE_OBJECT 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 'ACE_DISPLAY_SINGLE_ACE_OBJECT'"Display Individual Accrual Object (Without Tree).
EXPORTING
ID_COMP = "Accrual Engine Application Component
ID_BUKRS = "Company Code
ID_OBJID = "Accrual Object (Internal Display in Form of a GUID)
ID_SUBID = "Accrual Subobject (Internal Display, Sequence Number)
ID_KEYDATE = "Posting Date / Key Date for Accruals
* ID_MODE = '03' "Edit Mode
* ID_DISPLAY_TREE = "Display Tree
* ID_TREE_VARIANT = "Tree variant
EXCEPTIONS
NOT_FOUND = 1 NO_AUTHORIZATION = 2 ERROR_OCCURRED = 3
IMPORTING Parameters details for ACE_DISPLAY_SINGLE_ACE_OBJECT
ID_COMP - Accrual Engine Application Component
Data type: ACE_COMPOptional: No
Call by Reference: Yes
ID_BUKRS - Company Code
Data type: ACE_BUKRSOptional: No
Call by Reference: Yes
ID_OBJID - Accrual Object (Internal Display in Form of a GUID)
Data type: ACE_GUIDOptional: No
Call by Reference: Yes
ID_SUBID - Accrual Subobject (Internal Display, Sequence Number)
Data type: ACE_SUBIDOptional: No
Call by Reference: Yes
ID_KEYDATE - Posting Date / Key Date for Accruals
Data type: ACE_KEYDATEOptional: No
Call by Reference: Yes
ID_MODE - Edit Mode
Data type: ACEDS_AUTH_ACTIVITYDefault: '03'
Optional: Yes
Call by Reference: Yes
ID_DISPLAY_TREE - Display Tree
Data type: FLAGOptional: Yes
Call by Reference: Yes
ID_TREE_VARIANT - Tree variant
Data type: ACE_TREEVARIOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - Not Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORIZATION - No authorization for this action
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_OCCURRED - An error has occurred
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ACE_DISPLAY_SINGLE_ACE_OBJECT 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_id_comp | TYPE ACE_COMP, " | |||
| lv_not_found | TYPE ACE_COMP, " | |||
| lv_id_bukrs | TYPE ACE_BUKRS, " | |||
| lv_no_authorization | TYPE ACE_BUKRS, " | |||
| lv_id_objid | TYPE ACE_GUID, " | |||
| lv_error_occurred | TYPE ACE_GUID, " | |||
| lv_id_subid | TYPE ACE_SUBID, " | |||
| lv_id_keydate | TYPE ACE_KEYDATE, " | |||
| lv_id_mode | TYPE ACEDS_AUTH_ACTIVITY, " '03' | |||
| lv_id_display_tree | TYPE FLAG, " | |||
| lv_id_tree_variant | TYPE ACE_TREEVARI. " |
|   CALL FUNCTION 'ACE_DISPLAY_SINGLE_ACE_OBJECT' "Display Individual Accrual Object (Without Tree) |
| EXPORTING | ||
| ID_COMP | = lv_id_comp | |
| ID_BUKRS | = lv_id_bukrs | |
| ID_OBJID | = lv_id_objid | |
| ID_SUBID | = lv_id_subid | |
| ID_KEYDATE | = lv_id_keydate | |
| ID_MODE | = lv_id_mode | |
| ID_DISPLAY_TREE | = lv_id_display_tree | |
| ID_TREE_VARIANT | = lv_id_tree_variant | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| NO_AUTHORIZATION = 2 | ||
| ERROR_OCCURRED = 3 | ||
| . " ACE_DISPLAY_SINGLE_ACE_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM ACE_DISPLAY_SINGLE_ACE_OBJECT
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.| DATA(ld_id_mode) | = '03'. | |||
Search for further information about these or an SAP related objects