SAP Function Modules

CMS_DB_RBL_GET_SNG SAP Function module - Fetch details for an Obligation







CMS_DB_RBL_GET_SNG 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_DB_RBL_GET_SNG into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CMS_DB_RBL
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM CMS_DB_RBL_GET_SNG - CMS DB RBL GET SNG





CALL FUNCTION 'CMS_DB_RBL_GET_SNG' "Fetch details for an Obligation
  EXPORTING
    i_rbl_guid =                " cms_dte_rbl_guid  GUID for a Receivable
*   i_flg_db = SPACE            " cms_dte_flg_fetch_from_db  Flag: Indicates that the data is to be fetched from database
*   i_str_rbl_reqd_data =       " cms_str_rbl_reqd_data  Data that is required for a receivable fetch
  IMPORTING
    e_tab_rbl =                 " cms_tab_rbl   Receivable Details
    e_tab_rbl_bp =              " cms_tab_rbl_bp  Receivable - Business Partner Details
    e_tab_rc =                  " cms_tab_msg_col_message  Return Code and corresponding Message
    .  "  CMS_DB_RBL_GET_SNG

ABAP code example for Function Module CMS_DB_RBL_GET_SNG





The ABAP code below is a full code listing to execute function module CMS_DB_RBL_GET_SNG 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_tab_rbl  TYPE CMS_TAB_RBL ,
ld_e_tab_rbl_bp  TYPE CMS_TAB_RBL_BP ,
ld_e_tab_rc  TYPE CMS_TAB_MSG_COL_MESSAGE .

DATA(ld_i_rbl_guid) = 'Check type of data required'.
DATA(ld_i_flg_db) = 'Check type of data required'.
DATA(ld_i_str_rbl_reqd_data) = 'Check type of data required'. . CALL FUNCTION 'CMS_DB_RBL_GET_SNG' EXPORTING i_rbl_guid = ld_i_rbl_guid * i_flg_db = ld_i_flg_db * i_str_rbl_reqd_data = ld_i_str_rbl_reqd_data IMPORTING e_tab_rbl = ld_e_tab_rbl e_tab_rbl_bp = ld_e_tab_rbl_bp e_tab_rc = ld_e_tab_rc . " CMS_DB_RBL_GET_SNG
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_tab_rbl  TYPE CMS_TAB_RBL ,
ld_i_rbl_guid  TYPE CMS_DTE_RBL_GUID ,
ld_e_tab_rbl_bp  TYPE CMS_TAB_RBL_BP ,
ld_i_flg_db  TYPE CMS_DTE_FLG_FETCH_FROM_DB ,
ld_e_tab_rc  TYPE CMS_TAB_MSG_COL_MESSAGE ,
ld_i_str_rbl_reqd_data  TYPE CMS_STR_RBL_REQD_DATA .

ld_i_rbl_guid = 'Check type of data required'.
ld_i_flg_db = 'Check type of data required'.
ld_i_str_rbl_reqd_data = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CMS_DB_RBL_GET_SNG or its description.