SAP ACE_CONVERT_GENERIC_RANGES Function Module for Conversion of Range Tables into Where-Clauses
ACE_CONVERT_GENERIC_RANGES is a standard ace convert generic ranges SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Conversion of Range Tables into Where-Clauses 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 convert generic ranges FM, simply by entering the name ACE_CONVERT_GENERIC_RANGES into the relevant SAP transaction such as SE37 or SE38.
Function Group: ACE3
Program Name: SAPLACE3
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ACE_CONVERT_GENERIC_RANGES 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_CONVERT_GENERIC_RANGES'"Conversion of Range Tables into Where-Clauses.
EXPORTING
IS_COMP_RANGES = "Selection Options
IMPORTING
ET_WHERE_CLAUSES = "Where-Clauses
IMPORTING Parameters details for ACE_CONVERT_GENERIC_RANGES
IS_COMP_RANGES - Selection Options
Data type: ACE_COMP_SPECIFIC_OBJ_RANGESOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ACE_CONVERT_GENERIC_RANGES
ET_WHERE_CLAUSES - Where-Clauses
Data type: RSDS_WHERE_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ACE_CONVERT_GENERIC_RANGES 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_is_comp_ranges | TYPE ACE_COMP_SPECIFIC_OBJ_RANGES, " | |||
| lv_et_where_clauses | TYPE RSDS_WHERE_TAB. " |
|   CALL FUNCTION 'ACE_CONVERT_GENERIC_RANGES' "Conversion of Range Tables into Where-Clauses |
| EXPORTING | ||
| IS_COMP_RANGES | = lv_is_comp_ranges | |
| IMPORTING | ||
| ET_WHERE_CLAUSES | = lv_et_where_clauses | |
| . " ACE_CONVERT_GENERIC_RANGES | ||
ABAP code using 7.40 inline data declarations to call FM ACE_CONVERT_GENERIC_RANGES
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