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

Function FKK_BPC_UPDATE_SAMPLE 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_BPC_UPDATE_SAMPLE'".
EXPORTING
IV_GPART = "
IV_ORIGIN = "
IV_TYPE = "
* IX_SIMU = ' ' "
IMPORTING
ET_MESSAGES = "
IMPORTING Parameters details for FKK_BPC_UPDATE_SAMPLE
IV_GPART -
Data type: GPART_KKOptional: No
Call by Reference: Yes
IV_ORIGIN -
Data type: ORIGIN_MDC_KKOptional: No
Call by Reference: Yes
IV_TYPE -
Data type: TYPE_MDC_KKOptional: No
Call by Reference: Yes
IX_SIMU -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FKK_BPC_UPDATE_SAMPLE
ET_MESSAGES -
Data type: FKK_BAL_MSG_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_BPC_UPDATE_SAMPLE 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_iv_gpart | TYPE GPART_KK, " | |||
| lv_et_messages | TYPE FKK_BAL_MSG_T, " | |||
| lv_iv_origin | TYPE ORIGIN_MDC_KK, " | |||
| lv_iv_type | TYPE TYPE_MDC_KK, " | |||
| lv_ix_simu | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'FKK_BPC_UPDATE_SAMPLE' " |
| EXPORTING | ||
| IV_GPART | = lv_iv_gpart | |
| IV_ORIGIN | = lv_iv_origin | |
| IV_TYPE | = lv_iv_type | |
| IX_SIMU | = lv_ix_simu | |
| IMPORTING | ||
| ET_MESSAGES | = lv_et_messages | |
| . " FKK_BPC_UPDATE_SAMPLE | ||
ABAP code using 7.40 inline data declarations to call FM FKK_BPC_UPDATE_SAMPLE
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_ix_simu) | = ' '. | |||
Search for further information about these or an SAP related objects