SAP CRM_PARTNER_PROVIDE_DATA_2000 Function Module for









CRM_PARTNER_PROVIDE_DATA_2000 is a standard crm 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 crm partner provide data 2000 FM, simply by entering the name CRM_PARTNER_PROVIDE_DATA_2000 into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRM_PARTNER_UI
Program Name: SAPLCRM_PARTNER_UI
Main Program: SAPLCRM_PARTNER_UI
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CRM_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 'CRM_PARTNER_PROVIDE_DATA_2000'"
EXPORTING
IV_REF_GUID = "
* IV_REF_HANDLE = "
IV_REF_KIND = "
IV_MODE = "
* IV_FILTER = "
* IV_NO_FILTER = 'X' "
* IS_FCODES = "
* IV_CALENDAR_FLAG = ' ' "

TABLES
* IT_FILTER_TAB = "

EXCEPTIONS
PARTNERSET_NOT_FOUND = 1 PARAMETER_ERROR = 2 ENTRY_DOES_NOT_EXIST = 3
.



IMPORTING Parameters details for CRM_PARTNER_PROVIDE_DATA_2000

IV_REF_GUID -

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

IV_REF_HANDLE -

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

IV_REF_KIND -

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

IV_MODE -

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

IV_FILTER -

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

IV_NO_FILTER -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_FCODES -

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

IV_CALENDAR_FLAG -

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

TABLES Parameters details for CRM_PARTNER_PROVIDE_DATA_2000

IT_FILTER_TAB -

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

EXCEPTIONS details

PARTNERSET_NOT_FOUND -

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

PARAMETER_ERROR -

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

ENTRY_DOES_NOT_EXIST -

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

Copy and paste ABAP code example for CRM_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:
lv_iv_ref_guid  TYPE CRMT_OBJECT_GUID, "   
lt_it_filter_tab  TYPE STANDARD TABLE OF CRMC_PARTNER_FIL, "   
lv_partnerset_not_found  TYPE CRMC_PARTNER_FIL, "   
lv_iv_ref_handle  TYPE CRMT_HANDLE, "   
lv_parameter_error  TYPE CRMT_HANDLE, "   
lv_iv_ref_kind  TYPE CRMT_OBJECT_KIND, "   
lv_entry_does_not_exist  TYPE CRMT_OBJECT_KIND, "   
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, "   
lv_iv_calendar_flag  TYPE CRMT_BOOLEAN. "   SPACE

  CALL FUNCTION 'CRM_PARTNER_PROVIDE_DATA_2000'  "
    EXPORTING
         IV_REF_GUID = lv_iv_ref_guid
         IV_REF_HANDLE = lv_iv_ref_handle
         IV_REF_KIND = lv_iv_ref_kind
         IV_MODE = lv_iv_mode
         IV_FILTER = lv_iv_filter
         IV_NO_FILTER = lv_iv_no_filter
         IS_FCODES = lv_is_fcodes
         IV_CALENDAR_FLAG = lv_iv_calendar_flag
    TABLES
         IT_FILTER_TAB = lt_it_filter_tab
    EXCEPTIONS
        PARTNERSET_NOT_FOUND = 1
        PARAMETER_ERROR = 2
        ENTRY_DOES_NOT_EXIST = 3
. " CRM_PARTNER_PROVIDE_DATA_2000




ABAP code using 7.40 inline data declarations to call FM CRM_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.

 
 
 
 
 
 
 
 
"SELECT single FILTER FROM CRMC_PARTNER_FIL INTO @DATA(ld_iv_filter).
 
DATA(ld_iv_no_filter) = 'X'.
 
 
DATA(ld_iv_calendar_flag) = ' '.
 


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!