SAP CMSC_CAG_CMS_CAG_RULES_GET Function Module for Function Module for CMS_CAG_RULES
CMSC_CAG_CMS_CAG_RULES_GET is a standard cmsc cag cms cag rules get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Function Module for CMS_CAG_RULES 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 cmsc cag cms cag rules get FM, simply by entering the name CMSC_CAG_CMS_CAG_RULES_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_BDT_GET_COLLECT
Program Name: SAPLCMS_BDT_GET_COLLECT
Main Program: SAPLCMS_BDT_GET_COLLECT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMSC_CAG_CMS_CAG_RULES_GET 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 'CMSC_CAG_CMS_CAG_RULES_GET'"Function Module for CMS_CAG_RULES.
IMPORTING
E_TAB_CAG_RULES = "Agreement-Rules
TABLES
* T_DATA = "BP: Unformatted data transfer
EXPORTING Parameters details for CMSC_CAG_CMS_CAG_RULES_GET
E_TAB_CAG_RULES - Agreement-Rules
Data type: CMS_TAB_CAG_SNG_RULESOptional: No
Call by Reference: Yes
TABLES Parameters details for CMSC_CAG_CMS_CAG_RULES_GET
T_DATA - BP: Unformatted data transfer
Data type: BUSDATAOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CMSC_CAG_CMS_CAG_RULES_GET 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: | ||||
| lt_t_data | TYPE STANDARD TABLE OF BUSDATA, " | |||
| lv_e_tab_cag_rules | TYPE CMS_TAB_CAG_SNG_RULES. " |
|   CALL FUNCTION 'CMSC_CAG_CMS_CAG_RULES_GET' "Function Module for CMS_CAG_RULES |
| IMPORTING | ||
| E_TAB_CAG_RULES | = lv_e_tab_cag_rules | |
| TABLES | ||
| T_DATA | = lt_t_data | |
| . " CMSC_CAG_CMS_CAG_RULES_GET | ||
ABAP code using 7.40 inline data declarations to call FM CMSC_CAG_CMS_CAG_RULES_GET
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