SAP Reports / Programs
BATCHMAN_POST SAP ABAP Report - Transfer Data to Controlling
BATCHMAN_POST is a standard Executable ABAP Report available within your SAP system (depending on your version and release level). Below is the basic information available for this SAP report including which OBJECTS it interacts with such as TABLES, FUNCTION MODULES, INCLUDES ETC. Also check out the submitted Comments related to this SAP report or see any standard documentation available.
If you would like to execute this report or see the full code listing simply enter BATCHMAN_POST into the relevant SAP transactions such as SE38 or SE80
ABAP code to call this SAP report using the submit statement
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.
SUBMIT BATCHMAN_POST. "Basic submit
SUBMIT BATCHMAN_POST AND RETURN. "Return to original report after report execution complete
SUBMIT BATCHMAN_POST VIA SELECTION-SCREEN. "Display selection screen of submitted report to user
See more syntax options for the ABAP SUBMIT statement
Text pool values
Selection Text: P_ASERV = Application Server
Selection Text: P_EXTNUM = External Document No. Assignt
Selection Text: P_IGNWAR = Ignore warnings
Selection Text: P_PSERV = Presentation Server
Selection Text: P_TEST = Test
Selection Text: P_UPDATE = Post
Selection Text: P_FNAME = D .
Selection Text: P_LOGNAM = D .
Selection Text: P_TEXT = D .
Title: Transfer Data to Controlling
Text Symbol: 001 = File with Transfer Data
Text Symbol: 002 = Messages from
Text Symbol: 003 = the data transfer
Text Symbol: 004 = the test run
Text Symbol: 005 = Post
Text Symbol: 006 = Post After Test Run
Text Symbol: 107 = Continue
Text Symbol: 108 = Long Text
Text Symbol: GEN = Settings
Text Symbol: INP = Input File
Text Symbol: SRC = File System
INCLUDES used within this REPORT BATCHMAN_POST
TABLES used within REPORT and the associated SELECT statement:
No SAP DATABASE tables are accessed within this REPORT code!
Function Modules used within report and the associated call statement:
K41C_DOCUMENTS_GET_FROM_FILE call function 'K41C_DOCUMENTS_GET_FROM_FILE' exporting id_file_name = d_fname "739192 exceptions others = 1.
K41C_RUN_ID_CREATE call function 'K41C_RUN_ID_CREATE' exporting id_file_name = d_fname "739192 id_run_text = p_text importing ed_run_id = d_run_id exceptions others = 1.
K41C_DOCUMENTS_POST call function 'K41C_DOCUMENTS_POST' exporting id_run_id = d_run_id id_auto = p_auto id_test = p_test id_ignore_warnings = p_ignwar id_external_numbers = p_extnum exceptions others = 1.
K41C_RUN_ID_PROTOCOL_DISPLAY call function 'K41C_RUN_ID_PROTOCOL_DISPLAY' exporting id_loghandle = scm_message-log_handle id_callback_prog = gc_repid id_callback_form = gc_callback_form id_callback_type = gc_callback_type id_amodal = gc_modal id_test = p_test id_stop = gd_stop exceptions no_protocol_found = 1 error_in_logfile = 2 others = 3.
Contribute (Add Comments)
Although this basic information may have limited use it does provide an easy to find location to store any knowledge about this program/report.
The contribute/comments section below therefore offer's an opportunity for anyone to add additional information. This can be anything from useful hints, tips and screen shots to relevant SAP notes or anything else you feel is relevant to this report.
This will then be available for everyone to easily find by simply searching on the report name BATCHMAN_POST or its description.
BATCHMAN_POST - Transfer Data to Controlling BATCHMAN_POST - Transfer Data to Controlling BATCHMAN_ERRORS - Data Transfer to Controlling: Postprocessing BATCHMAN_ERRORS - Data Transfer to Controlling: Postprocessing BATCHMAN_DISPLAY - Data Transfer to Controlling: Display Log BATCHMAN_DISPLAY - Data Transfer to Controlling: Display Log