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

Function FKK_PARTNER_CHECK 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_PARTNER_CHECK'".
EXPORTING
* I_PARTNER = "Business Partner Number
* I_PARTNERGUID = "Business Partner GUID
* I_ROLECATEGORY = "BP role category
* I_XMEMORY = ' ' "
* I_XWA = ' ' "
* I_VALDT = '00000000' "Validity Date
* I_VALDT_SEL = SY-DATLO "
* IV_REQ_BLK_MSG = ' ' "
* IV_CHECK_CHNG_ACTVT = "
EXCEPTIONS
PARTNER_NOT_FOUND = 1 PARTNER_IN_ROLE_NOT_FOUND = 2 ROLE_NOT_FOUND = 3 WRONG_PARAMETERS = 4 INTERNAL_ERROR = 5 BLOCKED_PARTNER = 6
IMPORTING Parameters details for FKK_PARTNER_CHECK
I_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_PARTNERGUID - Business Partner GUID
Data type: BU_PARTNER_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ROLECATEGORY - BP role category
Data type: BU_PARTNERROLECATOptional: Yes
Call by Reference: Yes
I_XMEMORY -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_XWA -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_VALDT - Validity Date
Data type: SY-DATLODefault: '00000000'
Optional: Yes
Call by Reference: Yes
I_VALDT_SEL -
Data type: SY-DATLODefault: SY-DATLO
Optional: Yes
Call by Reference: Yes
IV_REQ_BLK_MSG -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CHECK_CHNG_ACTVT -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARTNER_NOT_FOUND - Business Partner Not Found
Data type:Optional: No
Call by Reference: Yes
PARTNER_IN_ROLE_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
ROLE_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
WRONG_PARAMETERS - Wrong Parameter Passed
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR - Internal Error
Data type:Optional: No
Call by Reference: Yes
BLOCKED_PARTNER -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_PARTNER_CHECK 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_partner | TYPE BU_PARTNER, " | |||
| lv_partner_not_found | TYPE BU_PARTNER, " | |||
| lv_i_partnerguid | TYPE BU_PARTNER_GUID, " | |||
| lv_partner_in_role_not_found | TYPE BU_PARTNER_GUID, " | |||
| lv_i_rolecategory | TYPE BU_PARTNERROLECAT, " | |||
| lv_role_not_found | TYPE BU_PARTNERROLECAT, " | |||
| lv_i_xmemory | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_wrong_parameters | TYPE BOOLE, " | |||
| lv_i_xwa | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_internal_error | TYPE BOOLE, " | |||
| lv_i_valdt | TYPE SY-DATLO, " '00000000' | |||
| lv_blocked_partner | TYPE SY, " | |||
| lv_i_valdt_sel | TYPE SY-DATLO, " SY-DATLO | |||
| lv_iv_req_blk_msg | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_iv_check_chng_actvt | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'FKK_PARTNER_CHECK' " |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_PARTNERGUID | = lv_i_partnerguid | |
| I_ROLECATEGORY | = lv_i_rolecategory | |
| I_XMEMORY | = lv_i_xmemory | |
| I_XWA | = lv_i_xwa | |
| I_VALDT | = lv_i_valdt | |
| I_VALDT_SEL | = lv_i_valdt_sel | |
| IV_REQ_BLK_MSG | = lv_iv_req_blk_msg | |
| IV_CHECK_CHNG_ACTVT | = lv_iv_check_chng_actvt | |
| EXCEPTIONS | ||
| PARTNER_NOT_FOUND = 1 | ||
| PARTNER_IN_ROLE_NOT_FOUND = 2 | ||
| ROLE_NOT_FOUND = 3 | ||
| WRONG_PARAMETERS = 4 | ||
| INTERNAL_ERROR = 5 | ||
| BLOCKED_PARTNER = 6 | ||
| . " FKK_PARTNER_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FKK_PARTNER_CHECK
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.| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xmemory). | ||||
| DATA(ld_i_xmemory) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xwa). | ||||
| DATA(ld_i_xwa) | = ' '. | |||
| "SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt). | ||||
| DATA(ld_i_valdt) | = '00000000'. | |||
| "SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt_sel). | ||||
| DATA(ld_i_valdt_sel) | = SY-DATLO. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_iv_req_blk_msg). | ||||
| DATA(ld_iv_req_blk_msg) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_iv_check_chng_actvt). | ||||
Search for further information about these or an SAP related objects