RS_DATASOURCE_CLBW_PROPOSAL SAP Function module - Proposal of the application for transfer rules

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

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

Pattern for FM RS_DATASOURCE_CLBW_PROPOSAL - RS DATASOURCE CLBW PROPOSAL

CALL FUNCTION 'RS_DATASOURCE_CLBW_PROPOSAL' "Proposal of the application for transfer rules
  EXPORTING
    i_logsys =                  " rsslogsys     Source System
    i_s_osource =               " rsaos_s_oltpsource  Replicate Table for OLTP Sources in BW
    i_workmode =                " rsworkmode    Work mode (with / without creating objects)
  IMPORTING
    e_s_isosmap =               " rsaos_s_isosmap  Mapping between InfoSources and OLTP Sources
    e_t_osfieldmap =            " rsaos_t_osfieldmap  Feld <-> InfoObject Mapping of an OLTP Source
    e_t_messages =              " rsaos_t_messages  Notification Transfer
    .  "  RS_DATASOURCE_CLBW_PROPOSAL

ABAP code example for Function Module RS_DATASOURCE_CLBW_PROPOSAL

The ABAP code below is a full code listing to execute function module RS_DATASOURCE_CLBW_PROPOSAL 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_s_isosmap  
 
 TYPE RSAOS_S_ISOSMAP
,
ld_e_t_osfieldmap  
 
 TYPE RSAOS_T_OSFIELDMAP
,
ld_e_t_messages  
 
 TYPE RSAOS_T_MESSAGES
.


DATA(ld_i_logsys) = 'some text here'.

DATA(ld_i_s_osource) = 'some text here'.

DATA(ld_i_workmode) = 'some text here'.
.

CALL FUNCTION 'RS_DATASOURCE_CLBW_PROPOSAL'
  EXPORTING
    i_logsys =                   ld_i_logsys
    i_s_osource =                ld_i_s_osource
    i_workmode =                 ld_i_workmode
  IMPORTING
    e_s_isosmap =                ld_e_s_isosmap
    e_t_osfieldmap =             ld_e_t_osfieldmap
    e_t_messages =               ld_e_t_messages
    .  "  RS_DATASOURCE_CLBW_PROPOSAL

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_s_isosmap
 
 TYPE RSAOS_S_ISOSMAP ,
ld_i_logsys
 
 TYPE RSSLOGSYS ,
ld_e_t_osfieldmap
 
 TYPE RSAOS_T_OSFIELDMAP ,
ld_i_s_osource
 
 TYPE RSAOS_S_OLTPSOURCE ,
ld_e_t_messages
 
 TYPE RSAOS_T_MESSAGES ,
ld_i_workmode
 
 TYPE RSWORKMODE .


ld_i_logsys = 'some text here'.
ld_i_s_osource = 'some text here'.
ld_i_workmode = 'some text here'.