Skip to Content
author's profile photo Sijin Chandran
0
Sijin Chandran

Message with Type E coming like that of Type A

Posted on Jan 04, 2012 at 10:24 AM 238 Views

Hello all ,

I have came across a really strange situation.

I have done my coding in BADI ME_HOLD_PO as follows :

if im_ekko-bedat is not initial.

if im_ekko-bsart ne 'ZSTM'.

if im_ekko-bedat < sy-datlo.

message 'Purchase order date is in the past' type 'E'.

endif.

endif.

endif.

Now the problem is that the above message is not coming as an error message (at status bar) instead its coming like a message with that of type 'A' i.e the message is being displayed as a pop up and the screen is reseted with the press of enter.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    author's profile photo Suhas Saha
    Suhas Saha
    Posted on Jan 04, 2012 at 10:36 AM
    1

    Hello,

    You've to understand in which programming event this BAdI is called to understand this behavior. You can also read the SAP documentation on the [behavior of messages|http://help.sap.com/abapdocu_702/en/abenabap_messages_types.htm].

    BR,

    Suhas

    PS: Check out the demo program DEMO_MESSAGES to have a feel of how messages react during different programming events.

    Add a comment
    10|10000 characters needed characters exceeded

    Comment on This Answer
  • author's profile photo Kesavadas Thekkillath
    Kesavadas Thekkillath
    Posted on Jan 04, 2012 at 10:56 AM
    0

    This badi is not suitable for raising messages. You are just validating the PO header values, please check for other customer exits and available badis for this check. As you have not mentioned the transaction used its hard for us to give you a solution. So search for available exits and Badi's in SCN.

    Kesav

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 22, 2013 at 09:17 PM
    0

    I had the same issue. Implement your check in ME_PROCESS_PO_CUST~CHECK and issue message as follows.

    CH_FAILED = MMPUR_YES.

    MMPUR_MESSAGE_FORCED <your message data>.

    -----------------------------------------

    Then maintain an implicit enhancement spot in class CL_PO_HEADER_HANDLE_MM method GET_TRANSACTION_STATE and set the flag EX_PARKING_ALLOWED_FINAL = MMPUR_NO.

    I exported a flag to memory in the CHECK method and imported it into GET_TRANSACTION_STATE to determine when to not allow parking.

    This will prevent the user from being prompted with an option to HOLD/PARK the PO.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.