SAP CACS_VERS_OVERLAP Function Module for NOTRANSL: Zeilen versionsgeführter Tabellen auf Überlappung prüfen
CACS_VERS_OVERLAP is a standard cacs vers overlap SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Zeilen versionsgeführter Tabellen auf Überlappung prüfen 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 cacs vers overlap FM, simply by entering the name CACS_VERS_OVERLAP into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_VERS
Program Name: SAPLCACS_VERS
Main Program: SAPLCACS_VERS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS_VERS_OVERLAP 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 'CACS_VERS_OVERLAP'"NOTRANSL: Zeilen versionsgeführter Tabellen auf Überlappung prüfen.
EXPORTING
I_LINE1 = "
I_LINE2 = "
* I_FIELD_TECH_BEGIN = 'TECH_BEGIN' "
* I_FIELD_TECH_END = 'TECH_END' "
* I_FIELD_BUSI_BEGIN = 'BUSI_BEGIN' "
* I_FIELD_BUSI_END = 'BUSI_END' "
IMPORTING
E_OVERLAP = "Boolean Variables (X=true, space=false)
EXCEPTIONS
ASSIGN_FAILED = 1
IMPORTING Parameters details for CACS_VERS_OVERLAP
I_LINE1 -
Data type:Optional: No
Call by Reference: Yes
I_LINE2 -
Data type:Optional: No
Call by Reference: Yes
I_FIELD_TECH_BEGIN -
Data type: FIELDNAMEDefault: 'TECH_BEGIN'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FIELD_TECH_END -
Data type: FIELDNAMEDefault: 'TECH_END'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FIELD_BUSI_BEGIN -
Data type: FIELDNAMEDefault: 'BUSI_BEGIN'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FIELD_BUSI_END -
Data type: FIELDNAMEDefault: 'BUSI_END'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CACS_VERS_OVERLAP
E_OVERLAP - Boolean Variables (X=true, space=false)
Data type: COptional: No
Call by Reference: Yes
EXCEPTIONS details
ASSIGN_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS_VERS_OVERLAP 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_i_line1 | TYPE STRING, " | |||
| lv_e_overlap | TYPE C, " | |||
| lv_assign_failed | TYPE C, " | |||
| lv_i_line2 | TYPE C, " | |||
| lv_i_field_tech_begin | TYPE FIELDNAME, " 'TECH_BEGIN' | |||
| lv_i_field_tech_end | TYPE FIELDNAME, " 'TECH_END' | |||
| lv_i_field_busi_begin | TYPE FIELDNAME, " 'BUSI_BEGIN' | |||
| lv_i_field_busi_end | TYPE FIELDNAME. " 'BUSI_END' |
|   CALL FUNCTION 'CACS_VERS_OVERLAP' "NOTRANSL: Zeilen versionsgeführter Tabellen auf Überlappung prüfen |
| EXPORTING | ||
| I_LINE1 | = lv_i_line1 | |
| I_LINE2 | = lv_i_line2 | |
| I_FIELD_TECH_BEGIN | = lv_i_field_tech_begin | |
| I_FIELD_TECH_END | = lv_i_field_tech_end | |
| I_FIELD_BUSI_BEGIN | = lv_i_field_busi_begin | |
| I_FIELD_BUSI_END | = lv_i_field_busi_end | |
| IMPORTING | ||
| E_OVERLAP | = lv_e_overlap | |
| EXCEPTIONS | ||
| ASSIGN_FAILED = 1 | ||
| . " CACS_VERS_OVERLAP | ||
ABAP code using 7.40 inline data declarations to call FM CACS_VERS_OVERLAP
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_i_field_tech_begin) | = 'TECH_BEGIN'. | |||
| DATA(ld_i_field_tech_end) | = 'TECH_END'. | |||
| DATA(ld_i_field_busi_begin) | = 'BUSI_BEGIN'. | |||
| DATA(ld_i_field_busi_end) | = 'BUSI_END'. | |||
Search for further information about these or an SAP related objects