SAP RSO_CTO_COLL_WRITE_TO_REQUEST Function Module for BW Transport: Collect Objects and Write to Transport
RSO_CTO_COLL_WRITE_TO_REQUEST is a standard rso cto coll write to request SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BW Transport: Collect Objects and Write to Transport 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 rso cto coll write to request FM, simply by entering the name RSO_CTO_COLL_WRITE_TO_REQUEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSO_CTO_RFC_API
Program Name: SAPLRSO_CTO_RFC_API
Main Program: SAPLRSO_CTO_RFC_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled + BasXML supported
Update:

Function RSO_CTO_COLL_WRITE_TO_REQUEST 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 'RSO_CTO_COLL_WRITE_TO_REQUEST'"BW Transport: Collect Objects and Write to Transport.
EXPORTING
I_T_TLOGO = "TLOGO Objects
* I_REQUEST_NON_BW = "Transport Request of Non-BW Objects
* I_COLLECT_GROUPING = '000' "Grouping of Types When Collecting Objects (000 = Default = Required Only)
* I_ONLY_CHECK = RS_C_TRUE "= X: Only Consistency Checks; = ' ' Also Write to an Order
* I_REQUEST_BW = ' ' "Request to Which BW Objects Were Written (' ': New Request)
IMPORTING
E_T_OBJECT_DETAILS = "Object Details
E_REQUEST = "Request/Order to Which the Objects Were Written
E_ERROR = "=X: Error
E_T_BAPI_MSG = "Table with BAPI Return Information
IMPORTING Parameters details for RSO_CTO_COLL_WRITE_TO_REQUEST
I_T_TLOGO - TLOGO Objects
Data type: RSO_T_TLOGOOptional: No
Call by Reference: No ( called with pass by value option)
I_REQUEST_NON_BW - Transport Request of Non-BW Objects
Data type: TRKORROptional: Yes
Call by Reference: No ( called with pass by value option)
I_COLLECT_GROUPING - Grouping of Types When Collecting Objects (000 = Default = Required Only)
Data type: RSO_COLLECT_GROUPINGDefault: '000'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ONLY_CHECK - = X: Only Consistency Checks; = ' ' Also Write to an Order
Data type: RS_BOOLDefault: RS_C_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_REQUEST_BW - Request to Which BW Objects Were Written (SPACE: New Request)
Data type: TRKORRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSO_CTO_COLL_WRITE_TO_REQUEST
E_T_OBJECT_DETAILS - Object Details
Data type: RSO_T_CTO_TLOGO_PROPOptional: No
Call by Reference: No ( called with pass by value option)
E_REQUEST - Request/Order to Which the Objects Were Written
Data type: TRKORROptional: No
Call by Reference: No ( called with pass by value option)
E_ERROR - =X: Error
Data type: RS_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
E_T_BAPI_MSG - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSO_CTO_COLL_WRITE_TO_REQUEST 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_t_tlogo | TYPE RSO_T_TLOGO, " | |||
| lv_e_t_object_details | TYPE RSO_T_CTO_TLOGO_PROP, " | |||
| lv_e_request | TYPE TRKORR, " | |||
| lv_i_request_non_bw | TYPE TRKORR, " | |||
| lv_e_error | TYPE RS_BOOL, " | |||
| lv_i_collect_grouping | TYPE RSO_COLLECT_GROUPING, " '000' | |||
| lv_e_t_bapi_msg | TYPE BAPIRETTAB, " | |||
| lv_i_only_check | TYPE RS_BOOL, " RS_C_TRUE | |||
| lv_i_request_bw | TYPE TRKORR. " SPACE |
|   CALL FUNCTION 'RSO_CTO_COLL_WRITE_TO_REQUEST' "BW Transport: Collect Objects and Write to Transport |
| EXPORTING | ||
| I_T_TLOGO | = lv_i_t_tlogo | |
| I_REQUEST_NON_BW | = lv_i_request_non_bw | |
| I_COLLECT_GROUPING | = lv_i_collect_grouping | |
| I_ONLY_CHECK | = lv_i_only_check | |
| I_REQUEST_BW | = lv_i_request_bw | |
| IMPORTING | ||
| E_T_OBJECT_DETAILS | = lv_e_t_object_details | |
| E_REQUEST | = lv_e_request | |
| E_ERROR | = lv_e_error | |
| E_T_BAPI_MSG | = lv_e_t_bapi_msg | |
| . " RSO_CTO_COLL_WRITE_TO_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM RSO_CTO_COLL_WRITE_TO_REQUEST
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_collect_grouping) | = '000'. | |||
| DATA(ld_i_only_check) | = RS_C_TRUE. | |||
| DATA(ld_i_request_bw) | = ' '. | |||
Search for further information about these or an SAP related objects