SAP CMS_OBJ_CAG_CREATE_TECH_KEY Function Module for Create GUID for line items(Por,Rules,CAG-BP,CAG-DOC)









CMS_OBJ_CAG_CREATE_TECH_KEY is a standard cms obj cag create tech key SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create GUID for line items(Por,Rules,CAG-BP,CAG-DOC) 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 cms obj cag create tech key FM, simply by entering the name CMS_OBJ_CAG_CREATE_TECH_KEY into the relevant SAP transaction such as SE37 or SE38.

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



Function CMS_OBJ_CAG_CREATE_TECH_KEY 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 'CMS_OBJ_CAG_CREATE_TECH_KEY'"Create GUID for line items(Por,Rules,CAG-BP,CAG-DOC)
 IMPORTING
   E_TAB_RC =  "Return Code and corresponding Message

CHANGING
   C_TAB_CAG_PORTIONS =  "Portions for a Collateral Agreement (Object Layer)
   C_TAB_CAG_BP =  "Business Partner for a Collateral Agreement
   C_TAB_CAG_POR_BP =  "Collateral Agreement Portion-Business Partner Relationship
   C_TAB_CAG_BP_TRM =  "Bupa termination details for a CAG
   C_TAB_CAG_DOC =  "Documents for a Collateral Agreement
   C_TAB_CAG_RULES =  "Rules for a Collateral Agreement
   C_TAB_CAG_SA =  "Special Arrangements for a Collateral Agreement
   C_TAB_CAG_EXP =  "Expenditure Incurred for a CAG
.



EXPORTING Parameters details for CMS_OBJ_CAG_CREATE_TECH_KEY

E_TAB_RC - Return Code and corresponding Message

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

CHANGING Parameters details for CMS_OBJ_CAG_CREATE_TECH_KEY

C_TAB_CAG_PORTIONS - Portions for a Collateral Agreement (Object Layer)

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

C_TAB_CAG_BP - Business Partner for a Collateral Agreement

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

C_TAB_CAG_POR_BP - Collateral Agreement Portion-Business Partner Relationship

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

C_TAB_CAG_BP_TRM - Bupa termination details for a CAG

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

C_TAB_CAG_DOC - Documents for a Collateral Agreement

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

C_TAB_CAG_RULES - Rules for a Collateral Agreement

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

C_TAB_CAG_SA - Special Arrangements for a Collateral Agreement

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

C_TAB_CAG_EXP - Expenditure Incurred for a CAG

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

Copy and paste ABAP code example for CMS_OBJ_CAG_CREATE_TECH_KEY 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_e_tab_rc  TYPE CMS_TAB_MSG_COL_MESSAGE, "   
lv_c_tab_cag_portions  TYPE CMS_TAB_CAG_POR_OBJ, "   
lv_c_tab_cag_bp  TYPE CMS_TAB_CAG_BP_OBJ, "   
lv_c_tab_cag_por_bp  TYPE CMS_TAB_CAG_POR_BP_OBJ, "   
lv_c_tab_cag_bp_trm  TYPE CMS_TAB_CAG_BP_TRM_OBJ, "   
lv_c_tab_cag_doc  TYPE CMS_TAB_CAG_DOC_OBJ, "   
lv_c_tab_cag_rules  TYPE CMS_TAB_CAG_RULES_OBJ, "   
lv_c_tab_cag_sa  TYPE CMS_TAB_CAG_SA_OBJ, "   
lv_c_tab_cag_exp  TYPE CMS_TAB_CAG_EXP_OBJ. "   

  CALL FUNCTION 'CMS_OBJ_CAG_CREATE_TECH_KEY'  "Create GUID for line items(Por,Rules,CAG-BP,CAG-DOC)
    IMPORTING
         E_TAB_RC = lv_e_tab_rc
    CHANGING
         C_TAB_CAG_PORTIONS = lv_c_tab_cag_portions
         C_TAB_CAG_BP = lv_c_tab_cag_bp
         C_TAB_CAG_POR_BP = lv_c_tab_cag_por_bp
         C_TAB_CAG_BP_TRM = lv_c_tab_cag_bp_trm
         C_TAB_CAG_DOC = lv_c_tab_cag_doc
         C_TAB_CAG_RULES = lv_c_tab_cag_rules
         C_TAB_CAG_SA = lv_c_tab_cag_sa
         C_TAB_CAG_EXP = lv_c_tab_cag_exp
. " CMS_OBJ_CAG_CREATE_TECH_KEY




ABAP code using 7.40 inline data declarations to call FM CMS_OBJ_CAG_CREATE_TECH_KEY

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!