SAP CMS_API_CAG_RBL_GEN_BY_RBL Function Module for Generate Collateral Agreement -Receivable links for a receivable









CMS_API_CAG_RBL_GEN_BY_RBL is a standard cms api cag rbl gen by rbl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Generate Collateral Agreement -Receivable links for a receivable 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 api cag rbl gen by rbl FM, simply by entering the name CMS_API_CAG_RBL_GEN_BY_RBL into the relevant SAP transaction such as SE37 or SE38.

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



Function CMS_API_CAG_RBL_GEN_BY_RBL 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_API_CAG_RBL_GEN_BY_RBL'"Generate Collateral Agreement -Receivable links for a receivable
EXPORTING
I_STR_CAG_RBL_RBL_DETAILS = "Receivable Interface Header Information with key
I_TAB_CAG_RBL_RBL_BP = "Receivable Interface: Business partners
* I_FLG_SIMULATE = "Flag: Simulate Collateral Agrement -Receivable links

IMPORTING
E_TAB_CAG_RBL_INS = "Collateral Agreement-Receivable details with the CAG-GUID
E_TAB_CAG_RBL_DEL = "Collateral Agreement-Receivable details with the CAG-GUID
E_TAB_CAG_RBL_EXISTING = "Collateral Agreement-Receivable details with the CAG-GUID
E_TAB_RC = "Return Code and corresponding Message
.



IMPORTING Parameters details for CMS_API_CAG_RBL_GEN_BY_RBL

I_STR_CAG_RBL_RBL_DETAILS - Receivable Interface Header Information with key

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

I_TAB_CAG_RBL_RBL_BP - Receivable Interface: Business partners

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

I_FLG_SIMULATE - Flag: Simulate Collateral Agrement -Receivable links

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

EXPORTING Parameters details for CMS_API_CAG_RBL_GEN_BY_RBL

E_TAB_CAG_RBL_INS - Collateral Agreement-Receivable details with the CAG-GUID

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

E_TAB_CAG_RBL_DEL - Collateral Agreement-Receivable details with the CAG-GUID

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

E_TAB_CAG_RBL_EXISTING - Collateral Agreement-Receivable details with the CAG-GUID

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

E_TAB_RC - Return Code and corresponding Message

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

Copy and paste ABAP code example for CMS_API_CAG_RBL_GEN_BY_RBL 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_cag_rbl_ins  TYPE CMS_TAB_CAG_RBL_LINK_DATA, "   
lv_i_str_cag_rbl_rbl_details  TYPE CMS_STR_CAG_RBL_RBL_DETAILS, "   
lv_e_tab_cag_rbl_del  TYPE CMS_TAB_CAG_RBL_LINK_DATA, "   
lv_i_tab_cag_rbl_rbl_bp  TYPE CMS_TAB_CAG_RBL_RBL_BP_DETAILS, "   
lv_i_flg_simulate  TYPE CMS_DTE_FLG_SIMULATE, "   
lv_e_tab_cag_rbl_existing  TYPE CMS_TAB_CAG_RBL_LINK_DATA, "   
lv_e_tab_rc  TYPE CMS_TAB_MSG_COL_MESSAGE. "   

  CALL FUNCTION 'CMS_API_CAG_RBL_GEN_BY_RBL'  "Generate Collateral Agreement -Receivable links for a receivable
    EXPORTING
         I_STR_CAG_RBL_RBL_DETAILS = lv_i_str_cag_rbl_rbl_details
         I_TAB_CAG_RBL_RBL_BP = lv_i_tab_cag_rbl_rbl_bp
         I_FLG_SIMULATE = lv_i_flg_simulate
    IMPORTING
         E_TAB_CAG_RBL_INS = lv_e_tab_cag_rbl_ins
         E_TAB_CAG_RBL_DEL = lv_e_tab_cag_rbl_del
         E_TAB_CAG_RBL_EXISTING = lv_e_tab_cag_rbl_existing
         E_TAB_RC = lv_e_tab_rc
. " CMS_API_CAG_RBL_GEN_BY_RBL




ABAP code using 7.40 inline data declarations to call FM CMS_API_CAG_RBL_GEN_BY_RBL

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!