RCSBI010 is a standard Executable ABAP Report available within your SAP system (depending on your version and release level). It is used for This report is used to copy bills of material
If you would like to execute this report or see the full code listing simply enter RCSBI010 into the relevant SAP transactions such as SE38 or SE80
Below is a list of transaction codes which are relevant to this SAP report
OS41 - Transfer BOM without Long Text
This report can be called from another progam/report simply by using the ABAP SUBMIT statement, see below for example ABAP code snipts of how to do this.
Selection Text: BDC_FLAG = ?...(BDC_FLAG)
Selection Text: LOG_NAME = Logical File Name
Title: Create BOMs using Batch Input
Text Symbol: 001 = Processing the data records imported from the file:
Text Symbol: 002 = Create Folder
Text Symbol: 003 = Selected: Always create BI sessions
Text Symbol: 004 = Not selected: Create BI sessions in case of error only
Text Symbol: 006 = Read file from application server
Text Symbol: 007 = Read File from Presentation Server
Text Symbol: 008 = Read File from External Application Server
Text Symbol: 009 = Storage location of file to be read
Text Symbol: 010 = Server Name
Text Symbol: 011 = The following messages were displayed:
No INCLUDES are used within this REPORT code!
No SAP DATABASE tables are accessed within this REPORT code!
TH_SELECT_SERVER CALL FUNCTION 'TH_SELECT_SERVER' EXPORTING services = msxxlist-msgtypes
IMPORTING server = server
EXCEPTIONS no_server_list_received = 04 no_server_selected = 08.
FILE_GET_NAME CALL FUNCTION 'FILE_GET_NAME' EXPORTING logical_filename = log_name use_presentation_server = data_frn
IMPORTING file_name = ds_phy_name
EXCEPTIONS file_not_found = 04.
FILE_VALIDATE_NAME CALL FUNCTION 'FILE_VALIDATE_NAME' EXPORTING LOGICAL_FILENAME = gc_logfile_ldm CHANGING PHYSICAL_FILENAME = ds_phy_name EXCEPTIONS LOGICAL_FILENAME_NOT_FOUND = 1 VALIDATION_FAILED = 2.
TH_SERVER_LIST CALL FUNCTION 'TH_SERVER_LIST' EXPORTING services = msxxlist-msgtypes
TABLES list = server_tab.
CS_BI_GET_BOM_FILE_REMOTE_HOST CALL FUNCTION 'CS_BI_GET_BOM_FILE_REMOTE_HOST' DESTINATION server EXPORTING bom_filename = ds_phy_name log_filename = log_name "n 1524781 TABLES bom_file = pc_data_tab EXCEPTIONS logical_filename_not_found = 01 "n 1524781 validation_failed = 02 "n 1524781 open_failure = 04 file_contains_no_data = 08.
BDC_CLOSE_GROUP CALL FUNCTION 'BDC_CLOSE_GROUP'.
BDC_CLOSE_GROUP CALL FUNCTION 'BDC_CLOSE_GROUP'.
BDC_CLOSE_GROUP CALL FUNCTION 'BDC_CLOSE_GROUP' "note535720 EXCEPTIONS "note535720 OTHERS = 1. "note535720
CS_BI_BOM_CREATE_BATCH_INPUT1 CALL FUNCTION 'CS_BI_BOM_CREATE_BATCH_INPUT1' EXPORTING bdc_flag = bdc_flag close_group = close_group commit_work = commit_work bom_header = bom_header group_data = bgr00 new_group = new_group tcode_mode = tcd_mode tcode_update = 'A'
IMPORTING msgty = message_type msgid = message_id msgno = message_number msgv1 = message_var1 msgv2 = message_var2 msgv3 = message_var3 msgv4 = message_var4
TABLES bom_item = bom_item bom_sub_item = bom_sub_item.
CS_BI_BOM_CREATE_BATCH_INPUT1 CALL FUNCTION 'CS_BI_BOM_CREATE_BATCH_INPUT1' EXPORTING bdc_flag = local_bdc_flag close_group = close_group commit_work = commit_work bom_header = bom_header group_data = bgr00 new_group = new_group tcode_mode = tcd_mode tcode_update = 'A'
IMPORTING msgty = message_type msgid = message_id msgno = message_number msgv1 = message_var1 msgv2 = message_var2 msgv3 = message_var3 msgv4 = message_var4
TABLES bom_item = bom_item bom_sub_item = bom_sub_item.
WRITE_MESSAGE CALL FUNCTION 'WRITE_MESSAGE' EXPORTING msgid = aux_msgid msgno = aux_msgno msgty = aux_msgty msgv1 = w_msgv1 msgv2 = w_msgv2 msgv3 = w_msgv3 msgv4 = w_msgv4 msgv5 = space
IMPORTING error = error_flag messg = loc_aux_message msgln = message_length.
Although this basic information may have limited use it does provide an easy to find location to store any knowledge about this program/report.