SAP BAPI_DFS_PM_FUNCTIONALLOC_SYNC Function Module for Bapi Wrapper for Functional Location
BAPI_DFS_PM_FUNCTIONALLOC_SYNC is a standard bapi dfs pm functionalloc sync SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Bapi Wrapper for Functional Location 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 bapi dfs pm functionalloc sync FM, simply by entering the name BAPI_DFS_PM_FUNCTIONALLOC_SYNC into the relevant SAP transaction such as SE37 or SE38.
Function Group: BAPI_DFS_PM
Program Name: SAPLBAPI_DFS_PM
Main Program: SAPLBAPI_DFS_PM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_DFS_PM_FUNCTIONALLOC_SYNC 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 'BAPI_DFS_PM_FUNCTIONALLOC_SYNC'"Bapi Wrapper for Functional Location.
EXPORTING
* IS_BAPI_INPUT = "Syclo BAPI Wrapper Standard Input Setting
* IV_OBJECT_TYPE = "Sync framework - Internal Object Type
* IV_OBJECT_KEY = "Sync Framework - Object Key
* IS_EXTERNAL_OBJECT_INFO = "Sync Framework - External sync object info
* IS_SPECIFIC = "PM: BAPI Structure for ITOBAPI_CREATE_FL_ONLY + READ Fields
* IS_GENERAL = "PM: BAPI Structure for ITOBAPI_CREATE + READ Fields
* IV_MASS = "Indicator for Mass Processing
* IV_SUBS_ID = "Subscription ID
* IS_CONTROL_STRUCTURE = "Control Structure
IMPORTING
ES_BAPI_OUTPUT = "Syclo BAPI Wrapper Standard Output Structure
TABLES
* ET_RETURN = "Return Parameter
* ET_TRANSACTION_REQ_STATUS = "Table type for /SMFND/IBQ_TRANS_REQ_STA_STR
* IT_TRANSACTION_REQ_INFO = "Table type for /SMFND/IBQ_TRANS_REQ_INFO_STR
* ET_SUBQ_TRANSACTION_REQ_INFO = "Table type for /SMFND/CORE_DEP_SYNC_INFO_STR
* IT_FUNCTIONALLOC_DATA = "Table Type for Functional Location Data
* IT_OBJECTS_LIST = "Table Type For Objects List
* IT_LONGTEXT = "DFS PM Object Long Texts
IMPORTING Parameters details for BAPI_DFS_PM_FUNCTIONALLOC_SYNC
IS_BAPI_INPUT - Syclo BAPI Wrapper Standard Input Setting
Data type: /SYCLO/CORE_BAPI_INPUT_STROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_OBJECT_TYPE - Sync framework - Internal Object Type
Data type: /SMFND/SYNC_OBJECT_TYPE_DTEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_OBJECT_KEY - Sync Framework - Object Key
Data type: /SMFND/SYNC_OBJECT_KEY_DTEOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_EXTERNAL_OBJECT_INFO - Sync Framework - External sync object info
Data type: /SMFND/CORE_EXT_SYNC_INFO_STROptional: Yes
Call by Reference: No ( called with pass by value option)
IS_SPECIFIC - PM: BAPI Structure for ITOBAPI_CREATE_FL_ONLY + READ Fields
Data type: BAPI_ITOB_FL_ONLYOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_GENERAL - PM: BAPI Structure for ITOBAPI_CREATE + READ Fields
Data type: BAPI_ITOBOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_MASS - Indicator for Mass Processing
Data type: BOOLEAN_FLGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SUBS_ID - Subscription ID
Data type: DFS_SUBS_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_CONTROL_STRUCTURE - Control Structure
Data type: DFS_CORE_BAPI_CTRL_PARAM_SOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_DFS_PM_FUNCTIONALLOC_SYNC
ES_BAPI_OUTPUT - Syclo BAPI Wrapper Standard Output Structure
Data type: /SYCLO/CORE_BAPI_OUTPUT_STROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_DFS_PM_FUNCTIONALLOC_SYNC
ET_RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
ET_TRANSACTION_REQ_STATUS - Table type for /SMFND/IBQ_TRANS_REQ_STA_STR
Data type: /SMFND/IBQ_TRANS_REQ_STA_TABOptional: Yes
Call by Reference: Yes
IT_TRANSACTION_REQ_INFO - Table type for /SMFND/IBQ_TRANS_REQ_INFO_STR
Data type: /SMFND/IBQ_TRANS_REQ_INFO_TABOptional: Yes
Call by Reference: Yes
ET_SUBQ_TRANSACTION_REQ_INFO - Table type for /SMFND/CORE_DEP_SYNC_INFO_STR
Data type: /SMFND/CORE_DEP_SYNC_INFO_TABOptional: Yes
Call by Reference: Yes
IT_FUNCTIONALLOC_DATA - Table Type for Functional Location Data
Data type: DFS_FUNCTIONALLOC_TTOptional: Yes
Call by Reference: Yes
IT_OBJECTS_LIST - Table Type For Objects List
Data type: DFS_OBJECT_LIST_TTOptional: Yes
Call by Reference: Yes
IT_LONGTEXT - DFS PM Object Long Texts
Data type: DFS_PM_LONGTEXT_TTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_DFS_PM_FUNCTIONALLOC_SYNC 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_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_is_bapi_input | TYPE /SYCLO/CORE_BAPI_INPUT_STR, " | |||
| lv_es_bapi_output | TYPE /SYCLO/CORE_BAPI_OUTPUT_STR, " | |||
| lv_iv_object_type | TYPE /SMFND/SYNC_OBJECT_TYPE_DTE, " | |||
| lt_et_transaction_req_status | TYPE STANDARD TABLE OF /SMFND/IBQ_TRANS_REQ_STA_TAB, " | |||
| lv_iv_object_key | TYPE /SMFND/SYNC_OBJECT_KEY_DTE, " | |||
| lt_it_transaction_req_info | TYPE STANDARD TABLE OF /SMFND/IBQ_TRANS_REQ_INFO_TAB, " | |||
| lv_is_external_object_info | TYPE /SMFND/CORE_EXT_SYNC_INFO_STR, " | |||
| lt_et_subq_transaction_req_info | TYPE STANDARD TABLE OF /SMFND/CORE_DEP_SYNC_INFO_TAB, " | |||
| lv_is_specific | TYPE BAPI_ITOB_FL_ONLY, " | |||
| lt_it_functionalloc_data | TYPE STANDARD TABLE OF DFS_FUNCTIONALLOC_TT, " | |||
| lv_is_general | TYPE BAPI_ITOB, " | |||
| lt_it_objects_list | TYPE STANDARD TABLE OF DFS_OBJECT_LIST_TT, " | |||
| lv_iv_mass | TYPE BOOLEAN_FLG, " | |||
| lt_it_longtext | TYPE STANDARD TABLE OF DFS_PM_LONGTEXT_TT, " | |||
| lv_iv_subs_id | TYPE DFS_SUBS_ID, " | |||
| lv_is_control_structure | TYPE DFS_CORE_BAPI_CTRL_PARAM_S. " |
|   CALL FUNCTION 'BAPI_DFS_PM_FUNCTIONALLOC_SYNC' "Bapi Wrapper for Functional Location |
| EXPORTING | ||
| IS_BAPI_INPUT | = lv_is_bapi_input | |
| IV_OBJECT_TYPE | = lv_iv_object_type | |
| IV_OBJECT_KEY | = lv_iv_object_key | |
| IS_EXTERNAL_OBJECT_INFO | = lv_is_external_object_info | |
| IS_SPECIFIC | = lv_is_specific | |
| IS_GENERAL | = lv_is_general | |
| IV_MASS | = lv_iv_mass | |
| IV_SUBS_ID | = lv_iv_subs_id | |
| IS_CONTROL_STRUCTURE | = lv_is_control_structure | |
| IMPORTING | ||
| ES_BAPI_OUTPUT | = lv_es_bapi_output | |
| TABLES | ||
| ET_RETURN | = lt_et_return | |
| ET_TRANSACTION_REQ_STATUS | = lt_et_transaction_req_status | |
| IT_TRANSACTION_REQ_INFO | = lt_it_transaction_req_info | |
| ET_SUBQ_TRANSACTION_REQ_INFO | = lt_et_subq_transaction_req_info | |
| IT_FUNCTIONALLOC_DATA | = lt_it_functionalloc_data | |
| IT_OBJECTS_LIST | = lt_it_objects_list | |
| IT_LONGTEXT | = lt_it_longtext | |
| . " BAPI_DFS_PM_FUNCTIONALLOC_SYNC | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_DFS_PM_FUNCTIONALLOC_SYNC
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