Workflow message/document

[Former Member]

Hi all!

Do workflow messages have a way to identify them such as it happens with the work items which are identified with the work item ID?

Where are workflow messages generated?

I am asking this since I am receiving some of them with error messages and I can not find where they are generated.

Thank you!

Andrea

[former_member184112 · Accepted solution]

HI Andrea,

Please check in Tcode SWI2_DIAG.

Check the error overview

Thanks and Regards,

Prabhakar Dharmala

[Former Member · Accepted solution]

Hi Dharmala,

Unluckily I do not have access to this transaction.

Is there another tcode to monitor this?

Thank you!

Andrea

[Former Member]

Hi,

according to Mike, check your message get your WF object ID and go to SWI6. Here you can look for all WF instances that refer to your BO (active, in error, finished,...).

Regards,

Gianluca

[pokrakam]

Hello Andrea,

If you are talking about messages informing you that a workflow is in error then there is no direct link.

This is because the message can be generated in various ways outside of WF. The most common is the error monitoring job RSWERRE which runs every 20 mins and will send these. Also, there could be a problem creating the workflow itself (i.e. there is no workflow, thus no ID)

In both cases you should refer to the contents of the message. In the second scenario for e.g. it may give you a Sales Order number for which a WF failed to start. You will need to work from the document and find the error.

Hope that helps,

Mike

[Former Member]

Thank you Mike. Just to clarify you, the message I am talking about is one which arrives to my inbox everyday in the documents folder not in workflow folder.

The message says:

Error processing following event linkage:

BUS2012 RELEASESTEPCREATED WS20000075

Following error occurred:

OL 365

ReleaseCode

Message text:

Mandatory import element 'ReleaseCode' missing

Event container contains following data:

CD_CHANGENR 000000010C0257574647

CD_OBJECTCLAS 000000015CEINKBELEG

CD_OBJECTID 000000090C4300312700

EVTCREATION_DATE 000000008D20070517

EVTCREATION_TIME 000000006T195248

EVTCREATOR 000000014CUSC059220

EVTLANGUAGE 000000001CE

EVTNAME 000000032CRELEASESTEPCREATED

EVTOBJECT 000000090oPRDCLNT100BUS2012 4300312700

EVTOBJKEY 000000070C4300312700

EVTOBJTYPE 000000010CBUS2012

EVTRECEIVER_ID 000000090C

Event linkage not changed.

Event stored temporarily.

Events can be redelivered via event queue

administration (transaction SWEQADM).

Thanks again!

Andrea

[former_member184112]

Hi Andrea,

then in this case

Purchase Order

SPRO-> MM>Purchasing->Pur ord-->Release procedure> Procedure with classification -

---

> set up procedure with classification--> double click on Release strategies

Check in ME22N any PO number with the status release code and Users within the SPRO..

I think... Not configured with Release Strategy in SPRO.

Please check with your MM functional Consult.

Thanks and Regards,

Prabhakar Dharmala

[pokrakam]

Hello Andrea,

This is an instance of the second scenario I described. In your example, an event RELEASESTEPCREATED is raised for PO 4300312700, but there is no release code, which is a mandatory parameter. You will not see a Workflow in error because it didn't start.

Either there is a problem with the event (is this being raised in custom code?) and there is no release code, or the RC is not being bound to the WF (goto the WF builder -> Header -> Triggering events -> binding).

Cheers,

Mike

[Former Member]

Thanks Mike for your soon reply! I have checked the binding before but everything seems to be ok. I am trying to understand how is the release code sent to the workflow task?

Thanks again!

Andrea

[Former Member]

Dharmala,

I could enter to SPRO however I did not find a place where it says MM->Purchasing... and all the options you asked me to go till I find Release Strategies.

On my SPRO I did find none of the options you mentioned. Does this mean that I have no release strategy ?

[former_member184112]

Hi Andrea,

MM - Material Management

Yes, I am sure it is the problem of Release strategies...

Depends on the Reelase code OL 365, your workflow will send a mail to that person which is assigned in the SPRO release strategies to that particular Manager.

Thanks and Regards,

Prabhakar Dharmala

[pokrakam]

Hello Andrea,

If the binding includes Release Code then your WF is correct and the problem is in the application.

To understand how the release code is send, have a look at the object BUS2012 (Txn SWO1). Under events, click on releasestepcreated, click the "Parameters" button in the toolbar. These event parameters in addition to the system ones (ReleaseCode in this case) must be populated by whatever raises the event. So if your event is raised by custom developments then your problem is there, else if it's customizing then I'd suggest asking an MM person to look at the release config.

Hope that helps,

Mike

[Former Member]

Thank you very much for your help!! I will check all your suggestions and let you know if I found what the problem might be...

Thanks again!

Andrea

[KKilhavn]

Check your release strategies. Are you using overall release? Then remember that SAP will only use information that is common when determining release strategies. You may have overlapping strategies, and that may be the cause of your problem.

See OSS Note 493900 (FAQ: Release strategy) - just in case there is something relevant there.

[Former Member]

Thank you Kilhavn!

Mike, I did what you suggested, I went to TCode SWO1 and I found that the release code parameter has the following value: 40A. Why is the task sending the error message if the parameter Release Code has a value?

Thanks for all your help!!

Andrea

[former_member184112]

Hi Andrea,

Error in OL Release code ....

I can suggest you one..

Go to SWELS do trace on,

Execute in SWUE -- >Object Key ---> Give PO --> Create Event --->Event Receiver

Check in SWEL

Please check all tell me what is there in SWEL

Thanks and Regards,

Prabhakar Dharmala

[pokrakam]

Hi Andrea,

That was in reply to your question "how is the release code sent to the workflow task?". I tried to show you where the event parameter is <i>defined</i>, the email you received contains the actual <i>contents</i> of the event container. RELEASECODE is missing so I would guess that your MM config is wrong.

I can see where the "40A" confusion came from.... it's labelled "First Release". However it refers to the SAP Release (Version) in which this parameter was first used and has nothing to do with PO releases.

Hope that clears it up...

Mike

[KKilhavn]

Mike has mentioned twice that the release code must be set by whoever raises the event and asked you if that is custom code or standard code. I can't see an answer to that question. It would be a good place to start since nothing else has helped so far..... Set a break-point in the code and check if there is a problem when filling the container (and that they indeed fill the container).

[Former Member]

Kilhavn,

I do not know how to see if it is a custom code or standard code. I did not develop it that's why I am trying to understand how it works.

Thanks

Andrea

[former_member184112]

Hi Mike,

I have one Small doubt.

But I need custom 9A should be a First Release Code.

My Doubt is If we do any configurations for First Release code 9A in R.Strategies will it appear

Thanks and Regards,

Prabhakar Dharmala

[Former Member]

Hi Mike,

I found the 40A on the Creation rel. column on the Parameter: Release Code Object type: BUS2012. Do you mean this is not the PO release?

Thanks for your patience!

Andrea

[pokrakam]

Hello,

Correct, that column has nothing to do with PO releases. It means the parameter was created in SAP version 4.0A. Have a look at some of the other parameters (e.g. assigned).

Prabhakar - I hope that answers your too.

Cheers,

Mike

[former_member184112]

hmmmmmmmm

[pokrakam]

Just to clarify: Please don't feel offended, I wasn't making fun of your English skills - a few people (mainly from India) have started to use "doubt" in this way. It was a thread I found both informative and funny.

Cheers,

Mike

[former_member184112]

Actually DOUBT come from

DOUBT - DATE OF Ur BIRTH & TIME

Thanks and Regards,

Prabhakar Dharmala