SAP CRM_CCM_CHANGES_SND Function Module for Send changed amounts to CRM









CRM_CCM_CHANGES_SND is a standard crm ccm changes snd SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Send changed amounts to CRM 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 crm ccm changes snd FM, simply by entering the name CRM_CCM_CHANGES_SND into the relevant SAP transaction such as SE37 or SE38.

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



Function CRM_CCM_CHANGES_SND 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_CCM_CHANGES_SND'"Send changed amounts to CRM
EXPORTING
IV_CASE_GUID = "Technical Case Key (Case GUID)
IS_OLD_ATTR = "Dispute Case attributes old values
IS_NEW_ATTR = "Dispute Case attributes new values

IMPORTING
ET_RETURN = "Return parameter table

EXCEPTIONS
DATA_NOT_SENT = 1
.



IMPORTING Parameters details for CRM_CCM_CHANGES_SND

IV_CASE_GUID - Technical Case Key (Case GUID)

Data type: SCMG_CASE_GUID
Optional: No
Call by Reference: Yes

IS_OLD_ATTR - Dispute Case attributes old values

Data type: CRMST_CCM_DC_CHG_ATTR
Optional: No
Call by Reference: Yes

IS_NEW_ATTR - Dispute Case attributes new values

Data type: CRMST_CCM_DC_CHG_ATTR
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CRM_CCM_CHANGES_SND

ET_RETURN - Return parameter table

Data type: BAPIRET2_T
Optional: No
Call by Reference: Yes

EXCEPTIONS details

DATA_NOT_SENT - data not sent to CRM

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CRM_CCM_CHANGES_SND 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_return  TYPE BAPIRET2_T, "   
lv_iv_case_guid  TYPE SCMG_CASE_GUID, "   
lv_data_not_sent  TYPE SCMG_CASE_GUID, "   
lv_is_old_attr  TYPE CRMST_CCM_DC_CHG_ATTR, "   
lv_is_new_attr  TYPE CRMST_CCM_DC_CHG_ATTR. "   

  CALL FUNCTION 'CRM_CCM_CHANGES_SND'  "Send changed amounts to CRM
    EXPORTING
         IV_CASE_GUID = lv_iv_case_guid
         IS_OLD_ATTR = lv_is_old_attr
         IS_NEW_ATTR = lv_is_new_attr
    IMPORTING
         ET_RETURN = lv_et_return
    EXCEPTIONS
        DATA_NOT_SENT = 1
. " CRM_CCM_CHANGES_SND




ABAP code using 7.40 inline data declarations to call FM CRM_CCM_CHANGES_SND

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!