SAP CONFIG_SYNC_POINT_INIT Function Module for NOTRANSL: Initialisierung für Erweiterung Homogenitätsliste
CONFIG_SYNC_POINT_INIT is a standard config sync point init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Initialisierung für Erweiterung Homogenitätsliste 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 config sync point init FM, simply by entering the name CONFIG_SYNC_POINT_INIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CCHO
Program Name: SAPLCCHO
Main Program: SAPLCCHO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CONFIG_SYNC_POINT_INIT 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 'CONFIG_SYNC_POINT_INIT'"NOTRANSL: Initialisierung für Erweiterung Homogenitätsliste.
EXPORTING
I_CONF_KEY = "Identical object
I_DATUV = "Date and Time, Current (Application Server) Date
IMPORTING Parameters details for CONFIG_SYNC_POINT_INIT
I_CONF_KEY - Identical object
Data type: AEPREC-CONF_KEYOptional: No
Call by Reference: No ( called with pass by value option)
I_DATUV - Date and Time, Current (Application Server) Date
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CONFIG_SYNC_POINT_INIT 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_conf_key | TYPE AEPREC-CONF_KEY, " | |||
lv_i_datuv | TYPE SY-DATUM. " |
  CALL FUNCTION 'CONFIG_SYNC_POINT_INIT' "NOTRANSL: Initialisierung für Erweiterung Homogenitätsliste |
EXPORTING | ||
I_CONF_KEY | = lv_i_conf_key | |
I_DATUV | = lv_i_datuv | |
. " CONFIG_SYNC_POINT_INIT |
ABAP code using 7.40 inline data declarations to call FM CONFIG_SYNC_POINT_INIT
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 CONF_KEY FROM AEPREC INTO @DATA(ld_i_conf_key). | ||||
"SELECT single DATUM FROM SY INTO @DATA(ld_i_datuv). | ||||
Search for further information about these or an SAP related objects