CMS_API_ACG_GET SAP Function module - Fetch Approved Coverage Gap Details

CMS_API_ACG_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CMS_API_ACG_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CMS_API_ACG
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM CMS_API_ACG_GET - CMS API ACG GET

CALL FUNCTION 'CMS_API_ACG_GET' "Fetch Approved Coverage Gap Details
  EXPORTING
    i_acg_guid =                " cms_dte_acg_guid  GUID for Table CMS_ACG ( Approved Coverage Gap)
*   i_flg_lock = 'X'            " cms_dte_flg_lock  Flag:Indicates that the entity needs to be locked
  IMPORTING
    e_str_acg =                 " cms_str_acg_get  Details for a single Approved Coverage Gap(without ACG_GUID)
    e_str_acg_proposal =        " cms_str_acg_proposal_get  Proposal details for a single ACG(without ACG_GUID)
    e_tab_acg_criteria =        " cms_tab_acg_criteria_get  Criteria details for a single ACG(without ACG_GUID)
    e_tab_rc =                  " cms_tab_msg_col_message  Return Code and corresponding Message
    .  "  CMS_API_ACG_GET

ABAP code example for Function Module CMS_API_ACG_GET

The ABAP code below is a full code listing to execute function module CMS_API_ACG_GET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_str_acg  
 
 TYPE CMS_STR_ACG_GET
,
ld_e_str_acg_proposal  
 
 TYPE CMS_STR_ACG_PROPOSAL_GET
,
ld_e_tab_acg_criteria  
 
 TYPE CMS_TAB_ACG_CRITERIA_GET
,
ld_e_tab_rc  
 
 TYPE CMS_TAB_MSG_COL_MESSAGE
.


DATA(ld_i_acg_guid) = 'Check type of data required'.

DATA(ld_i_flg_lock) = 'Check type of data required'.
.

CALL FUNCTION 'CMS_API_ACG_GET'
  EXPORTING
    i_acg_guid =                 ld_i_acg_guid
*   i_flg_lock =                 ld_i_flg_lock
  IMPORTING
    e_str_acg =                  ld_e_str_acg
    e_str_acg_proposal =         ld_e_str_acg_proposal
    e_tab_acg_criteria =         ld_e_tab_acg_criteria
    e_tab_rc =                   ld_e_tab_rc
    .  "  CMS_API_ACG_GET

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_str_acg
 
 TYPE CMS_STR_ACG_GET ,
ld_i_acg_guid
 
 TYPE CMS_DTE_ACG_GUID ,
ld_e_str_acg_proposal
 
 TYPE CMS_STR_ACG_PROPOSAL_GET ,
ld_i_flg_lock
 
 TYPE CMS_DTE_FLG_LOCK ,
ld_e_tab_acg_criteria
 
 TYPE CMS_TAB_ACG_CRITERIA_GET ,
ld_e_tab_rc
 
 TYPE CMS_TAB_MSG_COL_MESSAGE .


ld_i_acg_guid = 'Check type of data required'.
ld_i_flg_lock = 'Check type of data required'.