SAP CACS_CREATE_FLAT_COND_FILE Function Module for NOTRANSL: Erzeugen einer sequentiellen Datei
CACS_CREATE_FLAT_COND_FILE is a standard cacs create flat cond file 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: Erzeugen einer sequentiellen Datei 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 create flat cond file FM, simply by entering the name CACS_CREATE_FLAT_COND_FILE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_TRANSPORT
Program Name: SAPLCACS_TRANSPORT
Main Program: SAPLCACS_TRANSPORT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS_CREATE_FLAT_COND_FILE 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_CREATE_FLAT_COND_FILE'"NOTRANSL: Erzeugen einer sequentiellen Datei.
EXPORTING
I_APPL = "Commission Application Identification
IT_COND_TYPE = "Condition Type
IT_COND_TABLE = "Table Type for Interface (Range Table for Condition Types)
* I_CLIENT = SY-MANDT "Client
* I_USERNAME = SY-UNAME "User Name
* I_TCODE = 'XK15' "Transaction Code
I_STDCTR = "Number of partner contract
IMPORTING
E_PATH = "Field Length: 40 Characters
EXCEPTIONS
NO_COND_TABLES_FOUND = 1
IMPORTING Parameters details for CACS_CREATE_FLAT_COND_FILE
I_APPL - Commission Application Identification
Data type: CACSAPPLOptional: No
Call by Reference: Yes
IT_COND_TYPE - Condition Type
Data type: CACS_TT_RANGE_CONDTYPEOptional: No
Call by Reference: Yes
IT_COND_TABLE - Table Type for Interface (Range Table for Condition Types)
Data type: CACS_TT_RANGE_CONDTABLEOptional: No
Call by Reference: Yes
I_CLIENT - Client
Data type: MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: Yes
I_USERNAME - User Name
Data type: SY-UNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: Yes
I_TCODE - Transaction Code
Data type: TCODEDefault: 'XK15'
Optional: Yes
Call by Reference: Yes
I_STDCTR - Number of partner contract
Data type: CACS_CONTRACT_IDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CACS_CREATE_FLAT_COND_FILE
E_PATH - Field Length: 40 Characters
Data type: CHAR40Optional: No
Call by Reference: Yes
EXCEPTIONS details
NO_COND_TABLES_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CACS_CREATE_FLAT_COND_FILE 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_e_path | TYPE CHAR40, " | |||
| lv_i_appl | TYPE CACSAPPL, " | |||
| lv_no_cond_tables_found | TYPE CACSAPPL, " | |||
| lv_it_cond_type | TYPE CACS_TT_RANGE_CONDTYPE, " | |||
| lv_it_cond_table | TYPE CACS_TT_RANGE_CONDTABLE, " | |||
| lv_i_client | TYPE MANDT, " SY-MANDT | |||
| lv_i_username | TYPE SY-UNAME, " SY-UNAME | |||
| lv_i_tcode | TYPE TCODE, " 'XK15' | |||
| lv_i_stdctr | TYPE CACS_CONTRACT_ID. " |
|   CALL FUNCTION 'CACS_CREATE_FLAT_COND_FILE' "NOTRANSL: Erzeugen einer sequentiellen Datei |
| EXPORTING | ||
| I_APPL | = lv_i_appl | |
| IT_COND_TYPE | = lv_it_cond_type | |
| IT_COND_TABLE | = lv_it_cond_table | |
| I_CLIENT | = lv_i_client | |
| I_USERNAME | = lv_i_username | |
| I_TCODE | = lv_i_tcode | |
| I_STDCTR | = lv_i_stdctr | |
| IMPORTING | ||
| E_PATH | = lv_e_path | |
| EXCEPTIONS | ||
| NO_COND_TABLES_FOUND = 1 | ||
| . " CACS_CREATE_FLAT_COND_FILE | ||
ABAP code using 7.40 inline data declarations to call FM CACS_CREATE_FLAT_COND_FILE
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_client) | = SY-MANDT. | |||
| "SELECT single UNAME FROM SY INTO @DATA(ld_i_username). | ||||
| DATA(ld_i_username) | = SY-UNAME. | |||
| DATA(ld_i_tcode) | = 'XK15'. | |||
Search for further information about these or an SAP related objects