SAP FKK_PRENOTE_BACS_1052 Function Module for Change of business partner master data triggers prenotification entry
FKK_PRENOTE_BACS_1052 is a standard fkk prenote bacs 1052 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change of business partner master data triggers prenotification entry processing and below is the pattern details for this FM, 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 prenote bacs 1052 FM, simply by entering the name FKK_PRENOTE_BACS_1052 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKPNGB1
Program Name: SAPLFKPNGB1
Main Program: SAPLFKPNGB1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_PRENOTE_BACS_1052 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_PRENOTE_BACS_1052'"Change of business partner master data triggers prenotification entry.
EXPORTING
IS_BUPA_CHANGES = "
* IV_UPDTASK = ' ' "Single-character flag
IMPORTING Parameters details for FKK_PRENOTE_BACS_1052
IS_BUPA_CHANGES -
Data type: FKK_BUPA_CHANGESOptional: No
Call by Reference: Yes
IV_UPDTASK - Single-character flag
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKK_PRENOTE_BACS_1052 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_is_bupa_changes | TYPE FKK_BUPA_CHANGES, " | |||
| lv_iv_updtask | TYPE CHAR1. " SPACE |
|   CALL FUNCTION 'FKK_PRENOTE_BACS_1052' "Change of business partner master data triggers prenotification entry |
| EXPORTING | ||
| IS_BUPA_CHANGES | = lv_is_bupa_changes | |
| IV_UPDTASK | = lv_iv_updtask | |
| . " FKK_PRENOTE_BACS_1052 | ||
ABAP code using 7.40 inline data declarations to call FM FKK_PRENOTE_BACS_1052
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_iv_updtask) | = ' '. | |||
Search for further information about these or an SAP related objects