SAP COM_PARTNER_PROVIDE_DATA_2000 Function Module for
COM_PARTNER_PROVIDE_DATA_2000 is a standard com partner provide data 2000 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 com partner provide data 2000 FM, simply by entering the name COM_PARTNER_PROVIDE_DATA_2000 into the relevant SAP transaction such as SE37 or SE38.
Function Group: COM_PARTNER_UI
Program Name: SAPLCOM_PARTNER_UI
Main Program: SAPLCOM_PARTNER_UI
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COM_PARTNER_PROVIDE_DATA_2000 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 'COM_PARTNER_PROVIDE_DATA_2000'".
EXPORTING
* IV_PARTNER_SET_GUID = "
* IS_MSG_INFO = "
* IV_STARTUP_SUBSCREEN = '2001' "
* IV_CALENDAR_FLAG = ' ' "
* IV_REF_GUID = "GUID of a CRM Order Object
* IV_REF_KIND = "Object Type
* IS_PARTNER_CONTROL = "
* IS_COM_STRUCTURE = "
IV_MODE = "
* IV_FILTER = "
* IV_NO_FILTER = 'X' "
* IS_FCODES = "
TABLES
* IT_FILTER_TAB = "
IMPORTING Parameters details for COM_PARTNER_PROVIDE_DATA_2000
IV_PARTNER_SET_GUID -
Data type: CRMT_OBJECT_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_MSG_INFO -
Data type: COMT_MSG_INFOOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_STARTUP_SUBSCREEN -
Data type: DYNNRDefault: '2001'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CALENDAR_FLAG -
Data type: CRMT_BOOLEANDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_REF_GUID - GUID of a CRM Order Object
Data type: CRMT_OBJECT_GUIDOptional: Yes
Call by Reference: Yes
IV_REF_KIND - Object Type
Data type: CRMT_OBJECT_KINDOptional: Yes
Call by Reference: Yes
IS_PARTNER_CONTROL -
Data type: CRMT_PARTNER_CONTROLOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_COM_STRUCTURE -
Data type: ANYOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_MODE -
Data type: CRMT_MODEOptional: No
Call by Reference: No ( called with pass by value option)
IV_FILTER -
Data type: CRMC_PARTNER_FIL-FILTEROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_FILTER -
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IS_FCODES -
Data type: CRM_PARTNER_FCODEOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for COM_PARTNER_PROVIDE_DATA_2000
IT_FILTER_TAB -
Data type: CRMC_PARTNER_FILOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for COM_PARTNER_PROVIDE_DATA_2000 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_it_filter_tab | TYPE STANDARD TABLE OF CRMC_PARTNER_FIL, " | |||
| lv_iv_partner_set_guid | TYPE CRMT_OBJECT_GUID, " | |||
| lv_is_msg_info | TYPE COMT_MSG_INFO, " | |||
| lv_iv_startup_subscreen | TYPE DYNNR, " '2001' | |||
| lv_iv_calendar_flag | TYPE CRMT_BOOLEAN, " SPACE | |||
| lv_iv_ref_guid | TYPE CRMT_OBJECT_GUID, " | |||
| lv_iv_ref_kind | TYPE CRMT_OBJECT_KIND, " | |||
| lv_is_partner_control | TYPE CRMT_PARTNER_CONTROL, " | |||
| lv_is_com_structure | TYPE ANY, " | |||
| lv_iv_mode | TYPE CRMT_MODE, " | |||
| lv_iv_filter | TYPE CRMC_PARTNER_FIL-FILTER, " | |||
| lv_iv_no_filter | TYPE XFELD, " 'X' | |||
| lv_is_fcodes | TYPE CRM_PARTNER_FCODE. " |
|   CALL FUNCTION 'COM_PARTNER_PROVIDE_DATA_2000' " |
| EXPORTING | ||
| IV_PARTNER_SET_GUID | = lv_iv_partner_set_guid | |
| IS_MSG_INFO | = lv_is_msg_info | |
| IV_STARTUP_SUBSCREEN | = lv_iv_startup_subscreen | |
| IV_CALENDAR_FLAG | = lv_iv_calendar_flag | |
| IV_REF_GUID | = lv_iv_ref_guid | |
| IV_REF_KIND | = lv_iv_ref_kind | |
| IS_PARTNER_CONTROL | = lv_is_partner_control | |
| IS_COM_STRUCTURE | = lv_is_com_structure | |
| IV_MODE | = lv_iv_mode | |
| IV_FILTER | = lv_iv_filter | |
| IV_NO_FILTER | = lv_iv_no_filter | |
| IS_FCODES | = lv_is_fcodes | |
| TABLES | ||
| IT_FILTER_TAB | = lt_it_filter_tab | |
| . " COM_PARTNER_PROVIDE_DATA_2000 | ||
ABAP code using 7.40 inline data declarations to call FM COM_PARTNER_PROVIDE_DATA_2000
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_startup_subscreen) | = '2001'. | |||
| DATA(ld_iv_calendar_flag) | = ' '. | |||
| "SELECT single FILTER FROM CRMC_PARTNER_FIL INTO @DATA(ld_iv_filter). | ||||
| DATA(ld_iv_no_filter) | = 'X'. | |||
Search for further information about these or an SAP related objects