SAP CMS_API_ANL_CON_GET Function Module for Fetch Constellation









CMS_API_ANL_CON_GET is a standard cms api anl con 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 Fetch Constellation 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 anl con get FM, simply by entering the name CMS_API_ANL_CON_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function CMS_API_ANL_CON_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 'CMS_API_ANL_CON_GET'"Fetch Constellation
  EXPORTING
*  I_AST_GUID =  "GUID for Table CMS_AST
*  I_CAG_GUID =  "GUID for Table CMS_CAG
*  I_RBL_SKY =  "GUID for Table CMS_RBL
*  I_TAB_AST_STATUS =  "System status of the Asset
*  I_TAB_CAG_STATUS =  "System status for the Collateral Agreement
*  I_TAB_RBL_STATUS =  "Receivables Status
*  I_VALID_DATE =  "Date against which entity validity check is done

 IMPORTING
   E_TAB_AST_GUID =  "Technical Key of the Asset
   E_TAB_CHG =  "Charges on an Asset
   E_TAB_CAG_GUID =  "Technical Key of the Collateral Agreement
   E_TAB_CAG_RBL =  "Collateral Agreement - Receivable Link Details
   E_TAB_RBL_SKY =  "Technical Key of the Receivable
   E_TAB_REL_CAG_TO =  "Table of relationship details from CAG-POR to CAG
   E_TAB_RC =  "Return Code and corresponding Message
.



IMPORTING Parameters details for CMS_API_ANL_CON_GET

I_AST_GUID - GUID for Table CMS_AST

Data type: CMS_DTE_AST_GUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CAG_GUID - GUID for Table CMS_CAG

Data type: CMS_DTE_CAG_GUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_RBL_SKY - GUID for Table CMS_RBL

Data type: CMS_STR_RBL_SKY
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TAB_AST_STATUS - System status of the Asset

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

I_TAB_CAG_STATUS - System status for the Collateral Agreement

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

I_TAB_RBL_STATUS - Receivables Status

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

I_VALID_DATE - Date against which entity validity check is done

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

EXPORTING Parameters details for CMS_API_ANL_CON_GET

E_TAB_AST_GUID - Technical Key of the Asset

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

E_TAB_CHG - Charges on an Asset

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

E_TAB_CAG_GUID - Technical Key of the Collateral Agreement

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

E_TAB_CAG_RBL - Collateral Agreement - Receivable Link Details

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

E_TAB_RBL_SKY - Technical Key of the Receivable

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

E_TAB_REL_CAG_TO - Table of relationship details from CAG-POR to CAG

Data type: CMS_TAB_REL_CAG_TO
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_ANL_CON_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:
lv_i_ast_guid  TYPE CMS_DTE_AST_GUID, "   
lv_e_tab_ast_guid  TYPE CMS_TAB_AST_GUID, "   
lv_e_tab_chg  TYPE CMS_TAB_CHG, "   
lv_i_cag_guid  TYPE CMS_DTE_CAG_GUID, "   
lv_i_rbl_sky  TYPE CMS_STR_RBL_SKY, "   
lv_e_tab_cag_guid  TYPE CMS_TAB_CAG_GUID, "   
lv_e_tab_cag_rbl  TYPE CMS_TAB_CAG_RBL_LINK_DATA, "   
lv_i_tab_ast_status  TYPE CMS_TAB_SYS_STAT, "   
lv_e_tab_rbl_sky  TYPE CMS_TAB_RBL_SKY, "   
lv_i_tab_cag_status  TYPE CMS_TAB_SYS_STAT, "   
lv_e_tab_rel_cag_to  TYPE CMS_TAB_REL_CAG_TO, "   
lv_i_tab_rbl_status  TYPE CMS_TAB_RBL_STATUS, "   
lv_e_tab_rc  TYPE CMS_TAB_MSG_COL_MESSAGE, "   
lv_i_valid_date  TYPE CMS_DTE_CAG_VALID_FROM. "   

  CALL FUNCTION 'CMS_API_ANL_CON_GET'  "Fetch Constellation
    EXPORTING
         I_AST_GUID = lv_i_ast_guid
         I_CAG_GUID = lv_i_cag_guid
         I_RBL_SKY = lv_i_rbl_sky
         I_TAB_AST_STATUS = lv_i_tab_ast_status
         I_TAB_CAG_STATUS = lv_i_tab_cag_status
         I_TAB_RBL_STATUS = lv_i_tab_rbl_status
         I_VALID_DATE = lv_i_valid_date
    IMPORTING
         E_TAB_AST_GUID = lv_e_tab_ast_guid
         E_TAB_CHG = lv_e_tab_chg
         E_TAB_CAG_GUID = lv_e_tab_cag_guid
         E_TAB_CAG_RBL = lv_e_tab_cag_rbl
         E_TAB_RBL_SKY = lv_e_tab_rbl_sky
         E_TAB_REL_CAG_TO = lv_e_tab_rel_cag_to
         E_TAB_RC = lv_e_tab_rc
. " CMS_API_ANL_CON_GET




ABAP code using 7.40 inline data declarations to call FM CMS_API_ANL_CON_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



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!