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?