SAP CRM_CONTRACT_MDATA_CHANGES_EC Function Module for To check the assignment of each item of the agreement/contract.









CRM_CONTRACT_MDATA_CHANGES_EC is a standard crm contract mdata changes ec SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for To check the assignment of each item of the agreement/contract. 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 contract mdata changes ec FM, simply by entering the name CRM_CONTRACT_MDATA_CHANGES_EC into the relevant SAP transaction such as SE37 or SE38.

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



Function CRM_CONTRACT_MDATA_CHANGES_EC 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_CONTRACT_MDATA_CHANGES_EC'"To check the assignment of each item of the agreement/contract.
  EXPORTING
*  IV_OBJECT_NAME =  "Business Transaction Subobject
*  IV_EVENT_EXETIME =  "Execution Time for Callback Function in Event Handler
*  IV_EVENT =  "Event in Program Flow
*  IV_ATTRIBUT =  "Event in Program Flow
*  IV_HEADER_GUID =  "GUID of a CRM Order Object
*  IV_OBJECT_GUID =  "GUID of a CRM Order Object
*  IV_STRVAL_OLD =  "
*  IV_STRVAL_NEW =  "
*  IV_STRUC_NAME =  "Table name

EXCEPTIONS
   ABORT = 1
.



IMPORTING Parameters details for CRM_CONTRACT_MDATA_CHANGES_EC

IV_OBJECT_NAME - Business Transaction Subobject

Data type: CRMT_OBJECT_NAME
Optional: Yes
Call by Reference: Yes

IV_EVENT_EXETIME - Execution Time for Callback Function in Event Handler

Data type: CRMT_EVENT_EXETIME
Optional: Yes
Call by Reference: Yes

IV_EVENT - Event in Program Flow

Data type: CRMT_EVENT
Optional: Yes
Call by Reference: Yes

IV_ATTRIBUT - Event in Program Flow

Data type: CRMT_EVENT
Optional: Yes
Call by Reference: Yes

IV_HEADER_GUID - GUID of a CRM Order Object

Data type: CRMT_OBJECT_GUID
Optional: Yes
Call by Reference: Yes

IV_OBJECT_GUID - GUID of a CRM Order Object

Data type: CRMT_OBJECT_GUID
Optional: Yes
Call by Reference: Yes

IV_STRVAL_OLD -

Data type: ANY
Optional: Yes
Call by Reference: Yes

IV_STRVAL_NEW -

Data type: ANY
Optional: Yes
Call by Reference: Yes

IV_STRUC_NAME - Table name

Data type: TABNAME
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ABORT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CRM_CONTRACT_MDATA_CHANGES_EC 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_abort  TYPE STRING, "   
lv_iv_object_name  TYPE CRMT_OBJECT_NAME, "   
lv_iv_event_exetime  TYPE CRMT_EVENT_EXETIME, "   
lv_iv_event  TYPE CRMT_EVENT, "   
lv_iv_attribut  TYPE CRMT_EVENT, "   
lv_iv_header_guid  TYPE CRMT_OBJECT_GUID, "   
lv_iv_object_guid  TYPE CRMT_OBJECT_GUID, "   
lv_iv_strval_old  TYPE ANY, "   
lv_iv_strval_new  TYPE ANY, "   
lv_iv_struc_name  TYPE TABNAME. "   

  CALL FUNCTION 'CRM_CONTRACT_MDATA_CHANGES_EC'  "To check the assignment of each item of the agreement/contract.
    EXPORTING
         IV_OBJECT_NAME = lv_iv_object_name
         IV_EVENT_EXETIME = lv_iv_event_exetime
         IV_EVENT = lv_iv_event
         IV_ATTRIBUT = lv_iv_attribut
         IV_HEADER_GUID = lv_iv_header_guid
         IV_OBJECT_GUID = lv_iv_object_guid
         IV_STRVAL_OLD = lv_iv_strval_old
         IV_STRVAL_NEW = lv_iv_strval_new
         IV_STRUC_NAME = lv_iv_struc_name
    EXCEPTIONS
        ABORT = 1
. " CRM_CONTRACT_MDATA_CHANGES_EC




ABAP code using 7.40 inline data declarations to call FM CRM_CONTRACT_MDATA_CHANGES_EC

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!