SAP CMS_API_RBL_GET_SNG Function Module for Fetch single receivable
CMS_API_RBL_GET_SNG is a standard cms api rbl 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 single receivable 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 rbl get sng FM, simply by entering the name CMS_API_RBL_GET_SNG into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_API_RBL
Program Name: SAPLCMS_API_RBL
Main Program: SAPLCMS_API_RBL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMS_API_RBL_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_RBL_GET_SNG'"Fetch single receivable.
EXPORTING
I_RBL_GUID = "GUID for Table CMS_RBL
* I_FLG_LOCK = ' ' "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_RBL_REQD_DATA = "Data that is required for a receivable fetch
IMPORTING
E_STR_RBL_DETAIL_HDR = "Table type receivable interface header information
E_TAB_RBL_DETAIL_POS = "Table type receivable information position
E_TAB_RBL_BP = "Receivable - Business Partner Details (API)
E_TAB_RC = "Return Code and corresponding Message
IMPORTING Parameters details for CMS_API_RBL_GET_SNG
I_RBL_GUID - GUID for Table CMS_RBL
Data type: CMS_DTE_RBL_GUIDOptional: No
Call by Reference: Yes
I_FLG_LOCK - Flag:Indicates that the entity needs to be locked
Data type: CMS_DTE_FLG_LOCKDefault: SPACE
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_DBDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_STR_RBL_REQD_DATA - Data that is required for a receivable fetch
Data type: CMS_STR_RBL_REQD_DATAOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CMS_API_RBL_GET_SNG
E_STR_RBL_DETAIL_HDR - Table type receivable interface header information
Data type: CMS_STR_RBL_SNG_DETAIL_HDROptional: No
Call by Reference: Yes
E_TAB_RBL_DETAIL_POS - Table type receivable information position
Data type: CMS_TAB_RBL_SNG_DETAIL_POSOptional: No
Call by Reference: Yes
E_TAB_RBL_BP - Receivable - Business Partner Details (API)
Data type: CMS_TAB_RBL_BP_APIOptional: No
Call by Reference: Yes
E_TAB_RC - Return Code and corresponding Message
Data type: CMS_TAB_MSG_COL_MESSAGEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CMS_API_RBL_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.| DATA: | ||||
| lv_i_rbl_guid | TYPE CMS_DTE_RBL_GUID, " | |||
| lv_e_str_rbl_detail_hdr | TYPE CMS_STR_RBL_SNG_DETAIL_HDR, " | |||
| lv_i_flg_lock | TYPE CMS_DTE_FLG_LOCK, " SPACE | |||
| lv_e_tab_rbl_detail_pos | TYPE CMS_TAB_RBL_SNG_DETAIL_POS, " | |||
| lv_i_flg_db | TYPE CMS_DTE_FLG_FETCH_FROM_DB, " SPACE | |||
| lv_e_tab_rbl_bp | TYPE CMS_TAB_RBL_BP_API, " | |||
| lv_e_tab_rc | TYPE CMS_TAB_MSG_COL_MESSAGE, " | |||
| lv_i_str_rbl_reqd_data | TYPE CMS_STR_RBL_REQD_DATA. " |
|   CALL FUNCTION 'CMS_API_RBL_GET_SNG' "Fetch single receivable |
| EXPORTING | ||
| I_RBL_GUID | = lv_i_rbl_guid | |
| I_FLG_LOCK | = lv_i_flg_lock | |
| I_FLG_DB | = lv_i_flg_db | |
| I_STR_RBL_REQD_DATA | = lv_i_str_rbl_reqd_data | |
| IMPORTING | ||
| E_STR_RBL_DETAIL_HDR | = lv_e_str_rbl_detail_hdr | |
| E_TAB_RBL_DETAIL_POS | = lv_e_tab_rbl_detail_pos | |
| E_TAB_RBL_BP | = lv_e_tab_rbl_bp | |
| E_TAB_RC | = lv_e_tab_rc | |
| . " CMS_API_RBL_GET_SNG | ||
ABAP code using 7.40 inline data declarations to call FM CMS_API_RBL_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.| DATA(ld_i_flg_lock) | = ' '. | |||
| DATA(ld_i_flg_db) | = ' '. | |||
Search for further information about these or an SAP related objects