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

Function FKK_SAMPLE_1055 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_SAMPLE_1055'".
EXPORTING
I_PARTNER = "Business Partner Number
I_AKTYP = "Activity Category
* I_BPEXT = "
* I_BPKIND = "Business Partner Type
I_XCHDOC = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
I_XTEST = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
CHANGING
C_VALDT = "Validity Date of Changes (Direct Input)
C_VALID_DATE_CDATA = "Validity Date Central BP Data for Template Determination (YYYYMMDD)
C_VALID_FROM_CDATA = "Validity Start Central BP Data (YYYYMMDD)
C_VALID_TO_CDATA = "Validity End Central BP Data (YYYYMMDD)
C_BUT000 = "BP: General Data (Direct Input)
TABLES
* CT_DATA = "Incoming Data Records
CT_BUT020 = "BP: Address Data Transfer Structure (Direct Input)
CT_BUT021 = "BP: Address usage transfer structure (direct input)
CT_BUT0BK = "BP: Bank details (direct input)
CT_BUT0CC = "BP: Payment Cards (Direct Input)
CT_TAXNUM = "Direct Input Structure: Tax Numbers for Business Partner
CT_MESSAGE = "CBP: Messages for Each Object
IMPORTING Parameters details for FKK_SAMPLE_1055
I_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: No
Call by Reference: Yes
I_AKTYP - Activity Category
Data type: BU_AKTYPOptional: No
Call by Reference: Yes
I_BPEXT -
Data type: BU_BPEXTOptional: Yes
Call by Reference: Yes
I_BPKIND - Business Partner Type
Data type: BU_BPKINDOptional: Yes
Call by Reference: Yes
I_XCHDOC - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: Yes
I_XTEST - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: Yes
CHANGING Parameters details for FKK_SAMPLE_1055
C_VALDT - Validity Date of Changes (Direct Input)
Data type: BU_VALDT_DIOptional: No
Call by Reference: Yes
C_VALID_DATE_CDATA - Validity Date Central BP Data for Template Determination (YYYYMMDD)
Data type: BU_CENTRAL_VALID_DATE_DIOptional: No
Call by Reference: Yes
C_VALID_FROM_CDATA - Validity Start Central BP Data (YYYYMMDD)
Data type: BU_CENTRAL_DATE_FROM_DIOptional: No
Call by Reference: Yes
C_VALID_TO_CDATA - Validity End Central BP Data (YYYYMMDD)
Data type: BU_CENTRAL_DATE_TO_DIOptional: No
Call by Reference: Yes
C_BUT000 - BP: General Data (Direct Input)
Data type: BUS000_DIOptional: No
Call by Reference: Yes
TABLES Parameters details for FKK_SAMPLE_1055
CT_DATA - Incoming Data Records
Data type: BUSSDIOptional: Yes
Call by Reference: Yes
CT_BUT020 - BP: Address Data Transfer Structure (Direct Input)
Data type: BUS020_DIOptional: No
Call by Reference: Yes
CT_BUT021 - BP: Address usage transfer structure (direct input)
Data type: BUS021_DIOptional: No
Call by Reference: Yes
CT_BUT0BK - BP: Bank details (direct input)
Data type: BUS0BK_DIOptional: No
Call by Reference: Yes
CT_BUT0CC - BP: Payment Cards (Direct Input)
Data type: BUS0CC_DIOptional: No
Call by Reference: Yes
CT_TAXNUM - Direct Input Structure: Tax Numbers for Business Partner
Data type: FKKBPTAX_DIOptional: No
Call by Reference: Yes
CT_MESSAGE - CBP: Messages for Each Object
Data type: BUS0MSG1Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_SAMPLE_1055 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: | ||||
| lt_ct_data | TYPE STANDARD TABLE OF BUSSDI, " | |||
| lv_c_valdt | TYPE BU_VALDT_DI, " | |||
| lv_i_partner | TYPE BU_PARTNER, " | |||
| lv_i_aktyp | TYPE BU_AKTYP, " | |||
| lt_ct_but020 | TYPE STANDARD TABLE OF BUS020_DI, " | |||
| lv_c_valid_date_cdata | TYPE BU_CENTRAL_VALID_DATE_DI, " | |||
| lv_i_bpext | TYPE BU_BPEXT, " | |||
| lt_ct_but021 | TYPE STANDARD TABLE OF BUS021_DI, " | |||
| lv_c_valid_from_cdata | TYPE BU_CENTRAL_DATE_FROM_DI, " | |||
| lv_i_bpkind | TYPE BU_BPKIND, " | |||
| lt_ct_but0bk | TYPE STANDARD TABLE OF BUS0BK_DI, " | |||
| lv_c_valid_to_cdata | TYPE BU_CENTRAL_DATE_TO_DI, " | |||
| lv_c_but000 | TYPE BUS000_DI, " | |||
| lv_i_xchdoc | TYPE BOOLE_D, " | |||
| lt_ct_but0cc | TYPE STANDARD TABLE OF BUS0CC_DI, " | |||
| lv_i_xtest | TYPE BOOLE_D, " | |||
| lt_ct_taxnum | TYPE STANDARD TABLE OF FKKBPTAX_DI, " | |||
| lt_ct_message | TYPE STANDARD TABLE OF BUS0MSG1. " |
|   CALL FUNCTION 'FKK_SAMPLE_1055' " |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_AKTYP | = lv_i_aktyp | |
| I_BPEXT | = lv_i_bpext | |
| I_BPKIND | = lv_i_bpkind | |
| I_XCHDOC | = lv_i_xchdoc | |
| I_XTEST | = lv_i_xtest | |
| CHANGING | ||
| C_VALDT | = lv_c_valdt | |
| C_VALID_DATE_CDATA | = lv_c_valid_date_cdata | |
| C_VALID_FROM_CDATA | = lv_c_valid_from_cdata | |
| C_VALID_TO_CDATA | = lv_c_valid_to_cdata | |
| C_BUT000 | = lv_c_but000 | |
| TABLES | ||
| CT_DATA | = lt_ct_data | |
| CT_BUT020 | = lt_ct_but020 | |
| CT_BUT021 | = lt_ct_but021 | |
| CT_BUT0BK | = lt_ct_but0bk | |
| CT_BUT0CC | = lt_ct_but0cc | |
| CT_TAXNUM | = lt_ct_taxnum | |
| CT_MESSAGE | = lt_ct_message | |
| . " FKK_SAMPLE_1055 | ||
ABAP code using 7.40 inline data declarations to call FM FKK_SAMPLE_1055
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