cancel
Showing results for 
Search instead for 
Did you mean: 

PO Release Workflow Issue-Event : RELEASESTEPCREATED(BUS2012) Container not populated after 1st reelase

hafizul_mollah2
Participant
0 Kudos

Hi All,

I have done the workflow development in HR module and now moved to MM module recently and saw one difference with respect to the event triggering. In HR the we were triggering the event only once(like Hiring or Separating event) and that triggers the WF which completes the whole business process- all approvals and then backend update.

But for PO release workflow I am using Business object BUS2012 event RELEASESTEPCREATED and if I have multiple Release code in the Release strategy then after every release the same event is being triggered- this is my understanding so far ,please correct it if I am wrong.

In my scenario , I have Release code 10 and 20 in the Release Strategy as two levels of approvals are required.WF template copied from Standard WS20000075 and modified.

When I am creating the PO from ME21N , the event RELEASESTEPCREATED is triggering and dialog workitem is going to 1st  Approver for approval , once the 1st Approver releases the PO , the RELEASESTEPCREATED event is triggered but it failed to trigger the WF.

I have checked in SWEL , and from message it looks like the mandatory parameter is not populated with value in event container (may be the Release Code is not populated , though it is being shown in ME23N , next Release code is 20).

From : SWEL.

From ME23N- the next Release code : 20

Could you please help me identifying the root cause of why the Event container is not filled up properly after 1st Approver Releases the PO.

Thanks in advance.

Regards

Hafizul

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Hafizul,

Your understanding is correct about Releasestep event.

Mandatory parameter missing error will come,If Event --> Workflow ninding parameter missed.

So check inside workflow binding.

Check Release strategy config Release code : 20 properly configured or not.

Regards,

Ragav

hafizul_mollah2
Participant
0 Kudos

Hi Raghav,

Thanks for reply.

The binding looks fine ans Release strategy also looked fine as shown below.

Binding :

Release Strategy :

Though I am still not sure why was that happening but as you said to check event to WF binding , I went to SWU3 Event queue delivery settings and changed the receiver feedback option to 'Do not Change Linkage' from 'Mark Linkage as having errors' and then created PO again freshly and it is working fine now.Same workflow has been triggered with Release code 20 and 2nd approver has received the dialog workitem.

I will close the thread now thanks.

Regards

Hafizul

anjan_paul
Active Contributor
0 Kudos


Hi,

  Double clik on SWEL entris , and check the key filed, is the ReleaseCode generated

Answers (0)