SAP CACS_CLONE_GET_COND_TABLES Function Module for NOTRANSL: Konditionstabellen hohlen
CACS_CLONE_GET_COND_TABLES is a standard cacs clone get cond tables 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: Konditionstabellen hohlen 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 clone get cond tables FM, simply by entering the name CACS_CLONE_GET_COND_TABLES into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_CLONE
Program Name: SAPLCACS_CLONE
Main Program: SAPLCACS_CLONE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function CACS_CLONE_GET_COND_TABLES 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_CLONE_GET_COND_TABLES'"NOTRANSL: Konditionstabellen hohlen.
EXPORTING
IV_APPL = "Commission Application Identification
IV_XMLDATE = "Date
IV_XMLTIME = "Time
IMPORTING
EV_DATA = "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for CACS_CLONE_GET_COND_TABLES
IV_APPL - Commission Application Identification
Data type: CACSAPPLOptional: No
Call by Reference: No ( called with pass by value option)
IV_XMLDATE - Date
Data type: DATUMOptional: No
Call by Reference: No ( called with pass by value option)
IV_XMLTIME - Time
Data type: UZEITOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CACS_CLONE_GET_COND_TABLES
EV_DATA -
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS_CLONE_GET_COND_TABLES 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_error | TYPE STRING, " | |||
lv_ev_data | TYPE STRING, " | |||
lv_iv_appl | TYPE CACSAPPL, " | |||
lv_iv_xmldate | TYPE DATUM, " | |||
lv_iv_xmltime | TYPE UZEIT. " |
  CALL FUNCTION 'CACS_CLONE_GET_COND_TABLES' "NOTRANSL: Konditionstabellen hohlen |
EXPORTING | ||
IV_APPL | = lv_iv_appl | |
IV_XMLDATE | = lv_iv_xmldate | |
IV_XMLTIME | = lv_iv_xmltime | |
IMPORTING | ||
EV_DATA | = lv_ev_data | |
EXCEPTIONS | ||
ERROR = 1 | ||
. " CACS_CLONE_GET_COND_TABLES |
ABAP code using 7.40 inline data declarations to call FM CACS_CLONE_GET_COND_TABLES
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