SAP CMS_API_CAG_GET_SNG Function Module for Fetch Collateral Agreement Details

Search SAP Function Modules

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

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

Function CMS_API_CAG_GET_SNG 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_GET_SNG'"Fetch Collateral Agreement Details
  EXPORTING
   I_CAG_GUID =  "GUID for Table CMS_CAG
*  I_FLG_LOCK = 'X' "Flag:Indicates that the entity needs to be locked
*  I_FLG_DB = ' ' "Flag: Indicates that the data is to be fetched from database
*  I_STR_CAG_REQD_DATA =  "Data to be fetched for the CAG

 IMPORTING
   E_STR_CAG =  "Details for a single collateral agreement (without CAG_GUID)
   E_TAB_CAG_SYS_STAT =  "System status
   E_TAB_CAG_USR_STAT =  "User status
   E_TAB_CAG_NOTES =  "Text lines
   E_TAB_RC =  "Return Code and corresponding Message
   E_TAB_CAG_POR =  "Portion details for a single CAG(without CAG_GUID)
   E_TAB_CAG_BP =  "Business Partner Relationships for a CAG (without CAG_GUID)
   E_TAB_CAG_POR_BP =  "Business Partner Relationship for the portions of a CAG
   E_TAB_CAG_BP_TRM =  "Bupa termination details for a CAG (without CAG_GUID)
   E_TAB_CAG_DOC =  "Documents for a single CAG (without CAG_GUID)
   E_TAB_CAG_RULES =  "Rules for a single CAG(without CAG_GUID)
   E_TAB_CAG_SA =  "Special Arrangement for a single CAG (without CAG_GUID)
   E_TAB_CAG_EXP =  "Expenditure Incurred for a CAG (without CAG_GUID)

.

IMPORTING Parameters details for CMS_API_CAG_GET_SNG

I_CAG_GUID - GUID for Table CMS_CAG

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

I_FLG_LOCK - Flag:Indicates that the entity needs to be locked

Data type: CMS_DTE_FLG_LOCK
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_FLG_DB - Flag: Indicates that the data is to be fetched from database

Data type: CMS_DTE_FLG_FETCH_FROM_DB
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_STR_CAG_REQD_DATA - Data to be fetched for the CAG

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

EXPORTING Parameters details for CMS_API_CAG_GET_SNG

E_STR_CAG - Details for a single collateral agreement (without CAG_GUID)

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

E_TAB_CAG_SYS_STAT - System status

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

E_TAB_CAG_USR_STAT - User status

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

E_TAB_CAG_NOTES - Text lines

Data type: CMS_TAB_TXT_LINES
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

E_TAB_CAG_POR - Portion details for a single CAG(without CAG_GUID)

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

E_TAB_CAG_BP - Business Partner Relationships for a CAG (without CAG_GUID)

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

E_TAB_CAG_POR_BP - Business Partner Relationship for the portions of a CAG

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

E_TAB_CAG_BP_TRM - Bupa termination details for a CAG (without CAG_GUID)

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

E_TAB_CAG_DOC - Documents for a single CAG (without CAG_GUID)

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

E_TAB_CAG_RULES - Rules for a single CAG(without CAG_GUID)

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

E_TAB_CAG_SA - Special Arrangement for a single CAG (without CAG_GUID)

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

E_TAB_CAG_EXP - Expenditure Incurred for a CAG (without CAG_GUID)

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

Copy and paste ABAP code example for CMS_API_CAG_GET_SNG 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.

ABAP code using 7.40 inline data declarations to call FM CMS_API_CAG_GET_SNG

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