SAP DFM_INBOUND_SYNCH_FRAMEWORK Function Module for Starting point in synchronization process









DFM_INBOUND_SYNCH_FRAMEWORK is a standard dfm inbound synch framework SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Starting point in synchronization process 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 dfm inbound synch framework FM, simply by entering the name DFM_INBOUND_SYNCH_FRAMEWORK into the relevant SAP transaction such as SE37 or SE38.

Function Group: INM_SYNC_FRAMEWORK_RFC
Program Name: SAPLINM_SYNC_FRAMEWORK_RFC
Main Program: SAPLINM_SYNC_FRAMEWORK_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function DFM_INBOUND_SYNCH_FRAMEWORK 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 'DFM_INBOUND_SYNCH_FRAMEWORK'"Starting point in synchronization process
  EXPORTING
*  IV_WAIT_FOR_COMMIT =  "Boolean Variable (X=True, -=False, Space=Unknown)
   IS_SOURCE_OBJECT_CONTEXT =  "Context of INM object
   IS_OPERATION_CONTEXT =  "Application update context
*  IT_TARGET_TEMPLATES =  "Table of type-template associations
*  IT_PARAMS =  "Name and value list
*  IV_SYNCH_IN_NEW_TASK =  "Boolean Variable (X=True, -=False, Space=Unknown)

 IMPORTING
   ET_MESSAGES =  "Messages
   EV_RC =  "
.



IMPORTING Parameters details for DFM_INBOUND_SYNCH_FRAMEWORK

IV_WAIT_FOR_COMMIT - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_SOURCE_OBJECT_CONTEXT - Context of INM object

Data type: INM_OBJECT_CONTEXT
Optional: No
Call by Reference: No ( called with pass by value option)

IS_OPERATION_CONTEXT - Application update context

Data type: INM_OPERATION_CONTEXT
Optional: No
Call by Reference: No ( called with pass by value option)

IT_TARGET_TEMPLATES - Table of type-template associations

Data type: INM_TT_GROUP_TEMPLATE_ASSOC
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_PARAMS - Name and value list

Data type: INM_OF_TT_FIELD_NAMES_VALUES
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SYNCH_IN_NEW_TASK - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for DFM_INBOUND_SYNCH_FRAMEWORK

ET_MESSAGES - Messages

Data type: INM_OF_TT_MESSAGES
Optional: No
Call by Reference: No ( called with pass by value option)

EV_RC -

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for DFM_INBOUND_SYNCH_FRAMEWORK 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_et_messages  TYPE INM_OF_TT_MESSAGES, "   
lv_iv_wait_for_commit  TYPE BOOLEAN, "   
lv_ev_rc  TYPE I, "   
lv_is_source_object_context  TYPE INM_OBJECT_CONTEXT, "   
lv_is_operation_context  TYPE INM_OPERATION_CONTEXT, "   
lv_it_target_templates  TYPE INM_TT_GROUP_TEMPLATE_ASSOC, "   
lv_it_params  TYPE INM_OF_TT_FIELD_NAMES_VALUES, "   
lv_iv_synch_in_new_task  TYPE BOOLEAN. "   

  CALL FUNCTION 'DFM_INBOUND_SYNCH_FRAMEWORK'  "Starting point in synchronization process
    EXPORTING
         IV_WAIT_FOR_COMMIT = lv_iv_wait_for_commit
         IS_SOURCE_OBJECT_CONTEXT = lv_is_source_object_context
         IS_OPERATION_CONTEXT = lv_is_operation_context
         IT_TARGET_TEMPLATES = lv_it_target_templates
         IT_PARAMS = lv_it_params
         IV_SYNCH_IN_NEW_TASK = lv_iv_synch_in_new_task
    IMPORTING
         ET_MESSAGES = lv_et_messages
         EV_RC = lv_ev_rc
. " DFM_INBOUND_SYNCH_FRAMEWORK




ABAP code using 7.40 inline data declarations to call FM DFM_INBOUND_SYNCH_FRAMEWORK

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!