Skip to Content
author's profile photo Former Member
Former Member



I am creating an ER notification using bapi IQS4_CREATE_NOTIFICATION. I am passing the SM Order as one of the parameters in creating the ER notification. This bapi works fine the first time that I run it. However, if in another session, I carry out any functionality that TECOs (technically completes) an SM order (say SM Order b) and then come back to the first session and use this bapi again to create an ER notification by passing a new SM Order ( say SM Order a ) , then I get a short dump DUMP_STATUS_INCONSYSTENCY_FRE due to the fact that the SMOrder b is not cleared from memory and the status of this is TECO. If the status of the sm order created in the second session is anything other than TECO, then the creation of the notification in the other session passes.

Is there anyone out there that has come across this error and could advise of some solution? Is there an OSS note that could be applied to correct this error?

Please advise.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jan 26, 2007 at 10:03 PM

    Why don't you lock the SM order before calling the BAPI and unlock it after?


    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.