SAP FKK_S_CASH_SEC_REQUEST_CREATE Function Module for
FKK_S_CASH_SEC_REQUEST_CREATE is a standard fkk s cash sec request create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fkk s cash sec request create FM, simply by entering the name FKK_S_CASH_SEC_REQUEST_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKK_SEC
Program Name: SAPLFKK_SEC
Main Program: SAPLFKK_SEC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_S_CASH_SEC_REQUEST_CREATE 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 'FKK_S_CASH_SEC_REQUEST_CREATE'".
EXPORTING
I_FKK_SEC = "Security Deposit
* I_REASON = "Reason for Requesting a Security Deposit
I_WAERS = "Transaction Currency
I_BETRW = "Amount in Transaction Currency with +/- Sign
I_GPART = "Business Partner Number
I_VKONT = "Contract Account Number
* I_VTREF = ' ' "Reference Specifications from Contract
* I_POST = 'X' "
IMPORTING
E_FKKOP_T = "Table Type for FKKOP
E_FKKOPK_T = "Table Type for FKKOPK
E_FKK_SEC_C = "Contracts for Security Deposit
E_FKK_SEC_REQ = "Request Documents for Security Deposits
CHANGING
C_FKKKO = "Header Data for Open Item Accounting Document
IMPORTING Parameters details for FKK_S_CASH_SEC_REQUEST_CREATE
I_FKK_SEC - Security Deposit
Data type: FKK_SECOptional: No
Call by Reference: Yes
I_REASON - Reason for Requesting a Security Deposit
Data type: REASON_KKOptional: Yes
Call by Reference: Yes
I_WAERS - Transaction Currency
Data type: BLWAE_KKOptional: No
Call by Reference: Yes
I_BETRW - Amount in Transaction Currency with +/- Sign
Data type: BETRW_KKOptional: No
Call by Reference: Yes
I_GPART - Business Partner Number
Data type: GPART_KKOptional: No
Call by Reference: Yes
I_VKONT - Contract Account Number
Data type: VKONT_KKOptional: No
Call by Reference: Yes
I_VTREF - Reference Specifications from Contract
Data type: VTREF_KKDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_POST -
Data type: XFELDDefault: 'X'
Optional: No
Call by Reference: Yes
EXPORTING Parameters details for FKK_S_CASH_SEC_REQUEST_CREATE
E_FKKOP_T - Table Type for FKKOP
Data type: FKKOP_TOptional: No
Call by Reference: Yes
E_FKKOPK_T - Table Type for FKKOPK
Data type: FKKOPK_TOptional: No
Call by Reference: Yes
E_FKK_SEC_C - Contracts for Security Deposit
Data type: FKK_SEC_COptional: No
Call by Reference: Yes
E_FKK_SEC_REQ - Request Documents for Security Deposits
Data type: FKK_SEC_REQOptional: No
Call by Reference: Yes
CHANGING Parameters details for FKK_S_CASH_SEC_REQUEST_CREATE
C_FKKKO - Header Data for Open Item Accounting Document
Data type: FKKKOOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_S_CASH_SEC_REQUEST_CREATE 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_c_fkkko | TYPE FKKKO, " | |||
| lv_e_fkkop_t | TYPE FKKOP_T, " | |||
| lv_i_fkk_sec | TYPE FKK_SEC, " | |||
| lv_i_reason | TYPE REASON_KK, " | |||
| lv_e_fkkopk_t | TYPE FKKOPK_T, " | |||
| lv_i_waers | TYPE BLWAE_KK, " | |||
| lv_e_fkk_sec_c | TYPE FKK_SEC_C, " | |||
| lv_i_betrw | TYPE BETRW_KK, " | |||
| lv_e_fkk_sec_req | TYPE FKK_SEC_REQ, " | |||
| lv_i_gpart | TYPE GPART_KK, " | |||
| lv_i_vkont | TYPE VKONT_KK, " | |||
| lv_i_vtref | TYPE VTREF_KK, " SPACE | |||
| lv_i_post | TYPE XFELD. " 'X' |
|   CALL FUNCTION 'FKK_S_CASH_SEC_REQUEST_CREATE' " |
| EXPORTING | ||
| I_FKK_SEC | = lv_i_fkk_sec | |
| I_REASON | = lv_i_reason | |
| I_WAERS | = lv_i_waers | |
| I_BETRW | = lv_i_betrw | |
| I_GPART | = lv_i_gpart | |
| I_VKONT | = lv_i_vkont | |
| I_VTREF | = lv_i_vtref | |
| I_POST | = lv_i_post | |
| IMPORTING | ||
| E_FKKOP_T | = lv_e_fkkop_t | |
| E_FKKOPK_T | = lv_e_fkkopk_t | |
| E_FKK_SEC_C | = lv_e_fkk_sec_c | |
| E_FKK_SEC_REQ | = lv_e_fkk_sec_req | |
| CHANGING | ||
| C_FKKKO | = lv_c_fkkko | |
| . " FKK_S_CASH_SEC_REQUEST_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM FKK_S_CASH_SEC_REQUEST_CREATE
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_vtref) | = ' '. | |||
| DATA(ld_i_post) | = 'X'. | |||
Search for further information about these or an SAP related objects