Info type pop ups interrupting back ground jobs

[ricky_shaw]

Hi,
I am running a mass back ground job for a Z*prog(se38) which calls other Z*FM to do some FI postings by  
That Z* FM pops-up an info type 'msg i' pops-up for certain validations and i have to hit enter to continue.

So when i schedule my Z* prog in background, this pop up msg  is interrupting the background jobs. How do i suppress this pop up msg in my Z* prog?

 pls suggest.

[Sandra_Rossi]

You didn't explain the cause of this popup hence it's impossible to answer.

[ricky_shaw]

Oops!! i think i clearly mentioned that my prog calls other Z*FM which pops-up an information msg (type i) and i have to hit enter to continue.

[Sandra_Rossi]

I don't understand. If you don't share your Z code, do you think you can be helped? Obviously, the general answer is "change your Z code to not display the popup in batch" but I guess you're not looking for this obvious answer.

NB: "how to suppress popup in batch" has been asked hundreds of times in the forum.

[Sandra_Rossi]

In a background job, the following statement does not itself interrupt the code, it appends a message to the job log (while in dialog, it shows a popup/waits for user input):

MESSAGE i001(zanything) WITH optional_arguments.

Please describe exactly what you have observed, don't assume that it's this line of code which stops the job (I guess that other ABAP code is executed after this line of code which will stop the job).

Messages - Background Processing - ABAP Keyword Documentation (sap.com):

• Messages of type I and W are written to the log and the program continues. The user input Enter, which is required to continue the program, is created automatically.

[ricky_shaw]

oh ok..let me see again when Background jb is scheduled

[ricky_shaw]

Hi,
My Z*prog calls another Z*FM which has code for amount posting validations: 
My Z*prog has code like below:

 
call function 'Z_BI_POST_PLEDGE'
      exporting
	vkont       = <fs_pstdata>-vkont
        agency      = <fs_pstdata>-agency
     importing
        doc_no           = <fs_plgdata>-gw_doc

exceptions
        invalid_account    = 1
        invalid_agency     = 2
        invalid_amount     = 3
        posting_failed     = 4
        channel_empty      = 5
        others             = 6.

    if sy-subrc <> 0.
* Implement suitable error handling here
      case sy-subrc.
        when '2'.
          <fs_plgdata>-msg = 'Invalid Agency'.
        when '1'.
          lv_msg = 'Invalid Account'.
        when '3'.
          lv_msg = 'Invalid Amount'.
        when '6'.
          lv_msg = 'Pledge Channel Empty'.
        when others.
          lv_msg = 'Posting failed'.
      endcase.
    endif.

Inside the Z*FM,  When our posting amount > current balance it issues message as below:

Code inside other Z*FM:

IF  amount GT lv_currbal.        "This check issues a info type msg pop-up in calling prog(my above z*prog)                   
    gv_exceeds_balance = 'X'.   
 
    message = 'Posting amount greater than amount due'.
    MESSAGE i000(z_class1) WITH message."'Post amount greater than amount due'.
  ENDIF.

So, if above condition is satisfied  it issues a information type msg pop-up in calling prog(my above z*prog)