SAP RSB1_OSNAME_TO_ICNAME Function Module for InfoCube to a Data Source
RSB1_OSNAME_TO_ICNAME is a standard rsb1 osname to icname SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for InfoCube to a Data Source 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 rsb1 osname to icname FM, simply by entering the name RSB1_OSNAME_TO_ICNAME into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSBNAME
Program Name: SAPLRSBNAME
Main Program: SAPLRSBNAME
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RSB1_OSNAME_TO_ICNAME 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 'RSB1_OSNAME_TO_ICNAME'"InfoCube to a Data Source.
EXPORTING
I_OSOURCE = "DataSource
* I_OSTYPE = RSAOT_C_OSTYPE-TRAN "Single-Character Indicator
IMPORTING
E_ICNAME = "InfoCube
EXCEPTIONS
NAME_ERROR = 1
IMPORTING Parameters details for RSB1_OSNAME_TO_ICNAME
I_OSOURCE - DataSource
Data type: ROOSOURCEROptional: No
Call by Reference: No ( called with pass by value option)
I_OSTYPE - Single-Character Indicator
Data type: ROOSOURCE-TYPEDefault: RSAOT_C_OSTYPE-TRAN
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSB1_OSNAME_TO_ICNAME
E_ICNAME - InfoCube
Data type: RSINFOCUBEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NAME_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSB1_OSNAME_TO_ICNAME 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_e_icname | TYPE RSINFOCUBE, " | |||
| lv_i_osource | TYPE ROOSOURCER, " | |||
| lv_name_error | TYPE ROOSOURCER, " | |||
| lv_i_ostype | TYPE ROOSOURCE-TYPE. " RSAOT_C_OSTYPE-TRAN |
|   CALL FUNCTION 'RSB1_OSNAME_TO_ICNAME' "InfoCube to a Data Source |
| EXPORTING | ||
| I_OSOURCE | = lv_i_osource | |
| I_OSTYPE | = lv_i_ostype | |
| IMPORTING | ||
| E_ICNAME | = lv_e_icname | |
| EXCEPTIONS | ||
| NAME_ERROR = 1 | ||
| . " RSB1_OSNAME_TO_ICNAME | ||
ABAP code using 7.40 inline data declarations to call FM RSB1_OSNAME_TO_ICNAME
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.| "SELECT single TYPE FROM ROOSOURCE INTO @DATA(ld_i_ostype). | ||||
| DATA(ld_i_ostype) | = RSAOT_C_OSTYPE-TRAN. | |||
Search for further information about these or an SAP related objects