How to block Report or program ??

Former Member — Tue, 24 Jul 2007 12:50:39 GMT

hi all.

How to block Report or program ??which tcode i can use to temporary suspend the report or program to exexute.

thanks all.

Re: How to block Report or program ??

Former Member — Tue, 24 Jul 2007 13:08:19 GMT

I'm not sure of your requirement, but see this document... it might help you.....

So, let’s start with creating an order.

The function that we are going to use is CLOI_CHANGES_UPL_31.There is one important point that you have to keep in mind when working with the function: you are given just one call per session. That means, you can create one order or many orders, but with one call. After that, some internal state data is messed up and to save us from initializing it (which has to be done with some really internal functions), we better start a new session if we need to call the function again. So, in my example code below I am going to check whether the current session is not the last one allowed for the current user and call the function in a new task. Note that we have to do the check before EACH call unless we are really sure (I do it only once in the sample code below). Since it’s going to be an asynchronous call, we need to suspend our program until the function running in parallel finishes and get the return data into our program. This is achieved with standard SAP constructs like “performing … on end of task” in the CALL FUNCTION statement and “receive results” in the form that is performed. I am also using a global variable that tells me that the call is over. You can find more useful information in SAP OSS note 545860 that described those specifics about calling that function.

Sample code....

1. Create a production order.

data: t_cloi_ord_exp type standard table of cloiord,

lw_cloi_ord_exp type cloiord,

lt_cloi_msg_obj_log_exp type standard table of cloimoblog,

lt_cloi_methods_exp type standard table of cloimetlog,

t_cloi_messages_exp type standard table of cloimsglog,

lw_cloi_messages_exp type cloimsglog,

ls_cloi_if_par_v2 like cloiifpar.

data: lt_cloi_ordu type standard table of cloiordu,

lw_cloi_ordu type cloiordu,

lt_cloi_ordi type standard table of cloiordi,

lw_cloi_ordi type cloiordi,

lt_cloi_ord_opru type standard table of CLOIOPERU,

lw_cloi_ord_opru type CLOIOPERU.

data:

lf_date like sy-datum,

lf_date2 like sy-datum,

f_flag(1) type c,

f_aufnr like aufk-aufnr.

data: f_act_sess like sm04dic-counter,

f_max_sess like sm04dic-counter.

lf_date = sy-datum + 7. "let's try to schedule it next week

lf_date2 = sy-datum + 14.

clear: ls_cloi_if_par_v2.

those fields below are described in SAP help, but nevermind...

ls_cloi_if_par_v2-commitflg = 'C'.

ls_cloi_if_par_v2-r3_version = '40'.

ls_cloi_if_par_v2-metlog_req = 'X'.

ls_cloi_if_par_v2-msglog_req = 'X'.

ls_cloi_if_par_v2-msgobj_req = 'X'.

ls_cloi_if_par_v2-ord_req = 'X'.

ls_cloi_if_par_v2-ordseq_req = 'X'.

ls_cloi_if_par_v2-ordopr_req = 'X'.

in case if we have external number range,
we have to provide the future order number

lw_cloi_ordi-extaufnr = '1234567890'.

material

lw_cloi_ordi-field = 'MATNR'.

lw_cloi_ordi-value = 'MATNUM1'.