SAP FKK_GET_PROVIDER_CONTRACT_DATA Function Module for
FKK_GET_PROVIDER_CONTRACT_DATA is a standard fkk get provider contract data 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 get provider contract data FM, simply by entering the name FKK_GET_PROVIDER_CONTRACT_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKK_VT_DATA
Program Name: SAPLFKK_VT_DATA
Main Program: SAPLFKK_VT_DATA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_GET_PROVIDER_CONTRACT_DATA 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_GET_PROVIDER_CONTRACT_DATA'".
EXPORTING
IV_SUBAP = "
IV_VTKEY = "
* IV_VTPOS = "
IMPORTING
ES_VT_H = "
ES_VT_I = "
ET_VT_I = "
ET_VT_D = "
ET_VT_D_POS = "
ET_VT_TR = "
EXCEPTIONS
PROVIDER_CONTR_NOT_SUPPORTED = 1 PROVIDER_CONTR_DOES_NOT_EXIST = 2 PROVIDER_CONTR_NOT_ACTIVE = 3 SUBAP_NOT_ACTIVE = 4 WRONG_SUBAP = 5 PROVIDER_CONTR_ITEM_ERROR = 6
IMPORTING Parameters details for FKK_GET_PROVIDER_CONTRACT_DATA
IV_SUBAP -
Data type: SUBAP_KKOptional: No
Call by Reference: No ( called with pass by value option)
IV_VTKEY -
Data type: VTKEY_KKOptional: No
Call by Reference: No ( called with pass by value option)
IV_VTPOS -
Data type: VTPOS_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FKK_GET_PROVIDER_CONTRACT_DATA
ES_VT_H -
Data type: DFKK_VT_HOptional: No
Call by Reference: Yes
ES_VT_I -
Data type: DFKK_VT_IOptional: No
Call by Reference: Yes
ET_VT_I -
Data type: FKK_VT_I_TABOptional: No
Call by Reference: Yes
ET_VT_D -
Data type: FKK_VT_D_TABOptional: No
Call by Reference: Yes
ET_VT_D_POS -
Data type: FKK_VT_D_TABOptional: No
Call by Reference: Yes
ET_VT_TR -
Data type: FKK_VT_TR_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
PROVIDER_CONTR_NOT_SUPPORTED -
Data type:Optional: No
Call by Reference: Yes
PROVIDER_CONTR_DOES_NOT_EXIST -
Data type:Optional: No
Call by Reference: Yes
PROVIDER_CONTR_NOT_ACTIVE -
Data type:Optional: No
Call by Reference: Yes
SUBAP_NOT_ACTIVE -
Data type:Optional: No
Call by Reference: Yes
WRONG_SUBAP -
Data type:Optional: No
Call by Reference: Yes
PROVIDER_CONTR_ITEM_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_GET_PROVIDER_CONTRACT_DATA 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_es_vt_h | TYPE DFKK_VT_H, " | |||
| lv_iv_subap | TYPE SUBAP_KK, " | |||
| lv_provider_contr_not_supported | TYPE SUBAP_KK, " | |||
| lv_es_vt_i | TYPE DFKK_VT_I, " | |||
| lv_iv_vtkey | TYPE VTKEY_KK, " | |||
| lv_provider_contr_does_not_exist | TYPE VTKEY_KK, " | |||
| lv_et_vt_i | TYPE FKK_VT_I_TAB, " | |||
| lv_iv_vtpos | TYPE VTPOS_KK, " | |||
| lv_provider_contr_not_active | TYPE VTPOS_KK, " | |||
| lv_et_vt_d | TYPE FKK_VT_D_TAB, " | |||
| lv_subap_not_active | TYPE FKK_VT_D_TAB, " | |||
| lv_et_vt_d_pos | TYPE FKK_VT_D_TAB, " | |||
| lv_wrong_subap | TYPE FKK_VT_D_TAB, " | |||
| lv_et_vt_tr | TYPE FKK_VT_TR_TAB, " | |||
| lv_provider_contr_item_error | TYPE FKK_VT_TR_TAB. " |
|   CALL FUNCTION 'FKK_GET_PROVIDER_CONTRACT_DATA' " |
| EXPORTING | ||
| IV_SUBAP | = lv_iv_subap | |
| IV_VTKEY | = lv_iv_vtkey | |
| IV_VTPOS | = lv_iv_vtpos | |
| IMPORTING | ||
| ES_VT_H | = lv_es_vt_h | |
| ES_VT_I | = lv_es_vt_i | |
| ET_VT_I | = lv_et_vt_i | |
| ET_VT_D | = lv_et_vt_d | |
| ET_VT_D_POS | = lv_et_vt_d_pos | |
| ET_VT_TR | = lv_et_vt_tr | |
| EXCEPTIONS | ||
| PROVIDER_CONTR_NOT_SUPPORTED = 1 | ||
| PROVIDER_CONTR_DOES_NOT_EXIST = 2 | ||
| PROVIDER_CONTR_NOT_ACTIVE = 3 | ||
| SUBAP_NOT_ACTIVE = 4 | ||
| WRONG_SUBAP = 5 | ||
| PROVIDER_CONTR_ITEM_ERROR = 6 | ||
| . " FKK_GET_PROVIDER_CONTRACT_DATA | ||
ABAP code using 7.40 inline data declarations to call FM FKK_GET_PROVIDER_CONTRACT_DATA
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