2010 Sep 01 1:46 PM
Hello Everyone,
I have a kind of problem with running BDC transaction. I donu2019t know how get rid off success status message. I run MD03 transaction. Like this:
PERFORM bdc_transaction TABLES messtab USING 'MD03' ctu mode update.
Where CTU is set to u2018Xu2019 MODE is set to u2018Nu2019 and UPDATE is set to u2018Lu2019. As you can see table for collecting messages is also given. But in the end system displays the green message in status bar although I really donu2019t want. Iu2019ve looked through the network but found nothing. The program that call the BDC transaction works in foreground. Itu2019s a customer Z program which among the others does also this.
Is there anything I could do?
Regards
Pawel
2010 Sep 01 10:27 PM
if i understood yur question then,
just delete the messtab where message type = S.
2010 Sep 01 2:09 PM
Hi,
Use this:
call transaction 'MD03' mode 'N' using <bdcdata table>
update 'L' messages into lt_message.
Hope this helps
Regards
Shiva
2010 Sep 01 2:18 PM
I am not quite sure about it. The form BDC_TRANSACTION is the SAP standard form used with BDC recording.
FORM BDC_TRANSACTION TABLES P_MESSTAB
USING P_TCODE
P_CTU
P_MODE
P_UPDATE.
DATA: L_SUBRC LIKE SY-SUBRC.
IF P_CTU <> 'X'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING TCODE = P_TCODE
TABLES DYNPROTAB = BDCDATA
EXCEPTIONS OTHERS = 1.
ELSE.
CALL TRANSACTION P_TCODE USING BDCDATA
MODE P_MODE
UPDATE P_UPDATE
MESSAGES INTO P_MESSTAB.
ENDIF.
L_SUBRC = SY-SUBRC.
REFRESH BDCDATA.
SY-SUBRC = L_SUBRC.
ENDFORM.
So as you can see the transaction is being called exactly in the way you told me to. Unfortunately
Edited by: Pawel Kobylinski on Sep 1, 2010 3:21 PM
2010 Sep 01 10:27 PM
if i understood yur question then,
just delete the messtab where message type = S.
2010 Sep 01 11:02 PM
I think the problem is that the message is also displayed on the status bar and the OP doesn't want that.
And if this correct, try running with display errors only. I think the success messages may disappear.
Rob
Edited by: Rob Burbank on Sep 1, 2010 6:06 PM
2010 Sep 01 11:36 PM
Hi,
what you can do is overwrite that message immediately after the call transaction statement with ur custme message.
Even though the mode is N it runs in foreground without displaying the screens.
Or you can use mode E and try it as Rob said.
2010 Sep 02 11:38 AM
it seems that using 'E' mode instead od 'N' helped.
thanks a lot
regards
pawel
2010 Sep 02 11:46 AM
>
> Even though the mode is N it runs in foreground without displaying the screens.
Mode 'N' never runs in foreground irrepective of error or not. Can you please help me bit to understand this? I hope i"m mistaken.
Cheers
Amit.
2010 Sep 02 11:52 AM
Mode 'N' never runs in foreground irrespective of error or not.
I knew you had made a typo when you mentioned background instead of foreground
Cheers,
Suhas
Edited by: Suhas Saha on Sep 2, 2010 4:22 PM
2010 Sep 02 11:56 AM
I knew there are many other Suhas also,so i had to correct before anyone dig into
Cheers
Amit
2024 Jul 09 1:25 PM
Hi,
After completing the BDC CALL statement pass the below code.
This will suppress the standard BDC message.