cancel
Showing results for 
Search instead for 
Did you mean: 

How to suppress dialog/pop-up after BAPI_SALESORDER_CHANGE run ?

vinayad
Participant
0 Kudos
2,856

Hello all,

Any help would be appreciated!

I am trying to suppress dialog/pop-up after updating SO# using BAPI_SALESORDER_CHANGE but it is displaying dialog message <attached>.

CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.

SUPPRESS DIALOG.

      CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
        EXPORTING
          SALESDOCUMENT               = i_vbeln
          ORDER_HEADER_IN             = order_header
          ORDER_HEADER_INX            = order_headerx
        TABLES
          RETURN                      = t_return
          ORDER_ITEM_IN               = i_order_item_in
          ORDER_ITEM_INX              = i_order_item_inx
          SCHEDULE_LINES              = i_order_sch_in
          SCHEDULE_LINESX             = i_order_sch_inx
          EXTENSIONIN                 = i_extension_in.

pic.png

Accepted Solutions (1)

Accepted Solutions (1)

vinayad
Participant
0 Kudos

Hello,

I had set "sy-batch = 'X' and sy-binpt = 'X' ", now it is avoiding to display the pop-up which has attached earlier.

Thank you!

0 Kudos

Hello Vinayak,

I have a similar requirement. Can you paste the code here what you wrote ?

Regards,

Abhishek

Sandra_Rossi
Active Contributor

This solution of changing System Fields is not recommended by SAP.

Instead, as said by all other people in this thread, fix your custom development which is called by the BAPI, it should not display a dialog.

Answers (2)

Answers (2)

RaymondGiuseppi
Active Contributor

Check if the pop-up comes from

  • Poorly implemented Exit/BAdI/Enh (developer did not check if it was actually online and not running in a BAPI, BDC, RFC process or similar tool).
  • Standard SAP behavior (search for OSS notes, eventually create an OSS message
NTeunckens
Active Contributor

Check SAP-Notes on the BAPI, there are several Notes regarding code-corrections for Dialog / Popup related issues ...
Also there could be some Custom coding interfering (as mentioned by others), check through Debugging ...