SAP ACE_DATA_EXIST_CHECK Function Module for Check Whether Transaction Data Exists
ACE_DATA_EXIST_CHECK is a standard ace data exist check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Whether Transaction Data Exists 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 data exist check FM, simply by entering the name ACE_DATA_EXIST_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: ACE_DATA_CHECK
Program Name: SAPLACE_DATA_CHECK
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ACE_DATA_EXIST_CHECK 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_DATA_EXIST_CHECK'"Check Whether Transaction Data Exists.
EXPORTING
ID_COMP = "Application Component for Accrual
IT_GENERIC_RANGES = "Table with Field-Specific Selection Options
EXCEPTIONS
DATA_FOUND = 1 ERROR_OCCURRED = 2
IMPORTING Parameters details for ACE_DATA_EXIST_CHECK
ID_COMP - Application Component for Accrual
Data type: ACE_COMPOptional: No
Call by Reference: Yes
IT_GENERIC_RANGES - Table with Field-Specific Selection Options
Data type: ACE_FIELD_RANGES_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
DATA_FOUND - Transaction data exists in the Accrual Engine
Data type:Optional: No
Call by Reference: Yes
ERROR_OCCURRED - An error has occurred
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ACE_DATA_EXIST_CHECK 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_data_found | TYPE ACE_COMP, " | |||
| lv_error_occurred | TYPE ACE_COMP, " | |||
| lv_it_generic_ranges | TYPE ACE_FIELD_RANGES_T. " |
|   CALL FUNCTION 'ACE_DATA_EXIST_CHECK' "Check Whether Transaction Data Exists |
| EXPORTING | ||
| ID_COMP | = lv_id_comp | |
| IT_GENERIC_RANGES | = lv_it_generic_ranges | |
| EXCEPTIONS | ||
| DATA_FOUND = 1 | ||
| ERROR_OCCURRED = 2 | ||
| . " ACE_DATA_EXIST_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM ACE_DATA_EXIST_CHECK
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.Search for further information about these or an SAP related objects