SAP CMS_DB_CAG_RBL_DELETE_MLT Function Module for Delete Collateral Agreement-Receivable links
CMS_DB_CAG_RBL_DELETE_MLT is a standard cms db cag rbl delete mlt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete Collateral Agreement-Receivable links 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 db cag rbl delete mlt FM, simply by entering the name CMS_DB_CAG_RBL_DELETE_MLT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_DB_CAG_RBL
Program Name: SAPLCMS_DB_CAG_RBL
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMS_DB_CAG_RBL_DELETE_MLT 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_DB_CAG_RBL_DELETE_MLT'"Delete Collateral Agreement-Receivable links.
EXPORTING
I_TAB_CAG_RBL = "Collateral Agreement-Receivable link GUIDS
* I_FLG_UPDATE_TASK = "Flag: Use update task to save data
IMPORTING Parameters details for CMS_DB_CAG_RBL_DELETE_MLT
I_TAB_CAG_RBL - Collateral Agreement-Receivable link GUIDS
Data type: CMS_TAB_CAG_RBLOptional: No
Call by Reference: Yes
I_FLG_UPDATE_TASK - Flag: Use update task to save data
Data type: CMS_DTE_FLG_UPDATE_TASKOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for CMS_DB_CAG_RBL_DELETE_MLT 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_i_tab_cag_rbl | TYPE CMS_TAB_CAG_RBL, " | |||
| lv_i_flg_update_task | TYPE CMS_DTE_FLG_UPDATE_TASK. " |
|   CALL FUNCTION 'CMS_DB_CAG_RBL_DELETE_MLT' "Delete Collateral Agreement-Receivable links |
| EXPORTING | ||
| I_TAB_CAG_RBL | = lv_i_tab_cag_rbl | |
| I_FLG_UPDATE_TASK | = lv_i_flg_update_task | |
| . " CMS_DB_CAG_RBL_DELETE_MLT | ||
ABAP code using 7.40 inline data declarations to call FM CMS_DB_CAG_RBL_DELETE_MLT
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