SAP CMS_MAP_TC_CAG_NAVIGATE Function Module for Display Collateral Agreements using Agreemnet key (CAG GUID)
CMS_MAP_TC_CAG_NAVIGATE is a standard cms map tc cag navigate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Collateral Agreements using Agreemnet key (CAG GUID) 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 map tc cag navigate FM, simply by entering the name CMS_MAP_TC_CAG_NAVIGATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_MAP_CAG
Program Name: SAPLCMS_MAP_CAG
Main Program: SAPLCMS_MAP_CAG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CMS_MAP_TC_CAG_NAVIGATE 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_MAP_TC_CAG_NAVIGATE'"Display Collateral Agreements using Agreemnet key (CAG GUID).
EXPORTING
AGREEMENT_KEY = "GUID for Table CMS_CAG
IMPORTING Parameters details for CMS_MAP_TC_CAG_NAVIGATE
AGREEMENT_KEY - GUID for Table CMS_CAG
Data type: BAPICMS_DTE_TC_CAG_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CMS_MAP_TC_CAG_NAVIGATE 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_agreement_key | TYPE BAPICMS_DTE_TC_CAG_GUID. " |
|   CALL FUNCTION 'CMS_MAP_TC_CAG_NAVIGATE' "Display Collateral Agreements using Agreemnet key (CAG GUID) |
| EXPORTING | ||
| AGREEMENT_KEY | = lv_agreement_key | |
| . " CMS_MAP_TC_CAG_NAVIGATE | ||
ABAP code using 7.40 inline data declarations to call FM CMS_MAP_TC_CAG_NAVIGATE
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