SAP Reports / Programs | Cross-Application Components | European Monetary Union: Euro(CA-EUR) SAP CA

DTL_MT_RT_CHECK SAP ABAP Report - Checks whether the runtime function modules exist in the Sender System







DTL_MT_RT_CHECK 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 in the DTL context to check that all conversion objects, for which "GENERATED" flag is currently set to TRUE in DMC_MT_TABLES, if the runtime objects really exist in the sender system...see full standard documentation available for this report. Also check out the submitted Comments related to this SAP report and the details below to see which OBJECTS it interacts with such as TABLES, FUNCTION MODULES, INCLUDES ETC.

If you would like to execute this report or see the full code listing simply enter DTL_MT_RT_CHECK 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 DTL_MT_RT_CHECK. "Basic submit
SUBMIT DTL_MT_RT_CHECK AND RETURN. "Return to original report after report execution complete
SUBMIT DTL_MT_RT_CHECK 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_APPLIC = Application
Selection Text: P_MT_ID = Mass Transfer Id
Selection Text: P_PROJ = Project
Selection Text: P_RCV = check receiver system
Selection Text: P_SESSID = Session Id
Selection Text: P_SND = check sender system
Selection Text: P_SPROJ = Sub Project
Title: Checks whether the runtime function modules exist in the Sender System


INCLUDES used within this REPORT DTL_MT_RT_CHECK

No INCLUDES are used within this REPORT code!


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:

GET_JOB_RUNTIME_INFO CALL FUNCTION 'GET_JOB_RUNTIME_INFO' IMPORTING jobcount = l_jobcount jobname = l_jobname EXCEPTIONS OTHERS = 0.

ENQUEUE_E_DMC_JOB CALL FUNCTION 'ENQUEUE_E_DMC_JOB' EXPORTING mode_dmc_job_lock_struct = 'E' jobname = l_jobname jobcount = l_jobcount _scope = '2' _wait = 'X' _collect = ' ' EXCEPTIONS OTHERS = 0.

DMC_FUNCTION_EXISTS * CALL FUNCTION 'DMC_FUNCTION_EXISTS' * DESTINATION l_send_rfc_dest * EXPORTING * i_funcname = l_funcname * EXCEPTIONS * communication_failure = 1 MESSAGE l_text * system_failure = 2 MESSAGE l_text * function_not_exist = 3 * OTHERS = 4.

DMC_FUNCTION_EXISTS CALL FUNCTION 'DMC_FUNCTION_EXISTS' DESTINATION l_send_rfc_dest TABLES xt_function_modules = lt_gen_fm EXCEPTIONS communication_failure = 1 MESSAGE l_text system_failure = 2 MESSAGE l_text function_not_exist = 3 OTHERS = 4.

DMC_FUNCTION_EXISTS * CALL FUNCTION 'DMC_FUNCTION_EXISTS' * DESTINATION l_rcvr_rfc_dest * EXPORTING * i_funcname = l_funcname * EXCEPTIONS * communication_failure = 1 MESSAGE l_text * system_failure = 2 MESSAGE l_text * function_not_exist = 3 * OTHERS = 4.

DMC_FUNCTION_EXISTS CALL FUNCTION 'DMC_FUNCTION_EXISTS' DESTINATION l_rcvr_rfc_dest TABLES xt_function_modules = lt_gen_fm EXCEPTIONS communication_failure = 1 MESSAGE l_text system_failure = 2 MESSAGE l_text function_not_exist = 3 OTHERS = 4.



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 DTL_MT_RT_CHECK or its description.